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 designs a multi-VPC architecture on Google Cloud featuring a central hub VPC network connected to multiple independent spoke VPC networks using VPC Network Peering. The central hub hosts shared security and management tools and provides the sole connection to the corporate on-premises data center.
Security policies require workloads in Spoke-A to communicate with workloads in Spoke-B, while ensuring all inter-spoke traffic is inspected centrally within the hub network. Direct VPC peering connections between spokes are prohibited.
Which network design should you implement to enable inter-spoke communication?
Shared VPC allows an organization to connect resources from multiple service projects to a common, centrally managed host project VPC network. This architecture centralizes network administration, such as subnet creation, firewall rules, and routing, while delegating VM management to project administrators.
The organization wanted centralized network administration across multiple service projects within a single unified IP address space, rather than maintaining independent spoke VPC networks.
Private Service Connect (PSC) allows consumers to privately access services published by service producers (or Google APIs) across different VPC networks and organizations using private IP addresses inside the consumer VPC.
A single specific application or database hosted in one VPC needed to be securely exposed to consumer clients in another VPC without establishing full network peering or sharing IP routing tables.
Network Virtual Appliances (NVAs) are third-party or custom routing and firewall instances deployed within a Virtual Private Cloud (VPC). In a Google Cloud hub-and-spoke model using VPC Network Peering, NVAs deployed behind an internal Network Load Balancer serve as next-hop gateways that inspect, allow, or deny network traffic passing between peered networks.
Spoke-A cannot communicate directly with Spoke-B through the hub VPC using native VPC routing alone.This architecture complies strictly with Google Cloud network design best practices for hub-and-spoke topologies. It respects the non-transitive property of VPC peering while satisfying enterprise governance requirements for central traffic inspection.
Cloud Router is a fully distributed, managed Google Cloud service that exchanges dynamic routes with external networks using the Border Gateway Protocol (BGP). It operates primarily in conjunction with Cloud Interconnect and Cloud VPN.
You needed to dynamically advertise on-premises BGP IP prefixes across Cloud Interconnect to a single VPC network, rather than routing traffic across non-transitive VPC peering spokes.
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 Validated