Microsoft Active Server Pages (ASP): Which statement is accurate about classic ASP in the context of web application execution?

Introduction / Context:
Classic Microsoft Active Server Pages (ASP) is a server-side scripting technology. The server processes requests for .asp files, executes the embedded code, and returns HTML (or other content) to the client.

Given Data / Assumptions:

• Classic ASP files use the .asp extension.
• Server-side scripts are commonly embedded using <% ... %> delimiters.
• The client receives only the rendered output, not the server-side code.

Concept / Approach:
ASP separates server execution from client rendering. The server evaluates code (for example, VBScript or JScript), interacts with databases or components, and then generates the response. The browser displays the resulting HTML/CSS/JS; it does not execute ASP code itself.

Step-by-Step Solution:

Verification / Alternative check:
Documentation and tutorials show server execution and the presence of script blocks within ASP pages that are not sent to the client verbatim.

Why Other Options Are Wrong:

• Client execution: incorrect; the browser sees only the output.
• No tags/delimiters: ASP routinely uses script delimiters.
• .cfm files: those belong to ColdFusion, a different platform.
• Cannot mix HTML and code: classic ASP is designed to blend them.

Common Pitfalls:
Exposing server-side code accidentally; failing to separate logic and presentation in maintainable ways.

Final Answer:
ASP pages are stored in files with the .asp extension and execute on the server.