When you establish a federated service layer, you end up creating:

Question

Options

• Aa unified set of service contracts for the benefit of those building service consumers
• Ba unified set of service consumer programs for the benefit of those building services to be consumed
• Dall of the above

• A
  82% (14)
• B
  12% (2)
• D
  6% (1)

Explanation

Option A is correct because a federated service layer is an architectural governance model that produces standardized service contracts - shared definitions of how services behave, communicate, and are structured. These contracts primarily benefit service consumers (developers building client applications) by giving them a predictable, unified interface across services from potentially different teams or domains.

Option B reverses the relationship: a federated service layer does not produce consumer programs, and its primary beneficiary is not the service builders - it's the service consumers who gain from the consistency the contracts provide. Option D fails because it requires B to be true, which it isn't.

Memory tip: Think of "federated" like a federation of countries sharing a common legal contract - the contracts are what unify them, and travelers (consumers) benefit by knowing the rules everywhere they go.

No community discussion yet for this question.