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 two on-premises data centers to a Google Cloud VPC network hosting mission-critical workloads in us-central1 and us-east4. The enterprise must meet the following architectural and compliance requirements:
Which architecture and configuration should the enterprise implement?
IPSEC) dual-stack (IPV4_IPV6) VLAN attachments split across two metropolitan areas and two regions (us-central1 and us-east4) in different edge availability domains. Enable global dynamic routing on the VPC, set the VLAN attachment and VPC MTU to 8896 bytes to absorb IPsec overhead without fragmentation, and use a single Cloud Router per region to manage both the encrypted VLAN attachments and the HA VPN BGP sessions.This option correctly identifies Partner Interconnect across two metropolitan areas and two Google Cloud regions as the foundation for a 99.99% availability SLA, but it introduces three incompatible settings related to IP stack types, MTU sizing, and Cloud Router separation.
IPSEC) for HA VPN over Cloud Interconnect, only IPv4 single-stack (IPV4_ONLY) is supported. Dual-stack (IPV4_IPV6) is restricted to unencrypted VLAN attachments.--encrypted-interconnect-router is dedicated exclusively to exchanging VPN gateway IP prefixes across the VLAN attachments and cannot be shared with the HA VPN tier's BGP sessions.1460, 1500, or 8896 byte MTUs when matched on the VPC and on-premises routers.The deployment used unencrypted IPV4_IPV6 VLAN attachments (where 8896 MTU and single-tier Cloud Routers are valid) and did not require IPsec encryption over the Partner Interconnect circuit.
Forcing an 8896-byte VPC MTU alongside IPsec encapsulation would cause severe packet drops or fragmentation issues if endpoints attempt to transmit jumbo frames over a 1440-byte HA VPN tunnel.
IPSEC) IPV4_ONLY VLAN attachments split across two metropolitan areas and two regions (us-central1 and us-east4), placing each region's pair in zone1 and zone2. Enable global dynamic routing on the VPC, reserve regional internal IPv4 ranges (IPSEC_INTERCONNECT) for the HA VPN gateway interfaces, configure separate Cloud Routers for the Interconnect tier (using --encrypted-interconnect-router and ASN 16550) and the HA VPN tier, and operate within the 1440-byte HA VPN gateway MTU.Partner Interconnect extends on-premises networks to Google Cloud VPCs through a supported service provider without requiring customer-owned routers in a colocation facility. Layering HA VPN over Cloud Interconnect adds end-to-end IPsec encryption across the provider network while keeping traffic off the public internet.
us-central1 and us-east4), with each region's pair split across edge availability domains zone1 and zone2, satisfies Google Cloud's 99.99% SLA topology. Enabling global dynamic routing on the VPC allows Cloud Routers in both regions to advertise all subnets and fail over automatically if an entire metro becomes unreachable.IPSEC) IPV4_ONLY VLAN attachments and reserving regional internal IPv4 ranges with --purpose=IPSEC_INTERCONNECT (prefix length /26 to /29) allows HA VPN gateway interfaces to use private regional IP addresses instead of public external IPs.--encrypted-interconnect-router with ASN 16550) exclusively exchanges VPN gateway prefixes, while separate HA VPN-tier Cloud Routers exchange application VPC routes over the IPsec tunnels within the 1440-byte HA VPN gateway MTU.zone1 and zone2 within each metro ensures Google maintenance does not affect both links simultaneously.This design satisfies every availability, capacity, encryption, addressing, and protocol constraint simultaneously without requiring colocation infrastructure or violating encrypted VLAN attachment limits.
zone1 and zone2 with MACsec encryption enabled, associating two VLAN attachments in us-central1 with one Cloud Router and regional dynamic routing mode. Extend dark fiber from the colocation demarcation directly to the on-premises routers using 10GBASE-LR optics to avoid third-party service provider involvement.Dedicated Interconnect provides direct physical 10-Gbps, 100-Gbps, or 400-Gbps Ethernet circuits between your own routing equipment in a colocation facility and Google's peering edge. MACsec for Cloud Interconnect provides Layer 2 link encryption between your router and Google's edge router.
zone1 and zone2 only achieve a 99.9% availability SLA. Furthermore, regional dynamic routing mode prevents the us-central1 Cloud Router from advertising us-east4 subnets or providing cross-region failover.The enterprise already operated routers in two colocation facilities (or within 10 km), deployed four physical connections across two metros with global dynamic routing (or a PRODUCTION_CRITICAL single-region connection group), and accepted hop-by-hop MACsec instead of IPsec.
When colocation facilities are unreachable or bandwidth requirements are below 10 Gbps per site, Partner Interconnect paired with HA VPN over Cloud Interconnect eliminates hardware ownership while meeting strict IPsec mandates.
IPSEC) Partner Interconnect VLAN attachments through a Layer 3 service provider in a single metropolitan area across zone1 and zone2 in us-central1 using global dynamic routing. Enable Bidirectional Forwarding Detection (BFD) on the Cloud Interconnect BGP sessions for rapid tunnel failover, and configure distinct BGP Multi-Exit Discriminator (MED) values on the Layer 3 provider sessions to control active/passive traffic steering.In a Layer 3 Partner Interconnect deployment, the service provider manages the BGP peering between their edge routers and your Cloud Routers, allowing pre-activation of VLAN attachments. BFD and BGP MED are routing mechanisms commonly used in hybrid networks to accelerate link failure detection and influence route preference.
us-central1) leaves the workload vulnerable to a regional or metro-wide outage.PRODUCTION_CRITICAL connection groups), Partner Interconnect 99.99% topologies require two regions and two metros.IPSEC_INTERCONNECT ranges, and separate HA VPN Cloud Routers).It used a Layer 2 Partner Interconnect provider across two metros and two regions (where end-to-end BGP MED values are preserved), omitted BFD at the Interconnect tier, and fully configured the two-tier HA VPN over Cloud Interconnect architecture.
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