As shown in the figure, the firewall is active and backup in a backup network. By checking the HRP status on firewall A, the following information is obtained: Which of the following is not a…

Question

Options

• AThe heartbeat cable is not included in the safe area
• BThe peer does not enable dual-machine hot backup function
• CThe peer does not specify a heartbeat port
• DAll business interfaces on firewall B are faulty

• A
  3% (1)
• B
  13% (4)
• C
  7% (2)
• D
  77% (23)

Explanation

Option D is the correct answer because HRP (Hot Redundancy Protocol) heartbeat communication operates over a dedicated heartbeat link, completely independent of the business interfaces. Even if every business interface on Firewall B were to fail simultaneously, the heartbeat connection could still function normally, meaning HRP status on Firewall A would remain unaffected by that condition.

Options A, B, and C are all genuine causes: if the heartbeat interface isn't assigned to a security zone (A), HRP packets get dropped by the firewall's own policy; if the peer hasn't enabled the HRP function (B) or hasn't designated a heartbeat port (C), the two firewalls simply cannot establish the protocol handshake, all of which would produce the abnormal HRP status shown on Firewall A.

Memory tip: Separate the "heartbeat path" from the "business path" in your mind - HRP only cares about its own dedicated channel. Any answer involving business interface failures cannot break HRP, making D the odd one out.

No community discussion yet for this question.