Bird
0
0

What is the main purpose of setting immutable: true in a Kubernetes ConfigMap?

easy📝 Conceptual Q11 of 15
Kubernetes - ConfigMaps
What is the main purpose of setting immutable: true in a Kubernetes ConfigMap?
ATo delete the ConfigMap automatically after use
BTo allow automatic updates to the ConfigMap
CTo encrypt the ConfigMap data
DTo prevent any changes to the ConfigMap after creation
Step-by-Step Solution
Solution:

  1. Step 1: Understand the role of immutable: true

    This setting makes the ConfigMap read-only after creation, preventing accidental or unauthorized changes.

  2. Step 2: Compare with other options

    Options A, B, and D describe behaviors unrelated to immutability: automatic deletion, updates, or encryption are not controlled by this flag.

  3. Final Answer:

    To prevent any changes to the ConfigMap after creation -> Option D

  4. Quick Check:

    Immutable ConfigMap = No changes allowed [OK]
Quick Trick: Immutable means no changes allowed after creation [OK]
Common Mistakes:
  • Thinking immutable allows updates
  • Confusing immutability with encryption
  • Assuming immutable deletes the ConfigMap

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Health Checks and Probes - Startup probe concept - Quiz 12easy Ingress - Path-based routing - Quiz 6medium Ingress - Path-based routing - Quiz 14medium Networking - Pod-to-Pod communication - Quiz 4medium Persistent Storage - Access modes (ReadWriteOnce, ReadOnlyMany, ReadWriteMany) - Quiz 10hard Resource Management - CPU requests and limits - Quiz 4medium Scheduling - Pod affinity and anti-affinity - Quiz 11easy Scheduling - Taints and tolerations - Quiz 3easy Scheduling - Jobs and CronJobs for batch processing - Quiz 13medium Secrets - Base64 encoding in Secrets - Quiz 10hard