Last Attempt S90.04 Questions

service analyst

service developer

service custodian

None of the above.

Task and orchestrated task services are often designed after entity and utility services because of their dependency on other services to carry out their service composition logic.

Entity services are designed after task services because entity services have the greatest dependency on other services.

Utility services are often designed before task services because utility services provide agnostic service capabilities that can be leveraged by the service composition logic within task services.

Entity and task services are often designed at the same time because they both contain business logic that needs to be designed after the definition of utility logic.

A service capability candidate can be part of a service candidate.

A service candidate can be part of a service composition candidate.

A service candidate can be part of a service inventory blueprint.

None of these statements are false.

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.