
Answer-first summary for fast verification
Answer: Use a Lambda function alias that can point to the different versions
Use a Lambda function alias that can point to the different versions You can use versions to manage the deployment of your functions. For example, you can publish a new version of a function for beta testing without affecting users of the stable production version. Lambda creates a new version of your function each time that you publish the function. The new version is a copy of the unpublished version of the function. By publishing a version of your function, you can store your code and configuration as a separate resource that cannot be changed. A Lambda alias is like a pointer to a specific function version. Users can access the function version using the alias Amazon Resource Name (ARN). Each alias has a unique ARN. An alias can point only to a function version, not to another alias. You can update an alias to point to the different versions of the Lambda function. Incorrect options: Use a Route 53 weighted policy that can point to the different Lambda function versions - This option is a distractor, as Route 53 cannot be used for the given use case. Route 53 weighted policy lets you associate multiple resources with a single domain name (example.com) or subdomain name (acme.example.com) and choose how much traffic is routed to each resource. This can be useful for a variety of purposes, including load balancing and testing new versions of software. Use CodeDeploy to configure blue/green deployments for the different Lambda function versions - A deployment to the AWS Lambda compute platform is always a blue/green deployment. You do not specify a deployment type option. When you deploy to an AWS Lambda compute platform, the deployment configuration specifies the way traffic is shifted to the new Lambda function versions in your application. You can shift traffic using a canary, linear, or all-at-once deployment configuration. Once deployed, you cannot go back to the previous versions of your Lambda function. So this option is incorrect. Use Lambda function layers that can point to the different versions - Lambda layers provide a convenient way to package libraries and other dependencies that you can use with your Lambda functions. Using layers reduces the size of uploaded deployment archives and makes it faster to deploy your code. You cannot use the Lambda function layers to point to the different versions of the Lambda function.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A developer is working on deploying a Lambda function and requires a smooth method to revert back to previous versions whenever necessary. They need a solution that minimizes the complexity and management effort involved.
Which of the following solutions provides the LEAST operational overhead?
A
Use CodeDeploy to configure blue/green deployments for the different Lambda function versions
B
Use Lambda function layers that can point to the different versions
C
Use a Route 53 weighted policy that can point to the different Lambda function versions
D
Use a Lambda function alias that can point to the different versions