A developer is planning to use an Amazon API Gateway and AWS Lambda to provide a REST API. The developer will have three distinct environments to manage: development, test, and production. How…

Question

Options

• ACreate a separate API Gateway and separate Lambda function for each environment in the same
• BAssign a Region for each environment and deploy API Gateway and Lambda to each Region.
• CCreate one API Gateway with multiple stages with one Lambda function with multiple aliases.
• DCreate one API Gateway and one Lambda function, and use a REST parameter to identify the

• A
  6% (1)
• B
  13% (2)
• C
  75% (12)
• D
  6% (1)

Explanation

Option C is correct because API Gateway stages (dev, test, prod) and Lambda aliases are purpose-built AWS features for managing multiple environments from a single resource - stages allow independent deployments with stage-specific variables, while aliases point to specific Lambda versions, keeping environment isolation clean without multiplying resource counts.

Why the distractors fail:

• A - Creating separate API Gateways and Lambda functions per environment defeats the goal of minimizing resources; you're tripling your management overhead.
• B - Using separate AWS Regions per environment is an anti-pattern for environment management; Regions are for geographic availability and compliance, not dev/test/prod separation.
• D - Using a REST parameter to identify the environment is a brittle, non-native approach that forces business logic to handle routing that AWS infrastructure should own, and still doesn't reduce resource count.

Memory tip: Think "Stages for Gateway, Aliases for Lambda" - both are AWS's official answer to the question "how do I version and separate environments without duplicating infrastructure?" If an exam question mentions multiple environments + one API Gateway + one Lambda, the answer is always stages + aliases.

No community discussion yet for this question.