Question 659 of 1,746
Design for New SolutionsmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to implement a lifecycle hook in the Auto Scaling group that waits for the instance to signal readiness, combined with a target group health check that uses a longer interval and a higher healthy threshold. This works because the lifecycle hook pauses the instance at launch, preventing the Application Load Balancer from even attempting to route traffic until the instance sends a completion signal, while the adjusted health check settings—specifically a longer interval and higher healthy threshold—create a grace period that ensures the instance must pass multiple checks before being marked healthy, effectively eliminating the window where a partially initialized instance could receive traffic. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of the lifecycle hook’s ability to decouple instance initialization from Auto Scaling group scaling events, and it’s a common trap to confuse health check interval adjustments with the actual pause mechanism—remember, a lifecycle hook is the only way to enforce a true readiness gate. Memory tip: “Hook first, then check—pause before you pass.”

SAP-C02 Design for New Solutions Practice Question

This SAP-C02 practice question tests your understanding of design for new solutions. 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 company runs a critical web application on EC2 instances in an Auto Scaling group across three Availability Zones. The application uses an Application Load Balancer (ALB) with a target group that has health checks configured. Recently, the operations team noticed that during a deployment, the ALB started routing traffic to a new instance before it was ready to serve requests, causing a brief period of errors. The team wants to ensure that new instances are fully initialized and ready before receiving traffic. The application takes about 30 seconds to start up. Current health check settings: health check protocol HTTP, path /, interval 30 seconds, timeout 5 seconds, healthy threshold 2, unhealthy threshold 2. The deployment uses the Auto Scaling group's instance refresh feature. Which of the following is the MOST effective way to prevent traffic from being sent to instances that are not ready?

Question 1mediummultiple choice
Read the full NAT/PAT explanation →

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

Implement a lifecycle hook in the Auto Scaling group that waits for the instance to signal readiness. Also, configure the target group health check with a longer interval and a higher healthy threshold to ensure the instance is fully operational.

Option B is correct because the lifecycle hook pauses the instance until it is ready, and the health check with a longer grace period ensures the ALB does not consider the instance healthy until it passes. Option A is wrong because increasing the interval does not prevent early traffic; the instance might still pass the first check before being ready. Option C is wrong because the warm-up time in instance refresh is for the Auto Scaling group to launch instances, not for the application to become ready. Option D is wrong because pre-warming is not a service; it's a manual process.

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.

  • Implement a lifecycle hook in the Auto Scaling group that waits for the instance to signal readiness. Also, configure the target group health check with a longer interval and a higher healthy threshold to ensure the instance is fully operational.

    Why this is correct

    Lifecycle hooks can pause the instance launch until the application signals that it is ready, and the health check can be tuned to match the startup time.

    Related concept

    Static NAT maps one inside address to one outside address.

  • Increase the health check interval to 60 seconds and the healthy threshold to 5.

    Why it's wrong here

    This delays the time until the instance is considered healthy but does not prevent the ALB from sending traffic if the health check passes earlier.

  • Use the Auto Scaling group's instance refresh feature with a warm-up time of 60 seconds.

    Why it's wrong here

    Warm-up time in instance refresh specifies the time before the next batch of instances is terminated, not the time before an instance receives traffic.

  • Use AWS Global Accelerator to pre-warm the endpoints before directing traffic.

    Why it's wrong here

    Global Accelerator does not have a pre-warming feature; it routes traffic to healthy endpoints.

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 SAP-C02 NAT questions on configuration and troubleshooting.

Related practice questions

Related SAP-C02 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SAP-C02 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 SAP-C02 question test?

Design for New Solutions — This question tests Design for New Solutions — Static NAT maps one inside address to one outside address..

What is the correct answer to this question?

The correct answer is: Implement a lifecycle hook in the Auto Scaling group that waits for the instance to signal readiness. Also, configure the target group health check with a longer interval and a higher healthy threshold to ensure the instance is fully operational. — Option B is correct because the lifecycle hook pauses the instance until it is ready, and the health check with a longer grace period ensures the ALB does not consider the instance healthy until it passes. Option A is wrong because increasing the interval does not prevent early traffic; the instance might still pass the first check before being ready. Option C is wrong because the warm-up time in instance refresh is for the Auto Scaling group to launch instances, not for the application to become ready. Option D is wrong because pre-warming is not a service; it's a manual process.

What should I do if I get this SAP-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 SAP-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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 20, 2026

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.

Loading comments…

Sign in to join the discussion.

This SAP-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 SAP-C02 exam.