Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your company is deploying a distributed, replicated database workload onto a Google Kubernetes Engine (GKE) cluster.
The database architecture has the following operational requirements:
db-0, db-1) that persists across restarts and rescheduling.Which Kubernetes workload resource and configuration should you deploy?
A Job in Kubernetes is a controller designed for batch processing and finite computational tasks. It creates one or more Pods, tracks their execution, and ensures a specified number of them terminate successfully with an exit code of zero.
The goal was to run a one-time database schema migration script or nightly batch export job that terminates upon completion.
A DaemonSet is a Kubernetes workload controller that ensures all (or some selected) nodes run exactly one copy of a Pod. It is typically used for cluster-level background utilities such as log collectors and monitoring agents.
emptyDir volume is tied directly to the lifecycle of the Pod and its hosting node. When the Pod is restarted, terminated, or evicted, all data stored in the emptyDir volume is permanently deleted, violating persistence requirements.emptyDir are strictly temporary and non-persistent.The requirement was to deploy node-level log forwarding daemons (such as Fluentd) or node monitoring metrics exporters across every node in the cluster.
A StatefulSet is the Kubernetes workload controller designed specifically for stateful applications requiring unique, persistent identities and dedicated persistent storage. When paired with volumeClaimTemplates and a headless Service (a ClusterIP Service with clusterIP: None), Kubernetes manages the deployment and scaling of a set of Pods, providing guarantees about ordering and uniqueness.
db-0, db-1). When linked to a headless Service, Kubernetes creates dedicated DNS A/AAAA records for each individual Pod (e.g., db-0.db-service.default.svc.cluster.local), allowing direct addressing between database replicas.volumeClaimTemplates field automatically creates a distinct PersistentVolumeClaim (PVC) for each Pod ordinal (e.g., data-db-0, data-db-1). When a Pod restarts or moves to another node, Kubernetes reattaches the exact same volume to the recreated Pod.name-0, name-1, etc.) critical for clustered database master/replica discovery.Alternative controllers like Deployments treat Pods as ephemeral and interchangeable, sharing or losing storage mappings across pod replacements. StatefulSets are purpose-built to satisfy both storage persistence and network stability requirements simultaneously.
A Deployment is a declarative Kubernetes controller optimized for stateless workloads. It manages the lifecycle of Pods via ReplicaSets, treating all Pods as interchangeable, disposable entities without persistent identities.
db-7d4b96966f-k9x2w). If a Pod crashes or restarts, it is replaced by a newly named Pod with a different IP address and hostname, breaking cluster peer discovery.ReadWriteOnce access mode, preventing multiple Pods on different nodes from attaching to it simultaneously.volumeClaimTemplates.The workload were a stateless web frontend or API service where Pods share no local state and can be routed to arbitrarily through a single load-balanced ClusterIP.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated