S90-01A · Question #57
An IT enterprise proceeds with an SOA initiative that is based on the creation of a single enterprise service inventory. However, conflicts arise when different IT departments disagree on who will…
The correct answer is B. It is decided to proceed with the creation of multiple domain service inventories. This allows collections. Option B is correct because when enterprise-wide consensus on ownership and governance cannot be reached, splitting the single inventory into multiple domain service inventories is a recognized SOA strategy. Each IT department owns and governs its own domain, eliminating the…
Question
An IT enterprise proceeds with an SOA initiative that is based on the creation of a single enterprise service inventory. However, conflicts arise when different IT departments disagree on who will own the services and how they will be governed. Which of the following alternative approaches could be chosen to address these conflicts?
Options
- AThe top-down approach is chosen. This allows services to be modeled subsequent to their design,
- BIt is decided to proceed with the creation of multiple domain service inventories. This allows collections
- CThe established "contract last" approach is chosen, allowing different IT managers to focus on contract-
- DBecause SOA projects absolutely require enterprise-wide standardization and further demand the
How the community answered
(56 responses)- A9% (5)
- B84% (47)
- C2% (1)
- D5% (3)
Explanation
Option B is correct because when enterprise-wide consensus on ownership and governance cannot be reached, splitting the single inventory into multiple domain service inventories is a recognized SOA strategy. Each IT department owns and governs its own domain, eliminating the territorial conflict while still enabling a structured, service-oriented architecture.
Why the distractors are wrong:
- A is wrong because in a top-down approach, services are modeled before implementation, not subsequent to design - the description is self-contradictory and also doesn't resolve ownership disputes.
- C is wrong because "contract last" is a bottom-up implementation strategy (build logic first, derive the contract after); it addresses development sequence, not departmental ownership or governance conflicts.
- D is wrong because it implies SOA requires full enterprise-wide buy-in with no alternative - this is a false absolute. Domain service inventories are a legitimate fallback precisely when enterprise consensus fails.
Memory tip: Think "domain = department autonomy." When the enterprise can't agree, go smaller - carve the one big inventory into domain-sized pieces so each group governs their own turf. If you see a question about organizational conflict in SOA, domain service inventories are almost always the answer.
Topics
Community Discussion
No community discussion yet for this question.