Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
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?
This approach attempts to establish independent VPC Network Peering connections directly to individual NSX-T segments and relies on manual policy-based routes (PBR) configured on individual Compute Engine VM instances.
You were steering specific diagnostic traffic through a localized third-party Network Virtual Appliance (NVA) inside a standard VPC rather than establishing native GCVE-to-VPC routing.
This design attempts to map individual NSX-T segments directly to external Cloud Interconnect VLAN attachments (Dedicated or Partner Interconnect) while disabling dynamic BGP peering on the GCVE Tier-0 gateway.
You were configuring direct physical interfaces on bare-metal hardware in an on-premises data center without network virtualization abstractions like NSX-T.
This configuration assigns fragmented, non-contiguous IP blocks across logical segments, announces specific /32 host routes across BGP from the Tier-0 gateway, and redistributes static default routes (0.0.0.0/0) into the dynamic routing domain without filtering.
/32 routes and non-contiguous /24 subnets quickly exceeds the maximum quota of 250 unique routes that a private cloud can advertise to a VPC network in a region.0.0.0.0/0 into BGP without a filtering route map can override internet or on-premises egress paths, leading to severe network misdirection.You had a specialized requirement to steer traffic to individual virtual machines based on individual host IPs and had fewer than a dozen total workloads without any risk of exceeding Cloud Router prefix thresholds.
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.
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.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.
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