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 hybrid connectivity between its on-premises data center and a Google Cloud VPC (prod-vpc) in us-central1. Your on-premises edge routers are already configured with the public ASN 12345. You must meet the following requirements:
us-central1.How should you configure the Cloud Routers and BGP session parameters?
us-central1: assign ASN 16550 to the Partner Interconnect Cloud Router and a private ASN (such as 65001) to the HA VPN Cloud Router. Retain public ASN 12345 on the on-premises routers, and configure BGP graceful restart with a 20-second keepalive interval and a 60-second hold timer.Deploying two separate Cloud Routers with product-appropriate Autonomous System Numbers (ASNs) and properly tuned BGP timers ensures compliant hybrid peering across both Partner Interconnect and HA VPN while protecting traffic during control-plane maintenance.
16550, a Cloud Router managing Partner Interconnect VLAN attachments cannot also manage HA VPN BGP sessions. Creating a second Cloud Router with an RFC 6996 private ASN (64512–65534 or 4200000000–4294967294) such as 65001 satisfies HA VPN's private ASN requirement.12345 on the on-premises routers avoids any local-versus-peer ASN collision (16550 vs. 12345 and 65001 vs. 12345).16550) and HA VPN (private ASN).12345).Unlike designs that attempt to combine Partner Interconnect and HA VPN on one Cloud Router, reuse conflicting ASNs, or shorten hold timers below 60 seconds, this architecture satisfies every Google Cloud product constraint and aligns with recommended BGP timer settings.
us-central1: assign ASN 16550 to the Partner Interconnect Cloud Router and the organization's public ASN 12345 to the HA VPN Cloud Router. Configure the on-premises routers with private ASN 65001, a 15-second keepalive interval, and a 45-second hold timer with graceful restart enabled.This option swaps the public and private ASNs for the HA VPN path—placing the organization's public ASN 12345 on the HA VPN Cloud Router and a private ASN 65001 on the on-premises routers—while configuring a 15-second keepalive and 45-second hold timer.
16550 for Partner Interconnect, Cloud Router strictly requires an RFC 6996 private ASN (64512–65534 or 4200000000–4294967294). Attempting to configure a customer-owned public ASN (12345) on the HA VPN Cloud Router fails validation.15 seconds invalid on Cloud Router. Furthermore, a 45-second hold timer on-premises is shorter than the 60-second maximum duration of Cloud Router software migrations, risking BGP session flaps.16550 for Partner Interconnect), whereas the peer router on-premises may use either a public or private ASN.12345) introduces unnecessary operational risk and breaks existing external routing policies.65001, the on-premises routers kept their public ASN 12345, and the BGP timers were set to 20 seconds (keepalive) and 60 seconds (hold time).us-central1, assigning private ASN 65001 to both the Partner Interconnect and HA VPN Cloud Routers. Change the on-premises routers' local ASN to 65001 to match, and configure a 20-second keepalive interval with a 60-second hold timer without graceful restart.This approach creates two Cloud Routers in us-central1, assigns the private ASN 65001 to both, modifies the on-premises routers to use the identical ASN 65001, and omits BGP graceful restart.
16550, not a private ASN such as 65001.65001 to both the Cloud Router and the on-premises router causes an ASN collision (Local ASN conflicts with peer ASN specified by a router in the same region and network), preventing external BGP (eBGP) peering from establishing.12345) to a private ASN; Cloud Router supports both public and private peer ASNs.12345), and graceful restart was enabled on the on-premises routers.When configuring multiple Cloud Routers in the same region and VPC network, you must also ensure that each BGP session uses a unique link-local /30 subnet from 169.254.0.0/16 and that local Cloud Router ASNs never match any peer ASN configured in that region and network.
us-central1 with ASN 16550 to manage both the Partner Interconnect VLAN attachments and the HA VPN tunnels. Retain public ASN 12345 on the on-premises routers, and configure BGP graceful restart with a 10-second keepalive interval and a 30-second hold timer.This configuration attempts to consolidate Partner Interconnect and HA VPN BGP sessions onto a single Cloud Router assigned ASN 16550, while aggressively tuning BGP timers to a 10-second keepalive and 30-second hold time.
16550) can only manage BGP sessions for other Partner Interconnect VLAN attachments (or, as an exception, Dedicated Interconnect attachments where ASN 16550 is acceptable). It cannot manage BGP sessions for HA VPN tunnels, which require a Cloud Router configured with a private ASN.16550 and private-ASN sessions on the same router.10-second keepalive cannot be matched symmetrically on the Cloud Router side.16550 is acceptable) rather than HA VPN, and the BGP timers were set to 20 seconds (keepalive) and at least 60 seconds (hold time).If sub-second or faster link-failure detection is needed without causing maintenance flaps, Bidirectional Forwarding Detection (BFD) should be used alongside standard 20/60 BGP timers rather than lowering the BGP hold timer below 60 seconds.
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