Java Enterprise and Web Technologies

A WebLogic domain is an inter-related set of WebLogic Server resources (servers, clusters, applications) that are managed as a single administrative unit. It includes both Admin servers and Managed servers, ruling out A and C.

The WebLogic Administration Server uses Management Beans (MBeans), which are JavaBean-like objects that expose management and monitoring capabilities. MBeans follow the JMX (Java Management Extensions) standard.

When you delete a Managed Server through the Administration Server Console, WebLogic automatically removes the server's configuration from config.xml, which is the central domain configuration file. This file stores all server properties, attributes, and resources for the entire domain. The other files listed (server.xml, serverAttributes.xml) are not standard WebLogic configuration files.

A WebLogic Server cluster is a group of multiple WebLogic Server instances that run simultaneously and work together to provide scalability, reliability, and high availability. Clusters can contain any number of server instances (not just one or two), and they appear to clients as a single entity. Option B correctly describes the multi-instance nature.

Node Manager is a Java utility provided by WebLogic that enables you to start, stop, and restart Managed Server instances remotely. It is specifically designed for managing Managed Servers, not the Administration Server (which is typically started directly). Option B correctly identifies its purpose and target.

The weblogic.policy file is where you update license information and security permissions for WebLogic Server. This Java policy file defines the security permissions and licensing constraints for the server. The weblogic.properties and weblogic.licenses files are not the correct locations for license configuration.

The Intercepting Filter pattern in Java EE is implemented by creating a class that implements the javax.servlet.Filter interface. This interface defines methods like doFilter() that allow preprocessing and postprocessing of requests, enabling tasks like authentication, logging, and compression.

The Front Controller pattern is implemented by creating a servlet that implements the javax.servlet.Servlet interface (typically by extending HttpServlet). This allows a single controller to handle all requests and delegate to appropriate handlers. ServletConfig and ServletContext are configuration objects, not handler interfaces.

In Struts 1.x, ActionServlet serves as the Front Controller - it's the single entry point that receives all HTTP requests and delegates them to appropriate Action classes based on the struts-config.xml mapping. Action classes handle business logic, ActionForm holds form data, but ActionServlet is the centralized dispatcher implementing Front Controller.

Struts was originally developed by Craig McClanahan over a long holiday weekend in 2000 as a way to solve common web application development problems. It was not developed through an online exchange (A), not as a commercial package (C), and was donated to the Apache Software Foundation.

The Application Resources file (which contains i18n messages) is configured via the servlet init-param named 'application' in web.xml. This parameter specifies the base name of the resource bundle. Options B, C, and D are incorrect parameter names for this configuration.