Topic 1 Question 431
A company has an AWS Site-to-Site VPN connection between on-premises resources and resources that are hosted in a VPC. A SysOps administrator launches an Amazon EC2 instance that has only a private IP address into a private subnet in the VPC. The EC2 instance runs Microsoft Windows Server.
A security group for the EC2 instance has rules that allow inbound traffic from the on-premises network over the VPN connection. The on-premises environment contains a third-party network firewall. Rules in the third-party network firewall allow Remote Desktop Protocol (RDP) traffic to flow between the on-premises users over the VPN connection.
The on-premises users are unable to connect to the EC2 instance and receive a timeout error.
What should the SysOps administrator do to troubleshoot this issue?
Create Amazon CloudWatch logs for the EC2 instance to check for blocked traffic.
Create Amazon CloudWatch logs for the Site-to-Site VPN connection to check for blocked traffic.
Create VPC flow logs for the EC2 instance's elastic network interface to check for rejected traffic.
Instruct users to use EC2 Instance Connect as a connection method.
ユーザの投票
コメント(3)
- 正解だと思う選択肢: C👍 4mpl2032024/09/20
- 正解だと思 う選択肢: C
Here's why the other options are less likely:
(A) CloudWatch logs for the EC2 instance wouldn't show blocked traffic, but might reveal internal server issues. (B) CloudWatch logs for the VPN connection wouldn't provide details on traffic reaching the specific instance. (D) EC2 Instance Connect wouldn't be relevant since RDP is the desired connection method. Therefore, the best course of action is:
(C) Create VPC flow logs for the EC2 instance's elastic network interface. This will show whether RDP traffic is even reaching the instance and if it's being rejected by security groups or Network ACLs within the VPC.
👍 3klayytech2024/09/22 - 正解だと思う選択肢: C
I agree with C
👍 1seetpt2024/10/07
シャッフルモード