This set builds vocabulary for deploying and running static sites on an edge-hosted platform.
0 / 5 completed
1 / 5
At standup, a dev mentions a platform that builds and deploys a static frontend directly from a git push, serving it from a global edge network. Which platform type fits?
An edge-hosted static site platform like Cloudflare Pages automatically builds a project from a git push and distributes the output across a global edge network, so visitors are served from a nearby location rather than one central server. This reduces latency for a geographically distributed audience without requiring manual CDN configuration. It's a common deployment target for modern static and Jamstack-style sites.
2 / 5
During a design review, the team wants server-side logic, like an API route, to run at edge locations alongside the static assets. Which capability supports this?
Pages Functions let a developer add serverless, edge-executed logic, like an API route, alongside a static site's assets, so dynamic behavior runs close to the user rather than requiring a round trip to a distant origin server. This blends static hosting with lightweight dynamic capability in one deployment. It's especially useful for small backend tasks that don't warrant a full separate server.
3 / 5
In a code review, a dev notices every git branch pushed to the repository automatically gets its own preview deployment URL. What does this reflect?
Per-branch preview deployments automatically build and publish a unique URL for each pushed branch, letting a reviewer see a feature's actual running result before it merges to the main branch. This mirrors a common pattern across many git-integrated static hosting platforms. It removes the need to manually spin up a separate environment for every in-progress change.
4 / 5
An incident report shows a build failed silently and the site kept serving a stale previous deployment without anyone noticing for days. What practice would prevent this?
Configuring build failure notifications ensures the team is alerted immediately when a deployment doesn't go through, rather than discovering days later that the live site has been silently serving stale content. Relying on manual, infrequent checks leaves this kind of gap unnoticed for far too long. Automated alerting on deployment status is a basic operational safeguard for any CI-driven hosting workflow.
5 / 5
During a PR review, a teammate asks why the team deploys static assets to an edge network instead of a single origin server. What is the reasoning?
A single origin server forces every visitor, regardless of location, to fetch content from one place, while an edge network caches and serves assets from points of presence near each visitor, meaningfully reducing latency for a geographically spread audience. This distributed delivery is the core value proposition of edge-hosted static platforms. The tradeoff is less relevant for an audience concentrated in a single region.