An autonomous vehicle engineering company is migrating its real-time telemetry processing … — Google Cloud Professional Cloud Architect

An autonomous vehicle engineering company is migrating its real-time telemetry processing platform to Google Cloud. The infrastructure design requires hybrid network connectivity between their primary on-premises processing facility and a central Hub VPC in Google Cloud, which is connected to separate Spoke VPCs for analytics and long-term storage. The architecture must satisfy two core requirements:

1. Sustained throughput of $20\text{ Gbps}$ with direct, low-latency private connectivity between the on-premises data center and Google Cloud.
2. Workloads in the Spoke VPCs must be able to reach on-premises endpoints and communicate with each other through the Hub VPC without establishing direct VPC Network Peering links between individual spokes.

Which TWO architectural decisions must be implemented to fulfill these requirements? (Select TWO)

Provision a Dedicated Interconnect connection pair with VLAN attachments associated with Cloud Routers in the Hub VPC using BGP for dynamic route propagation.Answer
B
Deploy a High Availability (HA) VPN gateway cluster with multiple parallel IPsec tunnels using Equal-Cost Multi-Path (ECMP) routing to aggregate bandwidth up to $20\text{ Gbps}$ .
Utilize Network Connectivity Center (NCC) with Cloud Router hybrid spokes to manage transit routing through the Hub VPC, overcoming standard VPC Peering non-transitivity.Answer
D
Configure standard VPC Network Peering between the Hub VPC and each Spoke VPC to allow Spoke workloads to transitively reach on-premises networks through the Hub VPC's gateway.

Answer

The correct architecture requires provisioning Dedicated Interconnect with Cloud Routers for high-throughput (

20\text{ Gbps}

) hybrid connectivity, combined with Network Connectivity Center (NCC) to enable transitive spoke-to-hub-to-on-premises traffic routing.

Provisioning Dedicated Interconnect satisfies the high throughput demand (

20\text{ Gbps}

) via dedicated physical links and Cloud Router dynamic routing. Using Network Connectivity Center (NCC) solves the transit routing challenge by allowing the Hub VPC to route traffic between Spoke VPCs and on-premises networks, overcoming VPC Peering transitivity restrictions.

Step-by-Step Solution

Evaluate hybrid connectivity throughput requirement (

20\text{ Gbps}

Identify that Cloud VPN is limited to

3\text{ Gbps}

per tunnel. Throughput exceeding

10\text{ Gbps}

mandates Dedicated Interconnect (using 10 Gbps or 100 Gbps circuits).

Dedicated Interconnect provides private physical connectivity to Google's network capable of handling multi-gigabit sustained telemetry traffic with SLAs.

Evaluate spoke-to-hub transit routing requirements.

Identify that default VPC Network Peering is non-transitive and cannot route traffic from Spoke VPC to Hub VPC to On-Premises.

Google Cloud VPC Peering does not export routes learned from external BGP/Interconnect to other peered VPCs without transit routing architectures such as Network Connectivity Center (NCC).

Combine solutions to form valid architecture.

Select Dedicated Interconnect with Cloud Router BGP and Network Connectivity Center (NCC) hub-and-spoke transit management.

This combination satisfies both the physical connectivity throughput threshold and the logical transit routing requirements.

Key Concept

Hybrid Connectivity Selection and VPC Transitivity Limitations

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics