Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is architecting a mission-critical hybrid network topology connecting an on-premises data center to Google Cloud. The architecture must satisfy the following technical and operational requirements:
Which hybrid networking design should you implement?
This design establishes individual, isolated Cloud VPN tunnels from on-premises routers directly to each separate workload VPC. Workload instances receive direct external IP addresses, and routing tables advertise specific individual host routes (/32) over dynamic BGP sessions.
The workload consisted of isolated, independent cloud test environments that did not require centralized inspection or high-throughput private hybrid interconnects.
This architecture establishes a centralized transit hub-and-spoke topology that uses Cloud Interconnect for high-throughput, redundant hybrid connectivity. It leverages an internal passthrough Network Load Balancer as a next hop to distribute traffic evenly across a managed instance group (MIG) of firewall Network Virtual Appliances (NVAs), while using Cloud Router summary custom advertisements to manage BGP prefix scale.

Combining a transit hub VPC with an internal load balancer as the next hop provides the resilience, scalability, and deep inspection required by enterprise landing zones without compromising routing stability.
This setup attempts to place a public-facing external Application Load Balancer in front of internal hybrid traffic flows and indiscriminately redistributes default 0.0.0.0/0 static routes via BGP Cloud Routers to on-premises edge routers.
0.0.0.0/0 routes into on-premises BGP tables can override enterprise internet gateways, causing unintended routing loops and blackholing data center internet traffic.The primary goal was load balancing global, inbound public internet traffic to web application frontends with edge SSL termination.
This architecture places a standalone, unmanaged Compute Engine VM inside a hub VPC to act as a monolithic router and firewall. All spoke VPCs and on-premises routers rely on manually maintained static routes pointing to this single VM instance.
The deployment were a small, non-critical proof-of-concept where traffic volume is minimal and high availability is not a requirement.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated