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 manages a VPC network (prod-vpc) with subnets in us-central1 and us-east4 that must connect to an on-premises data center (ASN 64500). Your design must meet these requirements:
us-central1 to advertise and receive routes across all VPC regions.us-east4 as a secondary encrypted path.30 seconds and enable graceful restart on-premises.Which configuration should you implement?
prod-vpc dynamic routing mode to global. Create a single Cloud Router in us-central1 (ASN 16550) with --keepalive-interval=30 to manage both the us-central1 Partner Interconnect VLAN attachment and the us-east4 HA VPN tunnels. Configure matching --md5-authentication-key values on the Cloud Router BGP peers and on-premises routers, and enable graceful restart on-premises.This configuration enables global dynamic routing mode and sets valid timers and MD5 authentication, but it attempts to use a single Cloud Router in us-central1 with ASN 16550 to manage both a us-central1 Partner Interconnect attachment and us-east4 HA VPN tunnels.
us-central1 can only manage BGP sessions for connectivity resources (VLAN attachments or HA VPN tunnels) located in us-central1; it cannot attach to an HA VPN gateway in us-east4.16550: A Cloud Router must use the same ASN for all of its BGP sessions. Because Partner Interconnect requires ASN 16550, a Cloud Router using ASN 16550 can only manage BGP sessions for Partner Interconnect VLAN attachments (or Dedicated Interconnect attachments where 16550 is acceptable)—it cannot manage HA VPN BGP sessions.global dynamic routing mode on a VPC allows regional Cloud Routers to exchange routes with all VPC regions, but it does not make a Cloud Router itself global.16550.This option would be valid if a second Cloud Router were created in us-east4 using a private ASN (such as 65001) to manage the us-east4 HA VPN tunnels independently from the us-central1 Partner Interconnect Cloud Router.
prod-vpc dynamic routing mode to regional. Create a Cloud Router in us-central1 (ASN 65001) for Partner Interconnect and a Cloud Router in us-east4 (ASN 65002) for HA VPN, both with --keepalive-interval=30. Configure matching --md5-authentication-key values on all Cloud Router BGP peers and on-premises routers, and enable graceful restart on-premises.This configuration leaves the VPC network in regional dynamic routing mode while attempting to use private Autonomous System Numbers (ASNs) for both a Partner Interconnect Cloud Router and an HA VPN Cloud Router, alongside valid 30-second keepalive timers and MD5 authentication.
16550 on the associated Cloud Router. Assigning private ASN 65001 prevents the Partner Interconnect BGP session from being provisioned or established.prod-vpc in regional dynamic routing mode restricts each Cloud Router to advertising only local-region subnets and installing learned on-premises routes only within its own region. Consequently, the us-central1 Partner Interconnect attachment cannot advertise us-east4 subnets or propagate learned routes to us-east4.64512–65534 and 4200000000–4294967294) apply to HA VPN, Dedicated Interconnect, and Router appliances, whereas Partner Interconnect mandates ASN 16550.--keepalive-interval=30 and configuring matching MD5 authentication keys are valid practices, but they cannot overcome the ASN mismatch or regional routing boundary.This approach would be valid if prod-vpc were switched to global dynamic routing mode and the us-central1 Cloud Router used ASN 16550 for Partner Interconnect (or if us-central1 used Dedicated Interconnect instead of Partner Interconnect and global routing were enabled).
prod-vpc dynamic routing mode to global. Create a Cloud Router in us-central1 (ASN 16550) for Partner Interconnect and a Cloud Router in us-east4 (ASN 16550) for HA VPN, both with --keepalive-interval=10. Configure matching --md5-authentication-key values on all Cloud Router BGP peers and on-premises routers, and enable graceful restart on-premises.This option correctly enables global dynamic routing mode and places regional Cloud Routers in us-central1 and us-east4, but it assigns ASN 16550 to the HA VPN Cloud Router and specifies a 10-second BGP keepalive interval.
64512–65534 or 4200000000–4294967294) for HA VPN tunnels. ASN 16550 is a Google-owned public ASN specifically mandated for Partner Interconnect (and optionally accepted for Dedicated Interconnect), not for HA VPN.--keepalive-interval to integer values between 20 and 60 seconds inclusive (with a default of 20 seconds). Specifying --keepalive-interval=10 is rejected by the API and gcloud CLI.20 seconds are not supported on Cloud Router.20–60 second BGP keepalive range, Bidirectional Forwarding Detection (BFD) must be enabled in single-hop mode rather than lowering the BGP keepalive timer below 20 seconds.This option would be valid if the us-east4 HA VPN Cloud Router used an unused private ASN (such as 65001) and both Cloud Routers used --keepalive-interval=30 (within the 20–60 second range) as required.
prod-vpc dynamic routing mode to global. Create a Cloud Router in us-central1 (ASN 16550) for Partner Interconnect and a separate Cloud Router in us-east4 (ASN 65001) for HA VPN, both with --keepalive-interval=30. Configure matching --md5-authentication-key values on the Cloud Router BGP peers and on-premises routers, and enable graceful restart on-premises.This configuration deploys two regional Cloud Router instances within a global dynamic routing VPC network to manage exterior Border Gateway Protocol (eBGP) sessions across Partner Interconnect and HA VPN, adhering to product-specific ASN, timer, and MD5 authentication rules.
prod-vpc to global dynamic routing mode ensures the us-central1 Cloud Router advertises both us-central1 and us-east4 subnet ranges to the on-premises router and propagates learned on-premises routes to all VPC regions.16550 on the us-central1 Cloud Router, whereas HA VPN requires a private ASN (64512–65534 or 4200000000–4294967294), such as 65001, on the us-east4 Cloud Router.--keepalive-interval=30 falls within Cloud Router's supported 20–60 second range. Enabling graceful restart on the on-premises routers preserves data-plane forwarding during Cloud Router software task restarts as long as BGP re-establishes within the restart window.--md5-authentication-key secrets on Cloud Router BGP peers and the on-premises peers verifies every TCP segment exchanged over the eBGP sessions.Unlike designs that keep regional routing, reuse ASN 16550 on HA VPN, specify out-of-range timers, or attempt to span regions with a single Cloud Router, this topology satisfies every Google Cloud BGP constraint while delivering deterministic global hybrid reachability.
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