Users report web connectivity problems on the server (10.1.1.10). Which IP SLA configuration captures the failure details through the network to resolve the issue?
Users report web connectivity problems on the server (10.1.1.10). Which IP SLA configuration captures the failure details through the network to resolve the issue?
To capture failure details related to web connectivity issues, the ideal IP SLA should monitor HTTP traffic, as that is the protocol used for web services. Option B configures an IP SLA operation to issue an HTTP GET request to the server at 10.1.1.10. It uses a frequency of 60 seconds and a timeout of 3000 milliseconds, which are appropriate for monitoring and providing sufficient time for server responses. Thus, this configuration is best suited to capture relevant data and resolve web connectivity problems.
Frequency is in seconds (default 60sec) = (Optional) Sets the rate at which a specified IP SLAs operation repeats. timeout milliseconds is in milliseconds (Default 5000ms) == (Optional) Sets the amount of time an IP SLAs operation waits for a response from its request packet. So based on above the timers look aggressive on D, so B might be better Again, i do not think this is a high quality question, IP SLA seems not be used after an incident, it might be good idea to setup before issues arise.
C looks good also and easier.
nevermind, question states "Users report web connectivity problems" so its B
Keywork "url" is wrong, icmp-echo minimum frequency is 5 second. It's C.