Practice Exams:

Fortinet FCP_FGT_AD-7.6 Dumps

EXAM: FCP - FortiGate 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

FCP_FGT_AD-7.6 Premium ETE File


  • Premium File 128 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FGT_AD-7.6 Practice Test 26

Question 250

A trade exhibition permits a sponsored guest network only after a temporary portal login. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the trade exhibition deployment: 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.
  2. For the trade exhibition deployment: Implement: Choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source. Verify: Test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint.
  3. For the trade exhibition deployment: Implement: Validate RADIUS server reachability, shared secret, expected ports and user-group match for FortiGate authentication. Verify: Test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint.
  4. For the trade exhibition deployment: Implement: Choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source. Verify: Log in using a test user in the approved group and one outside it, then verify distinct authentication and traffic outcomes.

Answer & Explanations

Correct answer: B

A.

The situation is that a trade exhibition permits a sponsored guest network only after a temporary portal login. This action and check address the distinct objective “Collect Windows logon events for FSSO user mappings” instead of the stated acceptance requirement. The matching action is to choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source. Its confirming test is to test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint.

B.

The situation is that a trade exhibition permits a sponsored guest network only after a temporary portal login. Implement: Choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source. Verify: Test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint. This pairing is justified because 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.

C.

This action and check address the alternate operation “For the trade exhibition deployment: Implement: Validate RADIUS server reachability, shared secret, expected ports and user-group match for FortiGate…” instead of the stated acceptance requirement. The matching action is to choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source. Its confirming test is to test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint.

D.

This action and check address the alternate operation “For the trade exhibition deployment: Implement: Choose a supported active login or captive-portal method for users not already identified…” instead of the stated acceptance requirement. The matching action is to choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source. Its confirming test is to test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint.

Question 251

A manufacturing domain moved to new controllers and firewall FSSO mappings stopped updating. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the manufacturing domain deployment: Choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source.
  2. For the manufacturing domain deployment: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule.
  3. For the manufacturing domain deployment: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility.
  4. For the manufacturing domain deployment: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path.

Answer & Explanations

Correct answer: C

A.

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, FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

B.

This option addresses the distinct objective “Check FSSO group and IP mapping freshness”, not the immediate requirement. 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. For the stated case, FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

C.

Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility. This resolves the issue because FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale. To verify, perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.

D.

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, FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

Question 252

A manufacturing domain moved to new controllers and firewall FSSO mappings stopped updating. The engineer proposes this change: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the manufacturing domain deployment: 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.
  2. For the manufacturing domain deployment: FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
  3. For the manufacturing domain deployment: 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.
  4. For the manufacturing domain deployment: FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

Answer & Explanations

Correct answer: D

A.

That statement explains the distinct objective “Check FSSO group and IP mapping freshness” rather than the cause in this case. The deciding mechanism here is that FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

B.

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 FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

C.

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 FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

D.

FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale. It supports this action: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility. To confirm, perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.

Question 253

A manufacturing domain moved to new controllers and firewall FSSO mappings stopped updating. After implementing this change—Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility—which test best establishes that the intended outcome is actually working?

  1. For the manufacturing domain deployment: Perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.
  2. For the manufacturing domain deployment: Renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.
  3. For the manufacturing domain deployment: Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
  4. For the manufacturing domain deployment: Test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint.

Answer & Explanations

Correct answer: A

A.

Perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule. This is the relevant test because FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

B.

This check would help evaluate the distinct objective “Check FSSO group and IP mapping freshness”, but not the required result. For this case, perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.

C.

This check would help evaluate the distinct objective “Use controlled FSSO troubleshooting rather than global bypass”, but not the required result. For this case, perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.

D.

This check would help evaluate the distinct objective “Use active authentication when passive identity is unavailable”, but not the required result. For this case, perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.

Question 254

A manufacturing domain moved to new controllers and firewall FSSO mappings stopped updating. Which proposed shortcut would most directly cause identity rules missing new users because passive mappings were never learned, and therefore must be avoided for this requirement?

  1. For the manufacturing domain deployment: Permanently disable group filtering because stale IP mapping makes authentication seem intermittent.
  2. For the manufacturing domain deployment: Assume adding an LDAP server alone automatically populates live FSSO user-IP associations.
  3. For the manufacturing domain deployment: Add a top-level allow-any policy whenever the FSSO collector is briefly unavailable.
  4. For the manufacturing domain deployment: Treat a source IP address alone as authenticated identity when no passive sign-on event exists.

Answer & Explanations

Correct answer: B

A.

That shortcut would relate to the distinct objective “Check FSSO group and IP mapping freshness”, rather than the specific configuration or use described. The unsafe step in this case is to assume adding an LDAP server alone automatically populates live FSSO user-IP associations.

B.

