Google Professional Cloud Network Engineer Question 276
Single answerGoogle Cloud PlatformYour organization has multiple projects in Google Cloud that need to communicate with each other. You are tasked with designing a Virtual Private Cloud (VPC) topology that minimizes latency between projects while maintaining centralized control over shared services such as logging and monitoring. Which VPC topology would best meet these requirements?
- A
Star topology
- B
Hub-and-spoke topology
- C
Mesh topology
- D
Flat topology
Show answer and explanation
Correct answer: B
Explanation
The hub-and-spoke topology is the best fit for this scenario as it balances efficient communication between VPCs and centralized management of shared services. The hub VPC acts as a central point for shared services, while spoke VPCs communicate with each other through the hub. This ensures low latency and meets the organization's requirements for central control over logging and monitoring.
- A. Incorrect.
Star topology is not ideal in this case because it focuses on centralizing resources in a single VPC while other VPCs connect directly to it. This provides simplicity but may not offer the best balance of centralized control and efficient communication between multiple VPCs.
- B. Correct.
Hub-and-spoke topology is the best choice for this scenario as it allows centralized control over shared services in the hub VPC, while facilitating communication between spoke VPCs through the hub. This design minimizes latency and is scalable.
- C. Incorrect.
Mesh topology facilitates direct communication between all VPCs, but it lacks centralization and may become harder to manage as the number of VPCs increases. It is not the best fit for a setup requiring centralized control.
- D. Incorrect.
Flat topology is not a valid term or design in Google Cloud networking. This option is incorrect.