A containerized permitting API listens on port 8080 inside the container but must reach citizens on 443 outside. What container networking concept solves this?
Select an answer to reveal the explanation.
Short Explanation
Port mapping is the translator between the app's private door (8080) and the public street number citizens dial (443). The process inside still binds where it expects. You just publish the right outside port.
Full Explanation
Port mapping (or service port publishing) exposes an internal container port on a different host or load-balancer port. That lets applications keep familiar listen ports while external clients use standard HTTPS 443. Host affinity, object lifecycle, and archive retrieval do not perform TCP port translation for containers.