問題文
A custom container deployed to App Service starts, logs that it is listening, and then the platform reports that the site is unavailable. The container listens on a non-default port. Which cause fits?
選択肢
- One of the image's layers is corrupt, so the process starts but fails as soon as it accepts the first request from the platform's health probe
- The port that the platform forwards to does not match the port the container listens on, so requests are sent where nothing is listening
- The always-on setting is disabled, so the container is unloaded between requests and the platform reports it as unavailable while it is being reloaded
- A required application setting is missing, so the container falls back to a default configuration in which it refuses external requests