Question 879 of 1,616
SecurityhardMultiple SelectObjective-mapped

Quick Answer

The answer is to validate the issuer (iss) and audience (aud) or client ID (azp) claims in the Cognito JWT. These two token validations are critical because the issuer claim confirms the token was generated by your specific Cognito user pool, while the audience claim ensures the token was intended for your API Gateway application, preventing a token from a different user pool or client from being used to access your API. On the AWS Certified Developer Associate DVA-C02 exam, this concept tests your understanding of securing API Gateway endpoints with Cognito authorizers, often appearing in scenario-based questions where a developer must choose the correct validation logic to prevent unauthorized access. A common trap is forgetting to validate the audience claim, thinking the issuer check alone is sufficient. Remember the mnemonic: "Issuer for the source, Audience for the course" — the token must come from your pool and be meant for your API.

DVA-C02 Security Practice Question

This DVA-C02 practice question tests your understanding of security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A developer uses API Gateway with Cognito. Which two token validations are important when authorizing API access?

Question 1hardmulti select
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Validate issuer and audience/client ID

Option A is correct because API Gateway with Cognito requires validating the JWT's issuer (iss) claim to ensure the token was issued by the expected Cognito user pool, and validating the audience (aud) or client ID (azp) claim to confirm the token was intended for the specific API Gateway application. Without these checks, an attacker could use a token from a different user pool or client to access the API.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • Validate issuer and audience/client ID

    Why this is correct

    Correct for the stated requirement.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Accept any JWT signed with none algorithm

    Why it's wrong here

    This does not meet the stated requirement as directly as the correct option.

  • Validate scopes or group claims required by the route

    Why this is correct

    Correct for the stated requirement.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Trust only the username string sent in a header

    Why it's wrong here

    This does not meet the stated requirement as directly as the correct option.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often focus only on signature verification (which is critical) but overlook the equally important validation of issuer and audience claims, which prevents token reuse across different user pools or clients.

Detailed technical explanation

How to think about this question

Under the hood, Cognito issues JWTs with specific claims: 'iss' set to the user pool endpoint (e.g., https://cognito-idp.{region}.amazonaws.com/{userPoolId}), and 'aud' or 'client_id' matching the app client ID. API Gateway Lambda authorizers or Cognito authorizers automatically verify these claims, but custom authorizers must manually decode and validate the JWT using a library like jose or PyJWT, checking the signature against the user pool's JSON Web Key Set (JWKS). In a real-world scenario, failing to validate the issuer could allow a token from a rogue user pool to access your API, while missing audience validation could let a token meant for a different app client (e.g., a mobile app) be used against your API Gateway endpoint.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related DVA-C02 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DVA-C02 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this DVA-C02 question test?

Security — This question tests Security — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Validate issuer and audience/client ID — Option A is correct because API Gateway with Cognito requires validating the JWT's issuer (iss) claim to ensure the token was issued by the expected Cognito user pool, and validating the audience (aud) or client ID (azp) claim to confirm the token was intended for the specific API Gateway application. Without these checks, an attacker could use a token from a different user pool or client to access the API.

What should I do if I get this DVA-C02 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This DVA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DVA-C02 exam.