A Cloud Run service running your serverless application is unable to connect to an AlloyDB database created with default configurations. You need to troubleshoot and resolve the issue as quickly as…

The correct answer is B. Enable Direct VPC egress for the Cloud Run service, and send traffic directly to a VPC. Cloud Run services use outbound egress to connect to resources. Since AlloyDB is accessible only through private IP (no public endpoint), the Cloud Run service must use Direct VPC egress (via a Serverless VPC Connector) to connect to the VPC network hosting AlloyDB. This…

Submitted by lucia.co· Mar 30, 2026Managing and provisioning cloud solution infrastructure

Question

A Cloud Run service running your serverless application is unable to connect to an AlloyDB database created with default configurations. You need to troubleshoot and resolve the issue as quickly as possible. What should you do?

Options

AVerify that the Cloud Run service and AlloyDB instance are in the same region.
BEnable Direct VPC egress for the Cloud Run service, and send traffic directly to a VPC.
CDisable the default public IP address of the AlloyDB instance, and use the private IP address in
DCreate a Cloud SQL instance, and migrate the AlloyDB database to PostgreSQL on Cloud SQL.

How the community answered

(21 responses)

A
10% (2)
B
76% (16)
C
14% (3)

Explanation

Cloud Run services use outbound egress to connect to resources. Since AlloyDB is accessible only through private IP (no public endpoint), the Cloud Run service must use Direct VPC egress (via a Serverless VPC Connector) to connect to the VPC network hosting AlloyDB. This configuration enables secure, private communication between Cloud Run and AlloyDB.

Topics

#Cloud Run#AlloyDB#Direct VPC egress#private connectivity

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-ARCHITECT Practice