Question 270
An imaginary enterprise networking change reveals: A retail SD-WAN configuration identifies only destination ports and misclassifies web-hosted payment traffic as bulk browsing. Which architectural weakness BEST accounts for this customer outcome?
Explanation
Correct Answer
A retail SD-WAN configuration identifies only destination ports and misclassifies web-hosted payment traffic as bulk browsing. Coarse traffic identification cannot guarantee correct application-based policies for diverse modern flows. Use supported application identification or well-governed custom definitions and verify policy precedence. Representative traces classify each critical workload into the intended steering and QoS group.
Incorrect Answers
A retail SD-WAN configuration identifies only destination ports and misclassifies web-hosted payment traffic as bulk browsing. Unnecessary centralized internet egress may increase latency and consume costly WAN bandwidth, but coarse traffic identification cannot guarantee correct application-based policies for diverse modern flows.
SD-WAN tunnel health alone does not measure the end-user quality of application flows, whereas coarse traffic identification cannot guarantee correct application-based policies for diverse modern flows.
A retail SD-WAN configuration identifies only destination ports and misclassifies web-hosted payment traffic as bulk browsing. Steering alone cannot protect real-time sessions against contention on a congested egress link, while coarse traffic identification cannot guarantee correct application-based policies for diverse modern flows.