CLOUD-NETWORK practice question 25 of 30

You are configuring your Google Cloud environment to connect to your on-premises network. Your configuration must be able to reach Cloud Storage APIs…

Full set: 233 questions
You are configuring your Google Cloud environment to connect to your on-premises network. Your configuration must be able to reach Cloud Storage APIs and your Google Kubernetes Engine nodes across your private Cloud Interconnect network. You have already configured a Cloud Router with your Interconnect VLAN attachments. You now need to set up the appropriate router advertisement configuration on the Cloud Router. What should you do?
Answer options
A: Configure the route advertisement to the default setting.
B: On the on-premises router, configure a static route for the storage API virtual IP address which points to the Cloud Router's link-local IP address.
C: Configure the route advertisement to the custom setting, and manually add prefix 199.36.153.8/30 to the list of advertisements. Leave all other options as their default settings.
D: Configure the route advertisement to the custom setting, and manually add prefix 199.36.153.8/30 to the list of advertisements. Advertise all visible subnets to the Cloud Router. Correct answer
Correct Answer:
D. Configure the route advertisement to the custom setting, and manually add prefix 199.36.153.8/30 to the list of advertisements. Advertise all visible subnets to the Cloud Router.
Explanation

To allow on-premises hosts to reach Google APIs privately, you must advertise the specific IP range for restricted.googleapis.com (199.36.153.8/30) from the Cloud Router to your on-premises network. When you switch a Cloud Router's BGP session from default to custom advertisement mode, it stops advertising VPC subnets automatically. Therefore, you must explicitly re-advertise the VPC subnets to maintain connectivity to resources like GKE nodes, in addition to adding the custom IP range for the Google APIs.

Why Incorrect

A: The default setting only advertises VPC subnet ranges and does not include the special IP ranges required for Private Google Access from on-premises. B: Using a static route on-premises is less scalable and manageable than using BGP to dynamically learn the route from the Cloud Router. C: This option correctly adds the Google API prefix but fails to re-advertise the VPC subnets, which would break connectivity to the GKE nodes.

References

- Google Cloud Documentation, "Configuring Private Google Access for on-premises hosts". (https://cloud.google.com/vpc/docs/configure-private-google-access-on-premises). This guide specifies advertising the 199.36.153.8/30 range for restricted.googleapis.com.

- Google Cloud Documentation, "Cloud Router overview", section "Route advertisement". (https://cloud.google.com/network-connectivity/docs/router/concepts/overview#advertisement). It states, "When you customize the advertised routes for a BGP session, you specify which routes that Cloud Router advertises... If you don't customize the routes, Cloud Router advertises its default routes." This implies custom mode requires explicit definition of all desired routes.

Scroll to Top