Visitors to your site are served those static assets produced by the build. What best describes what is served?

Visitors to your site are served those static assets produced by the build. What best describes what is served?

• A. Source code in its original form
• B. Dynamic HTML on every request
• C. Static assets produced by the build
• D. Untouched assets from the public directory

Answer: (C)

The essential idea is that what a hosting environment serves is the prebuilt, static files produced by the build process. When you run a build, your frontend code is transformed into deployable assets like JavaScript bundles, CSS, and an HTML shell that can be delivered directly to the browser without running server-side code. These are static in the sense that they don’t get generated anew on each request; they’re prepared in advance and served as-is from a server or CDN. That’s why the best description is static assets produced by the build. This isn’t the original source code being sent to users, which would expose code and require a different security and optimization model. It’s not dynamic HTML generated on every request, since the HTML and assets are built ahead of time for quick delivery. While some assets might come from a public directory, the defining characteristic is that the build creates the assets that are then served directly to the client.

The essential idea is that what a hosting environment serves is the prebuilt, static files produced by the build process. When you run a build, your frontend code is transformed into deployable assets like JavaScript bundles, CSS, and an HTML shell that can be delivered directly to the browser without running server-side code. These are static in the sense that they don’t get generated anew on each request; they’re prepared in advance and served as-is from a server or CDN. That’s why the best description is static assets produced by the build.

This isn’t the original source code being sent to users, which would expose code and require a different security and optimization model. It’s not dynamic HTML generated on every request, since the HTML and assets are built ahead of time for quick delivery. While some assets might come from a public directory, the defining characteristic is that the build creates the assets that are then served directly to the client.