S90-04 practice question 24 of 35
The Inventory Management System project is delivering a modest solution comprised of three services. The project team is following a bottom-up approach whereby service developers are building the services to fulfill tactical (short-term) requirements. Although not everyone agrees with this approach, it does actually directly support the following service-oriented computing goal:
Full set: 100 questionsThe scenario describes a bottom-up service delivery approach focused on tactical, short-term requirements. This approach prioritizes immediate project-level needs over long-term, enterprise-wide strategic objectives. The goals listed in options A, B, and C are all strategic benefits of service-oriented computing that are realized through careful, often top-down, analysis and design. A tactical, bottom-up approach is generally at odds with these goals, as it tends to produce siloed, non-reusable services that are not aligned with broader business strategy. Therefore, this approach does not directly support any of the listed strategic goals.
A. Increased Intrinsic Interoperability: This strategic goal requires standardized service contracts and a focus on enterprise-wide compatibility, which is typically de-prioritized in a tactical, bottom-up approach focused on immediate integration needs.
B. Increased Business and Technology Alignment: This is a primary goal of a top-down strategy, where business processes are analyzed to derive service models. A bottom-up approach starts from existing technology, often failing to achieve this alignment.
C. Increased Federation: Federation is a strategic objective to unify disparate systems across an enterprise. It requires significant architectural planning and governance, which are contrary to a purely tactical, project-scoped approach.
1. Erl, T. (2008). SOA: Principles of Service Design. Prentice Hall.
Page 498, Section 17.2 (The bottom-up strategy): "The primary emphasis of a bottom-up approach is to deliver services to fulfill immediate business requirements... This approach is considered tactical in nature because it does not require an enterprise-wide, top-down analysis prior to the commencement of service delivery projects." This section clarifies that the bottom-up approach is tactical and contrasts it with the strategic nature of SOA goals.
Page 40, Section 3.2 (Strategic goals of service-oriented computing): This section lists and describes "Increased Intrinsic Interoperability," "Increased Federation," and "Increased Business and Technology Alignment" as key strategic goals that require deliberate, planned effort, which is not characteristic of the described bottom-up project.
Keep practicing
Take the free S90-04 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other S90-04 practice questions
- Question 1When collecting information for the purpose of defining business logic for potential serv…
- Question 2Which of the following statements describe business process steps that are not suitable f…
- Question 3Which of the following is an expected deliverable of successfully completing the service-…
- Question 4The top-down approach is not recommended when:
- Question 5Which of the following is not a valid reason for defining service composition candidates …
- Question 6Which of the following is not a common role on an SOA project?
