Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Gcve Nsx T Routing Architecture Best Practices

Section: Cloud-native network configuration for compute resources (e.g., Compute Engine, GKE, serverless networking, and Google Cloud VMware Engine)

Your organization is deploying a hybrid architecture connecting an on-premises data center with Google Cloud VMware Engine (GCVE) and native Google Cloud Virtual Private Cloud (VPC) networks hosting Google Kubernetes Engine (GKE) and Compute Engine workloads.

The network team plans to provision dozens of NSX-T segments across multiple application tiers. You need to design the routing topology between VMware Engine, native VPC services, and the on-premises environment to maintain scalable routing, prevent route table exhaustion, and adhere to recommended architectural best practices.

Which set of routing and NSX-T network configurations should you implement?

Allocate contiguous IP address space for NSX-T segments, configure route summarization at the Tier-0 gateway, and apply a route map when redistributing static routes into BGP to prevent 0.0.0.0/0 from being advertised

Connect each NSX-T segment directly to Cloud Interconnect using dedicated VLAN attachments and disable dynamic BGP peering on the Tier-0 gateway

Assign non-contiguous /24 subnets across NSX-T segments, export discrete /32 host routes from the Tier-0 gateway, and redistribute all static default routes into BGP sessions

Establish separate VPC Network Peering connections for each NSX-T segment and configure individual policy-based routes (PBR) on Compute Engine VMs to route VMware traffic

Professional Cloud Architect

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Gcve Nsx T Routing Architecture Best Practices

Section: Cloud-native network configuration for compute resources (e.g., Compute Engine, GKE, serverless networking, and Google Cloud VMware Engine)

Which set of routing and NSX-T network configurations should you implement?

Connect each NSX-T segment directly to Cloud Interconnect using dedicated VLAN attachments and disable dynamic BGP peering on the Tier-0 gateway

Assign non-contiguous /24 subnets across NSX-T segments, export discrete /32 host routes from the Tier-0 gateway, and redistribute all static default routes into BGP sessions

Establish separate VPC Network Peering connections for each NSX-T segment and configure individual policy-based routes (PBR) on Compute Engine VMs to route VMware traffic

Explanations

What this architecture entails

Google Cloud VMware Engine (GCVE) integrates VMware Software-Defined Data Center (SDDC) components—such as NSX-T Data Center—directly with Google Cloud's high-speed software-defined network. Within GCVE, routing between logical segments and the rest of the network is managed hierarchically via Tier-1 and Tier-0 gateways, which peer dynamically using Border Gateway Protocol (BGP) with Cloud Router across private service access.

How it meets the requirements

Contiguous IP address allocation: Assigning contiguous CIDR blocks across NSX-T workload segments allows multiple discrete subnet ranges to be aggregated into broader network prefixes.
Tier-0 route summarization: Summarizing NSX segment routes, NAT IP ranges, and management endpoints at the Tier-0 gateway dramatically reduces the number of route entries exported to Google Cloud. This keeps prefix advertisements well below the regional 250 advertised route limit from VMware Engine to the VPC network.
Route map filtering on redistribution: Applying a route map to block 0.0.0.0/0 during static-to-BGP redistribution prevents an accidental default route override, ensuring predictable routing behavior between on-premises and Google Cloud.

Key advantages and capabilities

Route scale management: Prevents exceeding Cloud Router learned route limits and private cloud route reception limits.
Deterministic traffic engineering: Summarized custom advertisements on Cloud Router ensure clean transit across Cloud Interconnect and Cloud VPN.
Operational hygiene: Eliminates routing loops and unexpected asymmetric blackholing caused by unintended default route leakage.

Why this is optimal

This approach aligns strictly with Google Cloud networking best practices for GCVE, optimizing route table capacity while preserving seamless Layer 3 connectivity across hybrid environments.

View source documentation

Professional Cloud Architect

Gcve Nsx T Routing Architecture Best Practices

Professional Cloud Architect

Gcve Nsx T Routing Architecture Best Practices

What this architecture entails

How it meets the requirements

Key advantages and capabilities

Why this is optimal

Related questions