A legacy regional planning partner still insists on XML envelope-style remote calls with a formal contract for municipal zoning exchanges. Which web service style are they most likely expecting?
Select an answer to reveal the explanation.
Short Explanation
That partner still talks in formal XML envelopes—the SOAP world. Municipal integrations often keep SOAP around for legacy enterprise partners even when the city prefers REST elsewhere. Matching their contract beats forcing a trendy API they cannot consume.
Full Explanation
SOAP remains a common legacy and enterprise web-service style that uses XML envelopes and explicit contracts (often WSDL) for remote operations. GraphQL, WebSockets, and IoT telemetry protocols serve different use cases. Cloud+ integration topics include recognizing when SOAP is the expected style for partner interoperability.