What condition can the Mule application automatically adjust to or recover from without needing to restart or redeploy the Mule application?

A Mule application uses the Database connector.

What condition can the Mule application automatically adjust to or recover from without needing to restart or redeploy the Mule application?
A . One of the stored procedures being called by the Mule application has been renamed
B . The database server was unavailable for four hours due to a major outage but is now fully operational again
C . The credentials for accessing the database have been updated and the previous credentials are no longer valid
D . The database server has been updated and hence the database driver library/JAR needs a minor version upgrade

Answer: B

Explanation:

* Any change in the application will require a restart except when the issue outside the app. For below situations, you would need to redeploy the code after doing necessary changes

— One of the stored procedures being called by the Mule application has been renamed. In this case, in the Mule application you will have to do changes to accommodate the new stored procedure name.

— Required redesign of Mule applications to follow microservice architecture principles. As code is changed, deployment is must

— If the credentials changed and you need to update the connector or the properties.

— The credentials for accessing the database have been updated and the previous credentials are no longer valid. In this situation you need to restart or redeploy depending on how credentials are configured in Mule application.

* So Correct answer is The database server was unavailable for four hours due to a major outage but is now fully operational again as this is the only external issue to application.