Which two resources can be made immutable to prevent changes after creation?

Which two resources can be made immutable to prevent changes after creation?

• A. ConfigMaps only
• B. Secrets only
• C. ConfigMaps and Secrets
• D. Pods and Services

Answer: (C)

Immutability is about locking down configuration data so it can’t be changed after it’s created, preventing accidental or unauthorized updates to what a workload uses. ConfigMaps and Secrets support an immutable flag; when you set it to true, updates to that object are rejected by the API, so the only way to change the data is to create a new ConfigMap or Secret (often with a new name) and update the consuming resources to reference it. This guarantees that the configuration seen by pods remains stable until you deliberately rotate it. Pods and Services don’t have an immutable setting, and Kubernetes treats them as resources you can modify or recreate as part of regular operations. So the two resources that can be made immutable to prevent changes after creation are ConfigMaps and Secrets.

Immutability is about locking down configuration data so it can’t be changed after it’s created, preventing accidental or unauthorized updates to what a workload uses. ConfigMaps and Secrets support an immutable flag; when you set it to true, updates to that object are rejected by the API, so the only way to change the data is to create a new ConfigMap or Secret (often with a new name) and update the consuming resources to reference it. This guarantees that the configuration seen by pods remains stable until you deliberately rotate it. Pods and Services don’t have an immutable setting, and Kubernetes treats them as resources you can modify or recreate as part of regular operations. So the two resources that can be made immutable to prevent changes after creation are ConfigMaps and Secrets.