☁️ Free practice test question from: KCNA (KCNA)

ConfigMaps are specifically designed to store non-sensitive configuration data in key-value pairs. They are ideal for separating configuration from application code and managing environment-specific settings.

******

A) Secret - Secrets are similar to ConfigMaps but are specifically intended for sensitive data. While they're encoded in base64 by default (not encrypted), Kubernetes treats them differently with more restrictive access controls. Since you specified that your configuration values are non-sensitive, using Secrets would be unnecessary and could make your configuration harder to debug.

B) env - This isn't actually a Kubernetes resource. While you can define environment variables directly in your Pod or Deployment specs using the "env" field, this approach hardcodes configuration into your deployment manifests, making it difficult to manage different environments and requiring redeployment for any configuration changes.

C) Volume - Volumes in Kubernetes are primarily for data persistence and sharing between containers. While you could use a Volume to mount configuration files, this would be unnecessarily complex for simple configuration values. Volumes are more appropriate for larger files, databases, or situations where you need shared access to data.