Storage

Storage Quiz

Quiz

Question 1 of 31 (0 answered)

Question 1

What happens to data stored in a pod’s local filesystem when the pod is deleted?

The data is automatically backed up to a PersistentVolume The data is lost permanently The data is transferred to the next pod that uses the same name The data is stored in the node’s /var/lib/kubernetes directory

✓

Correct!

By default, pod storage is ephemeral. When a pod is deleted, all data stored in its local filesystem is lost. This is why persistent storage solutions like PersistentVolumes are needed for stateful applications.

✗

Incorrect

Think about the ephemeral nature of pods in Kubernetes.

Question 2

An emptyDir volume survives pod deletion and can be reused by a new pod.

True False

✓

Correct!

An emptyDir volume is created when a pod is assigned to a node and exists only as long as that pod is running. It is deleted when the pod is removed. However, it does survive container restarts within the same pod.

✗

Incorrect

Consider the lifecycle relationship between emptyDir and the pod.

Question 3

Which of the following are valid use cases for emptyDir volumes?

Sharing data between multiple containers in the same pod Storing database data that must persist across pod restarts Temporary cache or scratch space Sharing configuration files across multiple pods Temporary storage for computational tasks

✓

Correct!

emptyDir is ideal for temporary, ephemeral storage needs: sharing data between containers in a pod, caching, and scratch space. It’s NOT suitable for persistent data (databases) or sharing across multiple pods.

✗

Incorrect

Remember that emptyDir is ephemeral and pod-scoped.

Question 4

Given this emptyDir configuration, what happens if the pod tries to write 2Gi of data?

volumes:
- name: cache
  emptyDir:
    sizeLimit: 1Gi

What will this code output?

The data is automatically compressed to fit The pod is evicted or the write operation fails The sizeLimit is automatically increased The data overwrites older cached data

✓

Correct!

When an emptyDir volume exceeds its sizeLimit, the pod may be evicted or the write operation will fail. The sizeLimit acts as a hard constraint to prevent runaway storage usage.

✗

Incorrect

When an emptyDir volume exceeds its sizeLimit, the pod may be evicted or the write operation will fail. The sizeLimit acts as a hard constraint to prevent runaway storage usage.

Consider what happens when a resource limit is exceeded in Kubernetes.

Question 5

What is the primary security concern with using hostPath volumes?

They consume too much network bandwidth They provide direct access to the host node’s filesystem They cannot be encrypted They don’t support ReadWriteMany access mode

✓

Correct!

hostPath volumes mount directories from the host node’s filesystem directly into the pod. This creates a security risk as it gives containers direct access to the host system, potentially allowing access to sensitive files or system directories.

✗

Incorrect

Think about what ‘hostPath’ means - accessing the host’s files.

Question 6

In a hostPath volume configuration, the type: ___ ensures the path exists as a directory before mounting.

✓

Correct!

The type: Directory validation ensures that the specified path exists on the host and is actually a directory before the volume is mounted. Other types include File, FileOrCreate, DirectoryOrCreate, and Socket.

✗

Incorrect

It’s a type that validates the path is a folder structure.

Question 7

Arrange these steps in the correct order for the PV-PVC binding process:

Drag to arrange from first to last step

⋮⋮ User creates PersistentVolumeClaim

⋮⋮ Administrator creates PersistentVolume

⋮⋮ Kubernetes matches and binds PVC to PV

⋮⋮ Pod references PVC in its volume configuration

⋮⋮ Pod can now read/write to persistent storage

✓

Correct!

The PV-PVC workflow: First, an admin provisions a PV. Then, a user requests storage via PVC. Kubernetes automatically binds the PVC to a suitable PV. The pod references the PVC name, and finally the pod can use the storage.

✗

Incorrect

Question 8

A pod needs persistent storage that can be mounted by multiple pods across different nodes simultaneously for read and write operations. Which access mode is required?

ReadWriteOnce (RWO) ReadOnlyMany (ROX) ReadWriteMany (RWX) ReadWriteOncePod (RWOP)

✓

Correct!

ReadWriteMany (RWX) allows the volume to be mounted by multiple nodes simultaneously with read-write access. This is typically supported by network storage solutions like NFS. RWO only allows one node, ROX is read-only, and RWOP restricts to a single pod.

✗

Incorrect

The requirement is ‘multiple nodes’ AND ‘read-write’.

Question 9

What is the difference between a PersistentVolume (PV) and a PersistentVolumeClaim (PVC)?

PersistentVolume (PV): A cluster-level storage resource provisioned by administrators. It represents actual storage (NFS, EBS, etc.) with specific capacity and access modes.

