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 enterprise is implementing a Network Connectivity Center (NCC) hub in a central project to interconnect multiple workload VPC networks (attached as VPC spokes) with an on-premises data center using Layer 2 Partner Interconnect, while also supporting site-to-site data transfer to a remote branch connected via another hybrid spoke. Your architecture must meet these requirements:
us-central1 and us-east4.Which configuration meets all of these requirements?
This option attempts to achieve multi-region resilience using two Partner Interconnect VLAN attachments split across two regions (us-central1 and us-east4), leaves the routing VPC at its default 1460-byte MTU, and shares a peer ASN with the branch spoke.
--mtu=1500 on the VLAN attachments while leaving the routing VPC at 1460 prevents end-to-end 1500-byte packet transmission. Both the VPC network and the VLAN attachments (along with on-premises routers) must share the same 1500 MTU value.1 and 2 guarantee that planned maintenance in one domain leaves the other domain active.1440, 1460, 1500, and 8896 MTUs, but effective 1500-byte or jumbo transport requires matching VPC and attachment MTUs.1500, and the data center spoke used a distinct peer ASN from the branch spoke.This configuration establishes a multi-region, mission-critical Network Connectivity Center (NCC) hybrid transit topology using Layer 2 Partner Interconnect VLAN attachments as hybrid spokes. It connects an on-premises data center to both workload VPC spokes and a remote branch office via site-to-site data transfer across Google's backbone.
us-central1 and us-east4), connected to two separate metropolitan areas across edge availability domains 1 and 2 in each metro—protects against both single-domain maintenance and regional outages. Pairing each regional pair with a dedicated Cloud Router and enabling global dynamic routing mode on the routing VPC satisfies the 99.99% SLA requirements.--mtu parameter to 1500 alone is insufficient; the routing VPC network MTU and on-premises router and VM MTUs must also be set to 1500 to prevent packet drops or fragmentation.--include-import-ranges=ALL_IPV4_RANGES, and enabling site-to-site data transfer allows workload VPC spoke subnets and remote branch routes to be dynamically advertised to the data center.16550, and NCC hybrid spokes require legacy best path selection mode. Using one consistent peer ASN across all BGP sessions in the data center spoke—while keeping that ASN distinct from the branch spoke's ASN—ensures proper route re-advertisement.This is the only configuration that simultaneously satisfies the 99.99% multi-region Partner Interconnect SLA, end-to-end 1500-byte MTU alignment, Partner Interconnect ASN (16550) rules, and NCC hybrid spoke project, path-selection, and ASN constraints.
This option separates the routing VPC and Partner Interconnect VLAN attachments into a project different from the NCC hub, enables regional dynamic routing mode, omits --include-import-ranges=ALL_IPV4_RANGES, and attempts to mix VLAN attachments and HA VPN tunnels inside a single hybrid spoke.
--include-import-ranges=ALL_IPV4_RANGES on the hybrid spoke (or configuring custom route advertisements on the Cloud Routers), workload VPC spoke subnets are not advertised to the on-premises routers.--include-import-ranges=ALL_IPV4_RANGES, and any HA VPN tunnels were placed in a separate hybrid spoke.This option correctly provisions four Partner Interconnect VLAN attachments across two regions and two edge availability domains with matching 1500-byte MTUs, global dynamic routing, and --include-import-ranges=ALL_IPV4_RANGES. However, it introduces three configuration errors in Cloud Router and BGP ASN settings.
64513 is supported for Dedicated Interconnect, but Partner Interconnect strictly requires every associated Cloud Router to use the Google ASN 16550.16550 Mandate: Partner Interconnect relies on ASN 16550 across both Layer 2 and Layer 3 service provider architectures.16550 (or the deployment used Dedicated Interconnect with private ASNs), the VPC used legacy best path selection mode, and both regional data center routers used the same peer ASN.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