CLOUD-NETWORK practice question 22 of 30

You are designing the network architecture for your organization. Your organization has three developer teams: Web, App, and Database. All of the…

Full set: 233 questions
You are designing the network architecture for your organization. Your organization has three developer teams: Web, App, and Database. All of the developer teams require access to Compute Engine instances to perform their critical tasks. You are part of a small network and security team that needs to provide network access to the developers. You need to maintain centralized control over network resources, including subnets, routes, and firewalls. You want to minimize operational overhead. How should you design this topology?
Answer options
A: Configure a host project with a Shared VPC. Create service projects for Web, App, and Database. Correct answer
B: Configure one VPC for Web, one VPC for App, and one VPC for Database. Configure HA VPN between each VPC.
C: Configure three Shared VPC host projects, each with a service project: one for Web, one for App, and one for Database.
D: Configure one VPC for Web, one VPC for App, and one VPC for Database. Use VPC Network Peering to connect all VPCs in a full mesh.
Correct Answer:
A. Configure a host project with a Shared VPC. Create service projects for Web, App, and Database.
Explanation

Shared VPC is the ideal Google Cloud feature for this scenario. It allows an organization to connect resources from multiple projects to a common Virtual Private Cloud (VPC) network. This enables a central network/security team to manage network resources like subnets, routes, and firewalls in a single "host project." The developer teams can then create and manage their own resources (like Compute Engine instances) in separate "service projects" that are attached to the host project's network. This model provides centralized control for the network team while giving autonomy to developer teams, perfectly matching the requirements and minimizing operational overhead by avoiding the management of multiple, separate networks and their interconnections.

Why Incorrect

B. Configuring separate VPCs with HA VPN creates decentralized management and significant operational overhead for connecting and maintaining three distinct networks, contradicting the requirements.
C. This creates three separate centralized domains, which is overly complex and defeats the purpose of a single point of control, massively increasing operational overhead.
D. VPC Network Peering connects separate VPCs but does not provide centralized control over the network resources within each VPC, failing a primary requirement.

References

1. Google Cloud Documentation, "Shared VPC overview". "Shared VPC allows an organization to connect resources from multiple projects to a common Virtual Private Cloud (VPC) network... This lets you create a centralized network and security administration." https://cloud.google.com/vpc/docs/shared-vpc

2. Google Cloud Documentation, "Provisioning Shared VPC". "With Shared VPC, you designate a project as a host project and attach one or more other service projects to it. The VPC networks in the host project are called Shared VPC networks." https://cloud.google.com/vpc/docs/provisioning-shared-vpc

Scroll to Top