Question 280
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A remote finance branch expects its ERP to use MPLS but the SD-WAN rule matches only the old ERP subnet. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, a remote finance branch expects its ERP to use MPLS but the SD-WAN rule matches only the old ERP subnet. The relevant technical mechanism is: A rule cannot select a preferred link for traffic outside its destination match. The most direct diagnostic or implementation action is: Update destination criteria for the current authorized ERP address ranges. A useful verification is: New ERP sessions match the private-transport rule and no unapproved subnets gain access. An ongoing safeguard is: Reconcile destination objects after enterprise application migrations. 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
That safeguard is relevant to: SD-WAN steering decisions require the full traffic match, not destination alone. The current failure instead follows from: A rule cannot select a preferred link for traffic outside its destination match. Its prevention measure is “Reconcile destination objects after enterprise application migrations”.
This routine guards against another mechanism: Rule member eligibility is limited by the specified zone and available paths. The recurring exposure in the current case is: A rule cannot select a preferred link for traffic outside its destination match. The matching preventive check is “Reconcile destination objects after enterprise application migrations”.
That safeguard is relevant to: New application prefixes require consistent routing and tunnel authorization at both ends. The current failure instead follows from: A rule cannot select a preferred link for traffic outside its destination match. Its prevention measure is “Reconcile destination objects after enterprise application migrations”.