Which statement completes the following sentence about SOA requirements? SOA requirements differ from traditional project requirements because SOA requirements...

• A. May be implemented by existing applications, applications that are being developed, or proposed applications that have not yet been delivered.
• B. Once handed to a project by the business, can be purely managed by that project.
• C. Are realized by shared Services which are not owned by any single application, consist of their own lifecycle, and are managed independently.
• D. Should only be managed by a SOA centre of excellence.
• E. Are focused on defining the integration points between applications,

View the exhibit to see the time invested to deliver a SOA Payment Service. Whatare the predicted net hourssaved per consumer, assuming a consumption factor of 20% and a production investment of 200%?

• A. 328 hours
• B. 205 hours
• C. 41 hours
• D. \Users\USERSEN3\Desktop\Untitled.jpg
• E. 164 hours
• F. 410 hours

A project manager has come to you as the SOA architect asking why his Service Candidate has to be justified before he can build it. What two reasons are you going to give that it is important that Services must be justified before they are implemented?

• A. No control over Service creation can result in Service proliferation resulting in a complex and inconsistent SOA that is difficult to manage and maintain.
• B. The Services must be implemented by a single team and the Justification process prevents otherteams from creating Services.
• C. The release of the Service needs to be co-ordinated with other projects and therefore his project will not be delivering it because the timescales are incompatible.
• D. SOA Services incur greater costs over their full lifecycle than application components and therefore must justify the extra investment before they are built.

Whether from new/changing business requirements or technical optimizations, your Services are bound to change and evolve over time. The lack of a Service versioning strategy will greatly impact the flexibility of your SOA initiative as it will severely hinder Service evolution. Which three principles should be part of a Service versioning strategy?

• A. Concurrent versions of a Service must always be deployed on the same physical server.
• B. Service providers must be able to release new versions into production without waiting for consumers to certify on them.
• C. Service consumers should not require code modifications in order to access the latest compatibleService versions.
• D. A new version of a Service must be developed using the same technology (for example, Java) thatthe original Service was developed in.
• E. Consumers must be able to test and certify on new Service versions before switching to the newversion in production.