Answer D. Synchronization Status The possible synchronization statuses are: Never been synchronized - immediately after the Secondary Security Management server has been installed it has not yet undergone the first manual synchronization that brings it up to date with the Primary Security Management server. Synchronized - the peer is properly synchronized and has the same database information and installed Security Policy Lagging - the peer Security Management Server has not been synchronized properly. For instance, on account of the fact that the Active Security Management Server has undergone changes since the previous synchronization (objects have been edited, or a Security Policy has been newly installed), the information on the Standby Security Management Server is lagging. Advanced - the peer Security Management Server is more up-to-date. Collision - the Active Security Management Server and its peer have different installed Security Policies and databases. The administrator must perform manual synchronization, and decide which of the Security Management Servers to overwrite.

D Down is not a state of management HA

Answer is D

Correct answer is D "down"

D is correct