PersistentVolumeClaim (PVC): A user’s request for storage. It’s like a “storage voucher” that asks for specific storage requirements (size, access mode). Kubernetes binds PVCs to suitable PVs.

Analogy: PV is like a parking spot, PVC is like a parking ticket requesting a spot.

Did you get it right?

✓

Correct!

✗

Incorrect

Question 10

Complete the PVC manifest to request 50Gi of storage:

Fill in the missing storage size

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-pvc
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: ___

Your answer:

✓

Correct!

In Kubernetes resource requests, storage is specified with units like Gi (gibibytes), Mi (mebibytes), etc. The format is a number followed by the unit.

✗

Incorrect

In Kubernetes resource requests, storage is specified with units like Gi (gibibytes), Mi (mebibytes), etc. The format is a number followed by the unit.

Question 11

What problem does StorageClass solve that manual PV provisioning cannot?

StorageClass provides better security encryption StorageClass automatically creates PVs on-demand when PVCs are created StorageClass allows ReadWriteMany access mode StorageClass makes storage faster

✓

Correct!

StorageClass enables dynamic provisioning - when a PVC references a StorageClass, the provisioner automatically creates a matching PV without manual administrator intervention. This solves the scalability problem of manually pre-creating PVs.

✗

Incorrect

Think about the word ‘dynamic’ in dynamic provisioning.

Question 12

Which of the following are components/parameters typically found in a StorageClass definition?

provisioner reclaimPolicy containerPort volumeBindingMode replicas parameters

✓

Correct!

StorageClass includes: provisioner (which CSI driver to use), reclaimPolicy (what happens when PVC is deleted), volumeBindingMode (when to provision), and parameters (provider-specific settings). containerPort and replicas are pod/deployment concepts.

✗

Incorrect

Think about storage-specific configuration, not pod configuration.

Question 13

When a PVC with reclaimPolicy: Retain is deleted, the underlying PersistentVolume and its data are automatically deleted.

True False

✓

Correct!

With reclaimPolicy: Retain, when a PVC is deleted, the PV is NOT automatically deleted. It enters a ‘Released’ state and retains the data, allowing administrators to manually reclaim or backup the data. Kubernetes supports three reclaim policies: (1) Retain — PV is kept in ‘Released’ state after PVC deletion, data preserved, manual cleanup required; (2) Delete — PV and its underlying storage asset are automatically deleted when the PVC is deleted; (3) Recycle (deprecated) — performs a basic scrub (rm -rf) on the volume and makes it available again for a new claim.

✗

Incorrect

What does ‘Retain’ mean in everyday language?

Question 14

A StorageClass has volumeBindingMode: WaitForFirstConsumer. When does the actual storage get provisioned?

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: fast-ssd
provisioner: ebs.csi.aws.com
volumeBindingMode: WaitForFirstConsumer

What will this code output?

Immediately when the PVC is created When the PV is manually created by an administrator When a pod that uses the PVC is scheduled to a node After 5 minutes of the PVC being in Pending state

✓

Correct!

WaitForFirstConsumer delays volume provisioning until a pod using the PVC is scheduled. This ensures the volume is created in the correct availability zone/region where the pod will run, which is especially important for cloud providers with zone-specific storage. Kubernetes supports two volumeBindingMode options: (1) Immediate — PV is provisioned and bound as soon as the PVC is created, regardless of whether any pod will use it (can cause zone mismatch issues in multi-zone clusters); (2) WaitForFirstConsumer — PV provisioning is delayed until a pod using the PVC is scheduled to a node, ensuring the volume is created in the correct zone.

✗

Incorrect

The keyword is ‘FirstConsumer’ - think about when the consumer (pod) appears.

Question 15

What is CSI (Container Storage Interface) and why is it important?

CSI (Container Storage Interface) is a standardized interface that allows Kubernetes to integrate with different storage systems through external plugins called CSI drivers. It decouples storage logic from Kubernetes core, enabling vendors to develop and maintain storage integrations independently without modifying Kubernetes.

Before CSI: Storage plugins were built into Kubernetes (in-tree) — required a Kubernetes release to update.

With CSI: Storage runs as external drivers (out-of-tree) — can be updated independently, works across orchestrators (Kubernetes, Mesos, etc.).

Example: AWS EBS CSI driver (ebs.csi.aws.com) can be updated by AWS without waiting for Kubernetes releases.

Did you get it right?

✓

Correct!

✗

Incorrect

Question 16

In a StatefulSet with volumeClaimTemplates creating 3 replicas, how many PVCs are automatically created?

1 PVC shared by all 3 pods 3 PVCs, one for each pod replica 0 PVCs, you must create them manually 6 PVCs, for redundancy

✓

Correct!

