A fundamental means of achieving business and technology alignment in support of service-oriented computing is:

Question

Options

• Athrough the use of a service registry because this allows business and technology-centric services to
• Bthrough the creation of business services because this enables services to encapsulate and express
• Cthrough the use of a business registry because this allows for the centralized registration of business
• Dthrough the creation of a vendor-specific architecture because this supports both the vendor- neutral

• A
  2% (1)
• B
  87% (40)
• C
  9% (4)
• D
  2% (1)

Explanation

Creating business services directly bridges the gap between business intent and technical implementation by expressing real-world business functions as discrete, reusable services - both business stakeholders and IT teams can reason about them using the same vocabulary, which is the essence of alignment in SOA.

Option A is wrong because a service registry is a discovery/catalog tool; it helps locate services but does not itself create conceptual alignment between business and technology concerns.

Option C is wrong because a "business registry" is not a recognized SOA construct - it conflates the idea of a service registry with business-oriented nomenclature without any architectural substance.

Option D is wrong because SOA is explicitly built on vendor-neutrality and interoperability; a vendor-specific architecture introduces lock-in and directly undermines the flexibility SOA is designed to provide.

Memory tip: Think "B for Bridge" - Business services Bridge the gap between business language and technical implementation, which is exactly what alignment means in service-oriented computing.

No community discussion yet for this question.