A credit-union batch image must always start the same scanner binary, but testers want to override only the folder argument without rebuilding. How should ENTRYPOINT and CMD be assigned?
Select an answer to reveal the explanation.
Short Explanation
ENTRYPOINT is the locked steering wheel—always the same scanner. CMD is the sticky note with the default folder that testers can swap at run time without baking a new image for every path.
Full Explanation
ENTRYPOINT should name the fixed scanner binary the credit-union batch image must always run. CMD should carry the default folder arguments that testers may override at container start without rebuilding. That split keeps the executable contract stable while allowing folder paths to change per test run through host-supplied command arguments or ACI/Container Apps overrides.
Putting the mutable folder path in ENTRYPOINT and leaving CMD empty makes ordinary argument overrides awkward or impossible depending on form, so testers lose the no-rebuild workflow. WORKDIR only sets a directory; EXPOSE only documents ports—neither defines the process nor supplies folder arguments. Baking every folder variant into separate images multiplies registry tags and rebuilds for what should be a runtime parameter.
Exam caveat: with exec-form ENTRYPOINT, CMD (or docker run args) append as arguments. With shell-form ENTRYPOINT, override semantics differ. Prefer exec form for predictable Azure host overrides.
Operational check: start one container with defaults and another with an overridden folder argument; confirm both launch the same scanner binary (inspect Entrypoint) while only the folder argument changes, and verify no new image tag was required.