- A
Deployment with pod affinity rules
Why wrong: Deployments create Pods with random names — they don't provide stable identities or ordered startup/shutdown.
- B
StatefulSet with a headless Service
StatefulSets provide stable Pod names (pod-0, pod-1...), stable DNS via headless Services, ordered deployment, and PVC retention across restarts — the standard choice for stateful clustered applications.
- C
DaemonSet with a unique hostname label on each node
Why wrong: DaemonSets run one Pod per node — they don't provide ordered startup or the stable identity semantics required by distributed databases.
- D
ReplicaSet with a fixed replica count
Why wrong: ReplicaSets maintain a fixed count of Pods but assign random names and don't guarantee ordering or stable network identities.
When to Use StatefulSet for Persistent Pod Identity
This ACE practice question tests your understanding of ace exam topics. 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 distributed database running on GKE requires stable, persistent hostnames (pod-0, pod-1, pod-2) and ordered startup/shutdown for proper cluster initialization. Pods must retain their identity across restarts. Which Kubernetes resource is designed for this?
Quick Answer
The answer is StatefulSet with a headless Service, as this Kubernetes resource is specifically designed to provide stable, persistent hostnames for pods in GKE. StatefulSet guarantees that each pod receives a unique, ordinal-based identity (e.g., pod-0, pod-1, pod-2) that remains fixed across rescheduling and restarts, while the headless Service exposes these individual hostnames as DNS records rather than load-balancing traffic. On the Google Associate Cloud Engineer exam, this question tests your understanding of workload identity requirements—a common trap is choosing a Deployment, which creates ephemeral, random pod names and lacks ordered startup/shutdown. The exam scenario often involves distributed databases like Cassandra or ZooKeeper that rely on consistent hostnames for cluster initialization. Remember the memory tip: “StatefulSet gives pods names that stick, like a permanent nametag, while a headless Service lets you call them by name.”
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
StatefulSet with a headless Service
StatefulSet is the correct resource because it provides stable, unique network identifiers (e.g., pod-0, pod-1, pod-2) via a headless Service, ordered startup and shutdown (pod-0 starts first, pod-2 terminates first), and persistent pod identity that survives restarts. These features are essential for distributed databases like Cassandra or ZooKeeper that require consistent hostnames and initialization order.
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.
- ✗
Deployment with pod affinity rules
Why it's wrong here
Deployments create Pods with random names — they don't provide stable identities or ordered startup/shutdown.
- ✓
StatefulSet with a headless Service
Why this is correct
StatefulSets provide stable Pod names (pod-0, pod-1...), stable DNS via headless Services, ordered deployment, and PVC retention across restarts — the standard choice for stateful clustered applications.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
DaemonSet with a unique hostname label on each node
Why it's wrong here
DaemonSets run one Pod per node — they don't provide ordered startup or the stable identity semantics required by distributed databases.
- ✗
ReplicaSet with a fixed replica count
Why it's wrong here
ReplicaSets maintain a fixed count of Pods but assign random names and don't guarantee ordering or stable network identities.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that a Deployment with a fixed number of replicas can provide stable identities, but Deployments treat pods as interchangeable and do not preserve hostnames or startup order, making StatefulSet the only correct choice for stateful workloads requiring persistent identity.
Detailed technical explanation
How to think about this question
Under the hood, a StatefulSet uses a headless Service (clusterIP: None) to create DNS records for each pod in the format <statefulset-name>-<ordinal>.<service-name>.<namespace>.svc.cluster.local, enabling direct pod-to-pod communication. The ordinal index (0, 1, 2) is stored in the pod's hostname and subdomain, and the StatefulSet controller ensures that pods are created or deleted in strict ordinal order (e.g., pod-0 must be Running before pod-1 starts), which is critical for quorum-based databases like etcd or MongoDB replica sets.
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.
Related practice questions
Related ACE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Configuring Access and Security practice questions
Practise ACE questions linked to Configuring Access and Security.
Planning and Configuring a Cloud Solution practice questions
Practise ACE questions linked to Planning and Configuring a Cloud Solution.
Ensuring Successful Operation of a Cloud Solution practice questions
Practise ACE questions linked to Ensuring Successful Operation of a Cloud Solution.
Deploying and Implementing a Cloud Solution practice questions
Practise ACE questions linked to Deploying and Implementing a Cloud Solution.
Setting Up a Cloud Solution Environment practice questions
Practise ACE questions linked to Setting Up a Cloud Solution Environment.
ACE fundamentals practice questions
Practise ACE questions linked to ACE fundamentals.
ACE scenario practice questions
Practise ACE questions linked to ACE scenario.
ACE troubleshooting practice questions
Practise ACE questions linked to ACE troubleshooting.
Practice this exam
Start a free ACE 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 ACE question test?
Read the scenario before looking for a memorised answer.
What is the correct answer to this question?
The correct answer is: StatefulSet with a headless Service — StatefulSet is the correct resource because it provides stable, unique network identifiers (e.g., pod-0, pod-1, pod-2) via a headless Service, ordered startup and shutdown (pod-0 starts first, pod-2 terminates first), and persistent pod identity that survives restarts. These features are essential for distributed databases like Cassandra or ZooKeeper that require consistent hostnames and initialization order.
What should I do if I get this ACE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 ACE practice questions
- A team's Cloud Build pipeline must: (1) run unit tests, (2) build a Docker image only if tests pass, (3) push the image…
- A team needs a database backup job to run every day at 2 AM UTC. The job calls an HTTP endpoint to trigger the backup. T…
- A team wants to receive an email alert when the average CPU utilization of VMs in a managed instance group exceeds 80% f…
- A Go service is consuming significantly more CPU than expected. The team suspects an inefficient function but doesn't kn…
- A network team is creating a new VPC and must decide between auto mode and custom mode. Why would they choose custom mod…
- A company organizes its GCP projects by business unit — Finance, Engineering, and Sales. Which resource is best suited t…
Last reviewed: Jun 30, 2026
This ACE 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 ACE 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.