Question 320
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: An enterprise deploys a voice SLA rule but sets loss threshold suitable for file downloads rather than calls. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, an enterprise deploys a voice SLA rule but sets loss threshold suitable for file downloads rather than calls. The relevant technical mechanism is: A correct rule match can still select an unsuitable path when its quality target is wrong. The most direct diagnostic or implementation action is: Update rule qualification with the approved real-time-media SLA. A useful verification is: Voice calls avoid a path that exceeds measured jitter or loss while file downloads remain possible. An ongoing safeguard is: Align steering SLAs with actual business application performance objectives. This is the INTENDED choice for the most useful ongoing preventive control. The issuer documents define the topic and product background, not the truth of this item-level intended key.
Incorrect Answers
The suggested review tracks a different technical risk: Editing a shadowed rule cannot change traffic captured by an earlier matching rule. Here the sustained control must address: A correct rule match can still select an unsuitable path when its quality target is wrong. Choose “Align steering SLAs with actual business application performance objectives”.
That safeguard is relevant to: Jitter alone does not characterize every application's bandwidth needs. The current failure instead follows from: A correct rule match can still select an unsuitable path when its quality target is wrong. Its prevention measure is “Align steering SLAs with actual business application performance objectives”.
This routine guards against another mechanism: Ordered policy decisions can shadow specific entries if a broad match is evaluated first. The recurring exposure in the current case is: A correct rule match can still select an unsuitable path when its quality target is wrong. The matching preventive check is “Align steering SLAs with actual business application performance objectives”.