Volumes vs Persistent Volumes in Kubernetes - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a simple emptyDir volume in a pod spec.

Kubernetes

volumes:
  - name: cache-volume
    [1]: {}

Drag options to blanks, or click blank then click option'

AemptyDir

BconfigMap

CpersistentVolumeClaim

DhostPath

Attempts:

3 left

💡 Hint

Common Mistakes

Using persistentVolumeClaim instead of emptyDir for temporary storage.

The emptyDir volume type creates a temporary directory that exists as long as the pod runs.

2fill in blank

medium

Complete the code to reference a PersistentVolumeClaim in a pod volume.

Kubernetes

volumes:
  - name: data-storage
    [1]:
      claimName: my-pvc

Drag options to blanks, or click blank then click option'

AhostPath

BemptyDir

CpersistentVolumeClaim

Dsecret

Attempts:

3 left

💡 Hint

Common Mistakes

Using emptyDir instead of persistentVolumeClaim for persistent storage.

The persistentVolumeClaim volume type links a pod to a PersistentVolumeClaim, which manages persistent storage.

3fill in blank

hard

Fix the error in the PersistentVolumeClaim YAML by completing the missing access mode.

Kubernetes

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-pvc
spec:
  accessModes:
    - [1]
  resources:
    requests:
      storage: 1Gi

Drag options to blanks, or click blank then click option'

AReadWriteMany

BReadWriteOnce

CWriteOnce

DReadOnlyMany

Attempts:

3 left

💡 Hint

Common Mistakes

Using WriteOnce which is not a valid access mode.

ReadWriteOnce is the most common access mode allowing the volume to be mounted as read-write by a single node.

4fill in blank

hard

Fill both blanks to create a pod volume that uses a PersistentVolumeClaim named 'data-pvc' and mounts it at '/data'.

Kubernetes

volumes:
  - name: data-volume
    [1]:
      claimName: data-pvc
containers:
  - name: app
    volumeMounts:
      - name: data-volume
        mountPath: [2]

Drag options to blanks, or click blank then click option'

ApersistentVolumeClaim

B/var/log

C/data

DemptyDir

Attempts:

3 left

💡 Hint

Common Mistakes

Using emptyDir instead of persistentVolumeClaim for persistent storage.

Mounting at wrong path like /var/log.

The volume uses persistentVolumeClaim to link to the claim, and the mount path /data is where the volume is accessible inside the container.

5fill in blank

hard

Fill all three blanks to define a PersistentVolume with 5Gi storage, access mode ReadWriteOnce, and hostPath '/mnt/data'.

Kubernetes

apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv-data
spec:
  capacity:
    storage: [1]
  accessModes:
    - [2]
  hostPath:
    path: [3]

Drag options to blanks, or click blank then click option'

A10Gi

BReadWriteOnce

C/mnt/data

D5Gi

Attempts:

3 left

💡 Hint

Common Mistakes

Using 10Gi instead of 5Gi for storage.

Wrong access mode or hostPath.

The storage capacity is set to 5Gi, the access mode is ReadWriteOnce, and the hostPath points to /mnt/data on the node.

Practice

1. What is the main difference between a Volume and a Persistent Volume in Kubernetes?

easy

A. Volumes are temporary and tied to pod lifecycle; Persistent Volumes are durable and independent.

B. Volumes are used only for databases; Persistent Volumes are for logs.

C. Volumes require manual creation; Persistent Volumes are created automatically.

D. Volumes can be shared across clusters; Persistent Volumes cannot.

Solution

1. Step 1: Understand Volume lifecycle

   Volumes exist only as long as the pod runs, so they are temporary storage tied to pod lifecycle.

2. Step 2: Understand Persistent Volume purpose

   Persistent Volumes exist independently of pods and provide durable storage that remains after pods are deleted.

3. Final Answer:

   Volumes are temporary and tied to pod lifecycle; Persistent Volumes are durable and independent. -> Option A

4. Quick Check:

   Volume lifecycle = temporary, Persistent Volume = durable [OK]

Hint: Remember: Volumes die with pods; Persistent Volumes live beyond pods [OK]

Common Mistakes:

• Thinking Volumes are durable storage
• Confusing Persistent Volumes as pod-specific
• Assuming Volumes can be shared across clusters

