This set builds vocabulary for branch-based preview deployments and environment isolation.
0 / 5 completed
1 / 5
At standup, a dev mentions that every git branch pushed to the repository gets its own unique, isolated deployment URL automatically. What is this pattern called?
Branch-based preview deployments generate a unique, isolated URL for each git branch pushed to the repository, so multiple in-progress features can be reviewed simultaneously without overwriting a shared staging environment. This isolation avoids the classic problem of one team's staging deploy clobbering another's. It's a defining feature of platforms designed around this workflow.
2 / 5
During a design review, the team wants environment variables specific to preview deployments, separate from production secrets, to avoid leaking sensitive production credentials. Which capability supports this?
Environment-scoped configuration lets different environment variables and secrets be defined specifically for preview deployments versus production, preventing sensitive production credentials from being exposed in a preview environment that might be shared more widely for review. This separation is an important security boundary given how easily a preview URL can be shared outside the core team. It reflects a broader principle of scoping secrets to the minimum environment that needs them.
3 / 5
In a code review, a dev notices a comment automatically posted on the pull request linking directly to that branch's live preview deployment. What does this integration represent?
Automated linking between the version control platform and the deployment service posts a comment with the live preview URL directly on the pull request, so a reviewer doesn't have to manually track down or construct the deployment link themselves. This tight integration reduces friction in the review workflow. It's a common pattern across git-integrated deployment platforms.
4 / 5
An incident report shows a preview deployment inadvertently connected to and modified data in the production database. What practice would prevent this?
A preview deployment should be configured to connect to an isolated, non-production data source, since accidentally pointing a preview build at the real production database risks unintended writes from code that hasn't been fully reviewed or tested. This isolation mirrors the same reasoning behind separating preview and production secrets. Careful environment-scoped configuration is what prevents this category of incident.
5 / 5
During a PR review, a teammate asks why the team relies on isolated per-branch preview deployments instead of one shared staging environment for all in-progress work. What is the reasoning?
A single shared staging environment risks one team's in-progress feature interfering with or overwriting another's during concurrent development, while isolated per-branch previews let each feature be reviewed independently without that collision. This isolation is especially valuable on teams with many concurrent pull requests. The tradeoff is the added infrastructure cost of provisioning many small, short-lived deployments.