Online Access Free Okta-Certified-Consultant Practice Test

In regards to OpenID Connect & OAuth 2.0 API, ''/authorize'' is the endpoint which has the following use:

• A.Return OpenID Connect metadata related to the specified authorization server
• B.Return claims about the authenticated end user
• C.Interact with the resource owner and obtain an authorization grant
• D.End the session associated with the given ID token

''invalid_client'' error is thrown when:

• A.The specified ,client_id, wasn,t found
• B.The request structure was invalid
• C.The scopes list contains an invalid or unsupported value

If you, for example, automate a script to call quickly too many API calls on the same endpoint it''s highly possible to get ratelimited.

• A.False, Okta does not ratelimit
• B.TRUE
• C.True, with three exceptions, which are the endpoints: ,/users,, ,/groups,, ,/events,

After you''ve created your external service, you have to register its endpoint in Okta.

• A.Statement is False, as only users are registered, not services
• B.Statement is True
• C.Statement is False, as you are using Header-Based authentication and the token you provide in API calls acts as an API token, token which is in fact received from the external service itself, hence there is no need to register the service,s endpoint in Okta as on each and every call the authorization header is passed on and it will know exactly which Okta domain is calling the service, so there is no need for a trust to be established in the Okta side as well

The Okta RADIUS Server agent:

• A.Communicates via UDP, over default port 1812 and supports multiple ports simultaneously
• B.Communicates via UDP, over default port 1812 and does not support multiple ports simultaneously
• C.Communicates via TCP, over default port 636 and does not support multiple ports simultaneously
• D.Communicates via TCP, over default port 443 and does not support multiple ports simultaneously
• E.Communicates via UDP, over default port 1812 and supports multiple ports simultaneously