NSE7_PBC-7.2 · Question #33
Refer to the exhibit. You attempted to access the Linux1 EC2 instance directly from the internet using its public IP address in AWS. However, your connection is not successful. Given the network…
The correct answer is D. There is no internet gateway attached to the Spoke VPC A. This is because the Linux1 EC2 instance is not accessible directly from the internet using its public IP address in AWS. An internet gateway is a horizontally scaled, redundant, and highly available VPC component that allows communication between instances in your VPC and the…
Question
Refer to the exhibit. You attempted to access the Linux1 EC2 instance directly from the internet using its public IP address in AWS. However, your connection is not successful. Given the network topology, what can be the issue?
Exhibit
Options
- AThere is no connection between VPC A and VPC B.
- BThere is no elastic IP address attached to FortiGate in the Security VPC.
- CThe Transit Gateway BGP IP address is incorrect.
- DThere is no internet gateway attached to the Spoke VPC A.
How the community answered
(48 responses)- A6% (3)
- B17% (8)
- C2% (1)
- D75% (36)
Explanation
This is because the Linux1 EC2 instance is not accessible directly from the internet using its public IP address in AWS. An internet gateway is a horizontally scaled, redundant, and highly available VPC component that allows communication between instances in your VPC and the internet. Without an internet gateway, the Linux1 EC2 instance cannot receive or send traffic to or from the internet, even if it has a public IP address assigned to it. To fix this issue, you need to attach an internet gateway to the Spoke VPC A and configure a route table that directs internet-bound traffic to the internet gateway. You also need to ensure that the Linux1 EC2 instance has a security group that allows inbound and outbound traffic on the
Topics
Community Discussion
No community discussion yet for this question.
