A SysOps administrator is deploying a test site running on Amazon EC2 instances. The application requires both incoming and outgoing connectivity to the internet. Which combination of steps are…

Question

Options

• AAdd a NAT gateway to a public subnet.
• BAttach a private address to the elastic network interface on the EC2 instance.
• CAttach an Elastic IP address to the internet gateway.
• DAdd an entry to the route table for the subnet that points to an internet gateway.
• ECreate an internet gateway and attach it to a VPC.

• A
  7% (4)
• B
  3% (2)
• C
  14% (8)
• D
  76% (44)

Explanation

To give EC2 instances full internet access (both inbound and outbound), you must first create an internet gateway and attach it to the VPC (E), then add a route in the subnet's route table pointing to that gateway (D) - without both steps, traffic has no path to the internet even if the instance has a public IP. Option A (NAT gateway) only handles outbound traffic and is used for private subnets, not for a test site that also needs inbound connectivity. Option B is wrong because private IPs are not routable on the public internet - a public IP is required. Option C is a fabricated distractor; internet gateways don't have Elastic IPs attached to them, they are attached to VPCs.

Memory tip: Think of it as two layers - infrastructure (create + attach the IGW to the VPC) and routing (tell the subnet where to send internet-bound traffic). You always need both: the door (IGW) and the sign pointing to it (route table entry).

No community discussion yet for this question.