Actual Questions for Okta Certified Developer Exam

dumps2023-01-31T01:55:55+08:00

Okta Certified Developer exam is a proctored online exam. This Okta Certified Developer exam consists of two parts. There are 45 multiple-choice items in Part 1, and four performance-based hands-on use cases in Part II. Each candidate has 150 minutes (60 minutes for Part I, and 90 minutes for Part II) to finish Okta Certified Developer exam. We provide the latest Okta Certified Developer exam actual questions for you to prepare for the test. Free Okta Certified Developer exam actual questions are below.

Page 1 of 3

1. When you are using a Custom Authorization Server, you can configure the lifetime of the JWT tokens.

For access tokens the minimum is 60 minutes and the maximum is 1 year

For access tokens the minimum is 5 minutes and the maximum is 24 hours

For refresh tokens the idle window is at least 10 minutes and the maximum is 5 years

For refresh tokens the idle window is at least 5 minutes and the maximum is 24 hours

2. In regards to Authorization Server's Key Rotation:

You cannot rotate the keys manually, as it will surely cause permanent sync issues between authorization and resource servers

You can rotate the keys manually

Keys are rotated automatically by default

3. Apps created on '/api/v1/apps' endpoint default to:

'consent_method=REQUIRED', while those created on '/api/v1/clients' default to 'consent_method=TRUSTED'

'consent_method=REQUIRED', while those created on '/api/v1/clients' default to 'consent_method=REQUIRED'

'consent_method=TRUSTED', while those created on '/api/v1/clients' default to 'consent_method=TRUSTED'

'consent_method=TRUSTED', while those created on '/api/v1/clients' default to 'consent_method=REQUIRED'

4. If you request a scope which requires consent while using the 'client_credentials' flow:

The scope asked for is returned

A user auth prompt is returned. Because the user is not authenticated

An error is returned. Because as there is no user - no consent can be given

5. When speaking about Scopes we have a 'prompt' value, a 'consent_method' and the 'consent'. If the 'prompt' value is set to 'NONE', but the 'consent_method' and the 'consent' values to 'REQUIRED', the

You will have an error telling you that the 'prompt' value can never be 'NONE'

You will have WARN type of message displayed due to the fact that is redundant to set both 'consent_method' and 'consent' to 'REQUIRED'

You will be thrown an error

6. The scope name must only contain printable ASCII, except for:

Spaces

Double quotes

Backslashes

Commas

7. The scope name must:

Start with 'okta'

Not start with 'okta'

Start with 'okta:'

Not start with 'okta:'

Not be only 'okta' or '*'

Only be 'okta' or '*'

8. When you are using the Okta Authorization Server, the lifetime of the JWT token is hard-coded to the following values:

ID token: 60 minutes. Access token 30 minutes. Refresh token 60 minutes

ID token: 60 minutes. Access token 60 minutes. Refresh token 90 days

ID token: 30 minutes. Access token 60 minutes. Refresh token 60 minutes

ID token: 60 minutes. Access token 90 minutes. Refresh token 60 days

9. When you are using a Custom Authorization Server, you can configure the lifetime of the JWT tokens, for example the lifetime of ID tokens.

TRUE

False, with the exception of the fact that some tokens' lifetime can indeed be customized in this situation, just not the ID tokens' one

True, with the mention that only this token's lifetime can be customized in such a scenario

10. When you are using a Custom Authorization Server, you can configure the lifetime of the Refresh Tokens and you can even set those with a lifetime of 4 years or even more.

False, due to security issues

True, but with a limit at 10 years

TRUE

FALSE

Page 2 of 3

11. When using Okta as an authorization server:

You can set the audience to the preferred custom service you'll use

The audience is always set to Okta org itself

You cannot set the audience

You cannot set the audience as it can only be used with the Okta org in the userinfo request to get the user claims

12. In either cases: where Okta is the Authorization Server or where you are using a Custom Authorization Server - the ID tokens' lifetime is:

Set to 60 minutes

Set to 1 minute

Configurable between 5 minutes and 1 year

13. 'openid' is required for any OpenID request connect flow.

If the 'openid' scope value is not present, the request is not a valid OAuth 2.0 request either

If the 'openid' scope value is not present, the request may still be a valid OAuth 2.0 request and also a valid OpenID Connect request

If the 'openid' scope value is not present, the request may still be a valid OAuth 2.0 request, but not a valid OpenID Connect request

