Which two use cases are best suited to the RPC style of messaging using Simple Object Access
Protocol (SOAP)?
A.
Processing large sized communication messages
B.
Implementing line grained services
C.
Validating custom data types
D.
Implementing asynchronous web services
E.
Executing long running multi-part processes
I would choose c and d
AE
Developer has not deal with large and complicated message. Automatic conversion via SOAP is beneficial.
AD
AE
RPC : WSDL does not creates separate schema, within the WSDL we can find structure of complex data types.
Advantage: Easy to understand.
Disadvantage:
we can not validate SOAP messages.
tightly coupled
B
Explanation
A is not correct : The responsibility of marshalling and de marshalling lays with SOAP engine, This leads to significant performance degradations when message passed to an operation is large or complex. Hence Processing large sized communication messages cause performance issue.
D is not correct : Usually synchronous in nature.
B is correct answer : fine grained functionalities is better implemented by RPC style web services
E is not correct – because its synchronous communication , long running process will cause performance issue.
No idea about C option
Please check below URL to get more details:
https://towardssoa.wordpress.com/2008/09/12/rpc-style-vs-document-style-web-service/
B and E is correct answer.