WebSphere Application Server Administration

When a cluster member crashes, locks held by its transactions must be released by another member with access to the transaction log for recovery. The transaction log contains the state of in-flight transactions. Options A, B, and D don't address transaction log access which is required for lock recovery in clustered environments.

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.

To load balance HTTP traffic across Web servers, an IP sprayer (from WebSphere Edge Components load balancing module) distributes incoming requests across multiple servers. Option A (TAM) is for authentication/authorization, not load balancing. Server affinity (B) is a sticky session policy, not load balancing itself. Caching proxy (C) caches content but doesn't spray IP traffic.

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).

Web server plug-ins distribute incoming requests across multiple application server instances, while load balancers distribute network traffic across multiple servers. Both are essential for managing workload distribution and preventing overload on any single component.

Report Studio in Cognos is specifically designed for creating professional, formatted, pixel-perfect reports for business intelligence. It provides advanced layout control, styling, and corporate branding capabilities. Ad hoc reports are typically created through Query Studio or Analysis Studio. Cubes are dimensional data sources, not output report types.

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.

The best practice for high availability is using multiple machines each capable of handling the full production load, allowing for failover when one machine fails. Load balancers alone between web and app servers don't provide complete HA. Authentication servers should be behind firewalls, not outside. Using fewer, larger machines creates a single point of failure.

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.

YAHOO stands for 'Yet Another Hierarchy of Officious Oracle'. This was the original expansion chosen by founders Jerry Yang and David Filo. 'Officious' refers to being helpful or intrusive, reflecting the directory's nature.

The @ symbol was chosen for email addresses by Ray Tomlinson in 1972 when he created the first email system on ARPANET. He selected it to separate the user name from the host computer, following the convention of @ meaning at or located at.

Yahoo was founded in 1994 by David Filo and Jerry Yang, both Stanford University graduate students. They created it as a directory of websites called Jerry and David's Guide to the World Wide Web before renaming it Yahoo.

Ken Thompson co-created UNIX with Dennis Ritchie at Bell Labs in 1969. Thompson designed the original UNIX system and wrote the first version, while Ritchie developed the C programming language that was later used to rewrite UNIX.

Microsoft corporate headquarters are located in Redmond, Washington, in the Pacific Northwest region of the United States.