Server-Side Execution — What Handles HTTP Requests on the Web Server? Which Java component is invoked on the web server via HTTP to process requests coming from a user’s browser?

Introduction:
On the server side of web applications, Java servlets are the core components that receive HTTP requests and generate HTTP responses. Recognizing the difference between client-side and server-side Java technologies is fundamental to web architecture in Java.

Given Data / Assumptions:

• Requests originate from a user’s web browser.
• Processing occurs on the web server.
• We must choose a server-side handler.

Concept / Approach:
Servlets run within a servlet container (such as Tomcat or Jetty). They implement methods like doGet and doPost, interact with request/response objects, and produce dynamic content. Applets are downloaded to and run on the client; standalone Java applications are not inherently invoked by HTTP on the server. Therefore, the correct server-side component is the servlet.

Step-by-Step Solution:
1) Determine execution location: server, not client.2) Identify canonical Java HTTP handler on the server: servlet.3) Exclude applets and generic applications as they are not the HTTP endpoints on the server.

Verification / Alternative check:
Servlet specifications define the lifecycle and mapping of servlets to URL patterns, confirming their role as HTTP request processors on the server.

Why Other Options Are Wrong:

• Applet: Client-side component.
• Java application: Not necessarily an HTTP endpoint.
• JNLP app: Client-side launch technology.

Common Pitfalls:
Confusing download-and-run client technologies with server-side request handlers.

Final Answer:
A Java servlet