Test your Railway knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
How does Railway typically detect how to build and run a connected project?
In this round
How does Railway typically detect how to build and run a connected project?
How does Railway typically handle logs for a deployed service?
What is a `railway.json` (or `railway.toml`) configuration file used for in a Railway project?
What is the purpose of Railway's "cron jobs" / scheduled deployments feature (or a similar scheduled-service configuration)?
How does Railway generally price usage, in contrast to a fixed-monthly-fee VPS?
What does Railway's "build" step typically produce before deployment?
How does Railway typically expose a deployed web service to the public internet?
Why might a small team or solo developer choose Railway over manually configuring a VPS (e.g. via a raw DigitalOcean droplet) for deploying an application?
What is a reasonable comparison between Railway and Heroku, a well-known predecessor in the "simplified PaaS deployment" space?
What is the Railway CLI typically used for?
What is the purpose of "rollback" functionality on a Railway deployment?