You have an application running on Compute Engine that uses BigQuery to generate some results that are stored in Cloud Storage. You want to ensure that none of the application instances have…

Question

Options

• AEnable Private Google Access on all the subnets.
• BEnable Private Google Access on the VPC.
• CEnable Private Services Access on the VPC.
• DCreate network peering between your VPC and BigQuery.
• ECreate a Cloud NAT, and route the application traffic via NAT gateway.

• A
  71% (46)
• B
  5% (3)
• C
  17% (11)
• D
  8% (5)

Explanation

When VM instances have no external IP addresses, they cannot reach Google APIs (BigQuery, Cloud Storage) or the public internet by default. Two solutions address this: (A) Private Google Access, enabled per subnet, allows VMs without external IPs to reach Google APIs and services (such as BigQuery and Cloud Storage) using internal Google routing - no external IP or NAT needed for Google services. (E) Cloud NAT provides outbound internet connectivity for instances without external IPs, covering any remaining internet-bound traffic. Together they ensure full reachability without exposing instances externally. Option B is incorrect because Private Google Access is a subnet-level setting, not a VPC-level toggle. Option C (Private Services Access) is for connecting to managed services via VPC peering, not for Google API access. Option D is incorrect because VPC Network Peering is not applicable to BigQuery, which is a serverless service rather than a peered VPC resource.

No community discussion yet for this question.