An organization has several isolated VPC/VNet segments in the same public cloud provider. It wants the segments to exchange traffic over the provider's internal backbone rather than traversing the internet. Which approach best meets this requirement?
Establish VPC/VNet peering between the segments to enable private-IP routing across the provider's internal network
Configure a dedicated private link from the provider that terminates in the on-premises data center
Configure Network Address Translation so each segment uses public IPs to reach the others
Deploy a public content-delivery caching service to improve transfer speed between the segments
Creating a peering connection (sometimes called VPC/VNet peering) builds a private route table entry so that resources in each segment use their private IP addresses to reach one another across the provider's internal backbone. A dedicated provider link such as Direct Connect or ExpressRoute is primarily designed for hybrid connectivity to an on-premises network, adding unnecessary hops. Using NAT relies on public or shared external IP addressing and sends traffic through internet gateways. A public content-delivery or caching service accelerates downloads but still uses external paths. Peering therefore provides the most direct, private, and efficient communication between cloud segments.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is VPC/VNet peering?
Open an interactive chat with Bash
How does VPC/VNet peering differ from using NAT with public IPs?
Open an interactive chat with Bash
What are the advantages of using VPC/VNet peering over a dedicated private link to an on-premises data center?