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 interconnecting a Google Cloud VPC spanning us-central1 (primary) and us-east4 (secondary) with another cloud service provider (CSP). Your design must meet these requirements:
us-central1, use us-east4 strictly as a standby failover path, and maintain symmetric flows for stateful firewalls.Which architecture and BGP configuration should you implement?
us-central1 and us-east4 on a VPC with global dynamic routing, configure HA VPN over Cloud Interconnect allowing only VPN traffic, enable BGP MD5 authentication and graceful restart, and set equal lower MED values in us-central1 and equal higher MED values in us-east4 on both Cloud Routers and the peer CSP routers.HA VPN over Cross-Cloud Interconnect combines dedicated, high-speed Layer 2 physical connectivity between Google Cloud and another cloud provider with IPsec-encrypted HA VPN tunnels layered directly over the private VLAN attachments. Rather than exposing unencrypted traffic on the private interconnect, the underlying interconnect links are restricted to carrying only encrypted HA VPN traffic.
us-central1 and us-east4 and global dynamic routing mode, satisfies the topology requirements for a 99.99% uptime SLA and automatic cross-region failover.100) to both us-central1 sessions enables Equal-Cost Multi-Path (ECMP) active/active load balancing in the primary region. Assigning equal higher MED values (such as 200) to both us-east4 sessions on both the Cloud Router and peer CSP router sides keeps us-east4 as an active/passive standby and prevents asymmetric routing across stateful firewalls.Unlike standalone MACsec (which stops at Google's edge) or public-internet VPNs (which lack deterministic private transport SLAs), this design delivers carrier-grade 99.99% availability, end-to-end IPsec confidentiality, authenticated BGP peering, and deterministic symmetric failover.
us-central1 and us-east4 on a VPC with regional dynamic routing, configure HA VPN over Cloud Interconnect, enable BFD and MD5 authentication on the VPN BGP sessions, and configure a higher MED value in us-east4 solely on the Cloud Router.This option combines HA VPN over Cross-Cloud Interconnect with regional dynamic routing mode, BFD on VPN BGP sessions, and a one-sided MED adjustment on the Google Cloud side to influence failover.
us-central1 fails, us-east4 cannot route traffic to us-central1 workloads, violating the 99.99% multi-region SLA requirement.us-east4 solely on the Cloud Router only alters inbound path preference from the remote CSP into Google Cloud (or vice versa, depending on advertisement direction). Without configuring matching higher MED values on both the Cloud Router and the external CSP router, outbound and inbound flows can take different regions, breaking stateful firewall inspection.There is no scenario where this configuration is valid as written, because global dynamic routing is mandatory for multi-region failover, BFD is unsupported on Cloud VPN BGP sessions, and symmetric active/passive routing requires matching MED policies on both sides.
us-central1 with MACsec as a Network Connectivity Center (NCC) hybrid spoke, add a public-internet HA VPN gateway in us-east4 as a second NCC hybrid spoke, and advertise identical prefixes with equal MEDs across both spokes for ECMP.Network Connectivity Center (NCC) uses a central hub to connect hybrid spokes—such as Cloud Interconnect VLAN attachments, Cloud VPN gateways, and third-party Router appliances—so external networks can exchange routes with VPC spokes through a unified management plane.
us-east4 from operating as a strict standby path.The workload did not require end-to-end IPsec over the interconnect, accepted a 99.9% interconnect SLA backed by an active/passive (higher-MED) internet VPN backup rather than equal-cost ECMP across mixed spokes, and did not mandate BGP MD5 authentication.
us-central1 and us-east4 on a VPC with global dynamic routing, enable MACsec on all links without HA VPN, enable BFD and BGP graceful restart, and advertise identical MED values across all four BGP sessions for global ECMP.MACsec for Cloud Interconnect provides IEEE 802.1AE Layer 2 link-level encryption specifically between a customer or peer provider's edge router and Google's edge router. Pairing it with identical MED values across all regional BGP sessions and Bidirectional Forwarding Detection (BFD) instructs routers to load-balance traffic across all paths simultaneously while detecting physical or logical link failures rapidly.
us-central1 and us-east4 creates multi-region ECMP rather than designating us-east4 strictly as a standby failover path, increasing the risk of flow asymmetry across stateful inspection firewalls.The organization only needed Layer 2 link encryption to Google's peering edge, did not require end-to-end IPsec or BGP MD5 authentication, and wanted active/active traffic distribution across both regions without strict regional standby behavior.
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