A post-incident review at a supply-chain company identifies that both WAN interfaces show physical link up even though one ISP drops application packets intermittently. The same control is still uncorrected. Which exposure should the risk register record?
SD-WAN can keep sending applications through an unusable Internet path when only carrier state is checked. Performance SLAs measure path quality rather than merely physical interface status. The described exposure follows from leaving the performance SLA active probes dependency unresolved.
This describes a separate SD-WAN implicit rule failure. SD-WAN explicit service rules are evaluated before applicable implicit/default forwarding behavior. It does not identify the most direct consequence of leaving performance SLA active probes unresolved.
That risk is associated with manual SD-WAN rule preference rather than the failing performance SLA active probes dependency. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The present scenario establishes a different causal exposure.
It would be a concern if SD-WAN link recovery were misconfigured. Here Performance SLAs measure path quality rather than merely physical interface status. The selected alternative does not follow from the observed fault.
At a customer support center running FortiOS 7.6, two compliant ISPs pass the same voice SLA but finance prefers the cheaper qualified service. Which configuration or investigative change most directly resolves this issue?
Choose the lowest-cost SLA SD-WAN strategy with appropriate member costs and health targets. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. This corrects the FortiGate behavior described by the specific SD-WAN lowest-cost strategy fault.
Changing this could help when the fault is performance SLA active probes, because performance SLAs measure path quality rather than merely physical interface status. Here the evidence instead identifies SD-WAN lowest-cost strategy; the recommended correction addresses that dependency.
The proposed setting concerns best quality SD-WAN, not the actual source of failure. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. It would leave the cited symptom unresolved.
This correction targets SD-WAN SLA failover. SLA pass/fail state helps select viable paths rather than merely up/down interface state. It does not repair the stated SD-WAN lowest-cost strategy condition: two compliant ISPs pass the same voice SLA but finance prefers the cheaper qualified service.
During a post-upgrade smoke test, the business wants FortiGate to select the least-expensive healthy WAN member rather than the lowest RTT one. What should the FortiGate administrator change to meet the stated requirement?
Choose the lowest-cost SLA SD-WAN strategy with appropriate member costs and health targets. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. This corrects the FortiGate behavior described by the specific SD-WAN lowest-cost strategy fault.
Changing this could help when the fault is SD-WAN zone-based policy, because sD-WAN zone policy matching must permit the selected member path after routing decisions. Here the evidence instead identifies SD-WAN lowest-cost strategy; the recommended correction addresses that dependency.
This correction targets SD-WAN route eligibility and gateway. SD-WAN selection still relies on a valid route and firewall policy for the traffic. It does not repair the stated SD-WAN lowest-cost strategy condition: the business wants FortiGate to select the least-expensive healthy WAN member rather than the lowest RTT one.
Changing this could help when the fault is best quality SD-WAN, because sD-WAN best-quality strategy compares measured link metrics when choosing eligible members. Here the evidence instead identifies SD-WAN lowest-cost strategy; the recommended correction addresses that dependency.
A managed services provider discovers a FortiGate control gap during a quarterly security audit: two compliant ISPs pass the same voice SLA but finance prefers the cheaper qualified service; additionally, the business wants FortiGate to select the least-expensive healthy WAN member rather than the lowest RTT one. Which targeted correction should the team implement?
Choose the lowest-cost SLA SD-WAN strategy with appropriate member costs and health targets. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. This corrects the FortiGate behavior described by the specific SD-WAN lowest-cost strategy fault.
The proposed setting concerns SD-WAN route eligibility and gateway, not the actual source of failure. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. It would leave the cited symptom unresolved.
This correction targets SD-WAN SLA failover. SLA pass/fail state helps select viable paths rather than merely up/down interface state. It does not repair the stated SD-WAN lowest-cost strategy condition: two compliant ISPs pass the same voice SLA but finance prefers the cheaper qualified service.
The proposed setting concerns SD-WAN implicit rule, not the actual source of failure. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. It would leave the cited symptom unresolved.
The regional hospital team is verifying its fix for an incident where two compliant ISPs pass the same voice SLA but finance prefers the cheaper qualified service. Which specific observation most convincingly demonstrates the required FortiGate behavior?
Under equal SLA compliance, traffic uses the lower-cost qualified member; an unhealthy member is excluded. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. This is directly observable evidence for the SD-WAN lowest-cost strategy requirement, rather than a generic appliance-health indicator.
That observation is a useful test for manual SD-WAN rule preference, but not decisive proof of SD-WAN lowest-cost strategy. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The recorded acceptance check must demonstrate the actual requirement.
This verifies a different control: SD-WAN zone-based policy. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about SD-WAN route eligibility and gateway can be true while the SD-WAN lowest-cost strategy defect persists. SD-WAN selection still relies on a valid route and firewall policy for the traffic. It does not validate the tested dependency.
After a partner connectivity test, administrators correct a problem where the business wants FortiGate to select the least-expensive healthy WAN member rather than the lowest RTT one. Which test result should their acceptance record contain?
Under equal SLA compliance, traffic uses the lower-cost qualified member; an unhealthy member is excluded. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. This is directly observable evidence for the SD-WAN lowest-cost strategy requirement, rather than a generic appliance-health indicator.
A result about SD-WAN SLA failover can be true while the SD-WAN lowest-cost strategy defect persists. SLA pass/fail state helps select viable paths rather than merely up/down interface state. It does not validate the tested dependency.
That observation is a useful test for manual SD-WAN rule preference, but not decisive proof of SD-WAN lowest-cost strategy. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The recorded acceptance check must demonstrate the actual requirement.
This verifies a different control: SD-WAN link recovery. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. The stated incident requires evidence of its own packet, identity or policy behavior.
An auditor reviewing a public library system deployment finds that two compliant ISPs pass the same voice SLA but finance prefers the cheaper qualified service. The team claims this is resolved; which concrete evidence would substantiate that claim?
Under equal SLA compliance, traffic uses the lower-cost qualified member; an unhealthy member is excluded. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. This is directly observable evidence for the SD-WAN lowest-cost strategy requirement, rather than a generic appliance-health indicator.
A result about application-aware steering can be true while the SD-WAN lowest-cost strategy defect persists. Ordered SD-WAN service rules can steer selected applications based on classification and link conditions. It does not validate the tested dependency.
This verifies a different control: SD-WAN implicit rule. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about manual SD-WAN rule preference can be true while the SD-WAN lowest-cost strategy defect persists. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. It does not validate the tested dependency.
If a cloud operations team leaves the following FortiGate issue unresolved—two compliant ISPs pass the same voice SLA but finance prefers the cheaper qualified service—what is the most direct operational or security consequence?
Choosing a best-quality strategy may consume a higher-cost path when cost is the actual requirement. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. The described exposure follows from leaving the SD-WAN lowest-cost strategy dependency unresolved.
That risk is associated with SD-WAN route eligibility and gateway rather than the failing SD-WAN lowest-cost strategy dependency. SD-WAN selection still relies on a valid route and firewall policy for the traffic. The present scenario establishes a different causal exposure.
It would be a concern if performance SLA active probes were misconfigured. Here Lowest cost (SLA) selects the least-cost link that meets configured quality targets. The selected alternative does not follow from the observed fault.
That risk is associated with manual SD-WAN rule preference rather than the failing SD-WAN lowest-cost strategy dependency. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The present scenario establishes a different causal exposure.
During a planned cutover, engineers discover that the business wants FortiGate to select the least-expensive healthy WAN member rather than the lowest RTT one. What specific failure risk follows if the underlying fault remains?
Choosing a best-quality strategy may consume a higher-cost path when cost is the actual requirement. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. The described exposure follows from leaving the SD-WAN lowest-cost strategy dependency unresolved.
It would be a concern if SD-WAN link recovery were misconfigured. Here Lowest cost (SLA) selects the least-cost link that meets configured quality targets. The selected alternative does not follow from the observed fault.
This describes a separate application-aware steering failure. Ordered SD-WAN service rules can steer selected applications based on classification and link conditions. It does not identify the most direct consequence of leaving SD-WAN lowest-cost strategy unresolved.
That risk is associated with SD-WAN implicit rule rather than the failing SD-WAN lowest-cost strategy dependency. SD-WAN explicit service rules are evaluated before applicable implicit/default forwarding behavior. The present scenario establishes a different causal exposure.
A post-incident review at a retail logistics company identifies that two compliant ISPs pass the same voice SLA but finance prefers the cheaper qualified service. The same control is still uncorrected. Which exposure should the risk register record?
Choosing a best-quality strategy may consume a higher-cost path when cost is the actual requirement. Lowest cost (SLA) selects the least-cost link that meets configured quality targets. The described exposure follows from leaving the SD-WAN lowest-cost strategy dependency unresolved.
That risk is associated with application-aware steering rather than the failing SD-WAN lowest-cost strategy dependency. Ordered SD-WAN service rules can steer selected applications based on classification and link conditions. The present scenario establishes a different causal exposure.
It would be a concern if manual SD-WAN rule preference were misconfigured. Here Lowest cost (SLA) selects the least-cost link that meets configured quality targets. The selected alternative does not follow from the observed fault.
This describes a separate SD-WAN link recovery failure. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. It does not identify the most direct consequence of leaving SD-WAN lowest-cost strategy unresolved.
At an e-commerce platform running FortiOS 7.6, a voice application should use the WAN with the best measured jitter regardless of provider price. Which configuration or investigative change most directly resolves this issue?
Configure a best-quality SD-WAN rule with performance SLA criteria appropriate to voice. SD-WAN best-quality strategy compares measured link metrics when choosing eligible members. This corrects the FortiGate behavior described by the specific best quality SD-WAN fault.
This correction targets SD-WAN route eligibility and gateway. SD-WAN selection still relies on a valid route and firewall policy for the traffic. It does not repair the stated best quality SD-WAN condition: a voice application should use the WAN with the best measured jitter regardless of provider price.
The proposed setting concerns SD-WAN lowest-cost strategy, not the actual source of failure. SD-WAN best-quality strategy compares measured link metrics when choosing eligible members. It would leave the cited symptom unresolved.
This correction targets SD-WAN SLA failover. SLA pass/fail state helps select viable paths rather than merely up/down interface state. It does not repair the stated best quality SD-WAN condition: a voice application should use the WAN with the best measured jitter regardless of provider price.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
