Question

Difficulty: EasyAWS VPN, Direct Connect, and Transit Gateway Management

An organization wants to establish a dedicated connection from their on-premises datacenter to a private subnet in a single VPC using an existing AWS Direct Connect connection. Which type of virtual interface (VIF) should the SysOps administrator configure on the Direct Connect connection to meet this requirement?

  1. A Private VIFAnswer
  2. B
    A Public VIF
  3. C
    A Transit VIF
  4. D
    A Hosted VIF

Answer

A Private VIF
A Private VIF is the correct choice because it is designed to establish private connectivity between an on-premises network and a Virtual Private Gateway (VGW) associated with a single VPC using private IP addresses.

Step-by-Step Solution

1
Identify the destination and routing requirements.
The target is a private subnet within a single VPC, requiring private IP routing over the dedicated physical connection.
This determines whether the connection must route to private VPC endpoints or public AWS service endpoints.
2
Evaluate the virtual interface options based on destination.
A Private VIF routes to a virtual private gateway or Direct Connect Gateway for VPC private resources. A Public VIF routes to public AWS services. A Transit VIF routes to a Transit Gateway.
Choosing the correct VIF type ensures the routing behavior matches the target VPC environment.
3
Select the option that matches the single-VPC private subnet requirement.
A Private VIF is chosen because it directly maps to the Virtual Private Gateway associated with the target VPC.
This establishes the necessary private routing paths for the on-premises network to communicate with the VPC resources.

Key Concept

AWS Direct Connect Virtual Interface Types
Rate this question