Difficulty: Easy
Correct Answer: Incorrect
Explanation:
Introduction / Context:
This question tests understanding of server-side web technologies. JSP (JavaServer Pages) is part of the Java EE ecosystem, while ASP originally referred to Microsoft Active Server Pages and later ASP.NET on the .NET platform. Although both render dynamic HTML and can appear similar in syntax within templates, their engines, lifecycles, and deployment stacks are distinct.
Given Data / Assumptions:
Concept / Approach:
Compare lifecycle and runtime: JSP pages are translated to Java servlets, compiled to bytecode, then executed by the JVM. ASP.NET pages are compiled to Intermediate Language and executed by the Common Language Runtime. Classic ASP is interpreted by its own engine. The request pipelines, configuration, and libraries differ substantially.
Step-by-Step Solution:
Identify each platform’s runtime (JVM vs. CLR/Classic ASP engine).Note the compilation/translation step (JSP to servlet vs. ASP.NET to IL).Compare hosting (Tomcat/Jetty/Jakarta vs. IIS).Evaluate libraries and APIs (Servlet API/JSP vs. ASP.NET framework).Conclude that similarity is mostly superficial (template look), not technical underpinnings.
Verification / Alternative check:
Check deployment artifacts: JSP uses .war/.ear with web.xml or annotations; ASP.NET uses .NET projects deployed to IIS with web.config and assemblies.
Why Other Options Are Wrong:
“Only true for ASP.NET MVC” or “only on old IIS” does not change the fundamental runtime difference.
Common Pitfalls:
Equating similar templating syntax with identical technology; ignoring runtime and server differences.
Final Answer:
Incorrect
Discussion & Comments