DOP-C02 Question 332
Select 2Your team has deployed a microservices application on Amazon ECS using Fargate. Recently, users have reported intermittent high latency, and your team suspects an issue with one of the services. You want to identify which service is causing the latency and visualize the latency's root cause. Which combination of actions should you take to diagnose the issue?
- A
Enable AWS X-Ray tracing in the ECS task definition and instrument the application code with X-Ray SDK.
- B
Set up a CloudWatch Logs Insights query to filter for error logs across all ECS services.
- C
Create a CloudWatch dashboard to monitor ECS service CPU and memory utilization metrics.
- D
Use AWS X-Ray to trace requests across services and analyze service maps.
- E
Enable detailed monitoring for Amazon ECS to increase metric granularity.
Show answer and explanation
Correct answers: A, D
Explanation
To diagnose latency issues in a microservices architecture deployed on ECS Fargate, you need tracing data to identify which service is causing the problem. By enabling AWS X-Ray and instrumenting your application, you can collect detailed traces and visualize a service map, making it easier to pinpoint latency bottlenecks. While CloudWatch Logs Insights, ECS metrics, and detailed monitoring are useful for other aspects of performance monitoring, they do not provide the necessary tracing capabilities for this scenario.
- A. Correct.
Correct. Enabling X-Ray tracing and instrumenting the application code allows you to capture detailed tracing data, which is necessary to identify latency bottlenecks between services.
- B. Incorrect.
While this can help identify error logs, it does not directly address tracing or pinpoint service-level latency issues.
- C. Incorrect.
Monitoring ECS service CPU and memory utilization is helpful for resource usage analysis but does not provide insights into request latency or root cause analysis.
- D. Correct.
Correct. AWS X-Ray provides request tracing and service maps to visualize latency issues and identify problematic services in your microservices architecture.
- E. Incorrect.
Detailed monitoring increases metric granularity but does not provide the tracing capabilities needed to analyze latency issues at the service level.