Okta Certified Developer : Okta-Certified-Developer

The Okta Sign-ln widget doesn't make Cross-Origin requests as it uses stateless API requests.

• A. Statement is False
• B. Statement is True

Okta Certified Developer Exam Objectives

• A. Part I: 45 Discrete Option Multiple Choice QuestionsPart II: Four Performance-Based, Hands-on Use CasesExam takers complete Part I and then are permitted to start Part II.Exam takers are not permitted to return to Part I after they have completed it and submitted their responses for grading.Time allotted: Part I: 60 minutes, Part II: 90 minutesIMPORTANT:Each part is timed separately. Any time left over from Part I does NOT carry over to Part II.Because this is a two-hour and 30 minutes exam, come fully prepared to sit through the entire exam. There is no break between parts I and II of this exam.Exam fee: USD 250 (USD 100 for each subsequent retake)Format: Part I of this exam includes Discrete Option Multiple-Choice (DOMC) items. Part II contains performance-based, hands-on use cases.
• B. Okta Certified Developers are technically proficient at building secure, seamless experiences using Okta APIs and SDKs. Developers have experience working with RESTful APIs and developing web applications. They have general understanding of authentication and authorization standards such as OpenID Connect (OIDC) and OAuth, as well as how Okta supports these standards for building authentication, flexible authorization, and role-base access control. Developers also have experience configuring authorization with API Access Management and implementing Single Sign-On (SSO) with OIDC. They have working knowledge of Okta Lifecycle Management and administrative APIs.
• C. Part IAuthentication 9%SSO and API Access Management with OIDC and OAuth 18%Lifecycle Management 16%Administrative APIs 20%Debug Techniques 9%Design Principles 18%Okta Hooks 9%Working with the Sign-In widget for Authentication 2%Part IIOnboard new users using Okta,s Management SDK and User and Group APIs 27%Federate an App through OIDC 33%Securing an API using OAuth and Securely accessing an API from a client app using OAuth 20%Implement the Okta Sign-In Widget for Authentication Purposes 20%

'invalid_grant' error is thrown when:

• A. he ,redirect_uri, doesn,t match the one used in the authorization request
• B. he ,code,, ,refresh_token,, or ,username, and ,password combination is invalid
• C. he ,redirect_uri, doesn,t match the one used in the authentication request

An Admin revokes all refresh tokens issued by an Authorization Server for a specified client. That means that:

• A. Access tokens issued without a refresh token aren,t affected
• B. All access tokens are affected
• C. No access tokens issued with these refresh tokens will be revoked as well
• D. Any access tokens issued with these refresh tokens are also revoked

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', then:

• A. You will have WARN type of message displayed due to the fact that is redundant to set both ,consent_method, and ,consent, to ,REQUIRED,
• B. You will have an error telling you that the ,prompt, value can never be ,NONE,
• C. You will be thrown an error