nerdexam
Google

PROFESSIONAL-CLOUD-DEVELOPER · Question #126

You recently developed an application. You need to call the Cloud Storage API from a Compute Engine instance that doesn't have a public IP address. What should you do?

The correct answer is D. Use Private Google Access. Private Google Access enables VM instances that have only internal (RFC 1918) IP addresses - no external IP - to reach Google APIs and services such as Cloud Storage over Google's internal network without traversing the public internet. It is enabled at the subnet level. Option A

Integrating Google Cloud services

Question

You recently developed an application. You need to call the Cloud Storage API from a Compute Engine instance that doesn't have a public IP address. What should you do?

Options

  • AUse Carrier Peering
  • BUse VPC Network Peering
  • CUse Shared VPC networks
  • DUse Private Google Access

How the community answered

(27 responses)
  • A
    11% (3)
  • B
    7% (2)
  • C
    4% (1)
  • D
    78% (21)

Explanation

Private Google Access enables VM instances that have only internal (RFC 1918) IP addresses - no external IP - to reach Google APIs and services such as Cloud Storage over Google's internal network without traversing the public internet. It is enabled at the subnet level. Option A (Carrier Peering) is used by service providers to connect their networks to Google's edge network, not for VMs accessing Google APIs. Option B (VPC Network Peering) connects two VPC networks together, not VMs to Google APIs. Option C (Shared VPC) shares a VPC across projects for centralized network management but does not by itself enable API access from instances without public IPs.

Topics

#Compute Engine#Cloud Storage#Private Google Access#Networking

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVELOPER Practice