You and your team have a productive REST API with API Gateway and Lambda as backend. You want to make some code improvements to this API without making disruptions to your customers. Once completed the modifications to Lambda code you want to deploy this new version. How can you achieve this?

Answer options:

A.Create a version in the Lambda with the actual code. This version will be named “1”. After this start to make the modifications to the code. In the integration request of APi Gateway set the Lambda function to ${stageVariables.Lambdaenv}. Create a stage variable called lambdaenv in API gateway Prod stage. Set lambdaenv to the ARN ofversion “1” of the Lambda function. After finishing the modifications, set lambdaenv to the $latest Lambda function ARN.
B.Create a version in the Lambda with the actual code. This version will be named “1”. After this start to make the modifications to the code. In the integration request set the Lambda function to ${lambdaenv}. Create a stage variable called lambdaenv in API gateway Prod stage. Set lambdaenv to the ARN ofversion 1 of the Lambda function. After finishing the modifications, set lambdaenv to the $latest Lambda function ARN.
C.Start to make the modifications to the code. In the integration request of APi Gateway set the Lambda function to ${stageVariables.lambdaenv}. Create a stage variable called lambdaenv in API gateway Prod stage. Set lambdaenv to the ARN of$latest version Lambda function.
D.Start to make the modifications to the code. In the integration request of APi Gateway set the Lambda function to ${stageVariables.lambdaenv}. Create a stage variable called lambdaenv in API gateway Prod stage. Set lambdaenv to the ARN ofversion $initial of the Lambda function. After finishing the modifications, set lambdaenv to the $latest Lambda function ARN.

Correct Answer: A
Option A is CORRECT because with this you are pointing to your actual production code with the version 1 of Lambda. If you make modifications to the code this will not affect the version 1. After you complete your changes you can point to the $LATEST version of the Lambda. More details: https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html
Option B Is incorrect because ${lambdaenv} is not correct to refer to lambdaenv stage variable. The correct statement is${stageVariables.lambdaenv}. More details: https://aws.amazon.com/blogs/compute/using-api-gateway-stage-variables-to-manage-lambda-functions/#:~:text=There`s%20a%20new%20feature%20on,the%20API%20is%20running%20on.
Option C Is incorrect because you are pointing to the latest version of your Lambda and every modification that you make to the code will affect your customers.
Option D Is incorrect because there is no $initial version of Lambda by default. The only default version is $latest.More details: https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html