A court e-filing service image defines CMD, but the Pod template sets container command and args. Which statement is true?
Select an answer to reveal the explanation.
Short Explanation
The image ships a default playlist (ENTRYPOINT/CMD), but the Pod spec is the DJ—command and args override what actually starts. You do not need to rebuild just to tweak startup flags.
Full Explanation
Court e-filing service images define default CMD/ENTRYPOINT, but Pod templates may set container command and args. Those Pod fields override the image defaults for that container: command replaces ENTRYPOINT, and args replace CMD under the usual Docker/Kubernetes mapping. Developers can tweak startup flags for the e-filing process without rebuilding the image—useful for environment-specific server options under city change tickets.
Claiming image CMD always wins is false; the Pod spec takes precedence for the running container. Saying only args from the Pod apply while command is reserved for init containers is incorrect; both fields work on application and init containers. Asserting that overrides require rebuilding because the kubelet cannot change process arguments ignores the override mechanism Kubernetes provides in the Pod API.
Exam caveat: know the ENTRYPOINT/CMD versus command/args mapping; mis-setting command can accidentally drop the image entrypoint binary. CKAD often tests whether you understand overrides without an image rebuild.
Operational check: kubectl get pod -o jsonpath for .spec.containers[*].command and .args; compare with the image config; confirm the process argv in application logs matches the Pod override after a rollout.