For Management High Availability, which of the following is NOT a valid synchronization status?
For Management High Availability, which of the following is NOT a valid synchronization status?
For Management High Availability, valid synchronization statuses typically include terms like Synchronized, Lagging, Collision, Never been synchronized, and Advanced. The term 'Down' is not recognized as a valid synchronization status in this context.
Synchronization Status The possible synchronization statuses are: Never been synchronized - Synchronized - Lagging - Collision No "down"
A is correct answer
Should be A. https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk54160#1.4 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.
The question ask NOT VALID option.Since "down" is not including in valid sync status, B is correct answer.
There is no "down" https://support.checkpoint.com/results/sk/sk54160#1.4 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.
Had this question today in exam.
Down is not valid