Which solution will meet these requirements?
Update the Lambda code and create a new version of the Lambda function. Create a Lambda function trigger. Configure the traffic weights in the trigger between the two Lambda function versions. Send 90% of the traffic to the production version, and send 10% of the traffic to the new version.
Create a new Lambda function that uses the updated code. Create a Lambda alias for the production Lambda function. Configure the Lambda alias to send 90% of the traffic to the production Lambda function, and send 10% of the traffic to the test Lambda function.
Update the Lambda code and create a new version of the Lambda function. Create a Lambda proxy integration. Configure the Lambda proxy to split traffic between the two Lambda function versions. Send 90% of the traffic to the production version, and send 10% of the traffic to the new version.
Update the Lambda code and create a new version of the Lambda function. Create a Lambda function alias. Configure the traffic weights in the Lambda alias between the two Lambda function versions. Send 90% of the traffic to the production version, and send 10% of the traffic to the new version.
Explanations:
This option suggests creating a Lambda function trigger to configure traffic weights, but Lambda function triggers do not support traffic splitting. Traffic shifting can be done through aliases or API Gateway, but not through triggers directly.
This option involves creating a new Lambda function instead of using versions, which is not necessary. It suggests using a Lambda alias to split traffic, but aliases are typically used with versions rather than separate functions. This approach is inefficient and not aligned with best practices for deploying updates.
This option mentions creating a Lambda proxy integration to split traffic, which is not a supported method for managing traffic weights. Traffic splitting between versions is best handled through aliases, not proxy integrations.
This option correctly outlines the process of updating the Lambda code, creating a new version, and using a Lambda alias to configure traffic weights. This method allows 90% of the traffic to go to the production version and 10% to the new version, aligning perfectly with the rollout strategy required.
I categorize that the answer is:
Update the Lambda code and create a new version of the Lambda function. Create a Lambda function alias. Configure the traffic weights in the Lambda alias between the two Lambda function versions. Send 90% of the traffic to the production version, and send 10% of the traffic to the new version.