Your VPC has default subnets in us‑east1, us‑west4, and europe‑west4. A branch office in Europe connects via HA VPN with a Cloud Router in europe‑west4. To allow the branch to quickly access all VPC resources, what should you do?

Setting the VPC dynamic routing mode to Global is the correct solution because it allows the Cloud Router in europe-west4 to advertise all subnets in the VPC network (including us-east1 and us-west4) to the on-premises network. This ensures that the branch office can access resources across all regions of your VPC without needing additional configuration. Creating custom advertised routes for each subnet would be a manual and less scalable approach, and it's not necessary when Global dynamic routing handles this automatically. Configuring each subnet's VPN connections to use Cloud VPN is incorrect because the VPN connection is already established via HA VPN and Cloud Router; this option suggests creating new, redundant VPNs per subnet, which isn't how Cloud VPN works for inter-regional access within a single VPC. Setting the Cloud Router advertised routes to Global is not a direct configuration option; the scope of advertised routes is primarily controlled by the VPC's dynamic routing mode.