Question 360
A FortiOS 7.6 team examines: A helpdesk needs to show whether a denied packet lacks FSSO identity or fails a group restriction. Select TWO complementary choices: the most appropriate corrective action AND the specific evidence confirming success.
Explanation
Correct Answers
The reported FortiOS 7.6 condition is: A helpdesk needs to show whether a denied packet lacks FSSO identity or fails a group restriction. The targeted administrative response is: Compare identity collector events, current workstation addresses, group memberships and FortiGate policy logs before altering FSSO deployment. The relevant failure risk is: Guessing at a firewall address rule may conceal stale logon state or an actual collector synchronization failure. Validate with: After a controlled login and logout sequence the mapping updates and the user policy decision follows current identity.
For the observed situation (A helpdesk needs to show whether a denied packet lacks FSSO identity or fails a group restriction), the most specific acceptance evidence is: After a controlled login and logout sequence the mapping updates and the user policy decision follows current identity. It validates the recommended response: Compare identity collector events, current workstation addresses, group memberships and FortiGate policy logs before altering FSSO deployment. This addresses the documented risk: Guessing at a firewall address rule may conceal stale logon state or an actual collector synchronization failure.
Incorrect Answers
Implicit deny and least privilege (2.1) would demonstrate or implement: Approved protocol tests succeed while unmatched source, destination and service combinations are denied and logged as configured. This choice can be useful for that problem, but it does not establish the Fsso login troubleshooting and stale mappings control being assessed here.
Virtual IP destination nat for inbound services (2.2) would demonstrate or implement: A configured VIP without a matching permit or correct port mapping does not make the backend reachable securely. This case instead tests Fsso login troubleshooting and stale mappings; the choice measures or changes another part of the system.
Interactive user authentication policy design (2.3) addresses another technical failure: Unmatched authentication rules can permit access before identity validation or repeatedly prompt permitted users. The required paired action and test concerns Fsso login troubleshooting and stale mappings; a passing result for this alternative could leave that requirement unresolved.