S90.01 無料問題集「SOA Fundamental SOA & Service-Oriented Computing」

（A）silo-driven

（B）integration-centric

（C）business-driven

（D）inventory-neutral

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

（B）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.

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

（D）You can only create service-oriented solutions as service compositions.

（A）service contracts, service capabilities

（B）service capabilities, service compositions

（C）service compositions, service-oriented solutions

（D）service models, service layers

（A）enterprise-centric business models

（B）enterprise architectures

（C）enterprise resources

（D）enterprise definitions

（A）"Contract first" design is important to SOA because it makes you think about service contract design options at the same time that you are building the underlying service logic.

（B）"Contract first" design is an unproven design technique that is not commonly employed when delivering service-oriented solutions and is therefore not considered important to SOA.

（C）"Contract first" design is important to SOA because without a contract, services cannot be invoked. However, there is no preference as to when, during the service delivery lifecycle, the contract should be designed or established.

（D）"Contract first" design is important to SOA because it forces you to establish standardized service contracts prior to the development of the underlying service logic.

（A）Service compositions can be classified as service-oriented solutions.

（B）Service compositions are aggregates of services that are grouped together to carry out a specific task.

（C）Service compositions are aggregates of non-service-oriented applications that are grouped together and exposed as a service.

（D）Service composition design is not a common consideration with SOA projects. The emphasis of service-orientation is on producing services that are solely optimized for point- to-point data exchange.

（A）20

（B）50

（C）An enterprise service inventory is not comprised of domain service inventories.

（D）70

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

（B）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.

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

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

（A）The top-down approach is chosen. This allows services to be modeled subsequent to their design, thereby enabling each service to be governed by multiple owners.

（B）The established "contract last" approach is chosen, allowing different IT managers to focus on contract-related governance issues after the services are deployed and in use.

（C）Because SOA projects absolutely require enterprise-wide standardization and further demand the creation of an enterprise service inventory, the IT managers have no choice than to cancel the project.

（D）It is decided to proceed with the creation of multiple domain service inventories. This allows collections of services to be independently governed by different owners, while still enabling the IT enterprise as a whole to transition toward SOA.

（A）False

（B）True