CLOUD-DIGITAL-LEADER practice question 5 of 35

What are the network requirements for Private Google Access?

Full set: 411 questions
Answer options
A: Private Google Access automatically enables any API.
B: Your network must have appropriate routes for the destination IP ranges used by Google APIs and services. Correct answer
C: Both A and B
D: None of the Above
Correct Answer:
B. Your network must have appropriate routes for the destination IP ranges used by Google APIs and services.
Explanation

Private Google Access only succeeds if the VPC network can reach Google APIs and services over their special private virtual IP ranges (for example 199.36.153.8/30 or 199.36.153.4/30). Therefore the VPC must contain routes whose destinations match those Google API address ranges and whose next hop is the default internet gateway. Without these routes, packets never reach Google. Private Google Access itself does not enable or create APIs; it simply provides a private network path to them.

Why Incorrect

A. Private Google Access is a networking feature; it does not enable or “turn on” any Google API.
C. Incorrect because statement A is wrong, so both cannot be correct.
D. Statement B is true, so “None of the Above” is false.

References

1. Google Cloud documentation, “Configure Private Google Access,” Requirements section, bullet 3: “Your network must have appropriate routes for the destination IP ranges (199.36.153.8/30 or 199.36.153.4/30).” https://cloud.google.com/vpc/docs/configure-private-google-access#requirements

2. Google Cloud documentation, “Private Google Access overview,” “Routing requirements” paragraph. https://cloud.google.com/vpc/docs/private-google-access

3. Google Cloud documentation, “Private Google Access for on-premises hosts,” “Routing to Google APIs” section. https://cloud.google.com/vpc/docs/private-google-access-on-prem#routing

Scroll to Top