DVA-C02 Deployment Practice Question
A developer is using AWS CodeDeploy to deploy an application to an Auto Scaling group. The deployment is configured with a 'OneAtATime' deployment configuration. The developer notices that the deployment is taking a long time. What is the most likely reason?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The Auto Scaling group has a large number of instances, and deploying one at a time is slow.
The 'OneAtATime' deployment configuration deploys to one instance at a time, so if the Auto Scaling group has a large number of instances, the deployment will take a long time. Option A is incorrect because the load balancer configuration does not directly affect deployment speed when using 'OneAtATime'. Option C is incorrect because the deployment configuration is correctly set to 'OneAtATime', not 'AllAtOnce'. Option D is incorrect because if the CodeDeploy agent were not running, the deployment would likely fail entirely, not just be slow.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The deployment group is configured with an incorrect load balancer.
Why it's wrong here
An incorrectly configured load balancer in the deployment group typically causes health check failures or connectivity errors that surface as failed deployment events in CodeDeploy, not gradual slowness — the deployment would either fail outright at instance health verification or proceed normally, so misconfiguration alone doesn't explain a slow-but-otherwise-functioning rollout.
- ✓
The Auto Scaling group has a large number of instances, and deploying one at a time is slow.
Why this is correct
The OneAtATime deployment configuration deliberately updates exactly one instance at a time, waiting for each instance's lifecycle event hooks (BeforeInstall, ApplicationStop, Install, AfterInstall, ApplicationStart, ValidateService) to complete successfully before moving to the next; with a large Auto Scaling group, this strictly sequential process multiplies the per-instance deployment time by the total instance count, making the overall deployment noticeably slow by design.
- ✗
The deployment configuration is set to 'AllAtOnce', but the developer intended 'OneAtATime'.
Why it's wrong here
The scenario explicitly states the deployment configuration is set to OneAtATime, so a claim that it's actually AllAtOnce contradicts the given facts; AllAtOnce would in fact produce the fastest deployment time of the three built-in configurations, not a slow one, making this option internally inconsistent with the premise.
- ✗
The CodeDeploy agent on the instances is not running.
Why it's wrong here
If the CodeDeploy agent were not running on the target instances, the deployment lifecycle events could never start on those instances, resulting in an explicit deployment failure or a stuck/failed instance status reported in the CodeDeploy console — not a deployment that merely runs slowly to completion, so this describes a failure condition rather than a performance characteristic.
Go deeper
Related to this question
About these practice questions
This DVA-C02 question is part of Courseiva's 1,135-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DVA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DVA-C02 exam.