Exam AWS Certified Developer - Associate DVA-C02 topic 1 question 134 discussion

D is the correct answer.

https://docs.aws.amazon.com/whitepapers/latest/practicing-continuous-integration-continuous-delivery/deployment-methods.html#:~:text=A%20variation%20of,is%20gradually%20increased.

Selected answer is A. To them who have choosen D, you have forgotton also about "When the application is in production, the application cannot experience downtime outside the specified maintenance window."

D. Use the AWS CodeDeploy predefined canary deployment configuration to shift 10% of the traffic immediately and shift the remaining traffic after 5 minutes: The canary deployment strategy first shifts a small percentage of traffic to the new version (e.g., 10%) and, after a specified period (e.g., 5 minutes), shifts the remaining traffic. This approach allows for initial validation of the new version with minimal user exposure before full rollout, balancing speed and risk mitigation.

Lambda deploy supports just Linear or Canary. So answer is D. Linear or All

Answer A. https://aws.amazon.com/blogs/containers/aws-codedeploy-now-supports-linear-and-canary-deployments-for-amazon-ecs/

Canary deployment is supported: https://aws.amazon.com/blogs/compute/implementing-safe-aws-lambda-deployments-with-aws-codedeploy/

Canary is not supported in AWS CodeDeploy.

Canary is not supported in AWS CodeDeploy.

Canary is faster than linear in this case.

Explanation: In an AWS Lambda context, using the in-place deployment configuration minimizes deployment time and provides fast updates to the function's code. In this case, the application consists of AWS Lambda functions behind Amazon API Gateway APIs. With the in-place deployment configuration, all traffic is shifted to the updated versions of the Lambda functions immediately after deployment. Option B suggests a linear deployment configuration that shifts 10% of the traffic every minute. While this provides controlled deployment and gradual rollout, it might not be the fastest approach if you want to minimize deployment time. Option C suggests an all-at-once deployment configuration. While this configuration might be fast, it poses a higher risk of exposing potential errors to end users all at once.

Canary deployment

D is correct. Keyword: -"must minimize the exposure of potential errors to end users", you just have to trade-off 10% of traffic - "cannot experience downtime ", eliminate C. - "LEAST deployment time", with B, You have to take 10 mins other than D just 5 min.

the predefined canary deployment configuration, which shifts a small percentage of traffic to the updated versions immediately, and then shifts the remaining traffic after a specified period