Q81 — AWS DVA-C02 Ch.1

Question 81 of 100 | ← Chapter 1

A company has an AWS Lambda function that processes incoming requests from an Amazon API Gateway API. The API uses a Lambda alias to invoke the Lambda function. Developers updated the Lambda function code to handle more detailed information related to incoming requests. Developers want to deploy the new Lambda function for testing without impacting customers using the API. Which solution meets these requirements with the least operational overhead?

• A. Create a new version of the Lambda function. Create a new stage in API Gateway integrated with the new Lambda version. Test the Lambda function using the new API Gateway stage. ✓
• B. Update the existing Lambda alias used by API Gateway to a weighted alias. Add the new Lambda version as an additional Lambda function with a weight of 10%. Test in the existing API Gateway stage.
• C. Create a new version of the Lambda function. Create and deploy a second Lambda function to filter incoming requests from API Gateway. If the filtering Lambda function detects a test request, it invokes the new Lambda version; otherwise, it invokes the old Lambda version. Update the API Gateway API to use the filtering Lambda function.
• D. Create a new version of the Lambda function. Create a new API Gateway API for testing purposes. Update the new API to integrate with the new Lambda version. Use the new API for testing.

Correct Answer: A. Create a new version of the Lambda function. Create a new stage in API Gateway integrated with the new Lambda version. Test the Lambda function using the new API Gateway stage.

Explanation

Option A describes creating a new Lambda version and a new API Gateway stage integrated with that version, enabling testing without affecting production traffic. This approach requires minimal changes and avoids operational complexity. Option B introduces weighted aliases, which enable gradual rollout but adds configuration complexity. Option C adds an extra Lambda layer for routing, increasing latency and maintenance overhead. Option D creates redundant infrastructure (a new API), increasing cost and management burden. Thus, A delivers the lowest operational overhead.