Q: 8
Exhibit.
Refer to the exhibit, which shows the SD-WAN rule status and configuration.
Based on the exhibit, which change in the measured packet loss will make HUB1-VPN3 the new
preferred member?
Refer to the exhibit, which shows the SD-WAN rule status and configuration.
Based on the exhibit, which change in the measured packet loss will make HUB1-VPN3 the new
preferred member?Options
Discussion
B . If HUB1-VPN1 hits 12% packet loss, it's out of SLA since the threshold is set to 5%. That kicks it out of the preferred pool, so the device has to move to the next available member that meets the standards. Pretty sure this is standard FortiGate SD-WAN logic with lowest cost and SLA failover. Let me know if I'm missing something.
A is wrong, B. Seen similar logic tested in official practice questions and the admin guides.
Its B. As soon as HUB1-VPN1 gets 12% packet loss, it's way over the 5% SLA and Fortigate will skip it for SD-WAN preferred path. I think this is correct but only if VPN2 is also failing the SLA. Disagree?
C or D? But looking at the exhibit, B is the most logical. Once HUB1-VPN1 has 12% packet loss, it's way past the 5% SLA threshold, so it gets skipped for preferred member selection. Unless VPN2 is still within threshold (which isn't clear), VPN3 would become preferred. Anyone disagree?
B tbh, but is the SLA threshold definitely 5% here or could it be a custom value? If the threshold is different, that could make C or D possible instead.
Makes sense, B is the one. For VPN3 to be chosen, VPN1 needs to go over 5% packet loss and 12% definitely does it. Pretty sure that's what the SD-WAN rule expects here.
Not sure why D is listed in the answer text, but based on similar exam reports the change should be when HUB1-VPN1 exceeds the 5% SLA so B makes sense here.
Yeah, looks like B is right to me. HUB1-VPN1 hitting 12% packet loss puts it out of the SLA (threshold is 5%), so the SD-WAN checks for the next valid path. Unless VPN2 is under threshold, VPN3 gets picked. Anyone think otherwise?
B makes sense. The SD-WAN rule uses lowest cost with an SLA for max 5% packet loss-so once HUB1-VPN1 goes above that (like 12%), it's dropped from eligibility, and the device picks the next lowest (assuming VPN2 also fails). Pretty sure that's how failover logic works in FortiGate SD-WAN. If anyone sees a config detail I missed, let me know.
B Official guide covers this scenario well, and labs help with SD-WAN failover logic.
Be respectful. No spam.
