Often It Is a Requirement to Wrap a Legacy System

Multiple Choice

Often it is a requirement to wrap a legacy system with a service. This is typically accomplished by encapsulating calls to the legacy system's Application Programming Interface (API) within the core logic of the service. Care must be taken to not expose details of the underlying API through the service contract as it may unintentionally couple the service consumer to the legacy system. Which pair of service-orientation principles directly addresses this concern? Select the correct answer.

A) Service Loose Coupling, Service Abstraction
B) Service Statelessness, Service Autonomy
C) Service Loose Coupling, Service Statelessness
D) Service Autonomy, Standardized Service Contract