A company uses AWS CodeDeploy to deploy an application to Amazon EC2 instances. The SysOps administrator wants to implement a deployment strategy that minimizes risk by deploying the new version to a small number of instances first, verifying that the deployment is successful, and then deploying to the remaining instances. If the initial deployment fails, the process should stop and roll back. Which CodeDeploy deployment configuration should be used?

CodeDeployDefault.AllAtOnce

AllAtOnce deploys the new revision to all instances simultaneously. If the deployment fails, there is no gradual verification, and the impact could be widespread.

CodeDeployDefault.HalfAtATime

HalfAtATime deploys to half of the instances first, then to the remaining half. While it verifies the first half before proceeding, the first batch could be large depending on group size, which may be riskier than a very small batch.

CodeDeployDefault.Canary10Percent10Minutes

This is a traffic shifting configuration for AWS Lambda or Amazon ECS deployments, not for Amazon EC2 in-place deployments. It cannot be used for EC2 instances directly.

What does this SOA-C02 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: CodeDeployDefault.OneAtATime — CodeDeploy deployment configs define the rate of deployment. A canary deployment is not supported natively in CodeDeploy (it's available in CodeDeploy for Lambda but not for EC2). Linear deployments deploy in equal increments. OneAtATime deploys to one instance at a time. AllAtOnce deploys to all at once. The requirement is 'deploy to a small number first, verify, then deploy to the rest' which is essentially a canary or blue/green with a small initial batch. CodeDeploy supports blue/green deployments with a canary configuration where you specify a percentage of traffic to shift to the new environment. For in-place deployments, you can use a custom deployment config that defines a minimum healthy hosts and a deployment group with a small number of instances as a 'bake' time. However, CodeDeploy does not have a built-in canary for EC2 in-place. The best option is to use a blue/green deployment with a canary traffic shifting configuration. Alternatively, you could use an in-place deployment with the 'CodeDeployDefault.OneAtATime' config, which deploys to one instance at a time, and you can monitor health before proceeding. That doesn't exactly match 'small number first then rest' but OneAtATime does give you a small number (just one) first. The question says 'deploy to a small number of instances first' which could be batch of 1. But maybe they want a custom deployment config that deploys to, say, 10% first. Let's look at options: A: CodeDeployDefault.AllAtOnce - deploys to all, no verification. B: CodeDeployDefault.HalfAtATime - deploys to half then half, but if first half fails, it continues? half at a time deploys to 50% of instances, waits for health check, then deploys to remaining. If health fails, it stops. That could be considered small number if the group is large? Not necessarily small. C: CodeDeployDefault.OneAtATime - one instance at a time, verifies, then moves on. That matches 'small number first' but it deploys to one every time, not 'first one then the rest in bulk'. D: CodeDeployDefault.Canary10Percent10Minutes - that is a traffic shifting pattern for Lambda/ECS, not for EC2. So for EC2 in-place, CodeDeployDefault.OneAtATime is designed to minimize impact. But the requirement says 'deploy to a small number first, verify, then deploy to the remaining' implies a two-phase deployment: first batch (e.g., 1 or a few), then the rest all at once or in bulk. This is essentially a canary. But CodeDeploy for EC2 does not support custom canary percentages out of the box; you would need to use blue/green. However, the question likely expects 'CodeDeployDefault.OneAtATime' as it is the most cautious linear deployment. Or perhaps the correct answer is 'blue/green with canary traffic shifting' but that's for in-place? Let's see the options. I'll create options that include both. Since CodeDeploy for EC2 does not have a built-in canary, the best answer is to use a blue/green deployment with a canary traffic shift. But the question does not mention blue/green. It says 'deploy to EC2 instances'. The most direct answer: use a custom deployment configuration that defines a canary-like behavior. But among the given options, one might be 'CodeDeployDefault.Canary10Percent10Minutes' which is valid for Lambda/ECS only. So for EC2, the only option that limits risk per instance is OneAtATime. So I'll choose that as correct. But let's craft options to make OneAtATime correct: Option C: CodeDeployDefault.OneAtATime - deploys to one instance at a time, waits for health checks, and if any instance fails, the deployment stops. Option B: CodeDeployDefault.HalfAtATime also waits for health checks but halves are larger. So OneAtATime is the smallest batch. So that seems correct.

What should I do if I get this SOA-C02 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.