SOA S90.08 Dumps

Access to a single rules service can create a processing bottleneck.

An increase in performance demands due to the need to access and evaluate business rules at runtime.

Conflicts when also applying the Decoupled Contract pattern.

The need to adopt a business rules management product, which can create dependencies on vendor-specific technology.

Enterprise Service Bus

Orchestration

Federated Endpoint layer

Official Endpoint layer

True

False

agnostic, atomic, agnostic

non-agnostic, business, agnostic

non-agnostic, agnostic, agnostic

agnostic, rules-related, non-agnostic

entity service

utility service

wrapper service

None of the above.

service agent

service contract

service activity

None of the above.

redundantly deployed services

service agents that perform load-balanced access to services that are not redundantly deployed C. compositions that compose redundantly deployed services

core service logic contained within services that do not rely on the redundantly deployed service

Although the Logic Centralization pattern addresses the question of how to avoid redundant service logic, it does not address how the logic should be accessed.

The Contract Centralization pattern specifies how to access a service through its published contract, but it does not indicate which services should be accessed for specific purposes.

When the Logic Centralization and Contract Centralization patterns are applied together, they realize the Official Endpoint pattern because they effectively establish an official endpoint for a service.

All of these statements are true.

Schema Centralization, XML schemas

Message Metadata, SOAP message headers

Decoupled Contract, WSDL definitions

Policy Centralization, WS-Policy definitions

True

False

a service, acting as a publisher, issues event notification messages to an event management program that is responsible for broadcasting the messages

a service consumer, acting as a subscriber, can selectively subscribe to specific events

an intermediate event management program enters the role of subscriber when accepting event subscriptions

upon receiving a message associated with an event that a service consumer subscribed to, the service consumer enters the publisher role

common routing logic being removed from service logic and placed into service agents

common routing logic being removed from service agents and placed into a database

common routing logic being physically centralized into a single service

common routing logic being physically centralized into a single service composition

True

False

an intermediate buffer exists between a service and its service consumer

temporary message storage is provided in case either the service or service consumer are unavailable

periodic re-transmission of a message is supported until it is successfully delivered

enforcement of consistent, uninterrupted, synchronous communication between service and service consumer are guaranteed

The overuse of service agents can lead to dependencies on proprietary vendor platforms.

The use of service agents is limited to the service architecture.

Service agents are common in orchestration environments but not within enterprise service bus environments.

None of these statements are true.