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.
An enterprise is connecting its on-premises data center to a Google Cloud VPC network hosting mission-critical workloads in us-central1. The data center cannot reach a Dedicated Interconnect colocation facility and has the following requirements:
Which Partner Interconnect design and provisioning approach should the network engineer use?
This configuration attempts to provision four 2-Gbps pre-activated VLAN attachments across two metros and distinct edge availability domains using a single Cloud Router located only in us-central1.
us-central1) on a single Cloud Router.us-central1, Google Cloud requires two separate regions and at least two Cloud Routers (one per region) for 99.99% availability.us-central1, having attachments in two different physical metros does not prevent a total outage if all attachments terminate on a single region's Cloud Router.us-east4, Google Cloud cannot reroute on-premises traffic across its internal backbone around a regional disruption.The organization only required a 99.9% availability SLA (which uses two attachments in a single region and single metro across zone1 and zone2), or if two of the VLAN attachments were attached to a second Cloud Router in us-east4 alongside global dynamic routing.
This approach attempts to procure physical circuits using LOA-CFAs before creating VLAN attachments, disables pre-activation, and manually configures BGP peering sessions on the Cloud Routers for a Layer 3 Partner Interconnect connection.
PENDING_CUSTOMER state after provider configuration, blocking immediate traffic flow until manual activation occurs.The enterprise were provisioning a Dedicated Interconnect connection (which uses LOA-CFAs and manual BGP configuration) rather than a Layer 3 Partner Interconnect, and followed Dedicated Interconnect's physical cross-connect workflow.
This approach combines a 99.99% availability Partner Interconnect topology with Layer 3 service provider automation and API-based provisioning. Partner Interconnect provides private connectivity from 50 Mbps to 50 Gbps per VLAN attachment without requiring physical routing equipment in a colocation facility.
us-central1 and us-east4) with one Cloud Router per region, and four VLAN attachments split across two metropolitan areas and distinct edge availability domains (zone1 and zone2).ACTIVE and pass traffic immediately once the provider configures them, while the provider and Google Cloud automatically establish the BGP sessions.zone1 and zone2 via the API ensures coordinated maintenance windows within each metro never interrupt both links simultaneously.us-east4 allows traffic to reach us-central1 VMs over Google's backbone if us-central1 experiences an edge disruption.Unlike the Google Cloud Console, the Compute Engine API does not automatically distribute redundant attachments across different connections and edge availability domains. Manually specifying two regions, two metros, zone1 and zone2 domains, pre-activation, and pairing-key submission in the proper order delivers an automated, SLA-compliant 2-Gbps deployment.
This approach configures global dynamic routing, two Cloud Routers in two regions, Layer 3 pre-activation, and pairing keys, but relies on the Google Cloud API to automatically place the redundant VLAN attachments into distinct edge availability domains.
zone1 and zone2) to different connections.zone1), causing simultaneous downtime during scheduled maintenance.zone1 and zone2 are not taken offline together. Across different metros, maintenance is uncoordinated, making per-metro zone1 and zone2 separation mandatory for 99.99% availability.The network engineer either manually specified distinct Partner Interconnect connections and zone1 and zone2 edge availability domains in the API requests, or used the Google Cloud Console workflow to automatically assign redundant pairs across edge availability domains.
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