After implementing the configuration, 172.20.20.2 stops replying to ICMP echos, but the default route fails to be removed. What is the reason for this behavior?

By | December 1, 2022

Refer to the exhibit. After implementing the configuration, 172.20.20.2 stops replying to ICMP echos, but the default route fails to be removed. What is the reason for this behavior?

  • A. The threshold value is wrong.
  • B. The source-interface is configured incorrectly.
  • C. The destination must be 172.30.30.2 for icmp-echo.
  • D. The default route is missing the track feature.
Answer: Option D.
Explanation: 

No answer description available for this question

The post After implementing the configuration, 172.20.20.2 stops replying to ICMP echos, but the default route fails to be removed. What is the reason for this behavior? appeared first on Majanto.