StatefulSet’s volumeClaimTemplates automatically create one unique PVC for each pod replica. For 3 replicas, you get 3 PVCs (e.g., data-mysql-0, data-mysql-1, data-mysql-2), ensuring each pod has its own persistent storage.

✗

Incorrect

StatefulSets are designed for applications where each instance needs its own state.

Question 17

Complete the pod manifest to mount a PVC named ‘app-data’:

Fill in the PVC reference

volumes:
- name: storage
  persistentVolumeClaim:
    claimName: ___

Your answer:

✓

Correct!

To use a PVC in a pod, you reference it under volumes with persistentVolumeClaim.claimName pointing to the PVC’s name. The pod must be in the same namespace as the PVC.

✗

Incorrect

To use a PVC in a pod, you reference it under volumes with persistentVolumeClaim.claimName pointing to the PVC’s name. The pod must be in the same namespace as the PVC.

Question 18

Which storage provisioners would be appropriate for a multi-cloud or on-premise Kubernetes cluster?

kubernetes.io/aws-ebs nfs.io/nfs pd.csi.storage.gke.io local disk.csi.azure.com rook-ceph.rbd.csi.ceph.com

✓

Correct!

NFS, local, and Ceph (via Rook) provisioners are cloud-agnostic and work in on-premise or multi-cloud environments. AWS EBS, GCP Persistent Disk, and Azure Disk are cloud-specific and tied to their respective platforms. Rook-Ceph (rook-ceph.rbd.csi.ceph.com) is a popular open-source distributed storage system that runs entirely within Kubernetes and is commonly used for on-premise clusters.

✗

Incorrect

Which provisioners don’t have cloud provider names in them?

Question 19

What is the primary use case for mounting ConfigMaps and Secrets as volumes instead of using environment variables?

Volumes are more secure than environment variables Files can be updated automatically when ConfigMap/Secret changes, and applications can watch for file changes Volumes use less memory than environment variables Environment variables don’t support binary data

✓

Correct!

When ConfigMaps/Secrets are mounted as volumes, updates to the ConfigMap/Secret are reflected in the mounted files (after a sync period). Applications can watch these files and reload configuration without restarting. Environment variables are only set at container startup.

✗

Incorrect

Think about dynamic configuration updates without restarting pods.

Question 20

Arrange these storage abstractions from lowest (closest to hardware) to highest (closest to application):

Drag from lowest to highest abstraction level

⋮⋮ Physical storage backend (NFS, EBS)

⋮⋮ PersistentVolume (PV)

⋮⋮ StorageClass

⋮⋮ PersistentVolumeClaim (PVC)

⋮⋮ volumeMount in Pod

✓

Correct!

Abstraction layers from lowest to highest: Physical storage → StorageClass (provisioning template) → PersistentVolume (cluster resource) → PersistentVolumeClaim (user request) → volumeMount (application usage). Each layer abstracts complexity from the layer above.

✗

Incorrect

Question 21

A PersistentVolume with accessMode ReadWriteOnce can be mounted by multiple pods as long as they are on the same node.

True False

✓

Correct!

ReadWriteOnce (RWO) means the volume can be mounted as read-write by a single node, not a single pod. Multiple pods on the same node can share a RWO volume. If you need to restrict to a single pod across the entire cluster, use ReadWriteOncePod.

✗

Incorrect

RWO is ‘once per node’, not ‘once per pod’.

Question 22

The ___ for a PV determines what happens to the volume when its PVC is deleted.

✓

Correct!

The reclaimPolicy specifies what should happen to a PersistentVolume when the PersistentVolumeClaim bound to it is deleted. Options are Retain, Delete, or Recycle (deprecated).

✗

Incorrect

The reclaimPolicy specifies what should happen to a PersistentVolume when the PersistentVolumeClaim bound to it is deleted. Options are Retain, Delete, or Recycle (deprecated).

It’s about ‘reclaiming’ storage resources.

Question 23

You need storage for a database in a StatefulSet that must survive pod rescheduling, node failures, and cluster upgrades. Which solution is most appropriate?

emptyDir volume hostPath volume PersistentVolumeClaim with StorageClass ConfigMap volume

✓

Correct!

PersistentVolumeClaim with StorageClass provides true persistent storage that survives pod deletion, node failures, and rescheduling. emptyDir is ephemeral, hostPath is node-specific (data lost if pod moves), and ConfigMap is for configuration, not data storage.

✗

Incorrect

The requirement is survival across pod and node lifecycle events.

Question 24

What happens when this StatefulSet is scaled from 3 to 5 replicas?

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: db
spec:
  replicas: 5
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      storageClassName: fast
      accessModes: ["ReadWriteOnce"]
      resources:
        requests:
          storage: 10Gi

What will this code output?

