Practice the vocabulary of quick, integrated deployment workflows for prototypes and small apps.
0 / 5 completed
1 / 5
At standup, a dev mentions publishing an app directly from the same browser-based environment used to write the code, with no separate deployment pipeline to configure. What is this workflow called?
Integrated in-browser deployment publishes an application directly from the same environment used to write and run the code, without requiring the developer to separately configure a hosting provider or deployment pipeline. This tight integration is especially appealing for quickly shipping a small project or prototype. It trades some of the configurability of a dedicated deployment pipeline for significant simplicity and speed.
2 / 5
During a design review, the team wants a deployed app to automatically scale down to zero compute cost when it receives no traffic, and scale back up on the next request. Which capability supports this?
Autoscaling deployment with scale-to-zero automatically reduces a deployed app's compute usage to nothing when there's no incoming traffic, then scales back up to serve the next request, avoiding the cost of running a fixed-capacity server continuously for an app with light or sporadic usage. This is particularly cost-effective for small or hobby projects that don't need to be always warm. The tradeoff is a cold-start delay on the first request after a period of inactivity.
3 / 5
In a code review, a dev configures a deployment to keep running continuously and restart automatically if the process crashes. What does this represent?
An always-on deployment with automatic process restart keeps an application running continuously and recovers automatically if the process crashes, rather than staying down until a person notices and manually restarts it. This is important for an app expected to be reliably available at all times, unlike a scale-to-zero deployment better suited to sporadic traffic. Automatic restart on crash is a basic resilience feature for any continuously running service.
4 / 5
An incident report shows a deployed app exposed a hardcoded database password directly in the source code, discovered after the repository was accidentally made public. What practice would prevent this?
Storing a secret like a database password in a dedicated environment configuration, rather than hardcoding it directly in source code, means that even if the repository is accidentally exposed, the credential itself isn't sitting in plain text within it. Assuming a repository will always stay private is a fragile safeguard on its own, since accidental exposure does happen. This separation of secrets from source code is a basic security practice regardless of how quick and simple the deployment workflow otherwise is.
5 / 5
During a PR review, a teammate asks why the team deploys quick prototypes through an integrated in-browser workflow instead of setting up a full cloud infrastructure pipeline for every experiment. What is the reasoning?
Setting up a full cloud infrastructure pipeline involves meaningful upfront configuration that's often disproportionate to the needs of a short-lived experiment or prototype. An integrated in-browser deployment gets something live almost immediately, which is well suited to quickly validating an idea. For a project expected to grow into a long-term, higher-traffic production service, migrating to a more configurable pipeline eventually becomes worthwhile.