156-816.61 · Question #80
Which process uses an encrypted TCP connection to perform Full Synchronization of VSX Gateways in a cluster?
The correct answer is D. synd. Check Point Exam Code: , Exam Name: Check Point Certified Managed Security Expert - VSX NGX Version: 21.071 , Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at…
Question
Which process uses an encrypted TCP connection to perform Full Synchronization of VSX Gateways in a cluster?
Options
- Acpd
- Bsrd
- Cfwd
- Dsynd
- Evpnd
How the community answered
(49 responses)- A8% (4)
- C2% (1)
- D86% (42)
- E4% (2)
Explanation
Check Point Exam Code: , Exam Name: Check Point Certified Managed Security Expert - VSX NGX Version: 21.071 , Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at any of the email addresses listed below. Any problems about IT certification or our products, you could rely upon us, we will give you satisfactory answers in 24 hours.
Topics
Community Discussion
6D is correct. synd is the synchronization daemon responsible for cluster state sync in VSX, and it uses an encrypted TCP connection specifically for Full Synchronization so that connection table and state data transfers between cluster members are not sent in the clear. The other processes handle things like logging (fwd), general CP communication (cpd), and VPN (vpnd), none of which own the cluster sync job.
synd is the one you want here. It is the synchronization daemon that handles Full Sync between VSX cluster members over an encrypted TCP connection, which is how the gateway state gets replicated cleanly across the cluster.
The stem locks this down for me, encrypted TCP connection for full sync points straight at vpnd, because that process owns the encrypted channel management between cluster members. Strip out the noise around the other daemons and nothing else in that list handles the encryption layer the way vpnd does for VSX gateway-to-gateway communication.
Dervla, I actually think it is D, cpd, because that process owns the SIC-based encrypted TCP channel that carries full sync traffic between VSX cluster members, while vpnd handles VPN tunnel sessions rather than the cluster sync communication itself. My senior pointed that out to me when I mixed those two up the same way on a practice set last week.
Okay so I almost put C for fwd because I remember my senior saying fwd handles a lot of the daemon-level communication and I figured syncing gateways would fall under that. Then I second-guessed myself and looked at cpd because it feels like a central coordination process. What actually clicked for me was going back to the VSX cluster notes where it says synd is specifically the process built to handle state and Full Synchronization between cluster members, and it does it over an encrypted TCP channel, not UDP like the lighter delta sync. So D is right, synd is the answer. Anyone else get tripped up by fwd here or was that just me?
fwd trips almost everyone there because it genuinely does own inter-member communication, but the key is that synd is the dedicated handler for full sync sessions specifically, and if you remember that synd uses TCP while fwd leans on the lighter protocols for its own coordination traffic, the answer locks in fast.