
In default advertisement mode, a Cloud Router announces only the subnet routes of its own VPC network, within the reach of the network's dynamic routing mode. Anything else that on-premises needs to reach has to be added by switching the router to custom advertisement mode. Knowing which ranges fall outside the default set, and how to add them without losing the subnets already advertised, is a recurring hybrid routing topic for the Professional Cloud Network Engineer exam.
Custom mode doesn't require listing every subnet by hand. It still lets you keep the built-in group that advertises all subnets the router can see, and then add custom IP ranges alongside it. Turning off subnet advertisement while adding a custom range leaves your subnets unreachable from on-premises, even though the custom range itself is announced. Which subnets the router can see still depends on the dynamic routing mode, and a router in regional mode sees every subnet in its own region.
A custom advertisement handles only one direction, the path from on-premises toward the advertised range. For peered networks, the return path comes from the peering configuration. The routes a Cloud Router learns from on-premises are dynamic custom routes, and VPC Network Peering doesn't share custom routes unless you turn that on. The network that holds the Cloud Router has to export its custom routes, and the peered network has to import them, before workloads in the peered network can reach on-premises prefixes. Custom route import and export on their own don't make the Cloud Router announce peered subnets toward on-premises, so the two changes work as a pair.
Private services access follows the same pattern, because it connects your VPC network to a Google-managed service producer network through VPC Network Peering. By default that peering doesn't share the dynamic routes your Cloud Router learns from on-premises, so the producer network has no return path to the data center. Turning on custom route export on the peering fixes the return path, and the custom advertisement of the allocated range fixes the forward path. For a Cloud SQL instance reached by on-premises clients with RFC 1918 addresses, no authorized network entries are needed once routing works in both directions.
Advertisement settings can narrow what the peer learns as well as extend it. HA VPN with custom route advertisements can list only approved subnets. In a hub design, a hub Cloud Router in default mode advertises only the hub's own subnets, so routes learned from one spoke aren't passed to another. Avoid adding 0.0.0.0/0 unless the goal is to attract on-premises internet traffic into Google Cloud, because that is what advertising a default route does.
Custom learned routes are a separate feature from custom advertisements. They add routes into the VPC network as if they came from the BGP peer, so they work only in the inbound direction and can't advertise anything to on-premises. Advertisements also need a BGP session to travel over. A Cloud Router in a network that has no VLAN attachments or VPN tunnels has no BGP session to carry advertisements, so the announcement has to come from the Cloud Router that holds the hybrid sessions.
A reliable way to reason through these designs for the Professional Cloud Network Engineer exam is to ask which direction each change affects. Custom advertisements change what on-premises learns. Peering export and import change what peered networks learn. Custom learned routes change what the VPC network learns from the peer side.
Our Professional Cloud Network Engineer practice exams cover custom route advertisements alongside regional and global dynamic routing and VPC Network Peering, with detailed explanations that drill these distinctions.