Many base images default to root. What should a professional Dockerfile for a parks reservation API do before the process starts?
Select an answer to reveal the explanation.
Short Explanation
Running as root inside the container is like leaving the master key in the ignition. Creating a non-root USER and switching to it shrinks the blast radius if the process is compromised.
Full Explanation
Default root in many bases is convenient for installs but unsafe for the long-running process. Professional images create a dedicated user and use the USER instruction so the application does not retain container-root privileges. This is image hygiene, not a full host-hardening or PodSecurity exam topic.