SAP-C02 Continuous Improvement for Existing Solutions Practice Question
A company runs a microservices application on Amazon ECS with the Fargate launch type. The services communicate over a service mesh. The operations team wants to improve observability and reduce troubleshooting time for inter-service communication issues. They need to capture detailed request traces and metrics without modifying application code. Which solution should a solutions architect recommend?
⚠ Common exam trap
The trap here is assuming that container-level monitoring or manual debugging tools provide the same depth as a service mesh for inter-service tracing.
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
✓
Deploy AWS App Mesh with Envoy sidecar proxies and configure it to emit traces to AWS X-Ray and metrics to Amazon CloudWatch.
AWS App Mesh with Envoy sidecars provides layer 7 observability, including distributed tracing and metrics, without requiring application code changes. It integrates with X-Ray and CloudWatch, giving the operations team detailed visibility into inter-service communication. The other options either require code changes, lack granularity, or are not scalable.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Amazon CloudWatch Container Insights with enhanced observability for ECS, and enable VPC Flow Logs for the service subnets.
Why it's wrong here
Container Insights provides metrics and logs at the container and cluster level, but it does not capture detailed request traces between services. VPC Flow Logs record IP-level traffic but lack application-layer context. This combination does not provide the granular tracing needed for inter-service troubleshooting.
- ✗
Configure the application to use the AWS X-Ray SDK for instrumenting all service calls, and deploy the X-Ray daemon as a sidecar.
Why it's wrong here
Using the X-Ray SDK requires modifying application code, which violates the requirement to avoid code changes. While the X-Ray daemon can run as a sidecar, the SDK instrumentation is still needed for tracing. This option does not meet the no-code-change constraint.
- ✗
Enable ECS Exec on all tasks and use AWS Systems Manager Session Manager to run tcpdump on each container.
Why it's wrong here
ECS Exec allows interactive command execution in containers, but using tcpdump manually is not a scalable observability solution. It requires per-container access and does not provide centralized tracing or metrics. This approach increases operational overhead and does not meet the need for automated, code-free observability.
- ✓
Deploy AWS App Mesh with Envoy sidecar proxies and configure it to emit traces to AWS X-Ray and metrics to Amazon CloudWatch.
Why this is correct
AWS App Mesh uses Envoy sidecar proxies to intercept traffic between services, enabling detailed tracing and metrics without code changes. It integrates with X-Ray for distributed tracing and CloudWatch for metrics, providing the required observability for inter-service communication.
Go deeper
Related to this question
About these practice questions
One of 984 original SAP-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
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.