- A
The IAM policy binding granting the Cloud Tasks service account the Cloud Run Invoker role was removed during the deployment.
If the deployment pipeline modifies IAM policies, the binding for the Cloud Tasks service account may have been removed, causing 403 errors.
- B
The new revision has a bug causing a permission denied error when processing tasks.
Why wrong: A bug would result in 500 or 503 errors, not 403, and logs show requests reaching the service.
- C
The Cloud Tasks queue needs to be configured with an OIDC token and audience for the new revision.
Why wrong: OIDC configuration is on the queue and does not need to change per revision; it remains valid for the service URL.
- D
The Cloud Tasks queue's HTTP target URL needs to be updated to point to the new revision's specific URL.
Why wrong: The Cloud Run service URL remains the same across revisions, so the queue target does not need updating.
Fix Cloud Run Permission Denied for Cloud Tasks Invoker — Google Professional Cloud Developer Explained
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.
A company runs a microservices application on Cloud Run. One service, `order-processor`, is invoked asynchronously via a Cloud Tasks queue. The Cloud Tasks queue is configured with an HTTP target pointing to the `order-processor` service URL. The service requires authentication (no unauthenticated invocations). The service account used by Cloud Tasks to invoke the service is `cloud-tasks-system@project.iam.gserviceaccount.com`. After deploying a new revision of `order-processor` using Cloud Build and Cloud Deploy, the team notices that tasks are failing with a 403 status. The Cloud Run service logs show the requests are reaching the service but returning 403. The previous revision worked fine. 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 IAM policy binding granting the Cloud Tasks service account the Cloud Run Invoker role was removed during deployment. This is correct because when a Cloud Run service requires authentication, the invoker—in this case, the `cloud-tasks-system` service account—must have the `roles/run.invoker` role on the specific service. The 403 status indicates the request reached the service but was denied at the IAM level, not the application layer. On the Google Professional Cloud Developer exam, this scenario tests your understanding of how Cloud Deploy and Cloud Build can overwrite existing IAM bindings if the deployment pipeline includes a `gcloud run deploy` command without explicitly preserving the invoker role. A common trap is assuming the error is caused by a misconfigured OIDC token or a broken queue URL, but those would produce different errors. Memory tip: think of the Cloud Tasks service account as a guest needing a key (the invoker role) to enter the Cloud Run door—if the deployment process changes the locks, the guest gets a 403.
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 IAM policy binding granting the Cloud Tasks service account the Cloud Run Invoker role was removed during the deployment.
Option A is correct. When Cloud Run requires authentication, the invoker's service account must be granted the roles/run.invoker role on the Cloud Run service. Deploying a new revision with Cloud Build and Cloud Deploy may overwrite IAM policy bindings if the deployment pipeline includes IAM policy updates or uses a different service account. In this scenario, the IAM binding for the Cloud Tasks service account was likely removed or not applied to the new revision, causing the 403 error. Option B is incorrect because the service works correctly; the 403 is returned before the service processes the request, indicating an authorization failure, not an internal bug. Option C is incorrect because the OIDC token configuration on the queue is independent of the revision and does not affect IAM permissions. Option D is incorrect because the Cloud Tasks queue's HTTP target URL points to the Cloud Run service, not a specific revision, so it does not need to be updated.
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.
- ✓
The IAM policy binding granting the Cloud Tasks service account the Cloud Run Invoker role was removed during the deployment.
Why this is correct
If the deployment pipeline modifies IAM policies, the binding for the Cloud Tasks service account may have been removed, causing 403 errors.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Authentication checks who the user is.
- ✗
The new revision has a bug causing a permission denied error when processing tasks.
Why it's wrong here
A bug would result in 500 or 503 errors, not 403, and logs show requests reaching the service.
- ✗
The Cloud Tasks queue needs to be configured with an OIDC token and audience for the new revision.
Why it's wrong here
OIDC configuration is on the queue and does not need to change per revision; it remains valid for the service URL.
- ✗
The Cloud Tasks queue's HTTP target URL needs to be updated to point to the new revision's specific URL.
Why it's wrong here
The Cloud Run service URL remains the same across revisions, so the queue target does not need updating.
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.
Trap categories for this question
Command / output trap
A bug would result in 500 or 503 errors, not 403, and logs show requests reaching the service.
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 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.
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.
- →
Integrating Google Cloud services — study guide chapter
Learn the concepts, then practise the questions
- →
Integrating Google Cloud services practice questions
Targeted practice on this topic area only
- →
All PCD questions
999 questions across all exam domains
- →
Google Professional Cloud Developer study guide
Full concept coverage aligned to exam objectives
- →
PCD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCD practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Manage a Solution that Can Span Multiple Database Systems practice questions
Practise PCD questions linked to Manage a Solution that Can Span Multiple Database Systems.
Deploy Scalable and Highly Available Databases in Google Cloud practice questions
Practise PCD questions linked to Deploy Scalable and Highly Available Databases in Google Cloud.
Design Scalable and Highly Available Cloud Database Solutions practice questions
Practise PCD questions linked to Design Scalable and Highly Available Cloud Database Solutions.
Migrate Data Solutions practice questions
Practise PCD questions linked to Migrate Data Solutions.
Designing highly scalable, available, and reliable cloud-native applications practice questions
Practise PCD questions linked to Designing highly scalable, available, and reliable cloud-native applications.
Building and testing applications practice questions
Practise PCD questions linked to Building and testing applications.
Deploying applications practice questions
Practise PCD questions linked to Deploying applications.
Integrating Google Cloud services practice questions
Practise PCD questions linked to Integrating Google Cloud services.
Managing application performance monitoring practice questions
Practise PCD questions linked to Managing application performance monitoring.
PCD fundamentals practice questions
Practise PCD questions linked to PCD fundamentals.
PCD scenario practice questions
Practise PCD questions linked to PCD scenario.
PCD troubleshooting practice questions
Practise PCD questions linked to PCD troubleshooting.
Practice this exam
Start a free PCD 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 PCD question test?
Integrating Google Cloud services — This question tests Integrating Google Cloud services — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: The IAM policy binding granting the Cloud Tasks service account the Cloud Run Invoker role was removed during the deployment. — Option A is correct. When Cloud Run requires authentication, the invoker's service account must be granted the roles/run.invoker role on the Cloud Run service. Deploying a new revision with Cloud Build and Cloud Deploy may overwrite IAM policy bindings if the deployment pipeline includes IAM policy updates or uses a different service account. In this scenario, the IAM binding for the Cloud Tasks service account was likely removed or not applied to the new revision, causing the 403 error. Option B is incorrect because the service works correctly; the 403 is returned before the service processes the request, indicating an authorization failure, not an internal bug. Option C is incorrect because the OIDC token configuration on the queue is independent of the revision and does not affect IAM permissions. Option D is incorrect because the Cloud Tasks queue's HTTP target URL points to the Cloud Run service, not a specific revision, so it does not need to be updated.
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.
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?
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 →
Keep practising
More PCD practice questions
- A company is deploying a microservices architecture on GKE. They need to expose a set of related microservices under a s…
- You need to monitor the CPU usage of a Compute Engine instance and trigger an alert when it exceeds 80% for 5 minutes. W…
- A Cloud Bigtable instance has a single cluster. To improve availability and read throughput, the team decides to add a s…
- A developer wants to enable IAM database authentication for Cloud SQL for PostgreSQL. Which IAM role must be granted to…
- A company is using Cloud Bigtable for a time-series workload. They want to monitor performance and identify hot spots. W…
- A company wants to run hybrid transactional/analytical processing (HTAP) workloads on a PostgreSQL-compatible database w…
Last reviewed: Jun 24, 2026
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.