Anypoint MQ implements publish/subscribe fan-out by publishing a message to a message exchange and binding multiple queues to that exchange. Each subscribing application consumes from its own queue. As a result, a single gate-change event published by the Flight Management System can be copied to the Baggage Handler, Inflight Catering, and Passenger Notification queues independently.

MuleSoft documents that messages sent to an exchange are delivered to its bound queues and specifically describes exchanges as the mechanism for distributing one published message to multiple applications. A consumer does not directly consume from the exchange; consumption occurs from a queue. In fact, MuleSoft states that attempts to consume from a message exchange are rejected because the destination for consumption must be a queue.

Having all systems consume from one queue would instead create competing consumers: individual messages would normally be processed by one consumer rather than independently delivered to every subscribing system.

The required architecture is therefore: publisher → exchange → multiple bound queues → independent subscribers. This supplies asynchronous fan-out while preserving subscriber isolation and independent consumption.

Reference topics: Anypoint MQ exchanges; queue bindings; publish/subscribe; asynchronous event distribution.

Official documentation: https://docs.mulesoft.com/mq/

Official documentation: https://docs.mulesoft.com/mq/mq-exchanges

===============================================================

Standard TLS authenticates the server to the client through the server's public certificate. The client validates that certificate against its configured trusted certificate authorities. Mutual TLS extends this process by requiring the client to present its own certificate so that the server can authenticate the client's identity as well.

MuleSoft describes a TLS-enabled server as exposing its public certificate while retaining its private key, and states that TLS clients validate the server certificate against their trusted certificates. For two-way TLS, both keystore and truststore material are configured so that the server can additionally validate certificates presented by clients.

Accordingly, server identity authentication is part of the TLS handshake before completion of the mutual client-authentication exchange. This makes option C the valid statement in the context of the question.

mTLS does not inherently increase the symmetric encryption strength; cipher-suite strength is independent of whether one-way or two-way authentication is used. A hardware security module can be useful for protecting keys but is not mandatory for mTLS. Finally, mTLS authenticates certificate-bearing client identities, not necessarily individual application end users or their business authorization.

Reference topics: TLS; mutual TLS; two-way authentication; keystore; truststore; client certificate authentication.

Official documentation: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration

===============================================================

Reusable global configuration should be packaged once and consumed as a dependency rather than duplicated across individual Mule applications. A shared Mule project/plugin can contain common flows and global elements, including reusable error handlers. Each consuming application then declares the shared artifact as a dependency.

The crucial additional step is that the Mule configuration containing that global error handler must be imported into the consuming application. Simply placing a JAR/plugin on the Maven dependency graph does not automatically make every Mule XML configuration inside that artifact part of the application's active configuration.

MuleSoft currently documents the same pattern through imported project references: a JAR containing a shared Mule project can expose flows, error handlers, and connection configurations, and the consuming project specifies which Mule configuration file to import. Mule's configuration model also supports < import file="..."/ > for merging shared configuration files such as a global error handler.

A Mule domain is not the appropriate CloudHub reuse mechanism in this scenario. Option C is incomplete because it omits the configuration import step.

Reference topics: reusable Mule configurations; Mule plugin/shared project; Maven dependency reuse; configuration imports; global error handlers.

Official documentation: https://docs.mulesoft.com/anypoint-code-builder/int-global-config-elements

===============================================================