You are responsible for enabling Private Google Access for the virtual machine (VM) instances in your Virtual Private Cloud (VPC) to access Google APIs. All VM instances have only a private IP…

Question

Options

• ADelete the default route in your VPC.
• BDelete the default route in your VPC and configure your on-premises router to advertise 0.0.0.0/0
• CConfigure your on-premises router to advertise 0.0.0.0/0 via Border Gateway Protocol (BGP) with
• DDelete the default route in your VPC and configure your on-premises router to advertise 0.0.0.0/0

• A
  3% (1)
• B
  8% (3)
• C
  14% (5)
• D
  76% (28)

Explanation

The requirements are: (1) VMs use only private IPs, (2) all VM traffic routed to on-premises for scrubbing via Cloud Interconnect, and (3) traffic to Google APIs must stay within the VPC. The solution works as follows: deleting the default route (0.0.0.0/0 via internet gateway) removes direct internet access. The on-premises router then advertises 0.0.0.0/0 via BGP over Cloud Interconnect, making all non-specific traffic route through on-premises for scrubbing. Enabling Private Google Access creates more specific routes for Google API IP ranges (e.g., 199.36.153.8/30 or 199.36.153.4/30) within the VPC. Because these more-specific routes take precedence over the 0.0.0.0/0 BGP-advertised route (longest-prefix match), Google API traffic is handled directly within the VPC without traversing on-premises. Option A would break all outbound connectivity. Option B routes Google API traffic through on-premises too (no Private Google Access routes). Option C leaves the default route in place, creating routing conflicts.

No community discussion yet for this question.