The correct approach is to delete a pod and verify the new pod has the same data from the PersistentVolumeClaim. This works because StatefulSets assign each pod a stable identity and a dedicated PVC that survives pod deletion; when Kubernetes reschedules the replacement pod, it reattaches the same PVC, ensuring the PersistentVolume retains all original data. On the Google Professional Cloud Developer exam, this scenario tests your understanding of how StatefulSets guarantee sticky storage for stateful workloads, often appearing as a distractor where candidates mistakenly scale down replicas or drain nodes—actions that alter cluster state rather than validating pod-level persistence. A common trap is assuming pod rescheduling requires node failure, but simply deleting the pod isolates the persistence test cleanly. Memory tip: think of a StatefulSet pod as a named pet with its own food bowl (PVC)—even if the pet is temporarily removed, the bowl and its contents stay for the replacement.
PCD Building and testing applications Practice Question
This PCD practice question tests your understanding of building and testing applications. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 team deploys a stateful application on GKE using StatefulSets. They need to test data persistence after pod rescheduling. Which test scenario best validates this?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Delete a pod and verify the new pod has the same data from PersistentVolumeClaim
Option B is correct because deleting a pod in a StatefulSet triggers Kubernetes to reschedule a new pod with the same identity and PersistentVolumeClaim (PVC). The PVC retains the data from the original pod, so verifying that the new pod has the same data directly confirms that the PersistentVolume (PV) is correctly bound and the data persists across pod rescheduling. This tests the core persistence guarantee of StatefulSets without altering the replica count or cluster state.
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.
✗
Use a CronJob to regularly snapshot the data
Why it's wrong here
Snapshots test backup, not data persistence during pod rescheduling.
✓
Delete a pod and verify the new pod has the same data from PersistentVolumeClaim
Why this is correct
This directly tests the scenario of pod rescheduling and PVC data persistence.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Scale down the StatefulSet to 0 and scale up again, then check data
Why it's wrong here
This tests data persistence across scaling events but may not simulate pod failure as intended.
✗
Delete the entire cluster and recreate it from backups
Why it's wrong here
This is a disaster recovery test, not a test of normal pod rescheduling.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that scaling down to 0 and up is equivalent to pod rescheduling, but the trap here is that scaling down releases PVCs (depending on the volumeClaimTemplate policy) and may not preserve data if the StatefulSet is configured with a non-default PVC retention policy, whereas deleting a single pod always reuses the same PVC.
Detailed technical explanation
How to think about this question
StatefulSets use a unique pod identity (e.g., pod-name-0) and a corresponding PVC template that creates a dedicated PersistentVolume per replica. When a pod is deleted, the StatefulSet controller recreates the pod with the same name and reuses the existing PVC, which is bound to the original PV. The PV’s reclaim policy (typically Retain for StatefulSets) ensures data survives pod deletion. In real-world scenarios, this validates that the storage backend (e.g., GCE Persistent Disk) correctly maintains data even if the pod is rescheduled to a different node.
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 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 exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Building and testing applications — This question tests Building and testing applications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Delete a pod and verify the new pod has the same data from PersistentVolumeClaim — Option B is correct because deleting a pod in a StatefulSet triggers Kubernetes to reschedule a new pod with the same identity and PersistentVolumeClaim (PVC). The PVC retains the data from the original pod, so verifying that the new pod has the same data directly confirms that the PersistentVolume (PV) is correctly bound and the data persists across pod rescheduling. This tests the core persistence guarantee of StatefulSets without altering the replica count or cluster state.
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: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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.