Which three factors about SLA targets and SD-WAN rules should you consider when configuring SD-WAN rules? (Choose three.)

Question

Options

• AMember metrics are measured only if a rule uses the SLA target.
• BSLA targets are used only by SD-WAN rules that are configured with a Lowest Cost (SLA)
• CSD-WAN rules can use SLA targets to check whether the preferred members meet the SLA
• DWhen configuring an SD-WAN rule, you can select multiple SLA targets if they are from the same
• EWhen configuring an SD-WAN rule, you can select multiple SLA targets from different

• A
  18% (6)
• B
  73% (24)
• D
  9% (3)

Explanation

The use of SLA targets is specific to certain SD-WAN strategies. The "Lowest Cost (SLA)" and "Maximize Bandwidth (SLA)" strategies are explicitly designed to use the configured SLA targets to make routing decisions. The "Best Quality" strategy uses performance metrics but does not necessarily require or reference SLA targets in the same way, while "Manual" does not use metrics at all for path selection. This is a core function of SD-WAN rules with SLA targets. The purpose of configuring an SLA target with specific thresholds for latency, jitter, and packet loss is to define what is considered "acceptable" performance for an application. SD-WAN rules then use these targets to check if the members (interfaces) meet these requirements before a flow is steered over them, ensuring that a preferred path still offers a good user experience. FortiGate allows for a single SD-WAN rule to reference multiple, different performance SLAs. This is crucial for complex deployments where a single SD-WAN rule needs to handle traffic for multiple applications that have distinct performance requirements. For example, a single rule might direct VoIP traffic based on one performance SLA with strict latency/jitter targets, while simultaneously handling general web traffic using another performance SLA with more lenient

No community discussion yet for this question.