Private Google Access in GCP - Mini Project: Build & Apply

Enable Private Google Access on a GCP Subnet

📖 Scenario: You are setting up a Virtual Private Cloud (VPC) network in Google Cloud Platform (GCP) for a company. The company wants to ensure that virtual machines (VMs) in a specific subnet can access Google APIs and services without using public IP addresses. This is important for security and compliance.

🎯 Goal: Create a subnet in a VPC network and enable Private Google Access on that subnet so that VMs without external IPs can reach Google services privately.

📋 What You'll Learn

Create a VPC network named my-vpc

Create a subnet named my-subnet in region us-central1 with IP range 10.0.0.0/24

Enable Private Google Access on my-subnet

💡 Why This Matters

🌍 Real World

Many organizations require their cloud resources to access Google services securely without exposing public IPs. Private Google Access allows this by routing traffic internally within Google's network.

💼 Career

Cloud engineers and network administrators often configure Private Google Access to meet security policies and compliance requirements in enterprise environments.

1

Create a VPC network named my-vpc

Write a gcloud command to create a custom-mode VPC network called my-vpc.

GCP

# Use gcloud to create a custom VPC network named my-vpc
# Your code here

Hint

Use gcloud compute networks create with --subnet-mode=custom to create the VPC.

2

Create a subnet named my-subnet in region us-central1 with IP range 10.0.0.0/24

Write a gcloud command to create a subnet called my-subnet in the us-central1 region within the my-vpc network, using the IP range 10.0.0.0/24.

GCP

gcloud compute networks create my-vpc --subnet-mode=custom
# Create subnet my-subnet in us-central1 with IP range 10.0.0.0/24
# Your code here

Hint

Use gcloud compute networks subnets create with the correct network, region, and IP range.

3

Enable Private Google Access on my-subnet

Write a gcloud command to update the subnet my-subnet in us-central1 to enable Private Google Access.

GCP

gcloud compute networks create my-vpc --subnet-mode=custom
gcloud compute networks subnets create my-subnet --network=my-vpc --region=us-central1 --range=10.0.0.0/24
# Enable Private Google Access on my-subnet
# Your code here

Hint

Use gcloud compute networks subnets update with --enable-private-ip-google-access to enable Private Google Access.

4

Verify Private Google Access is enabled on my-subnet

Write a gcloud command to describe the subnet my-subnet in us-central1 and confirm that privateIpGoogleAccess is set to true.

GCP

gcloud compute networks create my-vpc --subnet-mode=custom
gcloud compute networks subnets create my-subnet --network=my-vpc --region=us-central1 --range=10.0.0.0/24
gcloud compute networks subnets update my-subnet --region=us-central1 --enable-private-ip-google-access
# Describe my-subnet to verify Private Google Access
# Your code here

Hint

Use gcloud compute networks subnets describe to check the subnet details.

Practice

1. What is the main purpose of Private Google Access in Google Cloud?

easy

A. Provide a VPN connection between Google Cloud and on-premises networks

B. Allow VMs with only private IPs to access Google APIs without using the public internet

C. Allow external users to access Google Cloud resources securely

D. Enable VMs to have public IP addresses automatically

Solution

1. Step 1: Understand Private Google Access purpose

   It allows virtual machines without public IP addresses to reach Google APIs and services securely.

2. Step 2: Compare options with this purpose

   Only Allow VMs with only private IPs to access Google APIs without using the public internet describes this feature correctly; others describe unrelated features.

3. Final Answer:

   Allow VMs with only private IPs to access Google APIs without using the public internet -> Option B

4. Quick Check:

   Private Google Access = Secure private VM API access [OK]

Hint: Private Google Access = private VM access to Google APIs [OK]

Common Mistakes:

• Confusing Private Google Access with VPN or public IP assignment
• Thinking it allows external user access
• Assuming it provides public IPs automatically

2. Which configuration enables Private Google Access on a subnet in Google Cloud?

easy

A. Set private_ip_google_access = false in the subnet settings

B. Enable firewall rule to allow all traffic

C. Assign a public IP to all VMs in the subnet

