Which statement accurately describes SOAP's support for formal contracts and reliability features?

• A. SOAP does not support formal contracts.
• B. SOAP is good for formal contracts via WSDL, WS-Reliable messaging, and stateful operations.
• C. SOAP only supports JSON.
• D. SOAP cannot enforce contracts or reliability.

Answer: (B)

SOAP’s ability to support formal contracts and reliability features comes from standards layered on top of the protocol. WSDL provides a formal contract by describing the service interface—what operations are available, the messages exchanged, and how they are bound to protocols and data formats. This makes the interaction between provider and consumer precise and machine-readable. For reliability, WS-ReliableMessaging (a WS-* specification) defines reliable delivery, proper sequencing, and fault handling, so messages can be delivered and retried in a predictable way, which is essential for business-critical integrations. While SOAP can support stateful interactions, HTTP is typically stateless, SOAP services can maintain session context across multiple operations if designed to do so. The claim that SOAP only supports JSON is incorrect since SOAP uses XML payloads, not JSON. Likewise, saying SOAP cannot enforce contracts or reliability ignores WSDL and WS-ReliableMessaging, the mechanisms that provide those capabilities.