Q: 1

A microservice running on Cloud Run needs to connect to an external on-premises database via a Dedicated Interconnect connection. What is the required networking configuration for the Cloud Run service?

Options

Discussion

PreciseLead6118 Oct 6, 2026 9:27 pm

C. encountered exactly similar question in my exam and this is the setup needed for Cloud Run to reach on-prem over Interconnect.

Anita Oct 16, 2026 3:17 pm

D, not C

RobinN Sep 28, 2026 1:04 pm

Maybe D, but only if the on-prem DB had a public IP instead of being accessed over Interconnect using private IPs. Otherwise C feels right for this scenario.

Robin Y. Oct 5, 2026 8:41 am

D. saw a similar question pop up in some practice sets.

MayaM Oct 2, 2026 4:15 pm

Option C is the right pick, not D. Assigning an external IP (option D) seems tempting but doesn't enable private connectivity to on-prem via Interconnect-that's what Serverless VPC Access does. I see folks mix that up a lot in practice.

HelpfulArchitect5127 Sep 30, 2026 5:43 pm

Probably C since Serverless VPC Access is needed for Cloud Run to hit internal IPs over Interconnect. Assigning an external IP (D) doesn't help with on-prem private resources, that's a common trap here. I think this lines up with how Google expects you to connect hybrid workloads, but happy for any corrections.

Daniel R. Sep 30, 2026 4:15 am

C/D? D is tempting but only works for public IPs, not private over Interconnect. C is correct in this context.

Zoe Oct 3, 2026 5:35 pm

Nah, D seems like a trap since assigning an external IP won't help Cloud Run reach on-prem private IPs over Interconnect. C is what you need for private connectivity. Anyone disagree?

Adam S. Sep 30, 2026 11:58 am

I'd say D makes sense here. If you assign an external IP to the Cloud Run service, it should be able to connect out to external resources like an on-prem database, assuming firewall rules allow it. I remember seeing a similar setup in a practice set, so I think D works, but open to other ideas if I'm missing a detail.

Rowan H. Oct 14, 2026 5:53 pm

C vs D? Not totally confident, but pretty sure C is right since Serverless VPC Access is usually needed for private connections back to on-prem. D doesn't really let Cloud Run reach internal IPs over Interconnect, if I'm remembering this right.

Be respectful. No spam.

Correct Answer:

Explanation

Cloud Run services, by default, run in a serverless environment isolated from your Virtual Private Cloud (VPC) network. To enable a Cloud Run service to send egress traffic to resources with internal IP addresses, such as an on-premises database connected via Cloud Interconnect, you must configure a Serverless VPC Access connector. This connector acts as a bridge, allowing the Cloud Run service to route traffic into the specified VPC. Since the Dedicated Interconnect links the on-premises network to this same VPC, the Cloud Run service can then reach the database through the connector and the interconnect.

Why Incorrect

A. Allow unauthenticated access on the Cloud Run service: This setting controls ingress (inbound) traffic to the service, determining who can invoke it. It has no effect on egress (outbound) connectivity from the service to a database.

B. Switch the Cloud Run service to run on a Compute Engine VM instead: This is an architectural change, not a configuration for the existing Cloud Run service. The question asks how to configure the Cloud Run service, not how to replace it.

D. Assign an external IP address to the Cloud Run service: An external IP address is for routing egress traffic to the public internet. The on-premises database is on a private network, accessible only via the private Dedicated Interconnect link, not the public internet.

References

1. Google Cloud Documentation, "Connecting to a VPC network": This document explicitly states: "To connect a Cloud Run service to resources in your VPC network, you need to set up Serverless VPC Access. You can send requests to your VPC network and receive the corresponding responses. This includes connecting to... on-premises resources connected to your VPC network using Cloud VPN or Cloud Interconnect."

Source: Google Cloud Documentation, Cloud Run > Networking > Connecting to a VPC network.

2. Google Cloud Documentation, "Serverless VPC Access overview": This page explains the core function: "Serverless VPC Access enables you to connect directly to your VPC network from serverless environments such as Cloud Run... By using Serverless VPC Access, you can access your Compute Engine VM instances, Cloud Memorystore instances, and any other resources with an internal IP address."

Source: Google Cloud Documentation, Serverless VPC Access > Overview.

3. Google Cloud Documentation, "Dedicated Interconnect overview": This document clarifies that Cloud Interconnect extends your on-premises network to your Google Cloud VPC network. "Dedicated Interconnect provides a direct physical connection between your on-premises network and Google's network." This confirms the on-premises database is reachable from within the VPC.

Source: Google Cloud Documentation, Cloud Interconnect > Dedicated Interconnect > Overview.

A microservice running on Cloud Run needs to connect to an external on-premises database via a Dedicated Interconnect connection. What is the required networking configuration for the Cloud Run service?

Premium Access Includes