ANS-C01 Question 132
Select 2Your company is running an application in a VPC that connects to an on-premises data center using AWS Direct Connect. Recently, users have reported intermittent connectivity issues when accessing the application. To troubleshoot, you need to identify whether the problem lies within the AWS infrastructure, the Direct Connect connection, or the on-premises network. Which of the following actions should you take to effectively isolate the issue? (Select TWO)
- A
Use AWS CloudWatch metrics to monitor the status of the Direct Connect virtual interface for errors or drops.
- B
Run a traceroute from an EC2 instance in the VPC to the on-premises network to identify any connectivity bottlenecks.
- C
Increase the Direct Connect connection bandwidth to handle intermittent traffic spikes.
- D
Use VPC flow logs to analyze traffic between your VPC and the on-premises data center.
- E
Enable AWS Global Accelerator to optimize network paths between the VPC and on-premises resources.
Show answer and explanation
Correct answers: A, B
Explanation
To isolate connectivity issues, it's essential to gather insights into the performance of the Direct Connect link and the path between the VPC and on-premises network. CloudWatch metrics help monitor the health of the Direct Connect connection, while traceroute identifies where connectivity bottlenecks occur. These actions enable effective troubleshooting and root cause analysis.
- A. Correct.
CloudWatch metrics for Direct Connect provide detailed insights into the performance of the physical connection, helping to identify any errors, latency, or packet drops.
- B. Correct.
Running a traceroute from the VPC can help pinpoint where the connectivity issue occurs (e.g., within AWS, the Direct Connect link, or the on-premises network).
- C. Incorrect.
Increasing the Direct Connect bandwidth does not address the root cause of intermittent connectivity issues; it only increases capacity, which may not be related to the problem.
- D. Incorrect.
VPC flow logs are useful for analyzing traffic patterns, but they will not provide insights into the Direct Connect physical connection or the on-premises network.
- E. Incorrect.
AWS Global Accelerator is not designed for troubleshooting Direct Connect issues, as it focuses on improving global application availability and performance.