Which is the least ideal Synchronization Status for Security Management Server High Availability deployment?

3 thoughts on “Which is the least ideal Synchronization Status for Security Management Server High Availability deployment?”

1. D is the Correct answer. The question was not , what is ideal, the question was that is the worst Status
   so D Collision is correct

   1

   Reply

2. Tricky question.
   Can anyone explain why – C. Lagging is incorrect? Is Lagging more ideal then Collision?

   Reply

   1. The CCSE R80.10 book states:

      “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 since the Active Security Management Server had changes applied to it.

      Advanced: The peer Security Management Server is more up-to-date.

      Collision: The Active Security Management Server and its peer have different installed policies and/or databases. The System Administrator must perform manual synchronization and decide which of the servers to overwrite. For example, when Security Management Server-A fails before a synchronization takes place, the changes made to databases or to the Security Policy cannot be synchronized with Security Management Server-B. When Security Management Server-B takes over from Security Management Server-A, the System Administrator may decide to modify the Security Policy.”

      From this I also take D to be the correct answer.

      I hope this helps.

      Reply