When enterprise-wide standardization is unattainable, multiple domain service inventories may need to be created instead of:

Question

Options

• Amultiple enterprise service inventories
• Ba single enterprise service inventory
• Cmultiple enterprise service registries
• Da single enterprise service registry

• A
  6% (1)
• B
  6% (1)
• D
  88% (14)

Explanation

Option D is correct because the goal of enterprise-wide SOA standardization is to achieve a single enterprise service registry - one unified, centralized catalog governing all services across the organization. When that level of standardization is unattainable (due to political, organizational, or technical barriers), architects must fall back to multiple domain-level service inventories, each governed independently within its own boundary.

Why the distractors are wrong:

• A (multiple enterprise service inventories): Multiple enterprise inventories would be the problem, not the alternative being avoided - you don't replace a registry with more inventories at the enterprise level.
• B (a single enterprise service inventory): Plausible but incorrect in this context; the question is about what the domain inventories substitute for in terms of the originally desired unified structure, which is framed as a registry here.
• C (multiple enterprise service registries): Multiple registries are not the target state; a single unified structure is always the goal, making "multiple" the wrong modifier here.

Memory tip: Think of it this way - "single" and "enterprise" are the two keywords that define the ideal state. The correct answer must have both words, and since the question is contrasting inventories with something else, the answer must use the other noun: registry. "Single enterprise service registry" = the dream; "multiple domain service inventories" = the fallback.

No community discussion yet for this question.