SOA Design & Architecture Set 3

The design principle most associated with an approach whereby the technical interface or contract of a service is designed prior to its underlying logic is:

A company is about to release a service for worldwide usage. As a result, the service contract receives a great deal of attention. After a review it is decided to limit the service contract content to only what is deemed absolutely necessary and to further have the service's Service Level Agreement (SLA) translated into several different languages so that the service can be easily located by those who may want to use it. Which pair of service-orientation principles directly supports these design-time considerations?

Each time our corporate development team makes a change to the service logic it is required to publish a new version of the service contract. Our customers are complaining because their service consumer programs become incompatible with new service contract versions and therefore no longer work. Which of the following service-orientation principles is most likely to help us solve this on-going problem?

When applying the Service Loose Coupling design principle, we want to __________________ the coupling of the service logic to the service contract because that allows the service contract to remain __________________ from the service logic.

Which of the following service-orientation principles support the application of the Service Composability principle? SELECT ALL THAT APPLY

The composition member is the runtime role assumed by a service with a capability that is executing the parent composition logic required to compose capabilities within other services.

Which of the following is not a design characteristic that is realized by the application of the Service Reusability principle?

The service-oriented architectural model is business-driven so that it can stay in alignment with how the business may change over time.

I have a service composition with three services. Service A retrieves a list of country codes from a database and keeps this data in memory while interacting with Service B and Service C. However, because Service A is concurrently invoked many times, and because each instance of Service A loads its own copy of the country code data into memory, the demands on the overall infrastructure become too high and performance and reliability are negatively affected. Which service- orientation principle can be applied to help solve this problem?

Which service-orientation principle would be used to justify a corporate policy that limits or restricts access to technical specifications that show design and technology details about the underlying implementation of a published service?