SOA-C02 Deployment, Provisioning, and Automation Practice Question
An administrator uses AWS CodeDeploy to deploy an application to an Auto Scaling group. The deployment fails with an error: "The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems." The deployment group has a minimum of 2 instances. What should the administrator check first?
⚠ Common exam trap
SOA-C02 often tests the tendency to jump to configuration settings, but the error message points to instance-level failures, so logs are the first check.
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 deployment logs on the individual EC2 instances.
The error message indicates that too many individual instances failed deployment. The first step is to check the deployment logs on the individual EC2 instances to identify the specific failure reason, such as script errors, missing dependencies, or permissions issues. This provides the most direct insight into why instances are failing.
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 application revision's compatibility with the instance operating system.
Why it's wrong here
Operating system compatibility would cause instance-level script failures, but the error names insufficient healthy instances and deployment group problems, pointing to health check or load balancer configuration. Checking revision compatibility is tempting because it is a common deployment failure cause, and would be correct if instances failed while running the application revision.
- ✗
The Auto Scaling group's health check settings.
Why it's wrong here
Auto Scaling health checks govern instance replacement, not CodeDeploy's per-instance deployment verdicts, so they cannot explain the failure threshold breach. Checking them is tempting because unhealthy instances do trigger this error, but that path applies when instances fail ELB or EC2 status checks rather than the deployment lifecycle events CodeDeploy itself evaluates.
- ✗
The deployment group's deployment configuration settings.
Why it's wrong here
The deployment configuration sets how many instances must stay healthy during rollout; with a minimum of two instances, a configuration such as one-at-a-time can halt the deployment before enough hosts succeed. It is tempting because it directly governs failure thresholds, but the stem asks what to check first when instances themselves are failing.
- ✓
The deployment logs on the individual EC2 instances.
Why this is correct
CodeDeploy's error is generic, so instance-level detail is decisive. The CodeDeploy agent writes lifecycle event logs to /opt/codedeploy-agent/deployment-root on each EC2 instance, revealing the actual failure (hook script, permissions, or missing dependencies) behind the aggregate deployment-group message.
Go deeper
Related to this question
About these practice questions
This SOA-C02 question is part of Courseiva's 1,169-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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
This SOA-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 SOA-C02 exam.