Question 530
Two VPCs need private communication and their CIDR blocks do not overlap. Which explanation MOST accurately accounts for the requirement?
Explanation
Correct Answer
VPC peering directly connects VPC networks but does not automatically make peering transitive. This principle explains why the suitable decision is: Consider VPC peering for supported private communication between the two VPCs. The confirming observation would be: A test VM accesses an authorized private endpoint across the peering connection. A useful continuing practice is: Document CIDR compatibility and routing before creating more peers.
Incorrect Answers
Route 53 is a managed DNS and traffic routing service rather than a virtual server. In this question, however, vPC peering directly connects VPC networks but does not automatically make peering transitive. The answer that meets the requirement is: VPC peering directly connects VPC networks but does not automatically make peering transitive.
AWS VPN and Direct Connect have different underlying paths and service properties. In this question, however, vPC peering directly connects VPC networks but does not automatically make peering transitive. The answer that meets the requirement is: VPC peering directly connects VPC networks but does not automatically make peering transitive.
NAT gateway enables outbound translation from private subnets rather than a public inbound listener. In this question, however, vPC peering directly connects VPC networks but does not automatically make peering transitive. The answer that meets the requirement is: VPC peering directly connects VPC networks but does not automatically make peering transitive.