Websites without a database backend: Which characteristic best describes such sites?

Introduction / Context:
Many websites are purely static. They deliver pre-built files—HTML, CSS, JavaScript, and media—without querying a database or running server-side code to generate content.

Given Data / Assumptions:

• No server-side database is attached.
• Content is pre-rendered or authored and deployed as files.
• The browser fetches resources via HTTP(S).

Concept / Approach:
Static site architectures simplify hosting and improve performance. Content can be authored manually or built by static site generators and then served from CDNs. Interactivity still exists via client-side JavaScript, but data persistence is not provided by a server database.

Step-by-Step Solution:

Verification / Alternative check:
Inspect response headers and file types (for example, .html, .css, .js) and absence of dynamic endpoints.

Why Other Options Are Wrong:

• Generating results via SQL implies a database.
• Browsers display static pages just fine.
• All web delivery uses TCP/IP; saying otherwise is incorrect.
• WebSockets are optional and unrelated to static serving.

Common Pitfalls:
Assuming “static” means non-interactive; client-side scripts can still offer rich UX without server databases.

Final Answer:
They present static information using HTML, CSS, and JavaScript files.