This set builds vocabulary for per-pull-request preview environments and collaborative review.
0 / 5 completed
1 / 5
At standup, a dev mentions that every pull request automatically gets its own live, shareable URL for reviewing the change before merging. What is this called?
A preview deployment automatically builds and deploys a live, isolated version of the application for each pull request, giving reviewers a real, clickable URL to test the actual change rather than relying solely on reading the diff. This closes the gap between code review and visual/functional verification. It is a standard feature of modern CI/CD-integrated hosting platforms.
2 / 5
During a design review, the team wants stakeholders without git access to review a UI change by simply clicking a link. Which capability supports this?
A preview URL can be shared with anyone, including non-technical stakeholders, letting them interact with the actual running change without needing to clone the repository or run it locally. This broadens who can meaningfully participate in reviewing a visual or UX change. It significantly lowers the friction of getting feedback before merging.
3 / 5
In a code review, a dev notices each new commit pushed to the pull request triggers a fresh build and updates the preview URL automatically. What does this reflect?
Continuous preview deployment rebuilds and updates the preview automatically on each new commit pushed to the pull request, so the shared URL always reflects the latest state of the branch without manual redeployment. This keeps the review experience current throughout the PR's lifecycle. It removes a manual step that would otherwise be easy to forget.
4 / 5
An incident report shows a preview deployment was accidentally left publicly accessible and exposed unreleased feature details. What practice would mitigate this?
Access protection, such as requiring authentication to view a preview deployment, prevents sensitive or unreleased functionality from being exposed if a preview URL is discovered or shared unintentionally. Preview URLs are often guessable or logged in various places, so relying purely on obscurity is risky. Enabling protection for sensitive branches is a standard security consideration for preview deployment features.
5 / 5
During a PR review, a teammate asks how a preview deployment differs from testing a change only in a local development environment. What is the key advantage?
A local development environment is only accessible on the developer's own machine, while a preview deployment runs in a shared, production-like environment reachable by anyone with the link, enabling broader collaborative review. This also surfaces environment-specific issues that might not appear locally. The combination of shareability and closer-to-production fidelity is what makes preview deployments valuable for team review workflows.