Websites without a database backend: Which characteristic best describes such sites?
-
AThey generate data via SQL on user requests.
-
BThey cannot use a browser to display pages.
-
CThey present static information using HTML, CSS, and JavaScript files.
-
DThey do not rely on TCP/IP networking.
-
EThey require WebSockets for every page load.
Answer
Correct Answer: They present static information using HTML, CSS, and JavaScript files.
Explanation
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:
Identify lack of server-side persistence.Confirm that pages are served as static assets.Select the option describing static HTML/JS content.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.