ANS-C01 · Question #241
A company is running business applications on AWS. The company uses 50 AWS accounts, thousands of VPCs, and 3 AWS Regions across the United States and Europe. A network engineer needs to establish…
The correct answer is C. Create transit VIF with a gateway association to a new Direct Connect gateway. Associate each. Explanation Option C is correct because a Transit VIF (transit virtual interface) is specifically designed to connect an on-premises data center to a Direct Connect gateway, which can then be associated with transit gateways in multiple Regions - this is the only VIF type that…
Question
A company is running business applications on AWS. The company uses 50 AWS accounts, thousands of VPCs, and 3 AWS Regions across the United States and Europe. A network engineer needs to establish network connectivity between an on-premises data center and the Regions. The network engineer also must establish connectivity between the VPCs. On- premises: users and applications must be able to connect to applications that run in the VPCs. The company has an existing AWS Direct Connect connection that the network engineer can use. The network engineer creates a transit gateway in each Region and configures the transit gateways as inter-Region peers. Which solution will provide network connectivity from the on-premises data center to the Regions and will provide inter-VPC communications across the different Regions?
Options
- ACreate a private VIF with a gateway type of virtual private gateway. Configure the private VIF to
- BCreate a private VIF to a new Direct Connect gateway. Associate the new Direct Connect
- CCreate transit VIF with a gateway association to a new Direct Connect gateway. Associate each
- DCreate an AWS Site-to-Site VPN connection that uses a public VIF for the Direct Connect
How the community answered
(44 responses)- A9% (4)
- B5% (2)
- C68% (30)
- D18% (8)
Explanation
Explanation
Option C is correct because a Transit VIF (transit virtual interface) is specifically designed to connect an on-premises data center to a Direct Connect gateway, which can then be associated with transit gateways in multiple Regions - this is the only VIF type that supports transit gateway associations, enabling both on-premises-to-VPC and inter-VPC connectivity at scale across Regions.
Why the distractors are wrong:
- Option A uses a private VIF with a virtual private gateway, which only connects to a single VPC and cannot associate with a Direct Connect gateway or transit gateway - it doesn't scale across thousands of VPCs.
- Option B uses a private VIF to a Direct Connect gateway, which is closer but incorrect - private VIFs can only associate with virtual private gateways, not transit gateways; you need a transit VIF for transit gateway associations.
- Option D uses a Site-to-Site VPN over a public VIF, which is unnecessarily complex, introduces VPN overhead, and public VIFs are designed for AWS public services - not private VPC connectivity at this scale.
Memory Tip: Think "T for T" - Transit VIF → Transit Gateway. Whenever you need to connect on-premises to transit gateways (for multi-VPC, multi-Region connectivity), always reach for a Transit VIF + Direct Connect Gateway combination.
Topics
Community Discussion
No community discussion yet for this question.