A PersistentVolume with reclaimPolicy: Retain is released after its PVC is deleted. What is the state of the PV and the underlying storage?

The PV is immediately deleted and the storage is removed

The PV becomes Available again and can be bound to a new PVC

The PV enters the Released state, and the underlying storage is not deleted automatically

The PV is deleted but the storage is kept

What does a PersistentVolumeClaim (PVC) represent in a Kubernetes cluster?

A configuration object that stores non-sensitive data for a Pod

A storage policy that defines the performance characteristics of a storage tier

A request for storage resources by a user or Pod, specifying size and access modes

A pre-allocated piece of storage that is ready to be mounted into a Pod

A StatefulSet manages a database cluster with three replicas. Each replica must have its own persistent volume that is not shared. The application also requires that the storage be dynamically provisioned. What is the correct way to configure this?

Add a volumeClaimTemplate to the StatefulSet that references a StorageClass

Use emptyDir volumes in the pod template

Create three separate PVCs manually and reference them in the pod template

Use a single PVC and mount it in all replicas

What is the key benefit of using a StatefulSet with persistent storage for a stateful application?

It allows all Pods to share a single, common PersistentVolume for data consistency

It provides a stable network identity and stable, persistent storage for each Pod

It guarantees that Pods are scheduled on the same node to maintain data locality

It automatically replicates data across all Pods to ensure high availability

You have a pod that needs to read a configuration file and also needs a temporary directory for caching. The configuration file is stored in a ConfigMap, and the cache should be cleared when the pod restarts. Which volume configuration should you use?

Mount a configMap volume for the configuration and an emptyDir volume for the cache

Mount a single emptyDir volume for both configuration and cache

Mount a hostPath volume for the configuration and an emptyDir for the cache

Mount a single configMap volume for both configuration and cache

Kubernetes and Cloud Native Associate (KCNA)

Domain 1Objective 5

Storage KCNA Practice Questions (Page 5)

Part of the Kubernetes Fundamentals domain, which accounts for 44% of the KCNA exam. Linux Foundation does not publish an official question count, but from its 90-minute exam (~35–60 total, ~15–26 in this domain), expect 3–4 from this objective — we provide 26 practice questions to prepare you well beyond it. (estimate)

26questions here

6free pages

6concepts

44%of the exam

Questions 21–25

21application · medium
A PersistentVolume with reclaimPolicy: Retain is released after its PVC is deleted. What is the state of the PV and the underlying storage?
Select an answer first
22foundation · easy
What does a PersistentVolumeClaim (PVC) represent in a Kubernetes cluster?
Select an answer first
23application · medium
A StatefulSet manages a database cluster with three replicas. Each replica must have its own persistent volume that is not shared. The application also requires that the storage be dynamically provisioned. What is the correct way to configure this?
Select an answer first
24foundation · easy
What is the key benefit of using a StatefulSet with persistent storage for a stateful application?
Select an answer first
25expert · medium
You have a pod that needs to read a configuration file and also needs a temporary directory for caching. The configuration file is stored in a ConfigMap, and the cache should be cleared when the pod restarts. Which volume configuration should you use?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to KCNA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Linux Foundation. “KCNA” is a trademark of its owner, used for identification only.