IBM SOA Fundamentals [2008] Set 7

It should be monitored. ✘ It only deals with automated tasks. ✘ It interacts with a single application. ✘ It has one primary Key Performance Indicator (KPI). ✔

Modularity and encapsulation ✘ SOA governance and service reuse ✘ Service reuse and process modeling ✘ Loose-coupling and separation of concerns ✔

Both architectures use XML to ensure interoperability. ✘ Web 2.0 technologies communicate using Remote Procedure Calls (RPC) to SOA services. ✘ JavaScript Object Notation (JSON) provides an efficient data format for SOA services. ✘ Asynchronous JavaScript + XML (Ajax) applications can make service requests from a Web browser. ✔

It rarely includes any manual steps. ✘ It can span people, systems and information. ✘ It takes a relatively short amount of time to complete. ✘ All services are linked to the process through an Enterprise Service Bus (ESB). ✔

Inheritance ✘ Encapsulation ✘ Cross-cutting concern ✘ Focus on messaging strategies ✔

Service implementations can be changed without changing the consumers. Services are compatible across technologies. Services can change location without affecting clients. Services provide an interface according to a SOAP file. Services can be stopped without disruption to the consumer.

Services often represent functions in an SOA. ✘ Existing applications may serve as the basis for service interfaces. ✘ The interface of a service allows it to be integrated into additional processes without changes. ✘ Service interface details may be defined at a high level according to anticipated business requirements. ✔

One that is structured around localized business representatives for the IT team(s). ✘ One in which the departments are small, geographically centralized, and provide many goods and services. ✘ One that is relatively large, geographically dispersed, and with a centralized management and fundingstructure. ✘ One in which the funding, management and control of IT resources are spread among multiple stakeholdersin different parts of the organization. ✔

Rogue Service ✘ Duplicate Service ✘ Shelfware Service ✘ Composite Application Service ✔

It must manage service distribution and rights management. ✘ It must enforce communication between stakeholders and subject matter experts. ✘ It must enforce coordination between service providers across the organization. ✘ It must coordinate communication of business requirements to development organizations during theplanning phase. ✔