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.
A producer team is publishing a regional service in us-central1 hosted behind an Internal passthrough Network Load Balancer on 16-vCPU backend VMs using Private Service Connect (PSC). Your design must meet these requirements:
How should you configure the PSC service attachments and subnets?
ACCEPT_MANUAL (one accepting project IDs and the other accepting VPC network names), assign each attachment its own dedicated PRIVATE_SERVICE_CONNECT NAT subnet, and keep the default 1 allocated NAT IP per PSC endpoint.This configuration correctly separates the project-based and VPC-network-based consumer accept lists across two service attachments with dedicated NAT subnets. However, targeting an IPv6 producer forwarding rule and keeping the default 1 NAT IP per endpoint introduces two critical failures for connectivity and scale.
--nat-ips-per-endpoint=2 paired with backend VMs having at least 16 vCPUs (which raises the limit to 131,070).Consumers only needed IPv6-only endpoints (never IPv4 endpoints) and each individual consumer endpoint required no more than 64,512 simultaneous connections.
ACCEPT_MANUAL (one accepting project IDs and the other accepting VPC network names), assign each attachment its own dedicated PRIVATE_SERVICE_CONNECT NAT subnet, and set --nat-ips-per-endpoint=2.This architecture publishes a single Internal passthrough Network Load Balancer through two independent Private Service Connect (PSC) service attachments in us-central1, each with its own PRIVATE_SERVICE_CONNECT NAT subnet, explicit approval (ACCEPT_MANUAL), and two allocated NAT IP addresses per PSC endpoint.
--nat-ips-per-endpoint=2 doubles the available NAT source ports, allowing up to 131,070 simultaneous IPv4 connections from a single endpoint to 16-vCPU backend VMs.PRIVATE_SERVICE_CONNECT subnet sized with enough usable IPs (accounting for 4 reserved IPs per subnet and 2 IPs per endpoint).ACCEPT_MANUAL enforces explicit allowlisting and supports per-project or per-network connection limits.It satisfies every scaling, protocol, and governance constraint natively at line rate without deploying extra proxy layers, duplicating backend VMs, or violating NAT subnet exclusivity and accept-list type restrictions.
ACCEPT_MANUAL (one accepting project IDs and the other accepting VPC network names), assign both attachments to the same PRIVATE_SERVICE_CONNECT NAT subnet, and set --nat-ips-per-endpoint=2.Deploying two service attachments against the same Internal passthrough Network Load Balancer forwarding rule correctly separates the project-based and VPC-network-based consumer accept lists, and --nat-ips-per-endpoint=2 addresses the high concurrency target. However, attempting to attach both service attachments to the same PRIVATE_SERVICE_CONNECT NAT subnet violates Google Cloud's subnet exclusivity rule.
PRIVATE_SERVICE_CONNECT NAT subnet cannot be referenced by more than one service attachment. Attempting to reuse the same NAT subnet on the second service attachment will be rejected.--purpose=PRIVATE_SERVICE_CONNECT are reserved solely for source NAT (SNAT) of incoming consumer traffic and cannot host VMs or forwarding rules.--nat-ips-per-endpoint=2 consumes two NAT IPs per connected endpoint (plus two per propagated spoke if Network Connectivity Center propagation is used).Each of the two service attachments was assigned its own separate, dedicated PRIVATE_SERVICE_CONNECT NAT subnet (or set of subnets) in us-central1 rather than attempting to share one subnet across both attachments.
ACCEPT_MANUAL, add both the project IDs and VPC network names to its consumer accept list, assign a dedicated PRIVATE_SERVICE_CONNECT NAT subnet, and set --nat-ips-per-endpoint=2.A Private Service Connect (PSC) service attachment with ACCEPT_MANUAL connection preference controls which consumers can connect by evaluating a consumer accept list and consumer reject list. While it is valid to configure an IPv4 target forwarding rule and --nat-ips-per-endpoint=2 for high connection volume, placing both project IDs and VPC network names on the same service attachment is invalid.
All internal consumers and external partners agreed to use the same consumer identifier type—for example, if both groups were allowlisted exclusively by project ID or exclusively by VPC network name on that single service attachment.
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