Which two strategies should their Ops team use to monitor the overall health of the API and database using API Functional Monitoring?

Northern Trail Outfitters is developing an API that connects to a vendor’s database.

Which two strategies should their Ops team use to monitor the overall health of the API and database using API Functional Monitoring? (Choose two.)
A . Monitor the CloudHub worker logs for JDBC database connection exceptions.
B . Make a call to a health-heck endpoint, and then verity that the endpoint is still running.
C . Monitor the Mule worker logs for "ERROR" statements and verity that the results match expected errors.
D . Make a GET call to an existing API endpoint, and then verify that the results match expected data.

View Answer

Answer: B, D

Explanation:

Health-Check Endpoint: Creating and regularly calling a health-check endpoint is a common strategy to ensure that the API and its underlying systems are operational. This endpoint typically performs basic checks such as database connectivity and service availability.

Reference: Health Check Pattern

GET Call to Existing Endpoint: Making a GET call to an existing API endpoint and verifying that the results match expected data helps ensure that the API is not only running but also functioning correctly. This approach validates that the API can retrieve data from the database as intended.

Reference: API Monitoring Best Practices

Monitoring CloudHub Worker Logs: While monitoring logs can be useful, it is more of a reactive approach. Proactive strategies like health-check endpoints and GET calls provide immediate validation of the API’s operational status.

Reference: CloudHub Monitoring

Verifying Mule Worker Logs for Errors: This approach can complement health-check endpoints and GET calls but should not be the primary strategy. Logs are helpful for diagnosing issues after they occur rather than ensuring ongoing health.

Reference: Error Handling and Logging