- A
The PVC is bound to a PV that is still attached to the failed node.
Why wrong: PV attachment is not the issue.
- B
The StorageClass has reclaimPolicy: Delete so the PV was deleted.
Why wrong: If Delete, PV would be gone, not pending.
- C
The PV's claimRef still points to the old PVC UID and is in Released state.
By default, PV has retain policy; claimRef must be removed to reuse.
- D
The StatefulSet's pod management policy prevents reattachment.
Why wrong: Pod management policy does not affect PV binding.
Question 217 of 999
Why Is My PVC Stuck in Pending State After a Node Failure in GKE?
This PCD practice question tests your understanding of deploying applications. 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 deploys a stateful application on GKE using a StatefulSet with PersistentVolumeClaims (PVCs). After a node failure, the pod is rescheduled to another node but the PVC remains in 'Pending' state. What is the most likely reason?
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 PV's claimRef still points to the old PVC UID and is in Released state. This is the most likely reason a PVC gets stuck in Pending after a node failure in GKE because when a node fails, the original PersistentVolume remains bound to the old PVC’s UID via its claimRef, even after the pod is rescheduled. The PV enters a Released state, meaning it cannot automatically rebind to the new PVC created for the replacement pod, leaving the new PVC in Pending until an administrator manually edits the PV to remove the stale claimRef. On the Google Professional Cloud Developer exam, this scenario tests your understanding of how Kubernetes volume lifecycle and binding mechanics interact with node failures—a common trap is assuming the reclaim policy alone (Retain or Delete) resolves the issue, but the real blocker is the orphaned claimRef. Remember the memory tip: “Released PVs are like locked doors—the claimRef is the old key that no longer fits.”
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 PV's claimRef still points to the old PVC UID and is in Released state.
Option C is correct because when a StatefulSet pod is rescheduled after a node failure, the original PersistentVolume (PV) may remain in a 'Released' state if its claimRef still points to the old PersistentVolumeClaim (PVC) UID. The PV cannot be re-bound to the new PVC (which has a different UID) until the claimRef is cleared, causing the PVC to remain 'Pending'. This is a known behavior in Kubernetes where PVs are not automatically recycled for reuse with a new PVC UID.
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.
- ✗
The PVC is bound to a PV that is still attached to the failed node.
Why it's wrong here
PV attachment is not the issue.
- ✗
The StorageClass has reclaimPolicy: Delete so the PV was deleted.
Why it's wrong here
If Delete, PV would be gone, not pending.
- ✓
The PV's claimRef still points to the old PVC UID and is in Released state.
Why this is correct
By default, PV has retain policy; claimRef must be removed to reuse.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The StatefulSet's pod management policy prevents reattachment.
Why it's wrong here
Pod management policy does not affect PV binding.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The key trap is that the PV's claimRef prevents re-binding until it is cleared, leading to a 'Pending' PVC state. This is a known behavior in GKE and Kubernetes, where PVs are not automatically recycled for reuse with a new PVC UID.
Detailed technical explanation
How to think about this question
Under the hood, when a PV is released (e.g., after a PVC deletion or node failure), its status changes to 'Released' and the claimRef retains the old PVC UID. The PV cannot be re-bound to a new PVC with a different UID unless the claimRef is manually removed or the PV is re-created. In real-world scenarios, this often requires a storage administrator to intervene by editing the PV to clear the claimRef, or using a dynamic provisioner with a Retain reclaimPolicy to preserve data but still require manual cleanup.
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.
TExam Day Tips
- 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 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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Deploying applications — study guide chapter
Learn the concepts, then practise the questions
- →
Deploying applications 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?
Deploying applications — This question tests Deploying applications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The PV's claimRef still points to the old PVC UID and is in Released state. — Option C is correct because when a StatefulSet pod is rescheduled after a node failure, the original PersistentVolume (PV) may remain in a 'Released' state if its claimRef still points to the old PersistentVolumeClaim (PVC) UID. The PV cannot be re-bound to the new PVC (which has a different UID) until the claimRef is cleared, causing the PVC to remain 'Pending'. This is a known behavior in Kubernetes where PVs are not automatically recycled for reuse with a new PVC UID.
What should I do if I get this PCD question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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?
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 →
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: Jul 4, 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.