Question 550
A branch uses Dead Peer Detection on a route-based IPsec VPN. The current operating problem is that the team tests peer liveness only by pinging an internal server. Which response best fits the observed symptoms?
Explanation
Correct Answer
The appropriate control is to check IKE DPD state alongside encrypted application reachability. A remote host's ICMP policy can mislead an otherwise healthy VPN liveness assessment.
Incorrect Answers
Inspect DPD and IKE negotiation events separately from static routing is useful when operators assume a down tunnel implies a missed routing update only. Peer liveness failures and route installation are distinct incident causes.
Review DPD timers and retransmission behavior against measured connectivity addresses a different symptom: DPD triggers constantly during brief planned link jitter and causes unnecessary renegotiation. Overly aggressive peer liveness checks can destabilize a marginal path.
Use an appropriate auto-negotiate or keepalive design if an always-ready SA is required is relevant when a partner VPN has no relevant traffic but on-demand negotiation leaves Phase 2 idle. On-demand SAs may remain inactive until matching protected traffic arrives.