Which command would you use to inspect a ConfigMap's details?

Which command would you use to inspect a ConfigMap's details?

• A. kubectl delete configmap/colour-configmap
• B. kubectl apply -f configmap.yaml
• C. kubectl describe configmap/colour-configmap
• D. kubectl get pods

Answer: (C)

Inspecting a ConfigMap's details is best done with a command that presents the resource’s full description, including metadata, data keys, and related events. The command kubectl describe configmap/colour-configmap does exactly that: it gives a human-readable view of the ConfigMap, showing its name, namespace, labels, annotations, the data stored inside (the configuration values), and any events related to the resource. This makes it ideal for quickly understanding what the ConfigMap contains and its current state. Other options don’t fit the goal. Deleting the ConfigMap would remove it, not inspect it. Applying a manifest creates or updates resources from a file, not provide a detailed view of an existing ConfigMap. Listing pods shows pod resources, not ConfigMaps. If you need the raw data instead of a human-friendly summary, you could also get the ConfigMap in YAML with a different command, but describe is the quickest way to inspect its details.

Inspecting a ConfigMap's details is best done with a command that presents the resource’s full description, including metadata, data keys, and related events. The command kubectl describe configmap/colour-configmap does exactly that: it gives a human-readable view of the ConfigMap, showing its name, namespace, labels, annotations, the data stored inside (the configuration values), and any events related to the resource. This makes it ideal for quickly understanding what the ConfigMap contains and its current state.

Other options don’t fit the goal. Deleting the ConfigMap would remove it, not inspect it. Applying a manifest creates or updates resources from a file, not provide a detailed view of an existing ConfigMap. Listing pods shows pod resources, not ConfigMaps. If you need the raw data instead of a human-friendly summary, you could also get the ConfigMap in YAML with a different command, but describe is the quickest way to inspect its details.