S90.01 Fundamental SOA & Service-Oriented Computing Questions and Answers

strategic (long-term), tactical (short-term)

strategic (long-term), unimportant (low priority)

tactical (short-term), unimportant (low priority)

unimportant (low priority), important (high priority)

autonomous, increase

stateless, decrease

scalable, decrease

agnostic, increase

process-specific, process-wide

domain, enterprise

domain, process-specific

enterprise, process-specific

You can only create service-oriented solutions as service compositions.

Services that compose multiple legacy systems can be designed to leverage only the parts of each system that are relevant to the functional context of the service.

Service compositions enable the service-oriented computing goal of Increased Federation by guaranteeing that service endpoints are consistently designed and developed.

Services that can be composed and recomposed support several service-oriented computing goals, including Increased ROI and Increased Organizational Agility.

two

three

one for each business domain

An enterprise service inventory is not comprised of domain service inventories.

Services benefit from up-front analysis because this allows them to be modeled before they are developed and deployed.

Services benefit from design standardization because this supports service-oriented computing goals, such as Increased Intrinsic Interoperability.

Services benefit from a "contract first" approach because this allows the contract to be the first part of the service that is installed and further enables the contract to be subsequently changed without impact to service consumers.

Services benefit from being concurrently invoked by different service compositions because this decreases their performance requirements while increasing their availability.

True

False

it has been built using Web services

it has been built using RPC technologies

it has been performance tested to a meaningful extent

service-orientation has been applied to a meaningful extent

Service-orientation is a design paradigm that must be applied on an enterprise-wide basis in order to be successful.

Service-orientation is a design paradigm comprised of a set of design principles.

Service-orientation is an evolutionary design paradigm that has been influenced by older, established IT paradigms and platforms.

Service-orientation is applied to logic in order to create service-oriented logic.

A natural increase in runtime performance that you will gain as a result of the fact that service compositions will often be comprised of a greater amount of individually participating programs (services) than traditional distributed applications.

The fact that the existing IT organizational structure will not have to change because of how well a service-oriented enterprise fits into traditional IT departmental structures that are focused on project-centric application delivery.

The tactical (short-term) focus of service-orientation, which allows for the initial rapid delivery of services without concerns about their subsequent governance.

The strategic (long-term) target state that is attainable when many of the services delivered are interoperable and reusable, thereby allowing for them to be repeatedly composed in response to new and changing business requirements.

A service inventory establishes a boundary for a collection of services.

Service inventories represent collections of related services that are independently standardized and governed.

The quantity of services within a service inventory will increase as new services that belong within the service inventory boundary are delivered.

Service inventories are ideally planned and modeled ahead of time via the creation of service inventory blueprints.

The statement is incorrect because services should never be delivered by different project teams.

The statement is incorrect because services rely on post-implementation integration effort in order to achieve interoperability, not design standards.

The statement is incorrect because SOA delivery projects require that services be created at exactly the same time in order to guarantee interoperability.

There is nothing wrong with this statement.