Service-oriented computing advocates a concept based on the creation of a service layer with standardized and unified endpoints (service contracts) while allowing individual service implementations…

Question

Options

• Ainteroperability
• Btransformation
• Cfederation
• Disolation

• A
  10% (4)
• B
  5% (2)
• C
  69% (27)
• D
  15% (6)

Explanation

Federation (C) describes exactly this SOA principle: a single, standardized service contract layer that unifies how services are accessed, while the backend implementations remain heterogeneous and independently governed - like a common storefront hiding different internal systems.

Why the distractors are wrong:

• Interoperability (A) is a capability (the ability of systems to work together), not the architectural concept of unified contracts over disparate implementations.
• Transformation (B) refers to converting data between formats/protocols - a mechanism, not a governance model.
• Isolation (D) is nearly the opposite: it emphasizes keeping services separated, not unified under a shared contract layer.

Memory tip: Think of a real-world federation like the United States - each state has its own laws and governance (disparate implementations), but they all operate under one Constitution (standardized contract). In SOA, federation = one contract, many backends.

No community discussion yet for this question.