The answer is to use AWS X-Ray to trace requests from the ALB to the application and downstream services. This is correct because intermittent latency spikes often stem from a specific component in the request path, such as a slow database query or a misconfigured backend, and X-Ray provides end-to-end trace data that pinpoints exactly where the delay occurs, unlike aggregated CloudWatch metrics which only show the symptom. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your ability to choose observability tools over scaling or infrastructure swaps—a common trap is assuming more instances (Option A) or switching to an NLB (Option C) will fix a performance issue, when the real need is application-level visibility. Remember the memory tip: when latency is a mystery, trace the story with X-Ray, not just the numbers.
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 company runs a critical application on Amazon EC2 instances behind an Application Load Balancer (ALB). The application experiences intermittent latency spikes. The operations team has enabled detailed CloudWatch metrics and logs, but cannot identify the root cause. What is the MOST effective way to troubleshoot the latency issue?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use AWS X-Ray to trace requests from the ALB to the application and downstream services.
Option B is correct because leveraging AWS X-Ray to trace requests end-to-end helps identify which component is causing latency. Option A is wrong because adding more EC2 instances may not address the root cause and could increase costs. Option C is wrong because switching to a Network Load Balancer (NLB) does not provide visibility into application-level latency. Option D is wrong because enabling detailed monitoring on the ALB only provides metrics, not traces. Option E is wrong because migrating to Lambda adds complexity and may not solve latency issues caused by other factors.
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.
✗
Enable detailed ALB metrics and create a CloudWatch dashboard.
Why it's wrong here
Metrics alone may not reveal the root cause; tracing is needed.
✗
Migrate the application to AWS Lambda to eliminate EC2 overhead.
Why it's wrong here
Lambda may not be suitable for all applications and does not automatically solve latency issues.
✗
Replace the ALB with a Network Load Balancer (NLB) for lower latency.
Why it's wrong here
NLB does not provide application-layer visibility.
✓
Use AWS X-Ray to trace requests from the ALB to the application and downstream services.
Why this is correct
X-Ray provides end-to-end tracing to pinpoint latency sources.
Related concept
Static NAT maps one inside address to one outside address.
✗
Add more EC2 instances behind the ALB to distribute the load.
Why it's wrong here
Scaling out does not identify the root cause of latency.
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
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
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: Use AWS X-Ray to trace requests from the ALB to the application and downstream services. — Option B is correct because leveraging AWS X-Ray to trace requests end-to-end helps identify which component is causing latency. Option A is wrong because adding more EC2 instances may not address the root cause and could increase costs. Option C is wrong because switching to a Network Load Balancer (NLB) does not provide visibility into application-level latency. Option D is wrong because enabling detailed monitoring on the ALB only provides metrics, not traces. Option E is wrong because migrating to Lambda adds complexity and may not solve latency issues caused by other factors.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company runs a web application on Amazon EC2 instances behind an Application Load Balancer (ALB). The application experiences intermittent latency spikes. The operations team has enabled detailed CloudWatch metrics and EC2 instance status checks. The team needs to identify the root cause of the latency. Which TWO actions should the team take to diagnose the issue? (Choose two.)
medium
A.Enable detailed monitoring (1-minute metrics) on the ALB and create a CloudWatch dashboard to view the RequestCount and TargetResponseTime metrics.
B.Integrate the application with AWS X-Ray and enable tracing on the EC2 instances to capture trace data for all requests.
✓ C.Set up an Amazon CloudWatch Synthetics canary that follows a step-by-step guide through the application and monitor the step durations.
✓ D.Enable access logging on the ALB and analyze the logs to find requests with high latency.
E.Enable VPC Flow Logs on the subnets where the EC2 instances reside and analyze the logs for packet loss.
Why C: Option C is correct because CloudWatch Synthetics canaries simulate user workflows step by step, and monitoring step durations helps pinpoint which specific part of the application is causing latency spikes. This provides granular, end-to-end visibility into the user experience beyond what aggregate metrics offer.
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.
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.