2. Which of the following is the correct way to declare a Persistent Volume Claim (PVC) in a pod spec?

easy

A. "volumes:\n - name: mypvc\n persistentVolumeClaim:\n claimName: myclaim"

B. "volumes:\n - name: mypvc\n emptyDir: {}"

C. "volumes:\n - name: mypvc\n hostPath:\n path: /data"

D. "volumes:\n - name: mypvc\n configMap:\n name: myconfig"

Solution

1. Step 1: Identify PVC syntax in pod spec

   Persistent Volume Claims are referenced under volumes with persistentVolumeClaim.claimName.

2. Step 2: Check other volume types

   emptyDir is temporary storage, hostPath mounts host directory, configMap mounts config data, none are PVCs.

3. Final Answer:

   volumes: - name: mypvc persistentVolumeClaim: claimName: myclaim -> Option A

4. Quick Check:

   PVC uses persistentVolumeClaim.claimName [OK]

Hint: PVCs use persistentVolumeClaim with claimName in volumes [OK]

Common Mistakes:

• Using emptyDir or hostPath instead of persistentVolumeClaim
• Missing claimName field
• Confusing configMap with PVC

3. Given this pod spec snippet, what type of storage is being used?

volumes:
  - name: temp-storage
    emptyDir: {}

medium

A. Persistent Volume storage

B. HostPath volume storage

C. Temporary Volume storage tied to pod lifecycle

D. Persistent Volume Claim storage

Solution

1. Step 1: Identify volume type from spec

   The volume uses emptyDir, which is a temporary directory created when the pod starts.

2. Step 2: Understand emptyDir lifecycle

   emptyDir storage is deleted when the pod is removed, so it is temporary and tied to pod lifecycle.

3. Final Answer:

   Temporary Volume storage tied to pod lifecycle -> Option C

4. Quick Check:

   emptyDir = temporary pod storage [OK]

Hint: emptyDir means temporary storage deleted with pod [OK]

Common Mistakes:

• Assuming emptyDir is persistent storage
• Confusing emptyDir with hostPath
• Thinking emptyDir uses Persistent Volume Claims

4. You created a pod with a volume referencing a Persistent Volume Claim, but the pod fails to start with an error about volume not found. What is the most likely cause?

medium

A. The Persistent Volume is deleted automatically when pod is deleted.

B. The pod spec uses emptyDir instead of persistentVolumeClaim.

C. The pod is missing a container image.

D. The Persistent Volume Claim does not exist or is not bound to a Persistent Volume.

Solution

1. Step 1: Analyze error cause

   If the pod cannot find the volume from PVC, likely the PVC does not exist or is not bound to any Persistent Volume.

2. Step 2: Check other options

   Using emptyDir would not cause volume not found error; missing container image causes different error; Persistent Volumes are independent of pods.

3. Final Answer:

   The Persistent Volume Claim does not exist or is not bound to a Persistent Volume. -> Option D

4. Quick Check:

   Volume not found = missing or unbound PVC [OK]

Hint: Check PVC existence and binding if volume not found error occurs [OK]

Common Mistakes:

• Assuming emptyDir causes volume not found
• Ignoring PVC binding status
• Confusing pod image errors with volume errors

5. You want to ensure data stored by your pod remains even if the pod is deleted and recreated. Which combination should you use?

hard

A. Use a Volume with emptyDir in the pod spec.

B. Use a Persistent Volume with a Persistent Volume Claim referenced in the pod spec.

C. Use a hostPath volume pointing to a temporary directory.

D. Use a ConfigMap volume to store data files.

Solution

1. Step 1: Identify storage durability requirement

   Data must persist beyond pod lifecycle, so temporary volumes like emptyDir or hostPath to temp dirs won't work.

2. Step 2: Choose correct storage type

   Persistent Volumes with PVCs provide durable storage independent of pods, ensuring data remains after pod deletion.

3. Final Answer:

   Use a Persistent Volume with a Persistent Volume Claim referenced in the pod spec. -> Option B

4. Quick Check:

   Persistent Volume + PVC = durable storage [OK]

Hint: For durable data, always use Persistent Volume with PVC [OK]

Common Mistakes:

• Using emptyDir for persistent data
• Using hostPath to temporary directories
• Confusing ConfigMap with storage for data