Fortinet FCP_FGT_AD-7.6 Dumps
Fortinet FCP_FGT_AD-7.6 Practice Test 27
Question 260
A regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?
Answer & Explanations
Correct answer: D
The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. This action and check address the distinct objective “Use active authentication when passive identity is unavailable” instead of the stated acceptance requirement. The matching action is to deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility. Its confirming test is to perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.
This action and check address the alternate operation “For the regional airline deployment: Implement: Inspect FSSO learned user, source address, group membership and logoff aging when a…” instead of the stated acceptance requirement. The matching action is to deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility. Its confirming test is to perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.
This action and check address the alternate operation “For the regional airline deployment: Implement: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring…” instead of the stated acceptance requirement. The matching action is to deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility. Its confirming test is to perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.
The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. Implement: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility. Verify: Perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule. This pairing is justified because FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.
Question 261
A shared classroom reassigns DHCP addresses and a former staff identity briefly appears on a student desktop. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?
Answer & Explanations
Correct answer: A
Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. This resolves the issue because a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session. To verify, renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
This option addresses the distinct objective “Use active authentication when passive identity is unavailable”, not the immediate requirement. Active authentication deliberately requests a user identity; a passive identity map requires trusted observation of sign-ins and cannot identify every unmanaged device by inference. For the stated case, a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
This option addresses the distinct objective “Collect Windows logon events for FSSO user mappings”, not the immediate requirement. FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale. For the stated case, a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
This option addresses the distinct objective “Use controlled FSSO troubleshooting rather than global bypass”, not the immediate requirement. FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction. For the stated case, a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
Question 262
A shared classroom reassigns DHCP addresses and a former staff identity briefly appears on a student desktop. The engineer proposes this change: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule Which explanation most accurately establishes why that change meets the operational requirement?
Answer & Explanations
Correct answer: B
That statement explains the distinct objective “Use active authentication when passive identity is unavailable” rather than the cause in this case. The deciding mechanism here is that a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
A firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session. It supports this action: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. To confirm, renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
That statement explains the distinct objective “Collect Windows logon events for FSSO user mappings” rather than the cause in this case. The deciding mechanism here is that a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
That statement explains the distinct objective “Use controlled FSSO troubleshooting rather than global bypass” rather than the cause in this case. The deciding mechanism here is that a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
Question 263
A shared classroom reassigns DHCP addresses and a former staff identity briefly appears on a student desktop. After implementing this change—Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule—which test best establishes that the intended outcome is actually working?
Answer & Explanations
Correct answer: C
This check would help evaluate the distinct objective “Use active authentication when passive identity is unavailable”, but not the required result. For this case, renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
This check would help evaluate the distinct objective “Collect Windows logon events for FSSO user mappings”, but not the required result. For this case, renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
Renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy. This is the relevant test because a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
This check would help evaluate the distinct objective “Use controlled FSSO troubleshooting rather than global bypass”, but not the required result. For this case, renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
Question 264
A shared classroom reassigns DHCP addresses and a former staff identity briefly appears on a student desktop. Which proposed shortcut would most directly cause a privileged policy applied to a stale or incorrect endpoint identity, and therefore must be avoided for this requirement?
Answer & Explanations
Correct answer: D
That shortcut would relate to the distinct objective “Collect Windows logon events for FSSO user mappings”, rather than the specific configuration or use described. The unsafe step in this case is to permanently disable group filtering because stale IP mapping makes authentication seem intermittent.
That shortcut would relate to the distinct objective “Use controlled FSSO troubleshooting rather than global bypass”, rather than the specific configuration or use described. The unsafe step in this case is to permanently disable group filtering because stale IP mapping makes authentication seem intermittent.
That shortcut would relate to the distinct objective “Use active authentication when passive identity is unavailable”, rather than the specific configuration or use described. The unsafe step in this case is to permanently disable group filtering because stale IP mapping makes authentication seem intermittent.
Permanently disable group filtering because stale IP mapping makes authentication seem intermittent. The proposed shortcut bypasses the needed control: A firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session. The appropriate response is to inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule.
Question 265
A shared classroom reassigns DHCP addresses and a former staff identity briefly appears on a student desktop. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?
Answer & Explanations
Correct answer: A
Implement: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Verify: Renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy. This pairing is justified because a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
This action and check address the alternate operation “For the shared classroom reassigns DHCP deployment: Implement: Deploy a supported FSSO collector with the configured DC-agent or other…” instead of the stated acceptance requirement. The matching action is to inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Its confirming test is to renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
This action and check address the alternate operation “For the shared classroom reassigns DHCP deployment: Implement: Inspect FSSO learned user, source address, group membership and logoff aging…” instead of the stated acceptance requirement. The matching action is to inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Its confirming test is to renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
This action and check address the distinct objective “Use active authentication when passive identity is unavailable” instead of the stated acceptance requirement. The matching action is to inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Its confirming test is to renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
Question 266
A call center reports random policy misses after roaming laptops swap wireless VLANs. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?
Answer & Explanations
Correct answer: B
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. This option addresses the distinct objective “Collect Windows logon events for FSSO user mappings”, not the immediate requirement. FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale. For the stated case, a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. This resolves the issue because a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session. To verify, renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. This option addresses the distinct objective “Use controlled FSSO troubleshooting rather than global bypass”, not the immediate requirement. FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction. For the stated case, a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. This option addresses the distinct objective “Use active authentication when passive identity is unavailable”, not the immediate requirement. Active authentication deliberately requests a user identity; a passive identity map requires trusted observation of sign-ins and cannot identify every unmanaged device by inference. For the stated case, a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
Question 267
A call center reports random policy misses after roaming laptops swap wireless VLANs. The engineer proposes this change: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule Which explanation most accurately establishes why that change meets the operational requirement?
Answer & Explanations
Correct answer: C
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. That statement explains the distinct objective “Collect Windows logon events for FSSO user mappings” rather than the cause in this case. The deciding mechanism here is that a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. That statement explains the distinct objective “Use controlled FSSO troubleshooting rather than global bypass” rather than the cause in this case. The deciding mechanism here is that a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. A firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session. It supports this action: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. To confirm, renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. That statement explains the distinct objective “Use active authentication when passive identity is unavailable” rather than the cause in this case. The deciding mechanism here is that a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
Question 268
A call center reports random policy misses after roaming laptops swap wireless VLANs. After implementing this change—Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule—which test best establishes that the intended outcome is actually working?
Answer & Explanations
Correct answer: D
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. This check would help evaluate the distinct objective “Use controlled FSSO troubleshooting rather than global bypass”, but not the required result. For this case, renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. This check would help evaluate the distinct objective “Use active authentication when passive identity is unavailable”, but not the required result. For this case, renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. This check would help evaluate the distinct objective “Collect Windows logon events for FSSO user mappings”, but not the required result. For this case, renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. Renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy. This is the relevant test because a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
Question 269
A call center reports random policy misses after roaming laptops swap wireless VLANs. Which proposed shortcut would most directly cause a privileged policy applied to a stale or incorrect endpoint identity, and therefore must be avoided for this requirement?
Answer & Explanations
Correct answer: A
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. Permanently disable group filtering because stale IP mapping makes authentication seem intermittent. The proposed shortcut bypasses the needed control: A firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session. The appropriate response is to inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. That shortcut would relate to the distinct objective “Use controlled FSSO troubleshooting rather than global bypass”, rather than the specific configuration or use described. The unsafe step in this case is to permanently disable group filtering because stale IP mapping makes authentication seem intermittent.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. That shortcut would relate to the distinct objective “Use active authentication when passive identity is unavailable”, rather than the specific configuration or use described. The unsafe step in this case is to permanently disable group filtering because stale IP mapping makes authentication seem intermittent.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. That shortcut would relate to the distinct objective “Collect Windows logon events for FSSO user mappings”, rather than the specific configuration or use described. The unsafe step in this case is to permanently disable group filtering because stale IP mapping makes authentication seem intermittent.
Question 270
A call center reports random policy misses after roaming laptops swap wireless VLANs. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?
Answer & Explanations
Correct answer: B
This action and check address the alternate operation “For the call center deployment: Implement: Inspect FSSO learned user, source address, group membership and logoff aging when a…” instead of the stated acceptance requirement. The matching action is to inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Its confirming test is to renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. Implement: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Verify: Renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy. This pairing is justified because a firewall identity rule depends on the current user-to-IP and group association; old IP leases or stale collector records can identify the wrong session.
The situation is that a call center reports random policy misses after roaming laptops swap wireless VLANs. This action and check address the distinct objective “Use active authentication when passive identity is unavailable” instead of the stated acceptance requirement. The matching action is to inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Its confirming test is to renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
This action and check address the alternate operation “For the call center deployment: Implement: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring…” instead of the stated acceptance requirement. The matching action is to inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Its confirming test is to renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
FCP - FortiGate 7.6 Administrator (FCP_FGT_AD-7.6) Practice Tests
- Fortinet FCP_FGT_AD-7.6 Practice Test 25 - 10 Questions (Last Reviewed 28-Oct-2026)
- Fortinet FCP_FGT_AD-7.6 Practice Test 26 - 10 Questions (Last Reviewed 27-Oct-2026)
- Fortinet FCP_FGT_AD-7.6 Practice Test 27 - 10 Questions (Last Reviewed 26-Oct-2026)
- Fortinet FCP_FGT_AD-7.6 Practice Test 28 - 10 Questions (Last Reviewed 25-Oct-2026)
- Fortinet FCP_FGT_AD-7.6 Practice Test 29 - 10 Questions (Last Reviewed 24-Oct-2026)