Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your organization operates a multi-VPC architecture across multiple Google Cloud projects. You have a central hub network named hub-vpc (10.0.0.0/16) that is connected via VPC Network Peering to spoke-a-vpc (10.1.0.0/16). You deploy a new custom VPC named spoke-b-vpc (10.2.0.0/16) and configure VPC Network Peering between spoke-b-vpc and hub-vpc.
Workloads running in spoke-b-vpc must directly access backend services running in spoke-a-vpc over private RFC 1918 IP addresses. Currently, network traffic from spoke-b-vpc fails to reach spoke-a-vpc. Furthermore, the ingress firewall rules in spoke-a-vpc only allow traffic originating from 10.1.0.0/16.
How should you resolve the connectivity issue while adhering to Google Cloud networking best practices?
Custom route exchange in VPC Network Peering allows networks to export and import static and dynamic routes (such as routes learned from Cloud Router via BGP) across a direct peering link.
spoke-a-vpc, which currently drop all traffic outside 10.1.0.0/16.hub-vpc hosted a Network Virtual Appliance (NVA) configured with multiple network interfaces (multi-NIC) acting as a Layer 3 router or next-hop gateway between the spokes.
To achieve hub-and-spoke transit routing in Google Cloud without direct peering between every spoke, organizations typically use Network Connectivity Center (NCC) with router appliances or multi-NIC NVAs.
VPC Network Peering allows private RFC 1918 connectivity across distinct Virtual Private Cloud networks without using external IP addresses, VPN gateways, or intermediate network appliances. Traffic remains entirely within Google's software-defined network (Andromeda).
hub-vpc) cannot route traffic between two other peered networks (spoke-a-vpc and spoke-b-vpc). Establishing a direct peering connection between spoke-a-vpc and spoke-b-vpc directly bridges their subnet route tables.spoke-a-vpc to spoke-b-vpc, and another from spoke-b-vpc to spoke-a-vpc—before the peering state moves to ACTIVE.10.2.0.0/16 in spoke-a-vpc and 10.1.0.0/16 in spoke-b-vpc (or broad RFC 1918 ranges) ensures the peer traffic is permitted.Direct peering combined with explicit ingress firewall rules directly resolves the non-transitive routing constraint and firewall denial without adding intermediate routing appliances, operational overhead, or additional network latency.
Cloud NAT (Network Address Translation) is a managed Google Cloud service that enables compute instances without external IP addresses to access the public internet or external destinations securely.
spoke-a-vpc.Workloads in spoke-b-vpc needed outbound internet access to download software packages or security patches without provisioning public IP addresses on each VM instance.
Enabling the export of subnet routes with public IPs allows privately used public IP ranges (PUPI) or external IPv4 ranges configured on subnets to be advertised across a VPC Network Peering connection.
spoke-a-vpc (10.1.0.0/16) and spoke-b-vpc (10.2.0.0/16) utilize standard RFC 1918 private IP addresses, which are shared by default across active peerings.spoke-b-vpc must be explicitly permitted by an ingress allow rule.hub-vpc does not alter the fundamental non-transitive property of VPC peering.The workloads were utilizing publicly routable IP addresses assigned as internal subnet ranges (PUPI) that needed to be advertised across a direct peering link.
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