A workload needs its ServiceAccount token, a ConfigMap, and a Secret presented together under one mount path for identity and config. Which volume type fits?
Select an answer to reveal the explanation.
Short Explanation
Projected volumes are the “one binder, three tabs” pattern—token, ConfigMap, and Secret land under one mount. You don’t stash identity files on the node or invent a PVC just to glue sources together.
Full Explanation
Projected volumes let a Pod mount multiple volume sources—such as a ServiceAccount token, ConfigMap, and Secret—as a single directory tree. That pattern supports workload identity and config co-location without hostPath or PVC misuse. emptyDir cannot materialize those API objects by itself.