SOA S90.04 Dumps

True

False

the definition of service implementation technology

the grouping of service capability candidates into service candidates

the preliminary identification of service autonomy-related issues

the definition of preliminary service boundaries

True

False

The schema custodian role is typically required where there is an opportunity to establish a separate XML Schema-based data architecture.

The schema custodian role is typically required when documenting service level agreements (SLAs) for service contracts.

The schema custodian role is only required when services are not subjected to design standards.

None of the above.

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.

The technical communications specialist role is usually held by someone with a background in technical writing.

The technical communications specialist is often responsible for expressing discoverability-related information about services in plain English.

The technical communications specialist is responsible for creating design standards.

The technical communications specialist may be expected to refine initial drafts of service profiles and service level agreements.

True

False

The previously delivered services remain in use until they can no longer fulfill their functional requirements, at which point they are retired and replaced with new services based on the final service candidates.

The previously delivered services are later redesigned and redeveloped as per the final service candidates in order to bring the services in the Claims Solution in alignment with the target service inventory blueprint.

The previously delivered services are not changed and the final service candidates serve as a constant reminder as to how they should have been designed.

None of the above.

service architect, enterprise architect, industry standards

service architect, service custodian, industry standards

enterprise architect, enterprise design standards custodian, design standards

policy custodian, governance specialist, design standards

technical service contract, service accessory

service level agreement, service accessory

service registry record, service accessory

None of the above.

Service modeling is a process by which business process logic is decomposed into granular actions that are grouped into technical service contracts.

Service modeling is a process by which business process logic is decomposed into granular actions that are grouped into service candidates.

Service modeling is a process by which business process logic is decomposed into granular actions that are subjected to a service inventory analysis.

None of these statements are true.

Our project team had 3 business analysts collaborate with a service architect and a service analyst during the service-oriented analysis phase.

Our project team had an enterprise architect that provided guidance throughout the service-oriented analysis and service-oriented design phases.

Our project team ended up delivering 3 services and then handed over the service profiles to a service custodian.

All of the above statements make sense.