What are two ways a container in a Pod can consume ConfigMap data? (Choose two.)

Question

Options

• AMounted as a Persistent Volume Claim (PVC)
• BFrom Read-only files
• CFrom Read-write files
• DFrom Environment variables
• EContainers do not consume ConfigMap data

• A
  4% (2)
• B
  87% (45)
• C
  8% (4)
• E
  2% (1)

Explanation

ConfigMaps can be consumed by containers in two primary ways: mounted as read-only files in the container's filesystem (option B), or injected as environment variables (option D) - both are core Kubernetes patterns for externalizing configuration. Option A is wrong because ConfigMaps are not Persistent Volume Claims; PVCs are for durable storage backed by a volume plugin, while ConfigMap volumes are ephemeral and config-focused. Option C is wrong because ConfigMap-mounted files are read-only by design - Kubernetes enforces this to prevent containers from mutating shared config. Option E is simply false; consuming ConfigMaps is one of the most common patterns in Kubernetes workloads.

Memory tip: Think "FE" - Files and Environment - the two clean, read-only ways to feed config into a container without hardcoding it into the image.

No community discussion yet for this question.