I Have a Service That Is Required to Access a Shared

Multiple Choice

I have a service that is required to access a shared database. When the load on the database is heavy (for example when the billing department is running reports) my service often times-out and returns a fault to the service consumer. Which service-orientation principle should I apply to address this problem? Select the correct answer.

A) Service Loose Coupling
B) Service Discoverability
C) Service Autonomy
D) Service Reusability