Google ACE Practice Question: Extending its on-premises network to Google Cloud…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Create a static route for the on-premises network on the VPC

  Why it's wrong here

  Creating a static route for the on-premises network on the VPC is incorrect because it bypasses dynamic BGP routing entirely. With HA VPN and Cloud Router, the goal is to exchange routes dynamically via BGP so that changes in on-premises prefixes are automatically propagated. A static route would require manual updates and would not participate in route failover or health-check-based re-advertisement, undermining the purpose of the Cloud Router deployment.

• ✓

  Configure a BGP session on the Cloud Router with the on-premises router's ASN and IP address

  Why this is correct

  Configuring a BGP session on the Cloud Router with the on-premises router's ASN and IP address is the correct step because Cloud Router is a BGP speaker that must peer with the on-premises router over the VPN tunnel. Without explicitly configuring the peer ASN and IP address, the Cloud Router has no way to establish the BGP adjacency, which is essential for dynamically exchanging network routes. This configuration enables automatic route learning and failover, aligning with the requirement to extend the network using BGP.

• ✗

  Assign an external IP address to the Cloud Router

  Why it's wrong here

  Assigning an external IP address to the Cloud Router is wrong because Cloud Router is a regional resource that communicates with on-premises routers using internal IP addresses over the VPN tunnel, not the public internet. The VPN gateway itself holds the external IP address, while Cloud Router only needs the BGP peer IP (the on-premises router's internal or tunnel address). An external IP on Cloud Router is neither required nor supported; it would not affect BGP peering and is irrelevant to route exchange.

• ✗

  Enable the IP forwarding feature on the VPN gateway

  Why it's wrong here

  Enabling the IP forwarding feature on the VPN gateway is not a valid step because Cloud VPN gateway is a managed Google Cloud service that already routes forwarded traffic once the VPN tunnel is established; there is no IP forwarding switch to turn on for the gateway. IP forwarding is a property of Compute Engine instances when they are used as routers or NAT devices, not for VPN gateways. Therefore, this option does not contribute to enabling BGP route exchange and is unnecessary for extending the on-premises network.

Go deeper

Related to this question