DVA-C02 · Question #100
A company has a web application that is deployed on AWS. The application uses an Amazon API Gateway API and an AWS Lambda function as its backend. The application recently demonstrated unexpected beha
The correct answer is B. Update the Lambda function in the API Gateway API integration request to use the hotfix alias. D. Modify the Lambda function by fixing the code. Test the Lambda function. When the Lambda. Using Lambda aliases with API Gateway integration allows a developer to create an isolated hotfix environment by pointing the API to a specific alias, preventing other developers from overwriting in-progress changes.
Question
A company has a web application that is deployed on AWS. The application uses an Amazon API Gateway API and an AWS Lambda function as its backend. The application recently demonstrated unexpected behavior. A developer examines the Lambda function code, finds an error, and modifies the code to resolve the problem. Before deploying the change to production, the developer needs to run tests to validate that the application operates properly. The application has only a production environment available. The developer must create a new development environment to test the code changes. The developer must also prevent other developers from overwriting these changes during the test cycle. Which combination of steps will meet these requirements with the LEAST development effort? (Choose two.)
Options
- ACreate a new resource in the current stage. Create a new method with Lambda proxy integration.
- BUpdate the Lambda function in the API Gateway API integration request to use the hotfix alias.
- CModify the Lambda function by fixing the code. Test the Lambda function. Create the alias hotfix.
- DModify the Lambda function by fixing the code. Test the Lambda function. When the Lambda
- ECreate a new API Gateway API for the development environment. Add a resource and method
How the community answered
(26 responses)- A23% (6)
- B58% (15)
- C12% (3)
- E8% (2)
Why each option
Using Lambda aliases with API Gateway integration allows a developer to create an isolated hotfix environment by pointing the API to a specific alias, preventing other developers from overwriting in-progress changes.
Creating a new resource and method in the current production stage does not isolate the environment and increases complexity without protecting against overwrites.
Updating the API Gateway integration request to reference a named alias (e.g., hotfix) isolates the API stage from the $LATEST version, so other developers modifying $LATEST do not affect this environment.
Creating the alias hotfix after testing is correct as a step, but without also updating API Gateway to point to that alias (step B), the isolation is incomplete.
Fixing the code and then publishing a numbered Lambda version (from which the alias is created) captures an immutable snapshot of the working code, ensuring the hotfix alias always points to that exact revision.
Creating an entirely new API Gateway API duplicates infrastructure and requires significant effort, violating the least-effort requirement.
Concept tested: Lambda versions and aliases for environment isolation
Source: https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html
Community Discussion
No community discussion yet for this question.