156-915.76 · Question #202
What process manages the dynamic routing protocols (ospp, RIP, etc) on SecurelPlatform Pro?
The correct answer is A. gated. See the full explanation below for the reasoning.
Question
What process manages the dynamic routing protocols (ospp, RIP, etc) on SecurelPlatform Pro?
Options
- Agated
- Barouted
- Crouterd
- DThere's no separate process, but the Linux default router can take care of that.
How the community answered
(38 responses)- A76% (29)
- B8% (3)
- C13% (5)
- D3% (1)
Community Discussion
7The answer is A, gated. On Check Point SecurePlatform Pro, the gated daemon is the process that handles dynamic routing protocols like OSPF, RIP, and BGP. It runs in the background and manages all the routing protocol interactions, which is why SecurePlatform Pro supports those advanced routing features that the regular SecurePlatform edition does not. The other options are made up, and the idea that Linux handles it natively without a dedicated process is wrong because standard Linux does not ship with full dynamic routing protocol support out of the box.
The correct answer is A, gated. On SecurePlatform Pro, the gated daemon is the process responsible for managing dynamic routing protocols like OSPF, RIP, and BGP. It is a well-known Unix/Linux routing daemon that has been around for decades and Check Point chose it for SecurePlatform Pro specifically because it handles the complexity of running multiple routing protocols simultaneously. The other options are made up, and the idea that Linux handles this on its own without a dedicated process is wrong since you need gated running to participate in dynamic routing.
The answer they are looking for is A, gated, and here is why that matters on the exam. SecurePlatform Pro runs a dedicated daemon called gated, short for gateway daemon, which is the process responsible for handling dynamic routing protocols including OSPF, RIP, and BGP on the platform. The other options are distractors, routerd and arouted are not real processes in this context, and the Linux kernel routing table alone does not manage the protocol negotiation and updates that dynamic routing requires. Gated acts as the intermediary between those protocol conversations and the kernel, which is the distinction Check Point wants you to understand here. Quick question to make sure you have the underlying concept locked in, do you know which configuration file on SecurePlatform Pro you would edit to define the gated settings, and whether changes to that file require a restart of the gated process to take effect? That relationship between the file and the process restart is something this exam has touched on before in different question forms.
Thought B was right, but gated is the actual daemon handling dynamic routing on SecureIPlatform.
Gated is your answer, and I remember the moment clearly because I almost second-guessed myself toward "routerd," which sounds plausible until you remember that SecureIPlatform Pro is built on a hardened Linux core and inherits the classic Unix gated daemon to handle all dynamic routing protocol negotiation, whether that is OSPF, RIP, or BGP. Lock in the mnemonic "G for Gated, G for GNU routing heritage" and this one never trips you up again.
Yep, A is right, gated is the daemon that handles dynamic routing protocols like OSPF and RIP on SecurePlatform Pro. It runs as a background process and Check Point built the platform around it specifically so the gateway could participate in dynamic routing without you having to rely on the base Linux networking stack.
The wording "dynamic routing protocols" alongside that list of examples might make you second-guess yourself if you have ever seen a Linux box handle routing on its own, but option D is there to trap you into conflating basic kernel IP forwarding with a full-featured routing daemon. On SecurePlatform Pro, gated is the dedicated process that handles dynamic routing protocols like OSPF and RIP, so A is your answer.