During a weekend failover rehearsal, an administrator wants deterministic interface preference rather than autonomous best-latency selection. What should the FortiGate administrator change to meet the stated requirement?
Configure a manual SD-WAN rule with appropriate interface preference and availability behavior. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. This corrects the FortiGate behavior described by the specific manual SD-WAN rule preference 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 manual SD-WAN rule preference; the recommended correction addresses that dependency.
The proposed setting concerns performance SLA active probes, not the actual source of failure. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. It would leave the cited symptom unresolved.
This correction targets SD-WAN DSCP-specific prioritization. SD-WAN can apply application and DSCP-aware steering rules to different traffic classes. It does not repair the stated manual SD-WAN rule preference condition: an administrator wants deterministic interface preference rather than autonomous best-latency selection.
A research institute discovers a FortiGate control gap during a configuration recovery exercise: a secure application must prefer a designated WAN member while falling back only when it becomes unusable; additionally, an administrator wants deterministic interface preference rather than autonomous best-latency selection. Which targeted correction should the team implement?
Configure a manual SD-WAN rule with appropriate interface preference and availability behavior. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. This corrects the FortiGate behavior described by the specific manual SD-WAN rule preference fault.
This correction targets best quality SD-WAN. SD-WAN best-quality strategy compares measured link metrics when choosing eligible members. It does not repair the stated manual SD-WAN rule preference condition: a secure application must prefer a designated WAN member while falling back only when it becomes unusable.
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 manual SD-WAN rule preference; the recommended correction addresses that dependency.
The proposed setting concerns SD-WAN implicit rule, not the actual source of failure. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. It would leave the cited symptom unresolved.
The public library system team is verifying its fix for an incident where a secure application must prefer a designated WAN member while falling back only when it becomes unusable. Which specific observation most convincingly demonstrates the required FortiGate behavior?
Traffic follows the preferred healthy member and moves to the intended backup during a controlled failure. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. This is directly observable evidence for the manual SD-WAN rule preference requirement, rather than a generic appliance-health indicator.
That observation is a useful test for SD-WAN SLA failover, but not decisive proof of manual SD-WAN rule preference. SLA pass/fail state helps select viable paths rather than merely up/down interface state. The recorded acceptance check must demonstrate the actual requirement.
A result about SD-WAN link recovery can be true while the manual SD-WAN rule preference defect persists. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. It does not validate the tested dependency.
That observation is a useful test for best quality SD-WAN, but not decisive proof of manual SD-WAN rule preference. SD-WAN best-quality strategy compares measured link metrics when choosing eligible members. The recorded acceptance check must demonstrate the actual requirement.
After an incident-response triage, administrators correct a problem where an administrator wants deterministic interface preference rather than autonomous best-latency selection. Which test result should their acceptance record contain?
Traffic follows the preferred healthy member and moves to the intended backup during a controlled failure. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. This is directly observable evidence for the manual SD-WAN rule preference requirement, rather than a generic appliance-health indicator.
This verifies a different control: SD-WAN implicit rule. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. 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 manual SD-WAN rule preference defect persists. SD-WAN selection still relies on a valid route and firewall policy for the traffic. It does not validate the tested dependency.
This verifies a different control: application-aware steering. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The stated incident requires evidence of its own packet, identity or policy behavior.
An auditor reviewing a factory network deployment finds that a secure application must prefer a designated WAN member while falling back only when it becomes unusable. The team claims this is resolved; which concrete evidence would substantiate that claim?
Traffic follows the preferred healthy member and moves to the intended backup during a controlled failure. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. This is directly observable evidence for the manual SD-WAN rule preference requirement, rather than a generic appliance-health indicator.
A result about application-aware steering can be true while the manual SD-WAN rule preference defect persists. Ordered SD-WAN service rules can steer selected applications based on classification and link conditions. It does not validate the tested dependency.
That observation is a useful test for SD-WAN link recovery, but not decisive proof of manual SD-WAN rule preference. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. The recorded acceptance check must demonstrate the actual requirement.
This verifies a different control: SD-WAN zone-based policy. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The stated incident requires evidence of its own packet, identity or policy behavior.
If a retail logistics company leaves the following FortiGate issue unresolved—a secure application must prefer a designated WAN member while falling back only when it becomes unusable—what is the most direct operational or security consequence?
Automatic load sharing can violate a required deterministic primary-path preference. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The described exposure follows from leaving the manual SD-WAN rule preference dependency unresolved.
It would be a concern if application-aware steering were misconfigured. Here Manual SD-WAN rules let administrators specify eligible outgoing interface preference. 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 manual SD-WAN rule preference unresolved.
That risk is associated with SD-WAN implicit rule rather than the failing manual SD-WAN rule preference dependency. SD-WAN explicit service rules are evaluated before applicable implicit/default forwarding behavior. The present scenario establishes a different causal exposure.
During a segmentation review, engineers discover that an administrator wants deterministic interface preference rather than autonomous best-latency selection. What specific failure risk follows if the underlying fault remains?
Automatic load sharing can violate a required deterministic primary-path preference. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The described exposure follows from leaving the manual SD-WAN rule preference dependency unresolved.
It would be a concern if SD-WAN link recovery were misconfigured. Here Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The selected alternative does not follow from the observed fault.
That risk is associated with best quality SD-WAN rather than the failing manual SD-WAN rule preference dependency. SD-WAN best-quality strategy compares measured link metrics when choosing eligible members. The present scenario establishes a different causal exposure.
It would be a concern if SD-WAN implicit rule were misconfigured. Here Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The selected alternative does not follow from the observed fault.
A post-incident review at an international service desk identifies that a secure application must prefer a designated WAN member while falling back only when it becomes unusable. The same control is still uncorrected. Which exposure should the risk register record?
Automatic load sharing can violate a required deterministic primary-path preference. Manual SD-WAN rules let administrators specify eligible outgoing interface preference. The described exposure follows from leaving the manual SD-WAN rule preference dependency unresolved.
This describes a separate best quality SD-WAN failure. SD-WAN best-quality strategy compares measured link metrics when choosing eligible members. It does not identify the most direct consequence of leaving manual SD-WAN rule preference unresolved.
That risk is associated with SD-WAN link recovery rather than the failing manual SD-WAN rule preference dependency. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. The present scenario establishes a different causal exposure.
This describes a separate SD-WAN route eligibility and gateway failure. SD-WAN selection still relies on a valid route and firewall policy for the traffic. It does not identify the most direct consequence of leaving manual SD-WAN rule preference unresolved.
At a distributed engineering campus running FortiOS 7.6, after an ISP recovers, SD-WAN health remains failed and traffic never returns to the restored link. Which configuration or investigative change most directly resolves this issue?
Correct the performance SLA probe server or thresholds and verify link recovery behavior. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. This corrects the FortiGate behavior described by the specific SD-WAN link recovery fault.
This correction targets SD-WAN implicit rule. SD-WAN explicit service rules are evaluated before applicable implicit/default forwarding behavior. It does not repair the stated SD-WAN link recovery condition: after an ISP recovers, SD-WAN health remains failed and traffic never returns to the restored link.
Changing this could help when the fault is SD-WAN route eligibility and gateway, because sD-WAN selection still relies on a valid route and firewall policy for the traffic. Here the evidence instead identifies SD-WAN link recovery; the recommended correction addresses that dependency.
The proposed setting concerns manual SD-WAN rule preference, not the actual source of failure. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. It would leave the cited symptom unresolved.
During a quarterly security audit, active probes use an obsolete target that no longer responds although the circuit is healthy. What should the FortiGate administrator change to meet the stated requirement?
Correct the performance SLA probe server or thresholds and verify link recovery behavior. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. This corrects the FortiGate behavior described by the specific SD-WAN link recovery fault.
The proposed setting concerns SD-WAN route eligibility and gateway, not the actual source of failure. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. 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 link recovery condition: active probes use an obsolete target that no longer responds although the circuit is healthy.
Changing this could help when the fault is SD-WAN implicit rule, because sD-WAN explicit service rules are evaluated before applicable implicit/default forwarding behavior. Here the evidence instead identifies SD-WAN link recovery; the recommended correction addresses that dependency.
A multi-site university discovers a FortiGate control gap during a segmentation review: after an ISP recovers, SD-WAN health remains failed and traffic never returns to the restored link; additionally, active probes use an obsolete target that no longer responds although the circuit is healthy. Which targeted correction should the team implement?
Correct the performance SLA probe server or thresholds and verify link recovery behavior. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. This corrects the FortiGate behavior described by the specific SD-WAN link recovery fault.
The proposed setting concerns best quality SD-WAN, not the actual source of failure. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. It would leave the cited symptom unresolved.
Changing this could help when the fault is SD-WAN SLA failover, because sLA pass/fail state helps select viable paths rather than merely up/down interface state. Here the evidence instead identifies SD-WAN link recovery; the recommended correction addresses that dependency.
The proposed setting concerns application-aware steering, not the actual source of failure. SD-WAN health status drives eligible route use and must measure a meaningful reachable target. It would leave the cited symptom unresolved.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
