The correct answer is to create a CloudWatch alarm for memory utilization and attach it to a scaling policy. This works because standard Auto Scaling health checks only monitor EC2 status or ELB pings, which miss internal resource pressure like memory exhaustion; by adding a custom CloudWatch metric alarm tied to a scaling policy, the group proactively scales out before memory usage triggers a health check failure, preventing the continuous termination-and-replacement cycle. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of Auto Scaling group health check failure root causes versus symptoms—a common trap is to choose instance type upgrades or scheduled scaling, which treat the effect rather than the cause. Remember the key distinction: health checks react to failure, while scaling policies based on memory utilization prevent it. Memory tip: think "Alarm before Armageddon"—the alarm scales out before memory hits the red zone.
SAP-C02 Continuous Improvement for Existing Solutions Practice Question
This SAP-C02 practice question tests your understanding of continuous improvement for existing solutions. 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 solutions architect notices that an Auto Scaling group's instances are continuously being terminated and replaced. CloudWatch logs show that health checks are failing due to high memory usage. The instances run a memory-intensive application. What should the architect do to improve stability?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a CloudWatch alarm for memory utilization and attach it to a scaling policy.
Option A is correct because adding a memory alarm allows the Auto Scaling group to scale out before memory exhaustion causes failures. Option B is wrong because increasing instance count per AZ doesn't address the root cause of memory pressure. Option C is wrong because memory-optimized instances provide more memory per instance, reducing the likelihood of failure. Option D is wrong because a scheduled scaling policy is for predictable traffic, not for memory-driven scaling.
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.
✗
Change the instance type to a memory-optimized family like R5.
Why it's wrong here
This reduces per-instance memory pressure but may not be cost-effective; scaling based on memory is more dynamic.
✗
Use a scheduled scaling policy to add instances during peak hours.
Why it's wrong here
Scheduled scaling is for predictable patterns, not for reactive scaling to memory usage.
✗
Increase the minimum number of instances in the Auto Scaling group.
Why it's wrong here
More instances don't fix memory pressure on each instance.
✓
Create a CloudWatch alarm for memory utilization and attach it to a scaling policy.
Why this is correct
Memory alarm triggers scaling before health check failures.
Related concept
Static NAT maps one inside address to one outside address.
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.
Continuous Improvement for Existing Solutions — This question tests Continuous Improvement for Existing Solutions — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Create a CloudWatch alarm for memory utilization and attach it to a scaling policy. — Option A is correct because adding a memory alarm allows the Auto Scaling group to scale out before memory exhaustion causes failures. Option B is wrong because increasing instance count per AZ doesn't address the root cause of memory pressure. Option C is wrong because memory-optimized instances provide more memory per instance, reducing the likelihood of failure. Option D is wrong because a scheduled scaling policy is for predictable traffic, not for memory-driven scaling.
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 →
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 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.
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.