All 5 pods share the existing 3 PVCs 2 new PVCs are automatically created for the new pods The scaling operation fails until you manually create PVCs The new pods start without any persistent storage

✓

Correct!

When a StatefulSet scales up, Kubernetes automatically creates new PVCs based on the volumeClaimTemplates for the new pods. Scaling from 3 to 5 replicas creates data-db-3 and data-db-4 PVCs. When scaling down, PVCs are retained by default.

✗

Incorrect

StatefulSet volumeClaimTemplates provide automatic PVC management.

Question 25

Explain the concept of ‘dynamic provisioning’ in Kubernetes storage.

Dynamic Provisioning automatically creates PersistentVolumes on-demand when a PVC is created, without manual administrator intervention.

How it works:

User creates PVC referencing a StorageClass
StorageClass’s provisioner (e.g., AWS EBS CSI) is triggered
Provisioner creates actual storage in backend (e.g., EBS volume)
Provisioner creates PV object in Kubernetes
Kubernetes binds PVC to the new PV
Pod can use storage immediately

Benefits:

Scalable: No need to pre-create PVs
Automated: Reduces manual operations
Efficient: Storage created only when needed

vs. Static Provisioning: Admin manually creates PVs, users claim from existing pool.

Did you get it right?

✓

Correct!

✗

Incorrect

Question 26

Which scenarios would benefit from using hostPath volumes despite the security risks?

A logging DaemonSet that needs to read container logs from /var/log A database requiring persistent storage across pod restarts A monitoring agent that needs access to /proc and /sys Sharing configuration files between multiple pods A node problem detector that inspects host system files

✓

Correct!

hostPath is appropriate for system-level pods (typically DaemonSets) that need host access: log collectors reading /var/log, monitoring agents accessing /proc or /sys, and node diagnostics. It’s NOT suitable for application data persistence or cross-pod sharing.

✗

Incorrect

Think about pods that need to inspect or monitor the host node itself.

Question 27

A PVC has been created but remains in ‘Pending’ status. What is the most likely cause?

The pod hasn’t been created yet No PersistentVolume matches the PVC’s requirements (size, access mode, StorageClass) The cluster has run out of CPU resources The namespace quota has been exceeded

✓

Correct!

A PVC stays Pending when Kubernetes cannot find or create a suitable PV. Common reasons: no PV with sufficient capacity, mismatched accessModes, wrong/missing StorageClass, or provisioner failure. Creating a pod is not required for PVC binding.

✗

Incorrect

Think about the PV-PVC matching process.

Question 28

ConfigMaps and Secrets mounted as volumes appear as files in the container’s filesystem.

True False

✓

Correct!

When ConfigMaps and Secrets are mounted as volumes, each key-value pair becomes a file in the mount path. The key becomes the filename and the value becomes the file content. For example, a ConfigMap with key ‘app.conf’ appears as a file named ‘app.conf’ in the mounted directory.

✗

Incorrect

Think about how volume mounting works in general.

Question 29

Complete the StorageClass to enable volume expansion after creation:

Fill in the parameter that allows PVC size increases

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: expandable
provisioner: ebs.csi.aws.com
___: true

Your answer:

✓

Correct!

The allowVolumeExpansion: true field in a StorageClass permits PVCs using that StorageClass to be expanded after creation by editing the PVC’s storage request. Not all storage backends support this feature.

✗

Incorrect

Question 30

What is the purpose of the subPath field in a volumeMount?

It creates a subdirectory in the volume It mounts only a specific file or subdirectory from the volume instead of the entire volume It specifies the path on the container where the volume should be mounted It defines the storage path on the backend system

✓

Correct!

The subPath field allows mounting a specific file or subdirectory from a volume rather than mounting the entire volume root. This is useful when multiple containers need different subdirectories from the same volume, or to avoid mounting over existing directories.

✗

Incorrect

It’s about mounting a ‘sub’ portion of the volume.

Question 31

What are the three reclaim policies for PersistentVolumes and what does each do?

1. Retain (default for manually created PVs):

PV is not deleted when PVC is deleted
Data is preserved
PV status becomes ‘Released’ (not ‘Available’)
Admin must manually clean up and reclaim
Use for: Critical data requiring manual backup

2. Delete (default for dynamic provisioning):

PV and underlying storage are automatically deleted when PVC is deleted
Data is permanently lost
Use for: Temporary data, development environments

3. Recycle (DEPRECATED):

Basic scrub (rm -rf on the volume)
PV becomes available for new claims
No longer recommended; use Delete + dynamic provisioning instead

Did you get it right?

✓

Correct!

✗

Incorrect

Quiz Results

Score

0/0

Accuracy

Right

Wrong

Skipped

Last updated on March 28, 2026

Ingress Configuration Management Quiz