Assume adding an LDAP server alone automatically populates live FSSO user-IP associations. The proposed shortcut bypasses the needed control: FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale. The appropriate response is to deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility.

C.

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 assume adding an LDAP server alone automatically populates live FSSO user-IP associations.

D.

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 assume adding an LDAP server alone automatically populates live FSSO user-IP associations.

Question 255

A manufacturing domain moved to new controllers and firewall FSSO mappings stopped updating. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the manufacturing domain deployment: Implement: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Verify: Perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.
  2. For the manufacturing domain deployment: Implement: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility. Verify: Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
  3. For the manufacturing domain deployment: 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.
  4. For the manufacturing domain deployment: Implement: Choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source. Verify: Test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint.

Answer & Explanations

Correct answer: C

A.

This action and check address the alternate operation “For the manufacturing domain 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.

B.

This action and check address the alternate operation “For the manufacturing domain 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.

C.

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.

D.

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.

Question 256

A regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the regional airline deployment: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path.
  2. For the regional airline deployment: Choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source.
  3. For the regional airline deployment: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule.
  4. For the regional airline deployment: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility.

Answer & Explanations

Correct answer: D

A.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. 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, FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

B.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. 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, FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

C.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. This option addresses the distinct objective “Check FSSO group and IP mapping freshness”, not the immediate requirement. 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. For the stated case, FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

D.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility. This resolves the issue because FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale. To verify, perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.

Question 257

A regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. The engineer proposes this change: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the regional airline deployment: FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.
  2. For the regional airline deployment: FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
  3. For the regional airline deployment: 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.
  4. For the regional airline deployment: 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.

Answer & Explanations

Correct answer: A

A.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale. It supports this action: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility. To confirm, perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.

B.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. 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 FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

C.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. 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 FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

D.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. That statement explains the distinct objective “Check FSSO group and IP mapping freshness” rather than the cause in this case. The deciding mechanism here is that FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

Question 258

A regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. After implementing this change—Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility—which test best establishes that the intended outcome is actually working?

  1. For the regional airline deployment: Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
  2. For the regional airline deployment: Perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.
  3. For the regional airline deployment: Test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint.
  4. For the regional airline deployment: Renew a test workstation address, generate a new login, then correlate its live IP, group and matching firewall policy.

Answer & Explanations

Correct answer: B

A.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. This check would help evaluate the distinct objective “Use controlled FSSO troubleshooting rather than global bypass”, but not the required result. For this case, perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.

B.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. Perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule. This is the relevant test because FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale.

C.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. This check would help evaluate the distinct objective “Use active authentication when passive identity is unavailable”, but not the required result. For this case, perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.

D.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. This check would help evaluate the distinct objective “Check FSSO group and IP mapping freshness”, but not the required result. For this case, perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.

Question 259

A regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. Which proposed shortcut would most directly cause identity rules missing new users because passive mappings were never learned, and therefore must be avoided for this requirement?

  1. For the regional airline deployment: Add a top-level allow-any policy whenever the FSSO collector is briefly unavailable.
  2. For the regional airline deployment: Treat a source IP address alone as authenticated identity when no passive sign-on event exists.
  3. For the regional airline deployment: Assume adding an LDAP server alone automatically populates live FSSO user-IP associations.
  4. For the regional airline deployment: Permanently disable group filtering because stale IP mapping makes authentication seem intermittent.

Answer & Explanations

Correct answer: C

A.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. 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 assume adding an LDAP server alone automatically populates live FSSO user-IP associations.

B.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. 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 assume adding an LDAP server alone automatically populates live FSSO user-IP associations.

C.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. Assume adding an LDAP server alone automatically populates live FSSO user-IP associations. The proposed shortcut bypasses the needed control: FSSO relates domain logon events and directory groups to client IP identities; missing collector reachability or event ingestion leaves identity mapping stale. The appropriate response is to deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility.

D.

The situation is that a regional airline wants domain workstation access grouped by Windows logon rather than repeated captive portal requests. That shortcut would relate to the distinct objective “Check FSSO group and IP mapping freshness”, rather than the specific configuration or use described. The unsafe step in this case is to assume adding an LDAP server alone automatically populates live FSSO user-IP associations.

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?

  1. For the regional airline deployment: Implement: Choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source. Verify: Test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint.
  2. For the regional airline deployment: Implement: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Verify: Perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.
  3. For the regional airline deployment: Implement: Deploy a supported FSSO collector with the configured DC-agent or other selected monitoring mode and verify domain logon visibility. Verify: Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
  4. For the regional airline deployment: 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.

Answer & Explanations

Correct answer: D

A.

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.

B.

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.

C.

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.

D.

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.

FCP - FortiGate 7.6 Administrator (FCP_FGT_AD-7.6) Practice Tests