Which statement about ConfigMaps is true?

Which statement about ConfigMaps is true?

• A. ConfigMaps provide a centralized location for configuration data on the cluster
• B. ConfigMaps store encrypted secrets
• C. ConfigMaps replace Secrets
• D. ConfigMaps are deprecated

Answer: (A)

ConfigMaps are Kubernetes objects used to store configuration data as key-value pairs that applications running in Pods can consume at runtime. They allow you to decouple configuration from container images, so you can change settings without rebuilding images, typically by mounting the data as files or injecting it as environment variables. They are scoped to a namespace, not cluster-wide, and they store non-sensitive data by default, not encrypted. They do not replace Secrets, and they are not deprecated. The statement that ConfigMaps provide a centralized location for configuration data on the cluster best captures their role: serving as a central store for config data used by workloads. Keep in mind the per-namespace scope, which is an important nuance.

ConfigMaps are Kubernetes objects used to store configuration data as key-value pairs that applications running in Pods can consume at runtime. They allow you to decouple configuration from container images, so you can change settings without rebuilding images, typically by mounting the data as files or injecting it as environment variables. They are scoped to a namespace, not cluster-wide, and they store non-sensitive data by default, not encrypted. They do not replace Secrets, and they are not deprecated.

The statement that ConfigMaps provide a centralized location for configuration data on the cluster best captures their role: serving as a central store for config data used by workloads. Keep in mind the per-namespace scope, which is an important nuance.