Question 290
A distributed security deployment has this problem: A critical payment application is accidentally handled as generic web traffic because its service port is different from the rule. Which explanation is the best starting point?
Explanation
Correct Answer
The relevant distinction is this: Source, destination, port and application criteria collectively determine traffic matching. Change the affected component by choosing to adjust the payment service match to the documented ports and verify surrounding rules. Evidence of resolution: Only authorized payment sessions reach the high-priority steering rule.
Incorrect Answers
This option serves the scenario “An SD-WAN policy sets one carrier as preferred but operators assume preference guarantees selection even when the member is down”. The relevant distinction is this: Preference applies among eligible routes and members and does not override link failure. The present scenario is distinguished by “Source, destination, port and application criteria collectively determine traffic matching”.
This alternative addresses the separate case “A branch policy refers to an obsolete SD-WAN member even after a new member has been added to its zone”. The relevant distinction is this: Rule membership preferences and eligible interfaces require updating during link replacement. The deciding requirement here is “Source, destination, port and application criteria collectively determine traffic matching”.
The option would apply to “In a Fortinet troubleshooting exercise, A network team assumes SD-WAN decisions for FortiGate-generated syslog traffic use the same policy as forwarded branch client traffic”. The best diagnosis is: Local-out flows can have separate SD-WAN behavior and source-interface settings. This question instead requires “Source, destination, port and application criteria collectively determine traffic matching”.