DOP-C02 Question 248
Select 3You are managing a web application hosted on Amazon EC2 instances behind an Application Load Balancer (ALB). Users have reported intermittent errors when accessing the application. To troubleshoot the issue, you decide to monitor relevant CloudWatch metrics and logs. Which combination of metrics and logs should you focus on to identify the root cause of the errors?
- A
5xxErrorCount metric from the ALB
- B
CPUUtilization metric from the EC2 instances
- C
RequestCount metric from the ALB
- D
QueueDepth metric from an Amazon SQS queue integrated with the application
- E
Access logs from the ALB
Show answer and explanation
Correct answers: A, B, E
Explanation
To identify the root cause of the reported errors, focusing on the 5xxErrorCount metric from the ALB will help detect server-side issues. Additionally, monitoring the CPUUtilization metric from the EC2 instances can reveal if resource exhaustion is contributing to the errors. Lastly, ALB access logs provide detailed insights into the request and response data, aiding in pinpointing the exact cause of the problem. Other metrics, such as RequestCount or QueueDepth, are less relevant to diagnosing intermittent errors in this specific scenario.
- A. Correct.
5xxErrorCount metric from the ALB is critical to identify server-side issues, such as application errors or misconfigurations, causing 5xx HTTP response codes.
- B. Correct.
CPUUtilization metric from the EC2 instances helps determine if the instances are under high load, which could be causing the errors.
- C. Incorrect.
RequestCount metric from the ALB tracks the number of requests received but does not directly identify errors.
- D. Incorrect.
QueueDepth metric from an Amazon SQS queue is unrelated to identifying errors in this scenario unless the issue involves queue backlog, which is not mentioned.
- E. Correct.
Access logs from the ALB provide detailed information about the requests and responses, which can help diagnose the source of the errors.