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 has established hybrid connectivity between its on-premises data center and a central Google Cloud Virtual Private Cloud (VPC) network using Dedicated Interconnect.
A partner team hosts a proprietary analytics service behind an internal Network Load Balancer in a separate, isolated VPC project. You need to enable private access to this analytics service from both on-premises systems and cloud instances located across multiple Google Cloud regions.
Your solution must meet the following requirements:
Which network architecture should you implement?
Cloud HA VPN provides secure, SLA-backed IPSec VPN connectivity over the public internet or private interconnects, dynamically exchanging routes between networks using Border Gateway Protocol (BGP) via Cloud Router.
The connection had to traverse an untrusted third-party transit network or public internet where IPSec encryption was mandatory by compliance policy.
Within Google Cloud's high-speed backbone, using HA VPN solely to connect two VPCs for a single managed service adds unnecessary encryption overhead and routing complexity when Private Service Connect fulfills the need natively.
Shared VPC allows an organization to connect resources from multiple projects to a common Virtual Private Cloud network hosted in a designated host project, enabling centralized network administration while delegating workload management to service projects.
The partner team was an internal department within the exact same Google Cloud organization that needed central network governance, unified security policies, and standard subnet delegation.
Shared VPC is designed for internal organizational infrastructure consolidation rather than decoupling and publishing isolated modular microservices across disparate environments.
VPC Network Peering connects two Virtual Private Cloud networks directly using Google's internal software-defined network, allowing Compute Engine resources in both networks to communicate using internal RFC 1918 IP addresses with low latency and high bandwidth.
Both VPCs were managed by the same team, had strictly non-overlapping IP address spaces, and only required direct VM-to-VM cloud communication without requiring transit from on-premises clients across the peering boundary.
Attempting to bridge on-premises traffic to a peered VPC requires deploying managed Network Virtual Appliances (NVAs) in the hub VPC, introducing unnecessary complexity and management overhead.
Private Service Connect (PSC) is a cloud-native networking feature that allows service producers to publish services via an internal load balancer, and service consumers to access those services privately using internal IP addresses assigned to endpoints or forwarding rules within their own VPC network. When global access is enabled on a consumer PSC endpoint, clients in any Google Cloud region as well as hybrid clients connecting from on-premises networks via Cloud Interconnect or Cloud VPN can route traffic directly to the endpoint.
Unlike VPC Network Peering, which requires unique, non-overlapping IP space and exposes entire network topologies, PSC establishes targeted, unidirectional service access. Combined with global access, it fulfills all multi-region and hybrid requirements natively without the operational burden of managing routing appliances.
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