S90-04 practice question 4 of 35
The top-down approach is not recommended when:
Full set: 100 questionsThe top-down service design approach is characterized by a significant, resource-intensive, up-front analysis phase. This involves analyzing and decomposing enterprise-wide business models and processes to derive a comprehensive service inventory blueprint. This initial investment in time, cost, and specialized skills can be substantial. If an organization operates in a highly volatile market, has limited funding, or cannot justify the potential for the initial investment to be lost due to changing priorities, the associated risk makes the top-down approach unsuitable. In such scenarios, a more agile or iterative approach, like the bottom-up or meet-in-the-middle strategy, is often preferred.
A. The top-down approach is a primary strategy for avoiding silo-based development, as it begins with a holistic, enterprise-level business process view.
B. The deployment target, such as the Web, is an implementation detail that does not influence the strategic choice of a top-down design methodology.
D. Option C provides a valid and critical reason for not recommending the top-down approach, making this "None of the above" option incorrect.
1. Erl, T. (2008). SOA: Principles of Service Design. Prentice Hall.
Page 148, Section 5.3, "Service-Oriented Analysis (The Top-Down Strategy)": The text explicitly states, "A top-down analysis requires a significant amount of upfront analysis... This can translate into a costly and lengthy initial stage for a service-oriented initiative." This directly supports the premise that the investment and effort introduce risk.
2. Erl, T. (2005). Service-Oriented Architecture: Concepts, Technology, and Design. Prentice Hall.
Page 468, Section 16.1, "Introduction to service-oriented design": In comparing design processes, the text describes the top-down approach as requiring a "heavy initial investment" and being potentially "costly and time-consuming," which are the core elements of the risk mentioned in the correct answer.
3. Josuttis, N. (2007). SOA in Practice: The Art of Distributed System Design. O'Reilly Media.
Page 48, Chapter 3, "The SOA Approach": The author discusses the challenges of the top-down approach, noting that "a complete business process analysis is a huge task" and that "the risk of such a project is very high" because business processes may change before the project is even finished. This reinforces the concept of risk associated with the up-front investment.
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 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?
- Question 7The following statements describe logic that is unique to a business process. Which of th…
