Which condition is a primary reason to use SOAP?

• A. Statelessness and microservices simplicity.
• B. High throughput for browser-based apps.
• C. Hardware-accelerated performance advantages.
• D. Legacy system support.

Answer: (D)

SOAP is built for enterprise-grade messaging with formal contracts and interoperability with older, established systems. When you’re integrating with legacy applications that already expect a SOAP interface, you benefit from a defined WSDL, standardized messaging, and built-in features like WS-Security and reliable messaging. Those capabilities are why legacy system support is the primary reason to choose SOAP.

The other scenarios describe REST-like benefits: statelessness and simpler services, optimized throughput for browser-based apps, or hardware-focused performance improvements. Those are not the strengths SOAP is designed to deliver, as SOAP tends to be heavier with XML processing and overhead compared to lightweight REST approaches.