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 is deploying a VPC network inside a VPC Service Controls perimeter for workloads in us-central1 and us-east1. You must configure Private Service Connect (PSC) to meet these requirements:
*.googleapis.com domains using a custom internal IP address, while blocking all other egress.us-central1 and us-east1 to privately initiate connections to a SaaS provider's PSC service attachment hosted in us-east1.Which configuration should you implement?
vpc-sc PSC endpoint, rely on the auto-created p.googleapis.com zone with Cloud Router custom route advertisements and restrictive egress firewall rules, and connect a PSC interface in a us-east1 PRIVATE_SERVICE_CONNECT subnet to a network attachment for the SaaS service.PRIVATE_SERVICE_CONNECT Subnets DoA Private Service Connect (PSC) interface is a special network interface attached to a producer resource that connects to a consumer's network attachment, allowing the producer to initiate outbound connections into the consumer VPC. Meanwhile, a subnet with the PRIVATE_SERVICE_CONNECT purpose is a producer-side NAT subnet used by service attachments to translate consumer traffic.
PRIVATE_SERVICE_CONNECT purpose subnets are used strictly on the producer side for NAT when publishing a service attachment. Consumer PSC endpoints (and network attachments) require regular subnets.*.googleapis.com DNS resolution for VPC and hybrid clients: Relying solely on the auto-created p.googleapis.com Service Directory zone does not intercept standard *.googleapis.com SDK queries, causing them to resolve to public Google Front End IPs (which are then dropped by the restrictive egress firewall). It also omits a Cloud DNS inbound forwarding policy for on-premises hosts.purpose=PRIVATE_SERVICE_CONNECT cannot host VM instances, forwarding rules, or consumer PSC endpoints.*.googleapis.com resolution requires a manually configured googleapis.com. private DNS zone.A PSC interface and network attachment (in a regular subnet) would be appropriate if the SaaS provider needed to initiate connections into your VPC resources, and a googleapis.com. zone plus inbound DNS policy were added for standard Google API domains.
googleapis.com. private DNS zone pointing to 199.36.153.4/30, advertise that range via Cloud Router custom routes with an inbound forwarding policy, and deploy two regional PSC endpoints targeting the SaaS service attachment—one in us-east1 and one in us-central1.Private Google Access allows VMs without external IPs (and on-premises hosts via custom route advertisements) to reach Google APIs using Google's predefined virtual IP ranges, such as the restricted VIP (199.36.153.4/30). Regional PSC endpoints connect a consumer subnet IP to a published service attachment.
199.36.153.4/30 range rather than using a PSC endpoint with a custom, organization-assigned internal IP address for granular routing and firewall control.DENY egress firewall rule (0.0.0.0/0) and a higher-priority ALLOW rule to the private API destination, the VPC's implied allow egress rule permits outbound traffic to the public internet.us-east1). Deploying a second PSC endpoint in us-central1 targeting a us-east1 service attachment is unsupported; cross-region access requires enabling global access (--allow-psc-global-access) on the us-east1 endpoint.199.36.153.4/30 or 199.36.153.8/30, whereas PSC for Google APIs lets you allocate custom internal IPv4 addresses.--allow-psc-global-access on a regional PSC endpoint makes a single endpoint reachable from all VPC regions.This model would work if Private Google Access were preferred over a custom PSC endpoint IP, restrictive egress firewall rules were added, and a single us-east1 PSC endpoint with global access enabled replaced the us-central1 endpoint.
all-apis PSC endpoint, use the auto-created p.googleapis.com Service Directory DNS zone with default Cloud Router route advertisements, and create a PSC endpoint in a us-central1 regular subnet targeting the us-east1 SaaS service attachment.This option attempts to deploy a PSC endpoint for global Google APIs inside an existing VPC subnet using the all-apis bundle, relies on Service Directory's automatic p.googleapis.com private zone and default BGP advertisements, and places a regional SaaS PSC endpoint in us-central1.
all-apis bundle grants access to Google APIs that do not support VPC Service Controls, violating the requirement to restrict traffic strictly to VPC-SC-supported services.p.googleapis.com zone only maps <service>-<endpoint>.p.googleapis.com hostnames. Standard *.googleapis.com requests bypass this zone and match Google's public DNS wildcard, resolving to public IP addresses instead of the PSC endpoint./32 PSC endpoint IPs. Additionally, a PSC endpoint for a published service cannot be created in a us-central1 subnet when the target service attachment resides in us-east1.all-apis vs. vpc-sc: all-apis mirrors private.googleapis.com, whereas vpc-sc mirrors restricted.googleapis.com for strict perimeter compliance.This approach would only work if the Google API endpoint IP were placed outside all subnet ranges, non-VPC-SC APIs were permitted, applications were refactored to use *.p.googleapis.com names locally without hybrid access, and the SaaS service attachment were hosted in us-central1.
vpc-sc PSC endpoint, configure a googleapis.com. private DNS zone with an inbound forwarding policy, advertise the IP via Cloud Router custom routes with restrictive egress firewall rules, and create a us-east1 PSC endpoint in a regular subnet with global access enabled.Private Service Connect (PSC) endpoints are internal IP addresses backed by forwarding rules in a consumer VPC network that provide private, unidirectional connectivity to Google APIs or published services (such as third-party SaaS applications) without traversing the public internet.
vpc-sc): Targeting the vpc-sc API bundle ensures the endpoint permits traffic only to Google APIs and services supported by VPC Service Controls, blocking access to unsupported services.--global --purpose=PRIVATE_SERVICE_CONNECT) that does not overlap with any primary or secondary subnet ranges in the local or peered VPCs.*.googleapis.com DNS resolution: Creating a Cloud DNS private zone for googleapis.com. with an A record pointing to the endpoint IP and a CNAME record for *.googleapis.com redirects standard SDK calls to the PSC endpoint instead of public Google Front End IPs. Enabling a Cloud DNS inbound forwarding policy lets on-premises hosts resolve these private records./32 IP via Cloud Router custom route advertisements enables on-premises reachability over Cloud Interconnect, while a low-priority DENY egress rule (0.0.0.0/0, priority 65534) paired with a high-priority ALLOW rule (TCP port 443 to the endpoint IP, priority 1000) blocks all other internet egress.us-east1).--allow-psc-global-access): Enabling global access allows VMs in us-central1 to reach the us-east1 PSC endpoint natively across Google's network.Unlike Private Google Access (which uses fixed 199.36.153.4/30 VIPs) or the all-apis bundle (which exposes non-VPC-SC APIs), this design enforces strict perimeter boundaries, custom IP control, seamless standard DNS resolution, and multi-region SaaS connectivity.
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