DVA-C02 Troubleshooting and Optimization Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Create the user pool and app client, then authenticate to receive tokens, then use tokens for authorization.

  Why this is correct

  Creating the Amazon Cognito User Pool and App Client is the foundational setup, defining where user identities are stored and how applications interact with the authentication service. Only after this infrastructure is in place can a user authenticate by providing credentials, leading to the issuance of ID, Access, and Refresh tokens. These tokens then serve as proof of identity and authorization, enabling access to protected resources or APIs.

• ✗

  Authenticate to receive tokens, then create the user pool and app client, then use tokens for authorization.

  Why it's wrong here

  Attempting to authenticate and receive tokens before creating the Amazon Cognito User Pool and App Client is fundamentally impossible. The User Pool acts as the identity store, validating user credentials and managing the authentication process. Without this configured service and an associated App Client, there is no endpoint or mechanism for an application to initiate an authentication request or for tokens to be generated.

• ✗

  Create the user pool and app client, then use tokens for authorization, then authenticate to receive tokens.

  Why it's wrong here

  This sequence incorrectly places "use tokens for authorization" before "authenticate to receive tokens." Authorization tokens (ID and Access tokens) are the result of a successful authentication process. An application cannot utilize tokens to authorize access to resources if those tokens have not yet been issued by Amazon Cognito after a user has successfully proven their identity. Tokens must first be obtained.

• ✗

  Use tokens for authorization, then create the user pool and app client, then authenticate to receive tokens.

  Why it's wrong here

  Starting with "use tokens for authorization" is incorrect because tokens are generated after a successful authentication, and authentication itself requires a pre-existing Amazon Cognito User Pool and App Client. This order attempts to use something that doesn't exist yet, and also places the foundational setup (creating the user pool) after an action that depends on it, making the entire sequence illogical and inoperable.

Go deeper

Related to this question