ANS-C01 · Question #248
A company has a VPC in the AWS Cloud. The company recently acquired a competitor that also has a VPC the AWS Cloud. A network engineer discovers an IP address overlap between the two VPCs. Both VPCs…
The correct answer is C. Configure AWS PrivateLink to facilitate connectivity between the VPCs and the partner service. Explanation AWS PrivateLink is the ideal solution because it enables private connectivity between VPCs and services without requiring the VPCs to peer directly with each other, meaning IP address overlap is irrelevant - each VPC connects independently to the partner service's…
Question
A company has a VPC in the AWS Cloud. The company recently acquired a competitor that also has a VPC the AWS Cloud. A network engineer discovers an IP address overlap between the two VPCs. Both VPCs require access to an AWS Marketplace partner service. Which solution will ensure interoperability among the VPC hosted services and the AWS Markelplace partner service?
Options
- AConfigure VPC peering with static routing between the VPCs. Configure an AWS Site-to-Site VPN
- BConfigure a NAT gateway in the VPCs. Configure default routes in each VPC to point to the local
- CConfigure AWS PrivateLink to facilitate connectivity between the VPCs and the partner service.
- DConfigure a NAT instance in the VPCs. Configure default routes in each VPC to point to the local
How the community answered
(23 responses)- A4% (1)
- B13% (3)
- C78% (18)
- D4% (1)
Explanation
Explanation
AWS PrivateLink is the ideal solution because it enables private connectivity between VPCs and services without requiring the VPCs to peer directly with each other, meaning IP address overlap is irrelevant - each VPC connects independently to the partner service's endpoint without routing traffic between themselves. This architecture neatly sidesteps the fundamental problem: overlapping CIDR blocks make direct VPC-to-VPC routing impossible.
Why the distractors fail:
- Option A is wrong because VPC peering cannot function with overlapping IP address ranges - AWS simply won't allow it, making static routing irrelevant in this context.
- Option B is partially tempting since NAT gateways can mask IPs, but configuring default routes between two overlapping VPCs still creates routing ambiguity and doesn't solve the partner service connectivity elegantly.
- Option D mirrors Option B's flaw - NAT instances are an older, self-managed alternative to NAT gateways, but the core routing logic remains broken with overlapping CIDRs.
Memory Tip: Think of PrivateLink as a "one-way mirror" - each VPC gets its own private window into the partner service without ever needing to "see" the other VPC. Whenever you see overlapping IPs + shared service access, PrivateLink is almost always the answer on AWS exams.
Topics
Community Discussion
No community discussion yet for this question.