The answer is to use a JWT authorizer configured for the OpenID Connect issuer. This is correct because the scenario demands standards-based token authentication from an external OpenID Connect (OIDC) provider, and API Gateway’s JWT authorizer natively validates JSON Web Tokens issued by OIDC providers without requiring any custom Lambda functions or operational scripts. The authorizer automatically verifies the token’s signature, expiry, and issuer by fetching the OIDC discovery endpoint, which directly satisfies the requirement to avoid custom operational scripts. On the SAA-C03 exam, this question tests your understanding of managed authorization options versus custom code—a common trap is choosing a Lambda authorizer when the problem explicitly forbids custom scripts. Remember that the JWT authorizer is purpose-built for OIDC flows, while Lambda authorizers are for non-standard or legacy token formats. Memory tip: “JWT for OIDC, Lambda for custom logic”—if the provider is OpenID Connect, the JWT authorizer is the zero-code choice.
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. A key principle to apply: jWT authorizers validate JSON Web Tokens issued by OIDC providers.. 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? The design must avoid adding custom operational scripts.
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
C is correct because the scenario requires standards-based token authentication from an external OpenID Connect (OIDC) provider, and API Gateway's JWT authorizer natively validates JWTs issued by OIDC providers without requiring custom code. This authorizer verifies the token's signature, expiry, and issuer against the OIDC discovery endpoint, meeting the requirement to avoid custom operational scripts.
Key principle: JWT authorizers validate JSON Web Tokens issued by OIDC providers.
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
JWT authorizers validate JSON Web Tokens issued by OIDC providers.
✗
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 token-based authentication (JWT/OIDC), or incorrectly assume IAM authorization can be used for external identity federation without custom Lambda authorizers or STS-based token exchange.
Detailed technical explanation
How to think about this question
The JWT authorizer works by fetching the OIDC provider's JWKS (JSON Web Key Set) from the issuer's well-known endpoint (e.g., /.well-known/openid-configuration) to verify the token's signature using RS256 or ES256 algorithms. It also validates the token's 'iss' (issuer) and 'aud' (audience) claims against the configured values, and can optionally check 'exp' and 'nbf' for time-based validity. In a real-world scenario, if the OIDC provider rotates signing keys, the JWT authorizer automatically fetches the updated JWKS, avoiding manual key management.
KKey Concepts to Remember
JWT authorizers validate JSON Web Tokens issued by OIDC providers.
They verify token signature, issuer, audience, and expiration.
JWT authorizers eliminate the need for custom Lambda authorizer code.
They integrate with external OIDC providers and Cognito User Pools.
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
JWT authorizers validate JSON Web Tokens issued by OIDC providers.
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.
Review jWT authorizers validate JSON Web Tokens issued by OIDC providers., then practise related SAA-C03 questions on the same topic to reinforce the concept.
Design Secure Architectures — This question tests Design Secure Architectures — JWT authorizers validate JSON Web Tokens issued by OIDC providers..
What is the correct answer to this question?
The correct answer is: JWT authorizer configured for the OpenID Connect issuer — C is correct because the scenario requires standards-based token authentication from an external OpenID Connect (OIDC) provider, and API Gateway's JWT authorizer natively validates JWTs issued by OIDC providers without requiring custom code. This authorizer verifies the token's signature, expiry, and issuer against the OIDC discovery endpoint, meeting the requirement to avoid custom operational scripts.
What should I do if I get this SAA-C03 question wrong?
Review jWT authorizers validate JSON Web Tokens issued by OIDC providers., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
JWT authorizers validate JSON Web Tokens issued by OIDC providers.
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 →
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.
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.
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.
Sign in to join the discussion.