Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization operates a Shared VPC architecture connected to an on-premises data center via redundant Dedicated Interconnect links across two regions with global dynamic routing enabled. Workloads in both Google Cloud and the on-premises environment must privately access Google Cloud APIs (such as Vertex AI and Cloud Storage) as well as third-party managed services.
Your security and networking teams have established the following requirements:
Which architectural design meets all of these requirements?
This option combines Private Service Connect (PSC) endpoints with Cloud Router default subnet advertisements, a Cloud DNS outbound forwarding zone, and an inverted egress firewall rule targeting 199.36.153.8/30.
35.199.192.0/19 egress range) sends DNS queries outbound from Google Cloud VPCs to on-premises DNS servers. For on-premises systems to resolve Google Cloud private DNS zones, you must configure a Cloud DNS inbound server policy (which allocates inbound forwarder IPs inside the VPC) or create local records on on-premises DNS servers.199.36.153.8/30 (the private.googleapis.com VIP range) while allowing 0.0.0.0/0 on TCP port 443 leaves the entire public internet—including default public Google API domains—open for outbound traffic.0.0.0.0/0) policy paired with narrow allow rules targeting specific internal endpoint IPs.This configuration would work only if custom route advertisements were added for the PSC endpoint IPs, the Cloud DNS forwarding zone were replaced with an inbound server policy, and the firewall rules were reversed to allow TCP:443 only to the PSC IP while denying 0.0.0.0/0.
Direct Peering establishes a direct physical interconnection between an organization's network and Google's public edge routers to exchange traffic with Google's public IP space. Classic VPN provides basic IPsec tunneling with static or dynamic routing, while VPC Network Peering connects two VPC networks directly at the routing layer.
Direct Peering is appropriate when an organization or ISP needs high-bandwidth, low-latency connectivity to public Google services such as Google Workspace or YouTube without requiring private RFC 1918 VPC extension.
Private services access establishes a private connection between a consumer VPC network and a Google-managed or third-party service producer's VPC network using VPC Network Peering. Private Google Access is a subnet-level feature that allows Compute Engine VMs without external IP addresses to reach Google APIs through internal routes to default public VIPs.
199.36.153.8/30 or 199.36.153.4/30) or custom API endpoint IPs to on-premises routers, leaving on-premises hosts unable to route to those private endpoints.0.0.0.0/0 and default public Google API domains, failing to prevent network-level data exfiltration.This pattern is viable only when workloads reside entirely inside Google Cloud subnets (without hybrid on-premises reachability needs to peered producers), sufficient non-overlapping IP space is available for peering allocations, and strict egress blocking of default public API domains is not required.
Private Service Connect (PSC) provides service-centric, private connectivity to Google APIs and first-party or third-party managed services using internal IP addresses within a consumer VPC network. Combined with Cloud Router custom route advertisements, Cloud DNS inbound server policies, egress firewall policies, and VPC Service Controls, it creates an end-to-end private, high-throughput access path across hybrid links without exposing traffic to the public internet.
0.0.0.0/0 blocks workloads from reaching default public Google API domains (such as storage.googleapis.com over public VIPs). Extending a VPC Service Controls perimeter over Dedicated Interconnect adds an identity- and context-aware boundary against unauthorized data exfiltration.*.googleapis.com and regional endpoints directly to the internal PSC IP.200 + RTT), keeping latency low.This architecture addresses every security, routing, DNS, and operational constraint simultaneously. Alternatives that rely on VPC Network Peering cannot natively traverse hybrid connections without complex transit overlays, while designs that omit custom route advertisements or 0.0.0.0/0 egress denies leave critical reachability gaps or data exfiltration paths open.
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