When running Cloud Bees Core on traditional platforms, what happens when a fail over lakes place on a High Availability configured Client Master?

When running Cloud Bees Core on traditional platforms, what happens when a fail over lakes place on a High Availability configured Client Master?
A . Users will notice that builds in progress on the failed node are lost but they will not notice any downtime on the service because the sessions and workload are shared between participating Client Master nodes; we have an active-active HA setup.
B . Users will not notice anything because participating Master nodes share workloads together; we have an active-active HA setup.
C . Users will experience a brief downtime, comparable to the time required to reboot a Jenkins master in a non-HA setup. Freestyle builds that were in progress are lost, but Pipeline builds will resume when the secondary master is online; we have an active passive setup.
D . Users will not notice anything because the sessions are shared between participating Client Masters and the $JE NKINS HOME directory of the failed Client Master Is copied to resume the failed master’s work; we have an active passive setup.

View Answer

Answer: C