Advanced
Prepare and test your skills
Advanced
Prepare and test your skills
Global Dynamic Routing for Multiregion Hybrid Ingestion
Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise is designing a hybrid network architecture to ingest high-throughput batch and streaming data from an on-premises data center into analytics workloads deployed across subnets in multiple Google Cloud regions (us-central1 and us-east4). The organization requires a secure, private, and highly resilient connection that does not traverse the public internet, while minimizing operational complexity.
The network design must ensure that on-premises data sources can reach processing backends in all VPC subnets across both regions through dynamic routing without deploying separate physical connections in every region.
Which network architecture and configuration should the team implement?
Explanations
Deploy dedicated physical Cloud Interconnect connections and Cloud Routers in each subnet, and configure the dynamic routing mode to local.
Deploy dedicated physical Cloud Interconnect connections and Cloud Routers in each subnet, and configure the dynamic routing mode to local.
What the option is/does
This option suggests deploying separate physical Dedicated Interconnect cross-connect circuits and Cloud Routers for every individual subnet, while configuring a nonexistent VPC routing mode called "local".
Why it doesn't meet the requirement
- Nonexistent configuration parameter: Google Cloud VPC networks support only
regionalandglobaldynamic routing modes; there is no "local" dynamic routing mode. - Architectural anti-pattern: Cloud Interconnect connections are physical port allocations at colocation facilities linked to VPCs via regional VLAN attachments, not per-subnet physical circuits. Attaching physical circuits to individual subnets is technically incorrect and excessively expensive.
Key characteristics and limitations
- VLAN attachment multiplexing: A single Dedicated Interconnect physical connection supports multiple VLAN attachments that route traffic across multiple VPCs and regions, eliminating the need for per-subnet physical infrastructure.
- VPC-level dynamic routing: Dynamic routing is a VPC-wide setting, not a per-subnet configuration.
This answer would be correct if
Google Cloud supported per-subnet physical circuit attachments and a local routing mode, neither of which exists in GCP networking fundamentals.
Set the VPC network dynamic routing mode to global, deploy Cloud Routers and VLAN attachments in the region associated with the Interconnect colocation facility, and establish BGP sessions to advertise all regional subnets.
Set the VPC network dynamic routing mode to global, deploy Cloud Routers and VLAN attachments in the region associated with the Interconnect colocation facility, and establish BGP sessions to advertise all regional subnets.
What global dynamic routing and Cloud Interconnect are
Cloud Interconnect provides high-capacity, low-latency physical connectivity between an on-premises network and Google Cloud without traversing the public internet. Coupled with Cloud Router and Border Gateway Protocol (BGP), it dynamically exchanges network reachability information between on-premises routers and Virtual Private Cloud (VPC) networks. The VPC dynamic routing mode dictates the regional scope of route advertisements and route propagation across the network.
How it meets the hybrid ingestion requirements
- Multi-region reachability: Setting the VPC dynamic routing mode to
globalallows a Cloud Router located in one region to advertise subnet IP ranges from all regions (us-central1andus-east4) to the on-premises BGP peer. - Private high-throughput ingestion: Deploying Dedicated or Partner Interconnect ensures data streams bypass the public internet, satisfying enterprise throughput, latency, and security constraints.
- Optimized resource footprint: Utilizing global dynamic routing avoids the requirement of provisioning redundant physical circuits or localized Cloud Routers in every single region where workloads reside.
Key advantages and capabilities
- Centralized dynamic route exchange: BGP sessions established over VLAN attachments automatically update forwarding tables when new subnets are added to any region in the VPC.
- Symmetric return routing: On-premises routers learn paths back to all cloud subnets automatically, preventing broken asymmetrical flows for ingestion pipelines.
- Scalable hybrid topology: Supports seamless cross-region expansion for future data lake and data warehouse pipelines without redesigning hybrid interconnects.
Why this is optimal
Global dynamic routing provides end-to-end multi-regional connectivity over localized Cloud Interconnect VLAN attachments, establishing automated, resilient, and manageable networking for multi-region data engineering workflows.
Configure custom static routes on the VPC pointing directly to the Cloud Interconnect physical ports as next hops, and disable Cloud Router BGP sessions.
Configure custom static routes on the VPC pointing directly to the Cloud Interconnect physical ports as next hops, and disable Cloud Router BGP sessions.
What the option is/does
This option attempts to bypass dynamic routing by configuring custom static routes in the VPC network using physical Cloud Interconnect ports as next hops and disabling Border Gateway Protocol (BGP).
Why it doesn't meet the requirement
- Technical invalidity: Cloud Interconnect connections (Dedicated or Partner) strictly require Cloud Router and dynamic BGP sessions over VLAN attachments (
interconnectAttachment). Google Cloud VPC networks do not support defining static routes pointing directly to physical Interconnect port identifiers. - Lack of automated failover: Disabling dynamic routing removes automated route reconvergence, link failure detection, and health status tracking, severely impairing pipeline resilience.
Key characteristics and limitations
- Cloud Interconnect prerequisites: Every VLAN attachment must be associated with a Cloud Router to manage BGP sessions and establish routes.
- Inflexible route distribution: Static routing cannot dynamically react to upstream network topology changes or automated maintenance events in the hybrid path.
This answer would be correct if
Static routing is sometimes used with legacy, policy-based Cloud VPN setups (classic VPN), but it is never supported or valid for Cloud Interconnect topologies.
Set the VPC network dynamic routing mode to regional, deploy a single Cloud Router in us-central1, and rely on default dynamic route propagation to advertise subnets located in us-east4.
Set the VPC network dynamic routing mode to regional, deploy a single Cloud Router in us-central1, and rely on default dynamic route propagation to advertise subnets located in us-east4.
What the option is/does
This option sets the VPC network's dynamic routing mode to regional and attempts to use a Cloud Router located exclusively in us-central1 to advertise all subnets across the entire VPC network to on-premises routers.
Why it doesn't meet the requirement
- Regional dynamic routing limitation: In regional dynamic routing mode, a Cloud Router only advertises subnets that exist in its own local region (
us-central1). Subnets in other regions (such asus-east4) are not advertised to the on-premises network over BGP. - Broken communication for secondary regions: Workloads running data ingestion jobs in
us-east4will be unreachable from the on-premises data center because the on-premises routers will lack route entries forus-east4.
Key characteristics and limitations
- Scope of route advertisement: Regional mode confines dynamic BGP route advertisements and learned dynamic route installation strictly to the Cloud Router's local region.
- Manual route management overhead: To connect to other regions under regional dynamic routing, administrators must either deploy separate Cloud Routers and VLAN attachments in every target region or configure complex custom advertisements.
This answer would be correct if
This architecture would only be appropriate if all data engineering ingestion targets and cloud compute pipelines were strictly confined to a single Google Cloud region without any multi-region requirements.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 1,353 practice questions across all 5 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
AdvancedProfessional Data Engineer
Private Service Connect NAT Subnet Firewall
Networking fundamentals
AdvancedProfessional Data Engineer
PSC NEG with Cloud DNS Inbound Server Policy
Networking fundamentals
AdvancedProfessional Data Engineer
Cloud SQL PostgreSQL WAL Compression
Data replication and failover (e.g., Cloud SQL, Redis clusters)
AdvancedProfessional Data Engineer
Cloud Composer Custom Lineage Inlets Outlets
Processing data
AdvancedProfessional Data Engineer
BigQuery Column-Level Security with AEAD Decryption
Integrating with new data sources
IntermediateProfessional Cloud Architect
Cloud SQL Point-in-Time Recovery
Backup and recovery
Last updated Validated