Google Professional Cloud Network Engineer Question 277
Single answerGoogle Cloud PlatformYour organization has multiple Virtual Private Cloud (VPC) networks in Google Cloud across different regions to support various business units. You want to enable connectivity between these VPCs in a way that minimizes latency and ensures scalability while keeping network administration centralized. Which VPC topology should you choose?
- A
Mesh topology
- B
Hub-and-spoke topology
- C
Star topology
- D
Point-to-point peering between all VPCs
Show answer and explanation
Correct answer: B
Explanation
The hub-and-spoke topology is the best choice for connecting multiple VPCs in a scalable and manageable way. By designating one VPC as the hub, you centralize control and enable other VPCs (spokes) to connect through it. This minimizes complexity compared to a full mesh or point-to-point configuration and provides low-latency communication between VPCs through the hub.
- A. Incorrect.
A mesh topology involves direct peering between all VPCs, which becomes unsustainable as the number of VPCs increases due to exponential growth in network connections and administrative overhead.
- B. Correct.
A hub-and-spoke topology centralizes network management by connecting all VPCs to a central hub, typically a shared services VPC. This approach minimizes latency, scales well, and is easier to administer, making it the most suitable choice for the scenario.
- C. Incorrect.
A star topology might seem similar to hub-and-spoke but typically involves direct connections between the central hub and each endpoint. It lacks the flexibility and scalability required for multi-VPC setups in different regions.
- D. Incorrect.
Point-to-point peering between all VPCs is the least scalable option and is not practical when dealing with multiple VPCs, as it leads to high administrative overhead and potential latency issues.