Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CheckPoint Exam 156-585 Topic 1 Question 36 Discussion

Actual exam question for CheckPoint's 156-585 exam
Question #: 36
Topic #: 1
[All 156-585 Questions]

In Security Management High Availability, if the primary and secondary managements, running the same version of R80.x, are in a state of 'Collision', how can this be resolved?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Kassandra
1 months ago
Collision? More like 'Collusion' if you ask me. These servers are probably just having a secret meeting behind our backs.
upvoted 0 times
...
Salena
1 months ago
Ah, the good old 'fw send synch force' and 'fw get sync quiet' commands. A bit technical, but it might just do the trick.
upvoted 0 times
...
Miesha
1 months ago
Resetting the SIC? That sounds a bit drastic. I hope the other options don't involve breaking things just to fix them.
upvoted 0 times
Cyril
1 days ago
Resetting the SIC? That sounds a bit drastic. I hope the other options don't involve breaking things just to fix them.
upvoted 0 times
...
Glendora
8 days ago
B) The Collision state does not happen in R80.x as the synchronizing automatically on every publish action
upvoted 0 times
...
Joseph
14 days ago
A) Administrator should manually synchronize the servers using SmartConsole
upvoted 0 times
...
...
Sina
2 months ago
C'mon, the Collision state can't just disappear in R80.x. Automatic synchronization is nice, but it doesn't solve everything.
upvoted 0 times
Willodean
24 days ago
D
upvoted 0 times
...
Lashonda
1 months ago
C'mon, the Collision state can't just disappear in R80.x. Automatic synchronization is nice, but it doesn't solve everything.
upvoted 0 times
...
Gracia
1 months ago
A
upvoted 0 times
...
...
Youlanda
2 months ago
I'm not sure, but I think the answer might be D) Run the command 'fw send synch force' on the primary server and 'fw get sync quiet' on the secondary server.
upvoted 0 times
...
Veronique
2 months ago
I disagree, I believe the answer is B) The Collision state does not happen in R80.x as the synchronizing automatically on every publish action.
upvoted 0 times
...
Kindra
2 months ago
I think the answer is A) Administrator should manually synchronize the servers using SmartConsole.
upvoted 0 times
...
Cherelle
2 months ago
Option A seems like the most straightforward solution. I'll make sure to carefully synchronize the servers using SmartConsole.
upvoted 0 times
Patti
24 days ago
It's important to ensure both servers are in sync to avoid any conflicts in Security Management High Availability.
upvoted 0 times
...
Ivette
1 months ago
I agree, manual synchronization using SmartConsole is the recommended method for resolving such issues.
upvoted 0 times
...
Garry
1 months ago
Yes, that's the best way to resolve the 'Collision' state between the primary and secondary managements.
upvoted 0 times
...
Markus
1 months ago
Option A seems like the most straightforward solution. I'll make sure to carefully synchronize the servers using SmartConsole.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77