Java Enterprise and Web Technologies

JNDI (Java Naming and Directory Interface) is the API and service that Tomcat uses to provide access to resources like databases, connection pools, and JavaMail sessions through a naming context. Naming Lookup is too vague, Class Loader is for Java classes, and Buffering is for I/O operations.

CGI (Common Gateway Interface) is the standard protocol for web servers to execute external programs that generate web content dynamically, typically processing form data. CORBA is for distributed objects, IIS Server is a Microsoft web server product, and Java Servlets are Java-based server-side programs (not external programs in the CGI sense).

The Admin web application is configured through an XML descriptor file located at CATALINA_BASE/webapps/admin.xml. This follows the standard Tomcat deployment descriptor pattern where configuration is in XML files, not HTML files. The CATALINA_BASE path is used for instance-specific configurations.

The WebDAV (Web Distributed Authoring and Versioning) application in Tomcat enables remote content management through WebDAV clients, allowing users to edit and manage website files as if they were local. Admin and Manager apps are for server administration, and Examples is for demonstration code.

Caching Proxy server provides reverse proxy capabilities for content-based routing and dynamic content caching integrated with servlet caching. These are core caching proxy features. File serving (C) and HTTP compression (D) are typically separate WebSphere Edge components or server features, not primary caching proxy functions.

WebSphere application server provides an embedded portlet container to support JSR 168 compliant portlets without requiring a separate portal server. This container manages portlet lifecycle, rendering, and aggregation. Option B is incorrect (no scaled-down portal). Option C describes a portal application, not the container. Option D is incorrect (Portal Express is a separate product).

WebSphere Application Server provides core infrastructure services including security (authentication/authorization), JNDI naming service for resource lookup, transaction management for distributed operations, and dynamic caching for performance. JMS messaging is available but not the primary focus in this grouping. User registry and HTTP Load Balancing are infrastructure components but not listed in the correct combination.

Session Initiation Protocol (SIP) servlets are packaged in SIP Archive (SAR) files, which are specialized archives for SIP applications. Standard web applications use WAR files, plain Java classes use JAR files, and enterprise beans use EJB-JAR files. SIP-JAR is not a standard archive type.

To answer this question, the user needs to have a basic understanding of WebSphere cell configuration and its components.

The correct answer is:

A. Deployment Manager

Explanation:

In a WebSphere cell configuration, the Deployment Manager is a single point of failure. The Deployment Manager is responsible for managing the deployment of applications across the cell, and if it fails, it can result in the entire cell being unavailable. The other components, such as the web container, EJB container, and HTTP server, can be distributed across multiple nodes in the cell, providing redundancy and fault tolerance.

Option B, web container, is incorrect because it is responsible for handling HTTP requests and is not a single point of failure.

Option C, EJB container, is incorrect because it manages the execution of EJB components and is not a single point of failure.

Option D, HTTP server, is incorrect because it is responsible for handling HTTP requests and can be distributed across multiple nodes in the cell.

Therefore, the correct answer is A. Deployment Manager.

When SSL ID tracking is enabled, Cookies and URL Rewriting should also be enabled as fallback mechanisms. SSL tracking can fail if clients don't support SSL sessions or if sessions are invalidated, so cookies provide primary persistence and URL rewriting ensures session continuity when cookies are disabled. Security Integration, Serial Access, and RMI are not session tracking mechanisms.

In Struts 1.1, the RequestProcessor's processPopulate method is the correct override point to control how form fields are populated from request parameters. Overriding ActionForm.populate is not the intended extension mechanism, and ActionMapping doesn't have a populateBean method.

In Struts, there is exactly one RequestProcessor instance per module, which handles all requests for that module. This is a singleton pattern within each module context. It's not one-per-application (multiple modules exist), not one-per-request (too expensive), and not one-per-ActionServlet (the module is the key).

The Struts 1 ActionServlet implements the Front Controller design pattern, where a single servlet receives all requests and delegates to appropriate handlers (Actions). Intercepting Filter is a different pattern (J2EE filters), Single Controller is not a standard pattern name, and Front Controller is the correct answer.

In Struts 1.2, the locale information is stored in session with the key Globals.LOCALE_KEY. The constant value is "org.apache.struts.action.LOCALE". This locale is automatically set by Struts based on the user's browser preferences or can be manually set. Option A uses ID instead of KEY which is incorrect. Option B incorrectly uses Commons prefix. Option D incorrectly uses Constants prefix.