When an API implementation is deployed on CloudHub without configuring automatic restarts in case of worker non-responsiveness, MuleSoft's monitoring and alerting behavior is as follows:
* API Invocation Alerts:
* If no clients are invoking the API, there will be no invocation alerts triggered, as alerts related to invocations depend on actual client requests.
* Implementation-Level Alerts:
* Even without invocation, CloudHub can still monitor the state of the API implementation. If the worker becomes unresponsive, an alert related to the API implementation's health or availability could still be raised.
* Why Option C is Correct:
* This option correctly identifies that no invocation-related alerts would be triggered in the absence of client requests, while implementation-level alerts could still be generated based on the worker's state.
ReferencesFor additional information, check MuleSoft documentation on CloudHub monitoring and alert configurations to understand worker status alerts versus invocation alerts.