How would you mount a ConfigMap as a volume in a Pod?

• A. Create a Service and expose endpoints via DNS.
• B. Attach the ConfigMap as a secret to the Pod.
• C. Define a volume of type configMap and mount it into the container at a path; optionally map keys to filenames.
• D. Use a PersistentVolumeClaim to store the ConfigMap.

Answer: (C)

Mounting a ConfigMap as a volume is done by defining a volume of type configMap in the Pod spec and then mounting that volume into the container at a chosen path. Each key in the ConfigMap becomes a file inside that mounted path, with the file’s contents equal to the key’s value, so your application can read its configuration as standard files. You can also refine what appears by mapping specific keys to filenames or selecting a subset of keys using the items field. This approach directly exposes configuration data to the running container in a predictable filesystem layout, which is exactly how a ConfigMap is intended to be used. The other options don’t fit this purpose: a Service is for networking, attaching the ConfigMap as a secret isn’t how ConfigMaps are consumed, and a PersistentVolumeClaim is for persistent storage, not configuration data.