Which command mounts config map cm1 as volume myvol into /tmp/config in deployment myapp?

• A. oc set volume deployment/myapp --remove -t configmap -m /tmp/config --name myvol --configmap-name cm1
• B. oc set volume deployment/myapp --add -t secret -m /tmp/config --name myvol --secret-name cm1
• C. oc set volume deployment/myapp --add -t configmap -m /tmp/config --name myvol --configmap-name cm1
• D. oc set volume deployment/otherapp --add -t configmap -m /tmp/config --name myvol --configmap-name cm1

Answer: (C)

To mount a config map as a volume in a deployment, you add a volume of type configmap and create a matching volumeMount in the containers. The correct command specifies the deployment to modify as myapp, uses --add to introduce a new volume, sets the type to configmap, mounts it at /tmp/config, names the volume myvol, and points to the config map cm1. This updates the deployment’s pod template so the containers receive a volume backed by cm1 and mounted at /tmp/config.

Using --remove would delete a volume, not mount one. Using -t secret would attach a secret instead of a config map. Targeting a different deployment would apply the changes to the wrong app.