- A
Increase the Auto Scaling group’s health check grace period so it exceeds the ~2-minute initialization time.
A health check grace period prevents the Auto Scaling group from treating early health check failures as instance health problems. This avoids terminating instances before the application finishes initializing, which stops the restart/replace loop during deployments while still allowing normal health checks to apply once the app is ready.
- B
Add more subnets across additional Availability Zones to distribute the same instances more widely.
Why wrong: Adding subnets/AZs increases fault tolerance, but it does not address the immediate cause of the outage: the target group (via ALB health checks) is marking instances unhealthy before the application is ready. The unhealthy/replace loop would still occur for each instance that starts during deployments.
- C
Switch the load balancer target type from instance targets to IP targets to avoid health check failures.
Why wrong: Target type does not change application readiness. Even with IP targets, the ALB health check fails until the application starts responding on the configured health check path/port, so the Auto Scaling group would still see unhealthy targets and replace instances.
- D
Reduce the ALB health check interval so unhealthy targets are removed faster.
Why wrong: Reducing the interval makes ALB detect failure conditions sooner. With a ~2-minute initialization time, this increases the chance that instances are marked unhealthy and replaced before they can become ready, making the problem worse rather than improving start-up resilience.
Quick Answer
The answer is to increase the Auto Scaling group’s health check grace period so it exceeds the ~2-minute initialization time. This is correct because the health check grace period prevents the Auto Scaling group from acting on ELB health check failures during instance startup, allowing new instances time to download artifacts and become ready without being prematurely marked unhealthy and replaced. On the SAA-C03 exam, this scenario tests your understanding of how the grace period decouples instance initialization from health check replacement logic, a common trap being that candidates mistakenly adjust the ALB health check interval or threshold instead, which would reduce availability after the app is healthy. A strong memory tip is to think of the grace period as a “buffer zone” for bootstrapping: it gives your instances a head start before the health check timer even begins, preventing the cascade of terminations that caused the outage.
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 web application runs on an Amazon EC2 Auto Scaling group behind an Application Load Balancer (ALB). After each deployment, new instances take about 2 minutes to download artifacts and become ready to accept requests on the target port. In the last deployment, the ALB started marking targets unhealthy before the app was ready, and the Auto Scaling group then replaced those instances repeatedly, causing a prolonged outage. Which change best improves resilience during instance start-up without reducing actual availability once the application is healthy?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"best"Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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
Increase the Auto Scaling group’s health check grace period so it exceeds the ~2-minute initialization time.
The Auto Scaling group's health check grace period allows instances to initialize without being marked unhealthy by the ELB health checks. By setting this grace period to exceed the ~2-minute artifact download time, the ASG will not replace instances that are still starting up, preventing the cascade of terminations and redeployments that caused the outage. This directly addresses the root cause—premature health check failures—without changing the health check configuration or reducing availability once the app is ready.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 health check grace period so it exceeds the ~2-minute initialization time.
Why this is correct
A health check grace period prevents the Auto Scaling group from treating early health check failures as instance health problems. This avoids terminating instances before the application finishes initializing, which stops the restart/replace loop during deployments while still allowing normal health checks to apply once the app is ready.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Add more subnets across additional Availability Zones to distribute the same instances more widely.
Why it's wrong here
Adding subnets/AZs increases fault tolerance, but it does not address the immediate cause of the outage: the target group (via ALB health checks) is marking instances unhealthy before the application is ready. The unhealthy/replace loop would still occur for each instance that starts during deployments.
- ✗
Switch the load balancer target type from instance targets to IP targets to avoid health check failures.
Why it's wrong here
Target type does not change application readiness. Even with IP targets, the ALB health check fails until the application starts responding on the configured health check path/port, so the Auto Scaling group would still see unhealthy targets and replace instances.
- ✗
Reduce the ALB health check interval so unhealthy targets are removed faster.
Why it's wrong here
Reducing the interval makes ALB detect failure conditions sooner. With a ~2-minute initialization time, this increases the chance that instances are marked unhealthy and replaced before they can become ready, making the problem worse rather than improving start-up resilience.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse the ALB health check interval or target type with the Auto Scaling group's lifecycle management, mistakenly thinking that changing how the ALB checks health (interval or target type) will fix the premature replacement, when the correct solution is to adjust the ASG's grace period to align with the application's startup time.
Detailed technical explanation
How to think about this question
The health check grace period is defined in the Auto Scaling group's `HealthCheckGracePeriod` parameter (in seconds). When an instance enters the `InService` state, the ASG waits this duration before checking the ELB health status. Under the hood, the ASG polls the ELB's `DescribeTargetHealth` API; if the instance is reported as unhealthy after the grace period expires, the ASG terminates it and launches a replacement. In real-world scenarios, if the grace period is too short, a deployment can trigger a 'rolling replacement storm' where each new instance is terminated before it finishes bootstrapping, leading to an infinite loop of replacements.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Design Resilient Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design Resilient Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SAA-C03 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
Design Resilient Architectures — This question tests Design Resilient Architectures — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Increase the Auto Scaling group’s health check grace period so it exceeds the ~2-minute initialization time. — The Auto Scaling group's health check grace period allows instances to initialize without being marked unhealthy by the ELB health checks. By setting this grace period to exceed the ~2-minute artifact download time, the ASG will not replace instances that are still starting up, preventing the cascade of terminations and redeployments that caused the outage. This directly addresses the root cause—premature health check failures—without changing the health check configuration or reducing availability once the app is ready.
What should I do if I get this SAA-C03 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
Last reviewed: Jun 11, 2026
This SAA-C03 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 SAA-C03 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.