A typical service-oriented enterprise architecture specification can encompass:

Question

Options

• Aonly one service inventory
• Bmultiple service inventories
• Cnon-service-oriented technology architectures
• DNone of the above.

• B
  92% (33)
• C
  3% (1)
• D
  6% (2)

Explanation

Option B is correct because a service-oriented enterprise architecture (SOA) specification is designed to span large organizations with diverse business domains, making it entirely feasible - and common - to define multiple service inventories, each scoped to a distinct domain or organizational unit (e.g., HR, Finance, Logistics).

Option A is wrong because limiting an enterprise architecture to a single service inventory would be overly restrictive; large enterprises routinely partition services across several inventories for governance, ownership, and scalability reasons. Option C is wrong because SOA specifications, by definition, are centered on service-oriented principles - including non-service-oriented technology architectures would contradict the specification's purpose, even if legacy systems exist in practice.

Memory tip: Think of an enterprise as a city: just as a city has multiple districts (each with its own infrastructure), an SOA enterprise can have multiple service inventories - one per domain. "Enterprise = multiple, not one."

No community discussion yet for this question.