Which statement best describes the public directory's purpose in a React app?

Which statement best describes the public directory's purpose in a React app?

• A. It contains source code that is transpiled.
• B. It contains development-only scripts.
• C. It contains static assets served directly without extra processing.
• D. It stores test configurations.

Answer: (C)

The public directory holds static assets that the app serves directly without going through the build or bundling process. Files placed here are not transformed by Webpack or Babel; they’re copied to the final build as-is and can be accessed by absolute URLs like /logo.png. The main HTML file that bootstraps the app also lives here, and during the build these assets are made available at the root of the served site. This is why it’s described as containing static assets served directly without extra processing. Other options point to things that belong elsewhere—source code lives in the src directory and is transpiled, development scripts live in the project configuration, and test configurations are stored separately—so they don’t fit the public directory’s role.

The public directory holds static assets that the app serves directly without going through the build or bundling process. Files placed here are not transformed by Webpack or Babel; they’re copied to the final build as-is and can be accessed by absolute URLs like /logo.png. The main HTML file that bootstraps the app also lives here, and during the build these assets are made available at the root of the served site.

This is why it’s described as containing static assets served directly without extra processing. Other options point to things that belong elsewhere—source code lives in the src directory and is transpiled, development scripts live in the project configuration, and test configurations are stored separately—so they don’t fit the public directory’s role.