156-315.76 · Question #614
In a Management High Availability (HA) configuration, you can configure synchronization to occur automatically, when: 1. The Security Policy is installed. 2. The Security Policy is saved. 3. The…
The correct answer is E. 1, 2, 4. See the full explanation below for the reasoning.
Question
Options
- A1, 2, 3
- B1, 2, 3, 4
- C1, 3, 4
- D1, 2, 5
- E1, 2, 4
How the community answered
(16 responses)- B13% (2)
- C6% (1)
- D6% (1)
- E75% (12)
Community Discussion
5
Anjali D.Mar 13, 2026The answer is E, options 1, 2, and 4. Automatic synchronization in Management HA triggers when the Security Policy is installed, when it is saved, or when a scheduled event fires, but option 3 is out because an admin manually switching the secondary to active is not an automatic sync trigger, and option 5 is wrong because installing the user database is not listed among the automatic sync events in the R76 documentation. Anyone in the group who has seen this framed differently on practice tests, please chime in so we can make sure we all have the same understanding before exam day.
Bahar F.Mar 15, 2026Solid breakdown, though worth flagging that the scheduled sync in option 4 only fires if the scheduled synchronization feature is actually enabled in the Management HA configuration, which is off by default in some R76 builds, so candidates should not assume it is always active.
Dejan C.Mar 20, 2026Went with B first because a scheduled sync felt obvious and I figured the admin-status change had to count for something automatic, but then I remembered that flipping the secondary to active is a manual failover step, not a sync trigger, so once you pull item 3 out the only legitimate automatic events left are install, save, and the scheduler, which is exactly E.
Mei-Ling H.Feb 21, 2026I saw this exact question and almost picked B until I went back and circled the word "automatically" in the stem, because option 3 says the administrator manually logs in and changes status to active, which is not automatic at all. Once I crossed out 3 and also crossed out 5 since user database install is not listed as a sync trigger, only E was left standing.
Bahar F.Mar 5, 2026Took this one on my first attempt and almost got burned by option D because I kept second-guessing whether the user database install counted as a sync trigger, but E is the one you want: policy install, policy save, and the scheduled event cover the automatic sync scenarios without any manual admin promotion or user db install muddying the picture. The admin logging in and flipping the secondary to active is a manual failover step, not an automatic sync trigger, and that distinction is exactly what Check Point is testing here.