Okta Okta Certified Consultant Okta Certified Consultant Online Training
Okta Okta Certified Consultant Online Training
The questions for Okta Certified Consultant were last updated at Apr 04,2025.
- Exam Code: Okta Certified Consultant
- Exam Name: Okta Certified Consultant
- Certification Provider: Okta
- Latest update: Apr 04,2025
Okta can be used to authenticate a user into a:
- A . Single Page App
- B . Web App
- C . Mobil App
Open ID Connect and OAuth 2.0 are used as follows:
- A . OIDC is used to authorize users into a web application, whereas OAuth 2.0 is used to authorize access for API purposes
- B . OIDC is used to authenticate users into a web application, whereas OAuth 2.0 is used to authorize access for API purposes
- C . OIDC is used to authorize users into a web application, whereas OAuth 2.0 is used to authenticate access for API purposes
- D . OIDC is used to authenticate users into a web application, whereas OAuth 2.0 is used to authenticate access for API purposes
You can use Okta org. as an authorization server.
- A . This is used with the issuer being https://okta.com
- B . This is used for OIDC use cases
- C . This is used for Authentication use cases
- D . This is used with an issuer being https://<subdomain>.okta.com
- E . You cannot use Okta org as an authorization server
Beside Okta org. being used as an authorization server, there also can be other types of authorization servers added (other custom ones).
- A . FALSE
- B . TRUE
- C . True and the issuer looks like: https://<subdomain>.okta.com/oauth2/${authorizationServerId}
- D . True and the issuer looks like: https://<subdomain>.okta.com
- E . True and the issuer looks like: https://okta.com
Okta org, when being used as an authorization server (issuer: https://<subdomain>.okta.com), can only be used for OIDC (Open ID Connect, hence Authentication) and not for OAuth (Authorization).
- A . Statement is False in its entirety
- B . Statement is True in its entirety
- C . True, but for the issuer part, where the URL is wrong
- D . False, but for the correlation between OIDC and Authentication, which is indeed True
You cannot:
- A . Have multiple authorization servers in Okta
- B . Edit the access policy in Okta, when Okta is the Default Authorization Server
- C . Have custom scopes when Okta is the authorization server
The authorization server also acts as an:
- A . OpenID Connect Provider, which means you can request ID tokens in addition to access tokens from the authorization server endpoints
- B . OpenID Connect protocol, which means you can request ID tokens in addition to OIDC or OAuth 2.0 tokens from the authorization server endpoints
- C . OpenID Connect Provider, which means you can request ID tokens in addition to access tokens from the authentication server endpoints
- D . OpenID Connect Provider, which means you can request Open ID Connect tokens in addition to access tokens from the authentication server endpoints
Access tokens are returned if ‘response_type’ included:
- A . ‘nonce’
- B . ‘none’
- C . ‘access’
- D . ‘token’
- E . ‘access_token’
‘code’ is an opaque value that is returned if ‘reponse_type’ includes:
- A . ‘code’ and ‘code’ has a lifetime of 45 seconds
- B . ‘token’ and ‘code’ has a lifetime of 24 hours
- C . ‘value’ and ‘code’ has a lifetime of 90 seconds
- D . ‘code’ and ‘code’ has a lifetime of 60 seconds
‘scope’ is returned only if the response includes:
- A . A ‘token’ value
- B . A ‘scope’ value
- C . A claim
- D . An access_token