S90-04 practice question 14 of 35

SOA projects introduce new considerations that tend to augment the traditional project lifecycle as follows:

Full set: 100 questions
Answer options
A: they tend to introduce the need for more up-front analysis effort Correct answer
B: they tend to require closer collaboration between business and technology experts Correct answer
C: they tend to require a careful prioritization of tactical (short-term) and strategic (long-term) requirements Correct answer
D: they tend to introduce new project roles Correct answer
Correct Answer:
A. they tend to introduce the need for more up-front analysis effort; B. they tend to require closer collaboration between business and technology experts; C. they tend to require a careful prioritization of tactical (short-term) and strategic (long-term) requirements; D. they tend to introduce new project roles
Explanation

SOA projects fundamentally augment the traditional project lifecycle by shifting the focus from building siloed applications to delivering reusable, enterprise-centric services. This strategic shift necessitates:
(A) more extensive up-front analysis to model business domains and identify shareable service candidates;
(B) tighter collaboration between business and IT teams to ensure services accurately represent business logic;
(C) a deliberate governance process to balance immediate project (tactical) needs with long-term enterprise (strategic) goals for reuse and standardization; and
(D) the introduction of new governance-related roles, such as Service Custodian, to manage the service lifecycle and enforce standards.

Why Incorrect

Not applicable, as all listed options are correct augmentations to the traditional project lifecycle introduced by SOA.

References

1. Erl, T. (2005). Service-Oriented Architecture: Concepts, Technology, and Design. Prentice Hall.

For A & B: Chapter 17, "Service-Oriented Analysis," details the increased analysis effort and the necessity of modeling business processes, which requires deep business and technology collaboration (pp. 551-575).

For C: Chapter 19, "Service-Oriented Enterprise," discusses the strategic nature of SOA and the need to align tactical project delivery with long-term enterprise goals (pp. 617-620).

For D: Chapter 20, "SOA Governance," explicitly describes the need for new organizational roles and processes to manage a service-oriented environment, including service ownership and custodianship (pp. 658-661).

2. Erl, T., et al. (2009). SOA Governance: Governing Shared Services and SOA. Prentice Hall.

For C & D: Chapter 5, "Defining SOA Governance," and Chapter 6, "SOA Governance and Service-Orientation," establish the core challenge of balancing tactical and strategic goals and introduce specific roles (e.g., SOA Governance Board, Service Custodian) required to manage this complexity.

Scroll to Top