Client-Side Execution — What Is Downloaded via HTTP and Runs on the User’s Computer? Identify the Java technology that is sent to the user over HTTP, launched using the HTTP protocol by the user’s environment, and executed on the user’s computer within a Java-capable container.

Introduction:
Before modern client-side frameworks became dominant, small Java programs called applets were embedded in web pages and executed on the user’s machine via a browser plugin or the Java Plug-in. This question distinguishes applets from server-side components such as servlets.

Given Data / Assumptions:

• Delivery occurs over HTTP to the client.
• Execution occurs on the user’s machine within a JVM-enabled environment.
• We must choose among common Java components.

Concept / Approach:
Applets are client-side Java programs downloaded to the browser and executed locally. Servlets, in contrast, run on the server under a servlet container (for example, Tomcat). A generic “Java application” is not specifically delivered and launched via the browser; it typically runs as a standalone program. Therefore, the description clearly matches a Java applet.

Step-by-Step Solution:
1) Identify where the code runs (client vs. server).2) Map client-side downloaded execution to the “applet” concept.3) Exclude server-side servlet execution.4) Select “A Java applet.”

Verification / Alternative check:
Historic Java web tutorials describe the applet lifecycle (init, start, stop, destroy) and the need for a browser plug-in or appletviewer, affirming client-side execution after HTTP delivery.

Why Other Options Are Wrong:

• Java application: Not necessarily delivered via HTTP for in-browser execution.
• Java servlet: Runs on the server, not the user’s computer.
• JSF page: A server-side view technology rendered to HTML; execution is server-side.

Common Pitfalls:
Conflating where code runs; applets (client) vs. servlets/JSF (server).

Final Answer:
A Java applet