During development, what should the developer do to view the request and response traffic to and from the SOAP service when using the Web Service Consumer module's Consume operation?

• A. Enable the built-in SoapTrafficViewer in Anypoint Studio.
• B. Set an async logger for org.mule.service.http.impl.service.HttpMessageLogger to log at DEBUG level in the log4j2.xml file.
• C. Disable all loggers to minimize overhead.
• D. Use the HTTP Requester to capture traffic.

Answer: (B)

Viewing SOAP traffic during development comes from logging the HTTP messages that flow through the Web Service Consumer. The best approach is to enable an asynchronous logger for the HTTP message logger class (org.mule.service.http.impl.service.HttpMessageLogger) at DEBUG level in your log4j2.xml. This logger prints the HTTP request and response payloads, so you can see the exact SOAP envelopes being sent and returned. Using an AsyncLogger helps keep the overhead low while still capturing the necessary details. Other options don’t provide reliable visibility: there isn’t a built‑in SoapTrafficViewer in Studio for this purpose; disabling all loggers would hide the traffic you need to inspect; and the HTTP Requester isn’t a logging mechanism.