Restrict Cloud Run Access to Specific Service Account
This PCD practice question tests your understanding of integrating google cloud services. 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.
Refer to the exhibit. A developer runs the command and sees that the Cloud Run service is publicly accessible. The security team requires that only authenticated requests from a specific service account in the same project are allowed. What should the developer do to modify the IAM policy?
The correct answer is to update the IAM policy to remove the allUsers member from the roles/run.invoker binding. This is because the allUsers principal grants unrestricted public access to invoke the Cloud Run service, which directly violates the security requirement to restrict cloud run access to a specific service account. By removing that binding, you revoke anonymous invocation rights, and since the target service account already holds the roles/run.viewer role, you only need to ensure it also has roles/run.invoker to authenticate and invoke the service. On the Google Professional Cloud Developer exam, this scenario tests your understanding of IAM role granularity for Cloud Run—specifically that roles/run.invoker controls who can call the service, while roles/run.viewer only allows listing and viewing metadata. A common trap is confusing ingress settings with IAM bindings, but ingress controls network-level access, not identity-based authentication. Remember the mnemonic: “Invoker invokes, Viewer views—remove allUsers, not the viewer.”
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
✓
Update the IAM policy to remove the allUsers member from the roles/run.invoker binding
Option B is correct because modifying the IAM policy to remove the allUsers member from the roles/run.invoker binding revokes public access, ensuring only authenticated requests are allowed. The service account can then be granted the roles/run.invoker role if it does not already have it. Option A adds the service account as an invoker but does not remove the allUsers member, so the service remains publicly accessible. Option C changes ingress settings, which controls network-level access, not IAM authentication; it does not address the requirement for authenticated requests. Option D removes the viewer role and adds the service account to invoker, but it fails to remove the allUsers member, leaving public access intact.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Add a new binding with the service account as the only member of roles/run.invoker
Why it's wrong here
This does not remove the allUsers binding, so public access remains.
✓
Update the IAM policy to remove the allUsers member from the roles/run.invoker binding
Why this is correct
Removing allUsers revokes public access. Then ensure the service account has invoker role.
Related concept
Read the scenario before looking for a memorised answer.
✗
Change the service's ingress settings to "Internal and Cloud Load Balancing"
Why it's wrong here
Ingress settings control network access, not IAM authentication.
✗
Remove the roles/run.viewer binding and add the service account to roles/run.invoker
Why it's wrong here
Removing the viewer role is unnecessary and may remove the ability to view configuration.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
What to study next
Got this wrong? Here's your next step.
Identify which PCD exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Integrating Google Cloud services — This question tests Integrating Google Cloud services — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Update the IAM policy to remove the allUsers member from the roles/run.invoker binding — Option B is correct because modifying the IAM policy to remove the allUsers member from the roles/run.invoker binding revokes public access, ensuring only authenticated requests are allowed. The service account can then be granted the roles/run.invoker role if it does not already have it. Option A adds the service account as an invoker but does not remove the allUsers member, so the service remains publicly accessible. Option C changes ingress settings, which controls network-level access, not IAM authentication; it does not address the requirement for authenticated requests. Option D removes the viewer role and adds the service account to invoker, but it fails to remove the allUsers member, leaving public access intact.
What should I do if I get this PCD question wrong?
Identify which PCD exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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.