Hosting 100 React Apps with PR Previews and Azure Repos CI/CD?
You plan to develop, deploy, and maintain 100 React-based web apps that will NOT require server-side rendering. You need to recommend a hosting solution for the apps. The solution must meet the following requirements: • Automatically deploy new versions of the apps when changes to the apps' source code are committed in Azure Repos. • Automatically stage a preview version of an app when a pull request is processed. • Support Azure API Management by using the /api • Minimize costs. What should you include in the recommendation?
Community Insight
The question tests whether you match a static front-end framework to a hosting service with native build/deploy and per-pull-request staging; the trap is grabbing the cheapest storage option and forgetting it has no built-in preview environments or /api routing.
Azure Static Web Apps is the hosting recommendation for React apps that skip server-side rendering but still need Azure Repos CI/CD and automatic pull request preview environments. This page shows why Static Web Apps beats Blob Storage, App Service, and Azure Functions on both features and cost at a scale of 100 apps.
Choosing Azure Blob Storage static sites because it looks like the lowest-cost way to host static React files, while ignoring that it provides no built-in Azure Repos build pipeline, no automatic pull request preview environments, and no /api path integration for API Management.
Community Discussion (2 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Azure Static Web Apps is purpose-built for front-end frameworks such as React when server-side rendering is not required. It integrates directly with Azure Repos (Azure DevOps) so a commit triggers a build and deployment, and it automatically creates a staging/preview environment for each pull request. Its routing rules send requests under /api to a linked API backend, which fits the API Management requirement without extra glue, and its Free and Standard tiers are far cheaper than running 100 App Service plans. That combination of native CI/CD, PR previews, /api routing, and low per-app cost makes D the only option that satisfies every stated requirement.Why the Other Options Are Wrong
Azure Blob Storage static sites can serve React build output cheaply, but they have no native Azure Repos pipeline, no per-pull-request preview environments, and no /api routing construct — you would have to engineer all of that yourself. Azure App Service web apps can host the apps and use deployment slots for staging, but 100 apps means 100 plans or slot-heavy configurations that inflate cost, and PR preview environments are not automatic. An Azure function is a serverless compute unit for event-driven code, not a front-end web host, so it cannot serve the React single-page apps at all.Community Comment Notes
Both commenters land on D, and denosore walks through the same elimination logic used here: Blob Storage "lacks built-in pull request preview environments," App Service is "generally more expensive for this use case," and Functions targets serverless code rather than React front ends. AllanHouston adds that Static Web Apps is designed for React without server-side rendering and "supports automatic deployments, pull-request previews, API Management integration," while being more cost-effective than App Service. That consensus matches the requirement-by-requirement analysis rather than relying on a vote count.Official Reference
Exam Strategy
When a question mentions React/Angular/Vue without server-side rendering plus CI/CD and pull request previews, Static Web Apps is almost always the intended answer; reserve App Service for SSR or full server workloads and Blob Storage only when no pipeline or preview requirement exists. Also scan for the cost constraint, since 100 apps makes per-app App Service plans a clear distractor.
Frequently Asked Questions
Why isn't Azure Blob Storage static sites the cheapest choice for these React apps?
It has no native Azure Repos build pipeline, no automatic pull request preview environments, and no /api routing, so you would build and maintain that tooling yourself.
Does Azure Static Web Apps work with Azure Repos, not just GitHub?
Yes. Static Web Apps supports Azure DevOps/Azure Repos as a source, triggering builds and deployments on commits and creating preview environments for pull requests.
Related Analysis
Practice All AZ-305 Questions
Access 95 questions with complete answers and detailed explanations.
View Full AZ-305 Practice Test →