問題文
A team declares three process types for a Heroku app: web, worker, and notifier. After deployment, requests to the app's public URL reach the code declared as web, but requests never reach notifier even though notifier also starts an HTTP server. Which explanation is correct?
選択肢
- The notifier process type must bind to the port given in the environment before it is eligible, and once it binds to that port the routers add it to the same pool that already serves the public URL.
- Only process types whose names appear in a routing configuration file receive traffic, and notifier was left out of that file when the application was deployed for the first time.
- The web process type is the only one that can receive external HTTP traffic from Heroku's routers, so any other process type must be reached by another mechanism.
- Requests reach notifier only after it is scaled to at least two dynos, because the router requires a minimum of two backends before it starts accepting and forwarding requests to a process type.