A DevOps team uses AWS CodePipeline, AWS CodeBuild, and AWS CodeDeploy to deploy an application. The application is a REST API that uses AWS Lambda functions and Amazon API Gateway. Recent…

Question

Options

• ASet the deployment configuration in CodeDeploy to LambdaAllAtOnce. Configure automatic
• BSet the deployment configuration in CodeDeploy to LambdaCanary10Percent10Minutes.
• CSet the deployment configuration in CodeDeploy to LambdaAllAtOnce. Configure manual
• DSet the deployment configuration in CodeDeploy to LambdaCanary10Percent10Minutes.

• A
  3% (1)
• B
  83% (24)
• C
  10% (3)
• D
  3% (1)

Explanation

Explanation

Option B is correct because LambdaCanary10Percent10Minutes routes only 10% of traffic to the new Lambda version for 10 minutes before shifting the remaining 90%, meaning errors only affect a small subset of customers. When combined with automatic rollback triggered by CloudWatch alarms, CodeDeploy can detect failures and revert to the stable version with minimal manual intervention - satisfying both the "fewest customers affected" and "most operational efficiency" requirements.

Option A is wrong because LambdaAllAtOnce shifts 100% of traffic immediately to the new version, meaning all customers are exposed to any errors - the opposite of limiting impact.

Option C is wrong for the same traffic-shifting reason as A (all-at-once), and manual approval/rollback adds operational overhead and human delay, which reduces efficiency.

Option D appears identical to B in the truncated choices shown, but likely differs in a critical detail (e.g., manual rollback instead of automatic), which would reduce operational efficiency compared to automated rollback in B.

Memory Tip

Think "Canary = Caution" - just like a canary in a coal mine tests the environment before full exposure, a Canary deployment tests with a small percentage of traffic first, protecting most customers while enabling automated rollback.

No community discussion yet for this question.