What is true about the connector reconnection strategy in Mule?

• A. It always retries immediately until success.
• B. There is no option to fail deployment if reconnection fails.
• C. A failsDeploy attribute can throw an exception if reconnection attempts fail and prevent startup.
• D. By default a failed connectivity test is logged and the application continues to run without trying to reconnect.

Answer: (D)

When Mule checks a connector’s connectivity at startup, the behavior you’ll observe is governed by the reconnection strategy. By default, if the connectivity test fails, Mule logs the issue and allows the application to keep running without attempting automatic reconnects. This makes the statement true: a failed connectivity test is logged and the application continues to run without trying to reconnect.

There are ways to change this behavior (to fail startup or to configure retries), so the other options don’t fit as the default behavior. The default is not endless immediate retries, and while you can enable startup failure under certain configurations, that isn’t the default mode.