The correct answer involves enabling a VPC Connector for each Cloud Run service, using service accounts with least privilege, and implementing Direct VPC egress. These three steps ensure secure communication with a VPC network and other Google Cloud services like Cloud Storage and Secret Manager by routing traffic through a private, isolated network path rather than the public internet. On the Google Professional Cloud Developer exam, this scenario tests your understanding of how Cloud Run integrates with VPCs for internal service-to-service calls and resource access, often appearing as a multi-select question where you must distinguish between Cloud Run and GKE-specific tools. A common trap is confusing Cloud Run’s networking with GKE features like internal load balancers or Cloud Service Mesh, which are not directly applicable here. Remember the mnemonic “VPC, SA, DVE” — VPC Connector, Service Accounts, Direct VPC Egress — to recall the three pillars of secure Cloud Run communication.
PCD Deploying applications Practice Question
This PCD practice question tests your understanding of deploying applications. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
A company is deploying a microservices architecture on Google Cloud using Cloud Run. They need to ensure that services can communicate securely with each other and with other Google Cloud services, such as Cloud Storage and Secret Manager. Which three steps should they take? (Choose three.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Cloud Run's direct VPC egress to access resources in a VPC network.
Options A, B, and E are correct. A VPC Connector (option A) enables Cloud Run services to communicate with resources in a VPC network, including internal communication between services if they are within the same VPC. Service accounts with least privilege (option B) ensure secure access to Google Cloud services. Direct VPC egress (option E) allows Cloud Run services to send traffic to a VPC network without a VPC Connector. Option C is incorrect because internal load balancing is not a standard feature for Cloud Run; it is used with GKE. Option D is incorrect because Cloud Service Mesh is primarily for GKE, not Cloud Run (standard Cloud Run does not support sidecar injection).
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Enable Cloud Service Mesh for sidecar proxy injection.
Why it's wrong here
Cloud Service Mesh is for GKE, not Cloud Run.
✗
Configure Cloud Run services to use internal load balancing.
Use Cloud Run's direct VPC egress to access resources in a VPC network.
Why this is correct
Direct VPC egress allows Cloud Run services to send traffic to VPC networks.
Related concept
Authentication checks who the user is.
✓
Use service accounts with least privilege permissions for each service.
Why this is correct
Least privilege service accounts are a security best practice.
Related concept
Authentication checks who the user is.
✓
Enable VPC Connector for each Cloud Run service.
Why this is correct
VPC Connector allows Cloud Run to access VPC resources securely.
Related concept
Authentication checks who the user is.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related PCD questions on access control and AAA configuration.
Deploying applications — This question tests Deploying applications — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Use Cloud Run's direct VPC egress to access resources in a VPC network. — Options A, B, and E are correct. A VPC Connector (option A) enables Cloud Run services to communicate with resources in a VPC network, including internal communication between services if they are within the same VPC. Service accounts with least privilege (option B) ensure secure access to Google Cloud services. Direct VPC egress (option E) allows Cloud Run services to send traffic to a VPC network without a VPC Connector. Option C is incorrect because internal load balancing is not a standard feature for Cloud Run; it is used with GKE. Option D is incorrect because Cloud Service Mesh is primarily for GKE, not Cloud Run (standard Cloud Run does not support sidecar injection).
What should I do if I get this PCD question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related PCD questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
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 →
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.
This PCD 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 PCD exam.
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.
Sign in to join the discussion.