The answer is to implement a Blue/Green deployment using a separate Elastic Beanstalk environment and swap CNAMEs after testing. This approach avoids downtime by keeping the original (blue) environment fully operational while the new (green) environment is deployed and validated; if the green environment fails health checks due to a memory leak, traffic is never routed to it, and the blue environment continues serving users uninterrupted. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this question tests your understanding of deployment policies and how to achieve zero-downtime releases, often contrasting Blue/Green with rolling or all-at-once strategies. A common trap is assuming rolling updates prevent downtime during a failed deployment, but they can still cause disruption when old instances are terminated before new ones pass health checks. Remember the memory tip: “Blue stays true, Green is the scene—swap the CNAME, keep the uptime game.”
SOA-C02 Deployment, Provisioning, and Automation Practice Question
This SOA-C02 practice question tests your understanding of deployment, provisioning, and automation. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company runs a critical web application on a fleet of EC2 instances behind an Application Load Balancer (ALB) across multiple Availability Zones. The application is deployed using AWS Elastic Beanstalk with a rolling update deployment policy. Recently, the development team pushed a new application version that introduced a memory leak. Within minutes, the instances started failing health checks, and Elastic Beanstalk initiated a replacement of the instances. However, during the replacement, the application experienced downtime because the new instances were not passing health checks, and the old instances were already terminated. The SysOps Administrator must modify the deployment to prevent downtime during future failed deployments. Which solution should the administrator implement?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement a Blue/Green deployment using a separate Elastic Beanstalk environment and swap CNAMEs after testing.
Option B is correct. Using a Blue/Green deployment with an immutable environment ensures that the new environment is fully tested before traffic is switched. If the new environment fails health checks, the old environment remains serving traffic, preventing downtime. Option A is wrong because All at once deployment would cause downtime even without failure. Option C is wrong because a classic load balancer does not provide the same health check granularity. Option D is wrong because Auto Scaling alone does not control deployment strategy.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Increase the Auto Scaling group's minimum and maximum size to handle more instances.
Why it's wrong here
Auto Scaling does not change deployment strategy.
✓
Implement a Blue/Green deployment using a separate Elastic Beanstalk environment and swap CNAMEs after testing.
Why this is correct
Blue/Green deployment avoids downtime by keeping old environment active.
Related concept
Static NAT maps one inside address to one outside address.
✗
Replace the ALB with a Classic Load Balancer to reduce complexity.
Change the deployment policy to All at once to speed up the deployment.
Why it's wrong here
All at once would cause downtime during deployment.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Got this wrong? Here's your next step.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SOA-C02 NAT questions on configuration and troubleshooting.
Deployment, Provisioning, and Automation — This question tests Deployment, Provisioning, and Automation — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Implement a Blue/Green deployment using a separate Elastic Beanstalk environment and swap CNAMEs after testing. — Option B is correct. Using a Blue/Green deployment with an immutable environment ensures that the new environment is fully tested before traffic is switched. If the new environment fails health checks, the old environment remains serving traffic, preventing downtime. Option A is wrong because All at once deployment would cause downtime even without failure. Option C is wrong because a classic load balancer does not provide the same health check granularity. Option D is wrong because Auto Scaling alone does not control deployment strategy.
What should I do if I get this SOA-C02 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SOA-C02 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.