Question 720 of 1,000
hardMultiple ChoiceObjective-mapped

Troubleshooting Serverless VPC Access to Cloud SQL in a Peered VPC | Google PCNE

This PCNE practice question tests your understanding of pcne exam topics. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

You are using Serverless VPC Access to connect Cloud Run services to a VPC network. The connector is in us-central1 with a /28 subnet. You have a Cloud SQL instance (private IP) in the same region but in a different VPC network (peered). The Cloud Run service cannot reach the Cloud SQL instance. What is the most likely cause?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

Quick Answer

The answer is that the VPC connector's subnet does not have a route to the peered VPC where Cloud SQL resides. This is the most likely cause because Serverless VPC Access routes all outbound traffic from Cloud Run through the connector’s VPC, but peering does not automatically propagate routes—the connector’s subnet must have an explicit route pointing to the Cloud SQL private IP range in the peered VPC. On the Google Professional Cloud Network Engineer exam, this scenario tests your understanding of transitive routing limitations: a VPC connector can only reach resources in its own VPC unless you manually add routes for peered networks. A common trap is assuming that VPC peering alone provides full connectivity, but the connector acts as a gateway and does not inherit peered routes. Remember the memory tip: “Peering is not transitive—if the connector can’t see it, you must route it.”

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

The VPC connector's subnet does not have a route to the peered VPC where Cloud SQL resides.

Serverless VPC Access routes traffic from Cloud Run through the connector's VPC. If the Cloud SQL instance is in a different VPC (even if peered), the connector's VPC must have a route to the peered VPC's subnet for the Cloud SQL private IP range. Since the connector's subnet is in us-central1 with a /28, it may not have such a route automatically. Option A is incorrect because Cloud SQL Proxy is not required for private IP access; it is needed for public IP or IAM-based access. Option B is incorrect because Private Google Access is used for accessing Google APIs, not for connectivity to a peered VPC. Option C is incorrect because Cloud SQL with private IP does not require an external IP; it is accessible within the VPC or through peering.

Key principle: Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • The Cloud SQL instance must have the Cloud SQL Proxy configured.

    Why it's wrong here

    Cloud SQL Proxy is for IAM authentication, not for connectivity.

  • Serverless VPC Access requires Private Google Access to be enabled on the connector's subnet.

    Why it's wrong here

    Private Google Access is for Google APIs, not for Cloud SQL private IP.

  • Cloud SQL requires an external IP for Serverless VPC Access connectivity.

    Why it's wrong here

    Cloud SQL can be accessed via private IP.

  • The VPC connector's subnet does not have a route to the peered VPC where Cloud SQL resides.

    Why this is correct

    VPC peering does not automatically propagate routes; you must configure custom route exchange or create routes.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    CIDR notation defines the prefix length.

Common exam traps

Common exam trap: usable hosts are not the same as total addresses

Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.

Detailed technical explanation

How to think about this question

Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.

KKey Concepts to Remember

  • CIDR notation defines the prefix length.
  • Block size helps identify subnet boundaries.
  • Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
  • The required host count determines the smallest suitable subnet.

TExam Day Tips

  • Write the block size before choosing the subnet.
  • Check whether the question asks for hosts, subnets or a specific address range.
  • Do not confuse /24, /25, /26 and /27 host counts.

Key takeaway

Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

Visual reference

192.168.1.0 /24 256 addresses (254 usable) 192.168.1.0 /25 Subnet A 128 addr (126 usable) 192.168.1.128 /25 Subnet B 128 addr (126 usable) Borrowing 1 bit from host portion creates 2 subnets (/25)

Quick reference

Cloud Service Model Comparison

ModelYou ManageProvider ManagesExamples
IaaSOS, runtime, apps, dataHardware, hypervisor, networkingEC2, Azure VMs, GCP Compute Engine
PaaSApps and dataOS, runtime, middleware, hardwareElastic Beanstalk, Azure App Service
SaaSData and settings onlyEverything elseMicrosoft 365, Salesforce, Workday
FaaS / ServerlessFunction code onlyInfra, scaling, runtimeLambda, Azure Functions, Cloud Run
CaaSContainers and appsKubernetes, OS, hardwareEKS, AKS, GKE

What to study next

Got this wrong? Here's your next step.

Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related PCNE subnetting questions on CIDR, address ranges, and subnet selection.

Related practice questions

Related PCNE practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PCNE practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PCNE question test?

CIDR notation defines the prefix length.

What is the correct answer to this question?

The correct answer is: The VPC connector's subnet does not have a route to the peered VPC where Cloud SQL resides. — Serverless VPC Access routes traffic from Cloud Run through the connector's VPC. If the Cloud SQL instance is in a different VPC (even if peered), the connector's VPC must have a route to the peered VPC's subnet for the Cloud SQL private IP range. Since the connector's subnet is in us-central1 with a /28, it may not have such a route automatically. Option A is incorrect because Cloud SQL Proxy is not required for private IP access; it is needed for public IP or IAM-based access. Option B is incorrect because Private Google Access is used for accessing Google APIs, not for connectivity to a peered VPC. Option C is incorrect because Cloud SQL with private IP does not require an external IP; it is accessible within the VPC or through peering.

What should I do if I get this PCNE question wrong?

Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related PCNE subnetting questions on CIDR, address ranges, and subnet selection.

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

What is the key concept behind this question?

CIDR notation defines the prefix length.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More PCNE practice questions

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This PCNE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCNE exam.