Enterprise Software Architecture Quiz

SOAP (Simple Object Access Protocol) is the correct answer because it specifically defines an XML-based extensible message format, provides standard bindings to HTTP protocol, and establishes conventions for encoding data and representing remote procedure calls. WSDL describes services but doesn't define message formats or bindings, XML is only a markup language, and UDDI is for service discovery.

Well-defined interfaces (A) specify contracts without revealing implementation, allowing services to interact through public interfaces only. Loose coupling (B) means services have minimal dependencies on each other's internal details. Service granularity (C) is about functional scope size, not implementation hiding. Stateless design (D) avoids maintaining conversation state but doesn't address implementation awareness.

Request-response pattern involves a client sending a message and receiving a reply, while one-way pattern sends a message without expecting a response. These are the two fundamental message exchange patterns in web services. Option A describes execution modes (async/sync), not patterns. Options C and D are SOAP encoding styles, not message exchange patterns.

In the SOA publish-find-bind model, Publish describes making service descriptions available in a registry (like UDDI). Find is searching for services, Bind is connecting to use a service, and Register isn't one of the three core SOA operations. The question specifically asks about sending descriptions TO a registry.

The standard web service consumption pattern is: query UDDI registry for services, retrieve WSDL description of the desired service, then use SOAP to bind and invoke the service. WSDL describes the service interface, UDDI is the registry, and SOAP is the communication protocol.

Loose coupling is the defining characteristic that distinguishes SOA from previous distributed approaches like CORBA, DCOM, or tight monolithic architectures. Loose coupling means services can evolve independently without breaking consumers. Object-based (B) is not unique to SOA, synchronous (C) isn't required, and SOA typically uses coarse-grained (not fine-grained) services.

Struts implements MVC architecture, cleanly separating business logic from presentation layer. It's a mature, enterprise-grade framework designed for reliability and scalability in large applications. Performance is not its primary advantage compared to lighter frameworks, so options A and B are correct but C is not.

Struts supports both declarative exception handling (configured in struts-config.xml using global-exceptions or exception mappings) and programmatic handling (try-catch blocks in Action classes). Declarative handling centralizes configuration while programmatic gives fine-grained control.

Struts provides five core tag libraries: bean, html, logic, nested, and tiles. However, the question may be referring to the four most commonly used ones (excluding nested or tiles depending on version). The core libraries are bean (for JavaBeans manipulation), html (for form/rendering), logic (for conditional logic), and tiles (for layout composition).

The three main Struts tag libraries are: Bean tags (for accessing JavaBeans and their properties), Logic tags (for conditional presentation and iteration), and HTML tags (for generating HTML forms and UI elements). There is no separate 'Xml tag library' - the HTML library is the third correct option.

The execute() method in a Struts Action class receives four parameters: ActionMapping (describes the action mapping), ActionForm (contains form data), HttpServletRequest (the HTTP request object), and HttpServletResponse (the HTTP response object). These provide all necessary context for request processing.

Spring Core container (specifically the BeanFactory and ApplicationContext) is responsible for creating, configuring, and managing beans. It defines how beans are instantiated, wired together, and their lifecycle is managed.

The Spring Framework architecture consists of around 20 modules, with 7 well-defined modules being commonly referenced: Core, AOP, Aspects, Context, DAO, ORM, and Web MVC/JEE.

Inversion of Control (IoC) is the design pattern where the Bean Factory manages object creation and dependency injection, separating configuration metadata from actual business logic code. This promotes loose coupling and easier testing.

The Spring Bean Factory supports two main scopes: singleton (default, one shared instance) and prototype (new instance per request). Option C correctly states that both are supported.

Phase B Business Architecture focuses on describing the baseline and target architectures, selecting tools and viewpoints, and addressing stakeholder concerns. Defining business requirements happens in earlier phases (Preliminary/Phase A), making D the exception.

Business Process Models, Use-Case Models, Class Models, and Information Exchange Matrix are all modeling techniques for capturing business aspects. The Traceability Matrix is a requirements management tool for tracking requirements to implementations, not a business modeling tool.

The question asks which is NOT a suggested step for gap analysis. All the options listed (Process Gap, Tools Gaps, Financial Gaps, Information Gaps) are valid gap types that should be analyzed. Since none of them should be excluded from gap analysis, E (none of the above) is correct.