An administrator wants to use FortiNAC-F to prevent internal engineers from accessing specific websites as...

The correct answer is C . FortiNAC-F security automation does not rely only on a trigger and action. After a security alert is received and the security trigger is satisfied, FortiNAC-F can also evaluate an associated user/host profile before generating the security alarm and executing the action. The study guide explains that user/host profiles are the same profiles used by security policies and are used in security rules to leverage “who, what, where, and when” visibility information. This is exactly what the question requires: the rule must apply specifically to internal engineers , not every user who triggers the FortiGate web-filter category event.

A compliance policy is wrong because compliance policies evaluate endpoint health, posture, scans, or agent results; they do not scope FortiGate web-filter-triggered automation to a user population. A firewall policy is configured on FortiGate, not as the FortiNAC-F-side matching condition in the security rule. A profiling method is also wrong because profiling methods classify rogue or unknown devices, such as printers, cameras, or phones; they do not identify internal engineers for a security automation workflow. The user/host profile is the correct FortiNAC-F object because it lets the same FortiGate security trigger produce a different response depending on the matched user, host, group, location, or ownership context.