A service inventory is considered to have normalized services when:

Question

Options

• Aits scope does not overlap with any existing databases
• Bservice boundaries within the service inventory do not overlap with each other
• Ceach service within the service inventory is not used by more than one service composition
• Dlegacy systems within the service inventory boundary do not overlap with each other

• A
  4% (1)
• B
  93% (25)
• D
  4% (1)

Explanation

Service inventory normalization means each service has a clearly defined, non-overlapping boundary - just as normalized data tables avoid redundant data, normalized services avoid redundant or conflicting functional scope. Option B is correct because overlapping service boundaries create ambiguity about which service owns a capability, leading to duplication, version conflicts, and governance problems.

Why the distractors are wrong:

• A is wrong because normalization concerns service-to-service boundaries, not database schemas - a service's scope is about its functional domain, not its data layer.
• C describes reusability constraints, not normalization; a service being used by multiple compositions is actually desirable and expected in SOA.
• D is wrong because legacy system boundaries are infrastructure concerns, not the logical service boundary concept normalization addresses.

Memory tip: Think of normalization the same way as database normalization - "no two things should own the same thing." If two services cover the same business function, the inventory isn't normalized.

No community discussion yet for this question.