S90-01A · Question #61
Below are excerpts from four different SOA adoption strategy documents. Based on your understanding of SOA, service-orientation, and the goals of service-oriented computing, select the adoption…
The correct answer is D. "Our strategy is to make the consistent application of service-orientation principles a priority in order to. Option D is correct because SOA success depends on consistent, organization-wide application of service-orientation principles - reusability, loose coupling, abstraction, composability, etc. - applied as a sustained strategic priority, not a one-off project. Without consistency…
Question
Below are excerpts from four different SOA adoption strategy documents. Based on your understanding of SOA, service-orientation, and the goals of service-oriented computing, select the adoption strategy that is clearly the most likely to succeed:
Options
- A"As part of our planned transition toward service-orientation, we will continue to extend the existing
- B"Each of our existing legacy applications already establishes a domain boundary that is defined by the
- C"Our strategy fully supports the tactical (short-term) nature of service-oriented computing by de-
- D"Our strategy is to make the consistent application of service-orientation principles a priority in order to
How the community answered
(39 responses)- A5% (2)
- B21% (8)
- C10% (4)
- D64% (25)
Explanation
Option D is correct because SOA success depends on consistent, organization-wide application of service-orientation principles - reusability, loose coupling, abstraction, composability, etc. - applied as a sustained strategic priority, not a one-off project. Without consistency across all services and teams, the inventory becomes fragmented and the core benefits (interoperability, reuse) never materialize.
Why the distractors fail:
- A - "Extending existing [legacy applications]" signals building on legacy structures rather than genuinely transforming toward service-orientation; this entrenches old boundaries and technical debt.
- B - Using legacy application boundaries as service boundaries is a classic anti-pattern; those boundaries reflect old technology/organizational silos, not natural business domains, so services inherit the wrong granularity and coupling.
- C - This is the clearest red flag: SOA is explicitly a long-term strategic investment, not a tactical/short-term one. Any strategy describing service-oriented computing as "tactical" fundamentally misunderstands it.
Memory tip: Remember "SOA = Strategic, not Tactical." On exam questions, any option framing SOA as short-term or tactical is wrong. The correct strategy always emphasizes consistent principles applied organization-wide over time - look for those two signals together.
Topics
Community Discussion
No community discussion yet for this question.