What are three best practices that can be implemented when generating WS-I Basic Profile compliant Web services? (Choose three.)
A.
Send arrays of nulls to ensure .NET and Java clients receive the same data.
B.
Define data types early in the integration cycle.
C.
Use complex data types to reduce the number of items exchanged.
D.
Test interoperability at every stage of development.
E.
Insert conformance headers in all SOAP messages.
F.
Keep data types simple for speed and stability.
Why is it important to be WS-I Basic Profile compliant?
Basically, WS-I Basic Profile provides the guidance on how to use together specifications like SOAP, WSDL and UDDI to develop interoperable web services. It is important because otherwise you will limit your target audience. A web service is meant to be connected to other components and having each component be WS-I compliant will make the job easier no matter the platforms, tools, applications or programming languages.
Using a non WS-I compliant web service in a private environment where you use the same technology stack for all components might not end up to be an issue, but when exposing a web service to the public, WS-I Basic Profile is important because it:
will significantly simplify the task of implementing interoperable Web services solutions within and across enterprise boundaries.
http://www.internetnews.com/dev-news/article.php/2247551