mediummultiple choiceObjective-mapped

A web application runs on an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). After a new release, instances begin failing ALB health checks with errors like 502 while the application is still starting up. CloudWatch shows that the ASG replaces the instances before they finish initializing, so traffic never reaches healthy targets. Which change most directly prevents premature replacement during startup so traffic can resume as soon as the instances are actually healthy?

Question 1mediummultiple choice
Full question →

A web application runs on an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). After a new release, instances begin failing ALB health checks with errors like 502 while the application is still starting up. CloudWatch shows that the ASG replaces the instances before they finish initializing, so traffic never reaches healthy targets. Which change most directly prevents premature replacement during startup so traffic can resume as soon as the instances are actually healthy?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Reduce the ALB health check timeout to 1 second so failures are detected faster.

Shortening the timeout can increase false negatives during startup and make instances appear unhealthy even sooner, which can increase churn.

B

Best answer

Increase the Auto Scaling group health check grace period to cover application startup and initialization time.

The ASG health check grace period tells Auto Scaling to ignore failing health checks for a period after instance launch. This prevents newly launched instances from being replaced before the application has finished booting and can pass ALB health checks.

C

Distractor review

Enable connection draining on the ALB target group but set deregistration delay to 0 seconds.

Connection draining helps in-flight requests complete during deregistration, but it does not stop the ASG from replacing instances that are failing health checks during startup.

D

Distractor review

Switch the ALB target group health checks from HTTP to TCP so the application does not need to return HTTP 200.

TCP health checks only confirm that the port is open. They can mark an instance healthy even if the application is not actually ready to serve requests.

Common exam trap

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.

Technical deep dive

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.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Increase the Auto Scaling group health check grace period to cover application startup and initialization time. — The failure mode is premature replacement of new instances before the application finishes starting. In AWS, the Auto Scaling group health check grace period is the setting that prevents Auto Scaling from acting on failed health checks too early after launch. This gives the application time to initialize, after which the ALB health checks can pass and traffic can resume normally. Reducing the ALB health check timeout can worsen startup false negatives. Connection draining affects how existing connections are handled during deregistration, not whether the ASG terminates instances during warmup. TCP health checks verify only connectivity, not application readiness, and can route traffic to an instance that is not actually healthy.

What should I do if I get this SAA-C03 question wrong?

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

Discussion

Loading comments…

Sign in to join the discussion.