A municipal utility team wants every build of its meter-reading API to run the same way on a laptop, in a registry, and later on a managed cluster. Which packaging choice best expresses that cloud-native unit of delivery?
Select an answer to reveal the explanation.
Short Explanation
A container is like a sealed lunchbox for the process: everything it needs travels with it. That portable, isolated bundle is why the same artifact can move from laptop to registry to cluster. Host installs and shared appliances break that portability story.
Full Explanation
Cloud-native delivery treats the process-plus-dependencies bundle as the unit you ship, so environments stay consistent without snowflake host setups. Containers provide isolation and a standard artifact that registries and orchestrators understand. Wiki-driven host installs, multi-app appliances, and ad-hoc binary copies reintroduce environment drift and couple delivery to specific machines.