Which combination of steps will meet these requirements with the LEAST development effort?
(Choose two.)
Create a new resource in the current stage. Create a new method with Lambda proxy integration. Select the Lambda function. Add the hotfix alias. Redeploy the current stage. Test the backend.
Update the Lambda function in the API Gateway API integration request to use the hotfix alias. Deploy the API Gateway API to a new stage named hotfix. Test the backend.
Modify the Lambda function by fixing the code. Test the Lambda function. Create the alias hotfix. Point the alias to the $LATEST version.
Modify the Lambda function by fixing the code. Test the Lambda function. When the Lambda function is working as expected, publish the Lambda function as a new version. Create the alias hotfix. Point the alias to the new version.
Create a new API Gateway API for the development environment. Add a resource and method with Lambda integration. Choose the Lambda function and the hotfix alias. Deploy to a new stage. Test the backend.
Explanations:
Creating a new resource in the current stage and deploying changes to the same stage does not isolate the changes. This could result in overwriting other changes made by different developers.
Updating the Lambda function to use a hotfix alias and deploying the API to a new stage ensures the changes are isolated in the new stage and does not affect the production environment.
Modifying the Lambda function code and using the $LATEST version doesn’t provide a way to isolate changes or prevent overwriting. The changes will affect the production environment.
Modifying the Lambda function, testing it, and then publishing a new version with a hotfix alias ensures that changes are isolated and cannot be overwritten. The alias points to a stable version, and tests can be done without affecting production.
Creating a completely new API Gateway API adds unnecessary complexity. The goal is to isolate changes, not create a new API, which could increase management overhead.