What happens to database polling and HTTP request handling in the time after the primary (master) node of the cluster has failed, but before that node is restarted?

Refer to the exhibit.

A Mule application is deployed to a cluster of two customer-hosted Mule runtimes. The Mule application has a flow that polls a database and another flow with an HTTP Listener.

HTTP clients send HTTP requests directly to individual cluster nodes.

What happens to database polling and HTTP request handling in the time after the primary (master) node of the cluster has failed, but before that node is restarted?
A . Database polling stops All HTTP requests are rejected
B . Database polling stops All HTTP requests continue to be accepted
C . Database polling continues Only HTTP requests sent to the remaining node continue to be accepted
D . Database polling continues All HTTP requests continue to be accepted, but requests to the failed node incur increased latency

View Answer

Answer: A