Question 630
A FortiSASE operator faces this issue: A security policy uses endpoint tags from a retired compliance rule and blocks newly managed devices. What corrective configuration or investigation is most appropriate?
Explanation
Correct Answer
The focused remedy is: Update references to the approved tag and validate rule-to-policy mappings. The underlying dependency is: Posture tag assignment and consuming access rules must use matching current identifiers. The acceptance check is: Compliant new devices receive access while noncompliant ones remain blocked.
Incorrect Answers
This alternative addresses the separate case “An employee changes from corporate LAN to public Wi-Fi and FortiClient does not switch to the intended off-net steering profile”. The corrective step is: Review on-net/off-net transition rules and test profile switching after network change. The deciding requirement here is “Update references to the approved tag and validate rule-to-policy mappings”.
The option would apply to “A team enables DEM on a small pilot but assumes its latency figures apply to every remote workforce geography”. The corrective step is: Expand supported DEM tests across required regions and critical applications. This question instead requires “Update references to the approved tag and validate rule-to-policy mappings”.
That proposal leaves the central dependency unresolved. The correction is: Update references to the approved tag and validate rule-to-policy mappings. The expected acceptance result is: Compliant new devices receive access while noncompliant ones remain blocked.