Struts provides four scope options: page (current page only), request (current HTTP request), session (user session across requests), and application (global to the web application). These scopes control data visibility and lifecycle throughout the application.

Service-Oriented Architecture is a software architecture style where application components provide services to other components through network protocols. It emphasizes loose coupling, reusability, service abstraction, and is often implemented using web services.

Singleton ensures exactly one instance exists per database, with global access. For connection pools, you want one pool object managing connections for each database. Factory patterns create new instances, and Prototype copies existing ones - neither controls instance count like Singleton does.

Observer defines one-to-many dependency: when subject changes, all dependents are notified automatically. This IS publish-subscribe: publishers (subjects) broadcast to subscribers (observers) without knowing who they are. The pattern decouples event generation from event handling.

The Service Locator pattern centralizes service lookup logic and abstracts the complexity of JNDI/EJB lookups. Multiple clients can share a single Service Locator instance, which improves performance by caching frequently used service references. This pattern hides low-level lookup details from client code, making it easier to maintain and modify. Options B, C, and F correctly identify reusability, performance through caching, and complexity hiding as key benefits.

The ServletContext object acts as a Singleton - there is exactly one ServletContext instance per web application that all servlets share. This shared context holds application-wide resources and configuration, accessible to all servlets within that application. While Mediator, State, and Interpreter serve different purposes, the key here is the single shared container instance. Singleton ensures one instance exists and provides global access, which matches how ServletContext functions.

The dumpNameSpace utility is primarily used for diagnosing JNDI and namespace-related issues, including applications having trouble accessing specific WebSphere resources like data sources that are registered in the JNDI namespace.

Virtual host configuration isolates web modules by controlling which applications/resources can be accessed through specific virtual hosts. This provides security and resource separation between different web modules.

For security and architectural design, implementing a firewall on a dedicated Unix/Linux edge server while hosting the core WebSphere application server directly on the z/OS mainframe allows secure external web access while keeping the application tier tightly coupled to mainframe backend data.

In IBM WebSphere ILOG JRules (now Operational Decision Manager), the default name of the Rule Execution Server console web application is 'bres'. This is the standard context root used when deploying the RES console application.

An idempotent method can be called multiple times yielding the same side effects. GET, HEAD, OPTIONS, and TRACE are safe and idempotent. POST is typically not idempotent because multiple identical requests can result in duplicate resource creation or state updates.

In HTTP, DELETE removes resources, POST creates new resources, and PUT updates or replaces resources - all of which change server state. Safe methods like GET, HEAD, OPTIONS, and TRACE only retrieve information without modifying state.

The select element has 5 unselected options. With multiple attribute enabled, all 5 could be selected in addition to the 2 pre-selected ones (Java, C), giving 7 total. The submit button is a different parameter and doesn't affect the Languages count.

According to the servlet specification, web.xml must be in the WEB-INF directory of the web application. This is specified either relative to the web app root (/WEB-INF) or as an absolute path within the application server's webapps directory structure.

In the deployment descriptor, initParm is configured as a servlet-specific initialization parameter under `. In the servlet code,sc.getInitParameteris called on theServletContext`, which retrieves context-wide parameters rather than servlet-specific ones. Thus, it returns null, making the output 'Initialization Parameter is: null'.