MuleSoft Developer 2 Certification Practice Exam

The concept tested is how a HTTP Connector handles client authentication when calling a downstream service. In Pass Through mode, the connector does not terminate or modify the client’s authentication. It simply forwards whatever authentication the client provided—such as an Authorization header—to the upstream API. This lets the downstream service enforce its own authentication/authorization using the same credentials, preserving end-to-end identity.

That’s why the option stating that Pass Through forwards authentication to the upstream API is the best fit. The other statements don’t match how Pass Through works: saying it isn’t supported is incorrect, since Pass Through is a valid mode; claiming credentials are forwarded “via TLS only” adds an unnecessary and misleading constraint about TLS rather than the forwarding behavior; and asserting that Pass Through requires OAuth is wrong because the mechanism can forward various types of credentials, not exclusively OAuth.