S90.04 Project Delivery & Methodology Questions and Answers

If a new utility service candidate is defined, it should be compared with existing utility service candidates to ensure that it does not overlap with previously identified functionality.

If functional overlap between a new entity service and an existing entity service is detected, their respective service capabilities should be reviewed to determine whether they should be combined into one entity service candidate.

When introducing new service inventory candidates into a larger IT enterprise, the existing service inventory boundary needs to be reassessed in order to identify and eliminate potential functional overlap.

If a new service candidate overlaps with the functional boundary of an existing service candidate, the overlap needs to be documented within the respective service profiles so that it can be carefully preserved, as the services will eventually evolve over time.

True

False

When defining service composition candidates you should only focus on the least common runtime scenarios because the most common runtime scenarios are defined during the service development stage.

When defining service composition candidates it is important to ensure that failure conditions that involve exception handling logic are captured.

The scope and complexity of a service composition candidate can help determine whether the eventual service composition should belong to the task service model or the orchestrated task service model.

The identification of service composition candidates may establish additional requirements that could impact the technical architecture of the service inventory (for example, the need to establish a transaction across services).

On our project team, the service registry custodian asked the technical communications specialist to improve the quality and legibility of the service contracts being published.

On our project team, the service developers collaborated with the schema custodian during the service modeling phase to update the service registry records.

On our project team, the policies for three services were authored by the service custodian of one of the three services. This person then handed the policies over to the service registry custodian.

All of the above statements make sense.

entity

hybrid

utility

task

bottom-up

top-down

meet-in-the-middle

round-about

The two service analysts that were working on the latest set of service candidates had a meeting with the governance specialist to get some advice as to the governance implications of a service composition that could be modeled to include four fine-grained services or two coarse-grained services.

The governance specialist was sick today, but since the individual acting as the service developer was available, we had her lead the governance strategy session with the project team. C. The two service analysts that were working on the latest set of service candidates completed the design of the corresponding technical service contracts on the same day.

All of the above statements make sense.

True

False

True

False

logic related to business rules

logic based upon the evaluation of a conditional statement

exception logic that specifies what should occur when an error is detected

composition logic that determines the sequence in which this service needs to compose other services

Service registry record is the name used to distinguish a service profile once its associated service is deployed.

The service profile and the service registry record are always the same document.

Service profiles and service registry records can contain similar types of information. However, their formats are often different because the service registry record format is usually dependent upon the specific service registry product being used.

A service registry record often contains a subset of the information found in a service profile due to the application of the Service Abstraction principle.

service-oriented design

service testing

service discovery

None of the above.