AWS Certified Developer - Associate

AWS Certified Developer - Associate

Get started today

Ultimate access to all questions.


A development team at a social media company is utilizing AWS Lambda in their serverless architecture on the AWS Cloud. For a new deployment, the Team Lead aims to divert only a specific percentage of the overall traffic to the newly deployed Lambda version. Additionally, in the event of a deployment failure, the solution must enable rolling back to a prior version of the Lambda function with minimal application downtime.

As a Developer Associate, which of the following options would you recommend to meet these requirements while ensuring minimal disruption and efficient traffic management?




Explanation:

You can use versions to manage the deployment of your AWS Lambda functions. For example, you can publish a new version of a function for beta testing without affecting users of the stable production version. You can change the function code and settings only on the unpublished version of a function. When you publish a version, the code and most of the settings are locked to ensure a consistent experience for users of that version.

You can create one or more aliases for your AWS Lambda function. A Lambda alias is like a pointer to a specific Lambda function version. You can use routing configuration on an alias to send a portion of traffic to a Lambda function version. For example, you can reduce the risk of deploying a new version by configuring the alias to send most of the traffic to the existing version, and only a small percentage of traffic to the new version.