Java Enterprise and Web Technologies

EJB stands for Enterprise JavaBeans, not Extensible JavaBean. EJB is a server-side software component that encapsulates the business logic of an application. The key word is 'Enterprise' - it's for building scalable, enterprise-level applications. Option B correctly identifies this as false.

JAAS is indeed Java Authentication and Authorization Service. It's a Java security API that enables authentication and authorization for user access control. The True option correctly identifies the full form of this Java security technology.

JAXP correctly stands for Java API for XML Processing. It's a Java API that provides a standard interface for processing XML documents using DOM, SAX, and XSLT. The True option accurately identifies this XML processing API.

JMX stands for Java Management Extensions, not Java Management XML. It's a Java technology that supplies tools for managing and monitoring applications, system objects, and service-oriented networks. The False option is correct as the expansion is wrong.

JNDI stands for Java Naming and Directory Interface, not Java Network and Directory Interface. It's a Java API for a directory service that allows Java software clients to discover and look up data and objects via a name. The False option is correct as 'Naming' replaces 'Network'.

JRE stands for Java Runtime Environment, not Java Runtime Engine. It's a software bundle that provides the Java class libraries, Java Virtual Machine, and other components to run Java applications. The False option is correct as 'Environment' replaces 'Engine'.

JSP correctly stands for JavaServer Pages. It's a server-side Java technology that enables developers to create dynamically generated web pages based on HTML, XML, or other document types. The True option correctly identifies this web technology.

JSF (JavaServer Faces) is a Java specification for building component-based user interfaces for web applications. It simplifies web development by providing reusable UI components and managing state between requests.

JTA stands for Java Transaction API, not Java Transport API. JTA provides a standard interface for managing transactions in Java, allowing coordination of distributed transactions across multiple resources.

JMS (Java Message Service) requires a listener to receive and process messages from a queue or topic. The listener continuously monitors the messaging destination and invokes service processing when messages arrive. EJB uses direct RMI/IIOP calls, SOAP and HTTP use request/response patterns - none require continuous listeners like JMS.

Thread-scoped data pages (formerly declare pages) live within the requestor thread context. When the requestor logs off, the session times out, or the session expires, the requestor context and its threads are destroyed, removing the pages from memory. This makes all three scenarios correct.

The Configuration Manager acts as the intermediary between the Message Broker toolkit and the execution groups (brokers). It stores the configuration information and deploys the message flows and bar files to the brokers. The Execution Group is where the message flows actually run, not the connection component.

HTTP is a stateless protocol, so session management requires client-side persistence. Cookies are the standard mechanism - the server sends a Set-Cookie header with a session identifier, and the client returns it on subsequent requests. Memory flags, request IDs, and request parameters don't persist across requests.

When a specific node causes application failure, the IMMEDIATE solution to restore availability is to remove that node and replace it with a healthy one. Debugging takes time and doesn't immediately solve the availability problem. Leaving it as-is keeps the application unavailable. The priority is restoring service quickly.

The Serializable interface in Java is a marker interface with no methods. It serves only to indicate that a class can be serialized - the actual serialization is handled by the JVM. Interfaces like Runnable, Servlet, and ActionListener all declare methods that must be implemented.