14. 'offline_access' can only be requested in combination with a 'response_type' that contains 'code'.

The statement is False is its entirety

The statement is True, with the exception that instead of 'code'. there should be 'REQUIRED'

The statement is True, as if the 'response_type' doesn't contain 'code', 'offline_access' is ignored

15. 'profile' requests access to these default profile claims:

'name', 'family_name', 'given_name', 'middle_name', 'nickname'

'gender', 'birthdate'

'profile'

'locale'

16. 'none' - Use this with clients that don't have a client secret:

Such as applications that use the authorization code flow with PKCE

Not with applications that use the authorization code flow with PKCE

Such as applications that use the implicit flow

Not with applications that use the implicit flow

17. When you want higher security in the flow, use:

'consent_method' set to 'REQUIRED'

'consent' set to 'REQUIRED'

'private_key_jwt'

'none' as the client secret

18. Use these method(s) when the client has a client secret. Okta supports the following authentication methods:

'client_secret_basic'

'client_secret_jwt'

'client_secret_post'

19. If your client's 'token_endpoint_auth_method' is 'either client_secret_basic' or 'client_secret_post' you need to include the client secret in outgoing requests.

Statement is False in its entirety

For 'client_secret_basic': Provide the 'client_id' and 'client_secret' values in the Authorization header as a Basic auth base64-encoded string within the POST request, as in: Authorization: Basic ${Base64(<client_id>:<client_secret>)}

For 'client_secret_post': Provide the 'client_id' and 'client_secret' as additional parameters in the POST request body

For 'client_secret_basic': Provide the 'client_id' and 'client_secret' values as additional parameters in the GET request body

For 'client_secret_basic': Provide the 'client_id' and 'client_secret' values in the Authorization header as a Basic auth non-base64-encoded string within the POST request, as in: Authorization: Basic ${<client_id>:<client_secret>}

20. If you use a JWT for client authentication ('client_secret_jwt' or 'private_key_jwt'), you can use the following token claims:

The 'jti' token claim. The 'jti' claim fails the request if the expiration time is more than one hour in the future or has already expired

The 'exp' token claim. The 'exp' claim fails the request if the expiration time is more than one hour in the future or has already expired

The 'exp' token claim. If 'exp' is specified, the token can only be used once. So, for example, subsequent token requests won't succeed

The 'jti' token claim. If 'jti' is specified, the token can only be used once. So, for example, subsequent token requests won't succeed

Page 3 of 3

21. If no prompt parameter is specified, the behavior(s) that occur(s) is / are:

If there is already and Okta session active, the user is silently authenticated

If there is not an Okta session active already, the user is prompted to authenticate

If scopes are requested that require consent and consent isn't yet given by the authenticated user, the user is prompted to give consent

22. For the 'prompt' parameter, there are several values that it can take:

'none'

'login'

'login consent'

'consent'

'consent login'

23. If 'consent' value is set for 'prompt', then:

Okta consent dialog will be displayed only if the user hasn't already given consent

Okta consent dialog might still be displayed, even if the user has already given consent

Statement is False, as 'consent' is not a value for 'prompt' parameter

24. Okta requires the OAuth 2.0 'state' parameter on all requests to the '/authorize' endpoint, in order to:

Prevent XSS (Cross Site Scripting) attacks

Prevent MITM (Man-in-the-middle) attacks

Prevent CSRF (Cross-site Request Forgery) attacks

Statement is False in its entirety as Okta does not have a requirement for that

25. 'redirect_uri' is only required if 'grant_type' is:

'client_credentials'

'authorization_code'

'refresh_token'

26. 'scope' is required only if 'password' is:

The 'grant_type'

The 'claim'

The 'password'

27. 'invalid_grant' error is thrown when:

The 'code', 'refresh_token', or 'username' and 'password' combination is invalid

The 'redirect_uri' doesn't match the one used in the authentication request

The 'redirect_uri' doesn't match the one used in the authorization request

28. 'invalid_request' error is thrown when:

The request structure was invalid

The basic authentication header is malformed

Both header and form parameters were used for authentication

No authentication information was provided

Actual Questions for Okta Certified Developer Exam

Actual Questions for Okta Certified Developer Exam

Share this post

Leave a Reply Cancel reply

Related Posts

Okta Certified Administrator Free Dumps Available

Good Dumps for Okta Certified Consultant Exam

Actual Questions for Okta Certified Professional Exam