A team is designing a storage solution for a microservices application. One service needs to share a configuration file with multiple replicas running on different nodes. The file is read-only and should be updated by the operations team without rebuilding the container image. Which approach should they use?

Create a PersistentVolumeClaim and mount it in the Pods.

Embed the configuration file in the container image.

Create a ConfigMap and mount it as a volume in the Pods.

Use an emptyDir volume and populate it with the configuration file.

A team is deploying a web application that needs persistent storage. The cluster administrator has enabled dynamic provisioning with a default StorageClass. The application requires read-write access from a single node. The team wants to minimize manual intervention. What should they do?

Create a PV manually with the same storage class and then create a PVC that references it.

Create a PVC with storageClassName: '' and accessModes: [ReadWriteOnce].

Create a PVC without specifying a storageClassName and with accessModes: [ReadWriteOnce], then mount it in the Pod.

Create a PVC with accessModes: [ReadWriteMany] and no storageClassName.

What is the lifecycle of a PersistentVolumeClaim (PVC) after it is created and bound to a PersistentVolume (PV)?

The PVC immediately becomes available for use by any Pod in the cluster.

The PVC is automatically deleted when the PV is deleted.

The PVC remains in a Pending state until a Pod mounts it.

The PVC is bound to a PV and can be mounted into Pods that reference it.

What is the primary purpose of a secret volume in a Pod?

To inject sensitive data, such as passwords or tokens, into the Pod as files.

To provide persistent storage that survives Pod deletion.

To store configuration data that can be updated without restarting the Pod.

To provide temporary storage for application data.

Certified Kubernetes Application Developer (CKAD)

Domain 1Objective 4

Utilize Persistent and Ephemeral Volumes CKAD Practice Questions (Page 1)

Part of the Application Design and Build domain, which accounts for 20% of the CKAD exam. Linux Foundation does not publish an official question count, but from its 120-minute exam (~50–80 total, ~10–16 in this domain), expect 3–4 from this objective — we provide 18 practice questions to prepare you well beyond it. (estimate)

18questions here

4free pages

6concepts

20%of the exam

Questions 1–5

1application · easy
A team is designing a storage solution for a microservices application. One service needs to share a configuration file with multiple replicas running on different nodes. The file is read-only and should be updated by the operations team without rebuilding the container image. Which approach should they use?
Select an answer first
2application · medium
A team is deploying a web application that needs persistent storage. The cluster administrator has enabled dynamic provisioning with a default StorageClass. The application requires read-write access from a single node. The team wants to minimize manual intervention. What should they do?
Select an answer first
3foundation · easy
What is the lifecycle of a PersistentVolumeClaim (PVC) after it is created and bound to a PersistentVolume (PV)?
Select an answer first
4foundation · easy
What is the primary purpose of a secret volume in a Pod?
Select an answer first
5foundation · easy
What is the default reclaim policy for a PersistentVolume (PV) when it is created?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CKAD

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. “CKAD” is a trademark of its owner, used for identification only.

Utilize Persistent and Ephemeral Volumes CKAD Practice Questions (Page 1)

Questions 1–5

A team is deploying a web application that needs persistent storage. The cluster administrator has enabled dynamic provisioning with a default StorageClass. The application requires read-write access from a single node. The team wants to minimize manual intervention. What should they do?

What is the lifecycle of a PersistentVolumeClaim (PVC) after it is created and bound to a PersistentVolume (PV)?

What is the primary purpose of a secret volume in a Pod?

What is the default reclaim policy for a PersistentVolume (PV) when it is created?

Keep studying — Application Design and Build