When a dual-DIA WAN Edge's DPI identifies a SaaS app, which behavior occurs?

When a dual-DIA (Direct Internet Access) WAN Edge's Deep Packet Inspection (DPI) identifies a SaaS application, the system leverages its understanding of application performance to make intelligent routing decisions. The correct behavior is that application flows are routed over the best-performing DIA circuit based on real-time path performance metrics. This ensures optimal user experience for SaaS applications by dynamically selecting the most efficient path. Incorrect options: "The gateway WAN Edge accepts DNS for SaaS; noncloud DNS follows the explicit path" is too specific and doesn't capture the primary routing decision based on performance. While DNS resolution is part of the process, the core behavior is about intelligent path selection. "DPI never selects a subperforming DIA circuit for the first application, and the WAN Edge locates the SaaS app" is partially true regarding avoiding subperforming circuits, but it doesn't fully explain the proactive and dynamic routing based on performance for all application flows. "Existing flows change path and drop traffic when the chosen path degrades" describes a reactive behavior to degradation, which can happen, but the primary action for new or ongoing flows is to select the best path proactively, not just reactively drop traffic.