Fortinet NSE6_FNC_AD-7.6 Exam With Confidence Using Practice Dumps

TheUser/Host Profileis the primary mechanism in FortiNAC-F for identifying and categorizing endpoints to determine their level of network access. According to theFortiNAC-F Administration Guide, a profile is built using a combination of criteria that define " Who " is connecting, " What " device they are using, and " Where " they are located on the network.

The three main categories of criteria available in the configuration are:

Host or User Attributes (B):This includes specific details such as the host ' s operating system, the user ' s role (e.g., Employee, Contractor), or custom attributes assigned to the record.

Host or User Group Memberships (A):Profiles can be configured to match endpoints that are members of specific internal FortiNAC groups or synchronized directory groups (like LDAP or Active Directory groups). This allows for broad policy application based on organizational structure.

Location (E):The " Where " component allows administrators to restrict a profile match to specific physical or logical areas of the network, such as a particular switch, a group of ports, or a specific SSID.

Criteria like an " applied access policy " (D) are theoutcomeof a profile match rather than a criterion used to define the profile itself. Similarly, the " Adapter current VLAN " (C) is a dynamic state that changes based on enforcement and is not a standard static identifier used for profile matching.

" User/Host Profiles are used to identify the hosts and users to which a policy will apply. Profiles are created by selecting various criteria in theWho/What(Attributes and Groups) andWhere(Locations) sections. Attributes can include Host Role, User Role, and OS. Group memberships allow matching based on internal or directory-based groups. Location criteria allow for filtering based on the device or port where the host is connected. " —FortiNAC-F Administration Guide: User/Host Profile Configuration.

A FortiNAC-F port can belong to both Forced Registration and Forced Remediation system groups . These enforcement groups are not mutually exclusive and are not evaluated according to a ranking between the groups. Instead, FortiNAC-F determines the applicable enforcement according to the state of each host connected through that point of connection .

The Study Guide explicitly demonstrates overlapping enforcement membership: all Building 1 ports are members of Forced Registration , while second- and third-floor ports are additionally members of Forced Remediation .

FortiNAC-F then applies state-specific logic:

A rogue/unregistered host on the port satisfies Forced Registration and is moved to the Registration isolation network.

An at-risk host on the same port satisfies Forced Remediation and is moved to the Quarantine/Remediation isolation network.

The exhibit is particularly relevant because the highlighted port shows Multiple Hosts connected. Each host is evaluated independently according to its state, so different enforcement mechanisms can apply to different endpoints sharing that port.

Therefore, placing the port in both groups enables both types of enforcement , depending on the state of the connected hosts.

Study Guide Reference: State-Based Control → System Groups; Logic to Determine Isolation; Non-Normal Status Device Evaluation , pp. 212–214 .

Top of Form

Bottom of Form

In FortiNAC-F, the maximum number of conference attendees/accounts is controlled by the Guest & Contractor template , not by the sponsor’s administrative profile. The FortiNAC-F 7.6 Administrator Study Guide states that conference accounts are initiated by a sponsor but automatically generated by FortiNAC-F, and specifically that “the maximum number of attendees is defined within the template.”

The Administration Guide provides the corresponding configuration field: Max Number Of Accounts , which is available when Visitor Type = Conference . Enabling this option allows the administrator to enter the maximum number of accounts that can ever be created using that template. Therefore, a value of exactly 30 can be configured; there is no requirement to use multiples of 25.

The administrative profile instead determines sponsor capabilities such as permitted account types, allowed templates, account-management scope, and maximum account duration. It does not define the numerical conference-account ceiling.

Thus, to enforce a limit of 30 conference accounts, configure Max Number Of Accounts = 30 in the conference Guest & Contractor template .

Study Guide Reference: Guest and Contractor Management → Creating Conference Accounts , pp. 292–302 .