Examkin

Soru

Zorluk: ZorConfiguring Network Topology and VPC Infrastructure

An enterprise organization is deploying a multi-VPC topology in Google Cloud consisting of a Central Hub VPC and two separate workload networks: Workload-VPC-A and Workload-VPC-B. The Central Hub VPC connects to an on-premises data center using a Dedicated Interconnect with Cloud Router configured for global dynamic routing. The network team has established VPC Network Peering between Workload-VPC-A and the Central Hub VPC, as well as between Workload-VPC-B and the Central Hub VPC, enabling custom route exchange on both peering connections. The architecture team mandates that Workload-VPC-A and Workload-VPC-B must be able to communicate with each other directly while retaining connectivity to the on-premises network. Which configuration accurately satisfies these requirements in accordance with Google Cloud networking rules?

  1. Establish a direct VPC Network Peering link between Workload-VPC-A and Workload-VPC-B for inter-workload communication, while maintaining the existing hub-and-spoke VPC Network Peering links with custom route import/export enabled to access the on-premises network.Cevap
  2. B
    Rely solely on the existing VPC Network Peering links to the Central Hub VPC, relying on the hub network to dynamically proxy and transit IP traffic between Workload-VPC-A and Workload-VPC-B once custom routes are exported.
  3. C
    Replace the Dedicated Interconnect in the Central Hub VPC with HA VPN tunnels connected to both workload VPCs to enable native IP routing transitivity across all peered networks.
  4. D
    Configure VPC Service Controls perimeters encompassing all three VPCs to act as a network relay for routing inter-spoke traffic without establishing direct peering between the workload VPCs.

Cevap

Establish a direct VPC Network Peering link between Workload-VPC-A and Workload-VPC-B for inter-workload communication, while maintaining the existing hub-and-spoke VPC Network Peering links with custom route import/export enabled to access the on-premises network.
VPC Network Peering in Google Cloud is strictly non-transitive. If Workload-VPC-A and Workload-VPC-B need to communicate directly, a direct VPC Network Peering link between them is necessary. Additionally, to allow instances in spoke VPCs to access on-premises networks connected via Dedicated Interconnect in the hub VPC, custom route export must be enabled on the hub side and custom route import must be enabled on the spoke side.

Adım Adım Çözüm

1
Analyze the network transitivity requirements for VPC Network Peering.
Recognize that VPC Network Peering does not support transitive routing (VPC A peering with VPC B, and VPC B peering with VPC C does not allow VPC A to reach VPC C).
Google Cloud VPC Network Peering rules strictly prohibit packets from traveling through an intermediate peered network.
2
Determine the requirement for inter-spoke communication.
Direct VPC Network Peering between Workload-VPC-A and Workload-VPC-B must be provisioned.
Direct peering enables full-mesh connectivity between the two workload networks for low-latency, internal IP communication.
3
Determine the requirement for hybrid connectivity access.
Enable custom route import and export on the VPC Peering connections between the hub and spoke VPCs.
This allows Cloud Router in the Central Hub VPC to advertise learned on-premises Dedicated Interconnect routes to the spoke VPCs.

Anahtar Kavram

VPC Network Peering Non-Transitivity and Hybrid Custom Route Exchange
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Configuring Network Topology and VPC Infrastructure

Bu konudan daha fazla soru