D. Set private_ip_google_access = true in the subnet settings

Solution

1. Step 1: Identify the correct subnet setting for Private Google Access

   The subnet must have private_ip_google_access set to true to enable this feature.

2. Step 2: Review options for correctness

   Only Set private_ip_google_access = true in the subnet settings correctly sets private_ip_google_access to true; others disable it or are unrelated.

3. Final Answer:

   Set private_ip_google_access = true in the subnet settings -> Option D

4. Quick Check:

   Enable private_ip_google_access = true [OK]

Hint: Enable private_ip_google_access = true on subnet [OK]

Common Mistakes:

• Setting private_ip_google_access to false
• Thinking public IPs are required
• Confusing firewall rules with Private Google Access

3. Given a VM in a subnet with private_ip_google_access = true and no public IP, what happens when it tries to reach https://storage.googleapis.com?

medium

A. The VM accesses the URL through Private Google Access without using the public internet

B. The VM accesses the URL only if a VPN is configured

C. The VM cannot reach the URL because it has no public IP

D. The VM must use a NAT gateway to reach the URL

Solution

1. Step 1: Understand Private Google Access behavior

   With private_ip_google_access enabled, VMs without public IPs can reach Google APIs like storage.googleapis.com privately.

2. Step 2: Analyze options based on this behavior

   The VM accesses the URL through Private Google Access without using the public internet correctly describes this private access; others incorrectly deny access or require VPN/NAT.

3. Final Answer:

   The VM accesses the URL through Private Google Access without using the public internet -> Option A

4. Quick Check:

   Private IP VM + private_ip_google_access = private API access [OK]

Hint: Private IP VM with private_ip_google_access can reach Google APIs [OK]

Common Mistakes:

• Assuming no access without public IP
• Thinking VPN or NAT is mandatory
• Confusing Private Google Access with general internet access

4. A subnet has private_ip_google_access set to false. A VM without a public IP in this subnet cannot reach Google APIs. What is the best fix?

medium

A. Create a firewall rule to allow all outbound traffic

B. Assign a public IP to the VM

C. Enable private_ip_google_access = true on the subnet

D. Configure a VPN to Google Cloud

Solution

1. Step 1: Identify cause of no access

   Private Google Access is disabled, so private IP VMs cannot reach Google APIs.

2. Step 2: Choose the best fix

   Enabling private_ip_google_access on the subnet allows private IP VMs to access Google APIs without public IPs.

3. Final Answer:

   Enable private_ip_google_access = true on the subnet -> Option C

4. Quick Check:

   Enable private_ip_google_access to fix private VM API access [OK]

Hint: Enable private_ip_google_access = true to fix private VM API access [OK]

Common Mistakes:

• Assigning public IPs unnecessarily
• Adding firewall rules that don't affect Private Google Access
• Thinking VPN is required for Google API access

5. You have two subnets: Subnet A with private_ip_google_access = true and Subnet B with it set to false. A VM in Subnet B without a public IP needs to access Google APIs securely. What is the best approach?

hard

A. Move the VM to Subnet A or enable private_ip_google_access on Subnet B

B. Assign a public IP to the VM in Subnet B

C. Set up a NAT gateway for Subnet B

D. Create a firewall rule allowing access to Google APIs

Solution

1. Step 1: Understand subnet settings impact

   Private Google Access must be enabled on the subnet for private IP VMs to reach Google APIs.

2. Step 2: Evaluate options for secure access

   Moving the VM to Subnet A or enabling private_ip_google_access on Subnet B ensures secure private access without public IPs.

3. Step 3: Consider security and best practice

   Assigning public IPs or NAT gateways exposes the VM to public internet, less secure than Private Google Access.

4. Final Answer:

   Move the VM to Subnet A or enable private_ip_google_access on Subnet B -> Option A

5. Quick Check:

   Enable private_ip_google_access or move VM for secure private API access [OK]

Hint: Enable private_ip_google_access or move VM to subnet with it enabled [OK]

Common Mistakes:

• Assigning public IPs unnecessarily
• Relying on firewall rules alone
• Ignoring subnet configuration for Private Google Access