SOA-C02 · Question #66
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…
The correct answer is C. Create VPC flow logs for the EC2 instance's elastic network interface to check for rejected traffic. https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html
Question
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?
Options
- ACreate Amazon CloudWatch logs for the EC2 instance to check for blocked traffic.
- BCreate Amazon CloudWatch logs for the Site-to-Site VPN connection to check for blocked traffic.
- CCreate VPC flow logs for the EC2 instance's elastic network interface to check for rejected traffic.
- DInstruct users to use EC2 Instance Connect as a connection method.
How the community answered
(37 responses)- A3% (1)
- B3% (1)
- C84% (31)
- D11% (4)
Explanation
https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html
Topics
Community Discussion
No community discussion yet for this question.