SOA Technology Concepts Set 1

solution logic that can only be accessed via HTTP methods ✘ solution logic accessible via binary RPC protocols ✘ solution logic that has been shaped by service-orientation design principles ✘ solution logic that can be accessed via a published WSDL definition ✔

The WS-I is an industry standards organization that provides basic profiles to help foster interoperability among solutions based on XML and Web services
industry standards. ✘ OASIS is an industry standards organization that has developed a number of important technology specifications, including WS-BPEL and UDDI. ✘ The W3C is a standards organization that has developed a number of important technology specifications, including SOAP, WSDL, and WS-Addressing. ✘ The OAS-C is an industry standards organization that has developed a number of important technology specifications, including WS-Security and XML Schema. ✔

When using WS-AtomicTransaction, services participating in a transaction vote on the outcome so as to communicate whether the transaction should be rolled
back or committed. ✘ When using WS-AtomicTransaction, services participating in a transaction use RPC protocols to communicate transaction results, so as to communicatewhether the transaction should be rolled back or committed. ✘ When using WS-AtomicTransaction, services participating in a transaction rely on the use of WS-Policy definitions to confirm the transaction results. ✘ When using WS-AtomicTransaction, services do not actually participate in a transaction. This specification governs intra-service transactions (transactions thatoccur within a service boundary) only. WS-BusinessActivity provides cross-service transaction protocols. ✔

WSDL definition HTTP definition XML schema WS-Policy definition

I built 3 SOAP-based Web services, each of which has its own published WSDL definition. 2 of the WSDL definitions share the same XML schema. ✘ I built 3 XML schemas, two of which are being shared by the same WSDL definition. ✘ I built 3 WSDL definitions and 3 XML schemas. Each WSDL definition is associated with its own XML schema. ✘ All of the above statements make sense. ✔

SOAP ✘ HTTP ✘ WSDL ✘ All of the above. ✔

REST services primarily rely on the use of SOAP headers to exchange message metadata. ✘ REST services primarily rely on the use of JMS headers to exchange message metadata. ✘ REST services primarily rely on the use of HTTP headers to exchange message metadata. ✘ REST services do not exchange messages with headers. ✔

WS-ReliableMessaging establishes a framework that provides an industry-standard means of transforming XML schema-based data models. ✘ WS-ReliableMessaging establishes a framework that provides an industry-standard means of rolling back changes that occur during a runtime servicetransaction. ✘ WS-ReliableMessaging establishes a framework that provides an industry-standard means of reliably communicating policy enforcement rules. ✘ None of these statements are true. ✔

technology protocol bridging requirements (such as when .NET and Java components need to speak to each other) ✘ data model transformation requirements (such as when similar data based on different XML schemas needs to be exchanged) ✘ layer transformation requirements (such as when data located in different architectural layers needs to be exchanged between architectural layers) ✘ service transformation requirements (such as when two versions of the same service exist) ✔

1 ✘