Answer-first summary for fast verification
Answer: Add two additional NICs to Instance #1 with the following configuration: NIC1 —VPC: VPC #2 —SUBNETWORK: subnet #2 NIC2 —VPC: VPC #3 —SUBNETWORK: subnet #3. Update firewall rules to enable traffic between instances.
The correct answer is B. Adding two additional NICs to Instance #1, each connected to a different VPC, will allow Instance #1 to communicate directly with Instance #2 and Instance #3 via internal IPs. This approach maintains the isolation of the subnets as required. Cloud Router (Option A) and VPN tunnels (Option C) do not meet the requirement of maintaining subnet separation. Peering all three VPCs (Option D) would enable communication between all instances, not just between Instance #1 and the other two instances.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your company has a project in Google Cloud with three Virtual Private Clouds (VPCs) to maintain network isolation. Each VPC contains one Compute Engine instance, and the subnets across these VPCs do not overlap. For security and organizational reasons, the subnets must remain separated. However, there is a requirement for Instance #1 to communicate directly with both Instance #2 and Instance #3 using internal IP addresses. How should you accomplish this while ensuring the VPCs remain isolated?
A
Create a cloud router to advertise subnet #2 and subnet #3 to subnet #1.
B
Add two additional NICs to Instance #1 with the following configuration: NIC1 —VPC: VPC #2 —SUBNETWORK: subnet #2 NIC2 —VPC: VPC #3 —SUBNETWORK: subnet #3. Update firewall rules to enable traffic between instances.
C
Create two VPN tunnels via CloudVPN: 1 — between VPC #1 and VPC #2. 1 — between VPC #2 and VPC #3. Update firewall rules to enable traffic between the instances.
D
Peer all three VPCs: Peer VPC #1 with VPC #2. Peer VPC #2 with VPC #3. Update firewall rules to enable traffic between the instances.
No comments yet.