Which combination of steps will meet these requirements?
(Choose two.)
Publish a version of the original Lambda function. Make the necessary changes to the Lambda code. Publish a new version of the Lambda function.
Use AWS CodeBuild to detect updates to the Lambda function. Configure CodeBuild to incrementally shift traffic from the original version of the Lambda function to the new version of the Lambda function.
Update the original version of the Lambda function to add a function URL. Make the necessary changes to the Lambda code. Publish another function URL for the updated Lambda code.
Create an alias that points to the original version of the Lambda function. Configure the alias to be a weighted alias that also includes the new version of the Lambda function. Divide traffic between the two versions.
Create an alias that points to the original function URL. Configure the alias to be a weighted alias that also includes the additional function URL. Divide traffic between the two function URLs.
Explanations:
Publishing separate versions of the Lambda function allows the developer to distinguish between the original and updated code. The developer can then configure traffic shifting.
AWS CodeBuild is not used to manage Lambda traffic shifting. CodeBuild is a CI/CD service and does not handle routing traffic between Lambda versions.
Adding function URLs does not enable traffic shifting between Lambda versions. Function URLs are separate endpoints and don’t support traffic splitting in this context.
Creating a weighted alias allows the developer to route a percentage of traffic to each version, which meets the requirement for testing both versions concurrently.
Aliases in Lambda cannot be assigned to function URLs; they work only with Lambda versions. Function URLs do not support traffic weighting between URLs in the way aliases do.
I categorize that the answer is:
Publish a version of the original Lambda function. Make the necessary changes to the Lambda code. Publish a new version of the Lambda function.