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.
A financial services company operates stateful workloads in us-central1 and us-east4 inside a single VPC network (vpc-prod) connected to two on-premises data centers through stateful boundary firewalls. You must design a hybrid connectivity architecture that meets these requirements:
Which architecture should you implement?
us-central1 and us-east4 attached to four separate Cloud Routers. Set vpc-prod to global dynamic routing mode, enable BFD on the attachments, and use ECMP active/active forwarding across all BGP sessions without graceful restart.This design places all four physical Dedicated Interconnect links in a single metropolitan area, uses Dataplane version 1 VLAN attachments with Equal-Cost Multi-Path (ECMP) active/active forwarding across four Cloud Routers, and omits BGP graceful restart.
us-central1 and us-east4 attachments on circuits in a single metro forces cross-region backhaul latency and leaves both regions vulnerable to a metro-wide outage.PRODUCTION_CRITICAL connection group and single-region attachments.The four connections were distributed across two metros (using both EADs per metro), attachments used Dataplane version 2 for BFD, symmetric MEDs enforced active/passive flow symmetry, and BGP graceful restart was enabled on two Cloud Routers.
zone1 in Dallas and zone2 in Ashburn), and deploy HA VPN over Cloud Interconnect using a single encrypted Cloud Router per region for both tiers. Set vpc-prod to global dynamic routing mode, enable BFD on the VLAN attachments for faster VPN tunnel failure detection, and apply active/passive MED values only on the Cloud Router.HA VPN over Cloud Interconnect layers IPsec-encrypted HA VPN tunnels on top of Cloud Interconnect VLAN attachments to provide end-to-end network encryption across private physical links without traversing the public internet.
zone1 and zone2) represented in each metro. Because Google Cloud does not coordinate maintenance across different metros, a single connection per metro cannot guarantee resilience during concurrent maintenance events.--encrypted-interconnect-router) that exchanges only VPN gateway prefixes, and a separate HA VPN Cloud Router that exchanges VPC and on-premises routes. A single Cloud Router cannot serve both tiers.The organization required IPsec encryption over Cloud Interconnect, deployed four connections across two metros and both edge availability domains, separated the Cloud Interconnect and HA VPN Cloud Routers, avoided underlay BFD, and configured symmetric MEDs on both sides.
zone1 and zone2) in each metro, with four Dataplane version 2 VLAN attachments connected to one Cloud Router per region in us-central1 and us-east4. Set vpc-prod to global dynamic routing mode, apply symmetric MED values on both Cloud Router and on-premises BGP peers, and enable BFD and BGP graceful restart.This design implements Google Cloud's 99.99% multi-region Dedicated Interconnect topology combined with global dynamic routing, symmetric active/passive BGP path selection, Dataplane version 2 BFD, and BGP graceful restart.
zone1 and zone2) in each metro—protects against both coordinated intra-metro maintenance and uncoordinated cross-metro maintenance. Mapping four VLAN attachments (two in us-central1 and two in us-east4) to one Cloud Router per region inside a global dynamic routing VPC ensures that every Cloud Router advertises all VPC subnets (giving higher priority to local regional subnets) and propagates learned on-premises prefixes globally across regions if one region fails.Unlike single-metro, two-connection, or Layer 3 Partner Interconnect alternatives, this topology satisfies every Google Cloud 99.99% SLA prerequisite while natively supporting BFD on Dataplane v2, symmetric MED propagation, and graceful restart during task maintenance.
us-central1 and two in us-east4 connected to one Cloud Router per region. Keep vpc-prod in regional dynamic routing mode for local path preference, enable BFD on all attachments, and configure matching active/passive MED values between Cloud Router and the on-premises routers.In a Layer 3 Partner Interconnect deployment, the service provider manages the BGP sessions between their edge routers and Google Cloud Router, while regional dynamic routing mode restricts Cloud Router route advertisements and learned dynamic routes strictly to the Cloud Router's own region.
vpc-prod in regional dynamic routing mode breaks multi-region disaster recovery. In regional mode, a Cloud Router in us-east4 only advertises us-east4 subnets and only installs learned on-premises routes in us-east4. If connectivity in us-central1 fails, us-central1 workloads cannot fail over through us-east4, violating the 99.99% multi-region SLA.You switched to Layer 2 Partner Interconnect (or Dedicated Interconnect) so BGP peers directly with your on-premises routers to exchange MED values, set vpc-prod to global dynamic routing mode, used Dataplane version 2 attachments for BFD, and enabled BGP graceful restart.
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