Which module and operation are used to invoke an external SOAP request from a Mule app?

• A. Web Service Consumer module's ConsumeNew operation
• B. HTTP Connector's Request operation
• C. Web Service Consumer module's Consume operation
• D. SOAP Connector's Invoke operation

Answer: (C)

The main idea is to call external SOAP services through a WSDL-defined client. The Web Service Consumer module is designed for this: it reads the service definition from the WSDL and creates a SOAP client that can invoke the remote operation. The Consume operation is the standard way to trigger a specific SOAP operation on that external service, automatically building the SOAP envelope with the correct namespaces, headers, and action, and then returning the mapped response to your flow. This approach hides the low-level SOAP details and ensures the payload matches what the service expects.

Using the HTTP Connector’s Request would require you to manually craft the SOAP envelope and manage SOAP-specific details, which is error-prone. The SOAP Connector’s Invoke could be used for SOAP calls, but the typical, streamlined path for external SOAP invocations in Mule is the Web Service Consumer with Consume. The ConsumeNew variant isn’t the conventional method for invoking a SOAP operation through a WSDL-defined client.