Question 217 of 1,040
Design Secure ArchitecturesmediumMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is the JWT authorizer configured for the OpenID Connect issuer. This is the right choice because API Gateway’s JWT authorizer natively validates JSON Web Tokens issued by an external OpenID Connect provider, verifying the token’s signature, expiry, and issuer against the provider’s JWKS endpoint without requiring custom Lambda code. On the SAA-C03 exam, this scenario tests your understanding of when to use a managed authorizer versus a Lambda authorizer—a common trap is choosing a Lambda authorizer for token validation, but the JWT authorizer is the simpler, standards-based solution for OpenID Connect tokens. Remember the key distinction: if the token is a JWT from an OIDC provider, use the JWT authorizer; if you need custom validation logic or non-JWT tokens, use a Lambda authorizer. A helpful memory tip is “JWT for OIDC, Lambda for custom logic.”

SAA-C03 Design Secure Architectures Practice Question

This SAA-C03 practice question tests your understanding of design secure architectures. 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 public API for a image sharing application is deployed on API Gateway. Clients must authenticate with standards-based tokens issued by an external OpenID Connect provider. Which authorization mechanism should be used?

Question 1mediummultiple choice
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

JWT authorizer configured for the OpenID Connect issuer

Option C is correct because API Gateway's JWT authorizer natively validates JSON Web Tokens (JWTs) issued by an external OpenID Connect (OIDC) provider. It verifies the token's signature, expiry, and issuer against the OIDC provider's JWKS endpoint, enabling standards-based authentication without custom Lambda code.

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.

  • A VPC endpoint policy

    Why it's wrong here

    Endpoint policies restrict private endpoint use, not public API user authentication.

  • API keys only

    Why it's wrong here

    API keys identify clients for usage plans but do not authenticate users securely.

  • JWT authorizer configured for the OpenID Connect issuer

    Why this is correct

    A JWT authorizer validates tokens from a trusted OIDC issuer with low operational overhead.

    Related concept

    Read the scenario before looking for a memorised answer.

  • IAM authorization for all internet users

    Why it's wrong here

    IAM authorization is suited to AWS principals, not general OIDC-authenticated application users.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse API keys (simple identification) with authentication, or assume IAM authorization is required for all API Gateway endpoints, overlooking the purpose-built JWT authorizer for federated OIDC tokens.

Detailed technical explanation

How to think about this question

The JWT authorizer works by configuring the API Gateway to trust the OIDC issuer's well-known JWKS URI (e.g., https://provider.com/.well-known/openid-configuration). During request processing, API Gateway automatically fetches and caches the public keys from the JWKS endpoint to verify the JWT's signature using RS256 or ES256 algorithms, and validates the 'iss', 'aud', and 'exp' claims. This eliminates the need for a custom Lambda authorizer, reducing latency and operational overhead.

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 SAA-C03 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 SAA-C03 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 SAA-C03 question test?

Design Secure Architectures — This question tests Design Secure Architectures — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: JWT authorizer configured for the OpenID Connect issuer — Option C is correct because API Gateway's JWT authorizer natively validates JSON Web Tokens (JWTs) issued by an external OpenID Connect (OIDC) provider. It verifies the token's signature, expiry, and issuer against the OIDC provider's JWKS endpoint, enabling standards-based authentication without custom Lambda code.

What should I do if I get this SAA-C03 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

Keep practising

More SAA-C03 practice questions

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 SAA-C03 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 SAA-C03 exam.