S90-04 practice question 9 of 35
Two service delivery projects are being carried out concurrently. Each project has its own project team. Even though both projects are delivering…
Full set: 100 questionsThe scenario describes a complete lack of SOA governance, where project teams operate in silos despite contributing to a common service inventory. This absence of centralized oversight, standards, and coordination inevitably leads to all the listed consequences. Teams will naturally adopt different design standards, leading to incompatible services (A). Without a shared view of the service portfolio, redundant logic will be developed (B). Furthermore, complete independence allows teams to choose different, and potentially conflicting, delivery methodologies (C). Therefore, all statements describe likely outcomes of this ungoverned approach.
A: This is a correct statement but incomplete. It only addresses the issue of incompatible standards, ignoring the equally likely problems of redundancy and divergent methodologies. B: This is a correct statement but incomplete. It focuses only on redundant logic and overlooks the critical issues of technical incompatibility and inconsistent delivery approaches. C: This is a correct statement but incomplete. While different delivery approaches are a probable result, this option omits the significant consequences of functional redundancy and non-interoperability.
1. Erl, T. (2008). SOA: Principles of Service Design. Prentice Hall.
Page 498, Section 17.2 (What is SOA Governance?): This section explains that SOA governance introduces "control... that would otherwise not exist," preventing the "uncontrolled and unmonitored" proliferation of services. The lack of this control directly leads to the issues described in options A, B, and C.
Page 503, Section 17.3 (Effects of SOA Governance): It is stated that governance helps "avoid the creation of redundant or overlapping services" (addressing option B) and establishes "standardization of service design" (addressing option A).
Page 478, Section 16.2 (Top-down strategy) & Page 482, Section 16.3 (Bottom-up strategy): These sections describe distinct delivery strategies. Without a governing body to align projects, teams are free to choose different approaches independently (addressing option C).
2. Josuttis, N. (2007). SOA in Practice: The Art of Distributed System Design. O'Reilly Media.
Chapter 3, Page 37 (The Need for SOA Governance): The text explicitly warns, "Without any governance, you will end up with a bunch of services that don't fit together, are redundant, and are not what the business needs." This statement directly supports that options A, B, and C are all likely consequences.
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?
