Fortinet FCP_FGT_AD-7.6 Dumps
Fortinet FCP_FGT_AD-7.6 Practice Test 28
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.
Question 271
A public works agency loses FSSO after a collector upgrade and is tempted to allow all internal traffic. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?
Answer & Explanations
Correct answer: C
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, FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
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 group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. This resolves the issue because FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction. To verify, correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
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 group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
Question 272
A public works agency loses FSSO after a collector upgrade and is tempted to allow all internal traffic. The engineer proposes this change: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path Which explanation most accurately establishes why that change meets the operational requirement?
Answer & Explanations
Correct answer: D
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 group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
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 group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
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 FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction. It supports this action: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. To confirm, correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
Question 273
A public works agency loses FSSO after a collector upgrade and is tempted to allow all internal traffic. After implementing this change—Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path—which test best establishes that the intended outcome is actually working?
Answer & Explanations
Correct answer: A
Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector. This is the relevant test because FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
This check would help evaluate the distinct objective “Use active authentication when passive identity is unavailable”, but not the required result. For this case, correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
This check would help evaluate the distinct objective “Check FSSO group and IP mapping freshness”, but not the required result. For this case, correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
This check would help evaluate the distinct objective “Collect Windows logon events for FSSO user mappings”, but not the required result. For this case, correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
Question 274
A public works agency loses FSSO after a collector upgrade and is tempted to allow all internal traffic. Which proposed shortcut would most directly cause persistent bypass of user-based access controls, and therefore must be avoided for this requirement?
Answer & Explanations
Correct answer: B
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 add a top-level allow-any policy whenever the FSSO collector is briefly unavailable.
Add a top-level allow-any policy whenever the FSSO collector is briefly unavailable. The proposed shortcut bypasses the needed control: FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction. The appropriate response is to compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path.
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 add a top-level allow-any policy whenever the FSSO collector is briefly unavailable.
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 add a top-level allow-any policy whenever the FSSO collector is briefly unavailable.
Question 275
A public works agency loses FSSO after a collector upgrade and is tempted to allow all internal traffic. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?
Answer & Explanations
Correct answer: C
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 compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Its confirming test is to correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
This action and check address the alternate operation “For the public works agency loses FSSO after a collector upgrade and deployment: Implement: Inspect FSSO learned user, source…” instead of the stated acceptance requirement. The matching action is to compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Its confirming test is to correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
Implement: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Verify: Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector. This pairing is justified because FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
This action and check address the alternate operation “For the public works agency loses FSSO after a collector upgrade and deployment: Implement: Compare collector connectivity, logon events…” instead of the stated acceptance requirement. The matching action is to compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Its confirming test is to correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
Question 276
A regional bank can ping the collector but staff group rules no longer match following a domain trust change. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?
Answer & Explanations
Correct answer: D
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. 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 group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. 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, FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. 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 group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. This resolves the issue because FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction. To verify, correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
Question 277
A regional bank can ping the collector but staff group rules no longer match following a domain trust change. The engineer proposes this change: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path Which explanation most accurately establishes why that change meets the operational requirement?
Answer & Explanations
Correct answer: A
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction. It supports this action: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. To confirm, correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. 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 group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. 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 FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. 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 group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
Question 278
A regional bank can ping the collector but staff group rules no longer match following a domain trust change. After implementing this change—Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path—which test best establishes that the intended outcome is actually working?
Answer & Explanations
Correct answer: B
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. This check would help evaluate the distinct objective “Check FSSO group and IP mapping freshness”, but not the required result. For this case, correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector. This is the relevant test because FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. This check would help evaluate the distinct objective “Collect Windows logon events for FSSO user mappings”, but not the required result. For this case, correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. This check would help evaluate the distinct objective “Use active authentication when passive identity is unavailable”, but not the required result. For this case, correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
Question 279
A regional bank can ping the collector but staff group rules no longer match following a domain trust change. Which proposed shortcut would most directly cause persistent bypass of user-based access controls, and therefore must be avoided for this requirement?
Answer & Explanations
Correct answer: C
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. 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 add a top-level allow-any policy whenever the FSSO collector is briefly unavailable.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. 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 add a top-level allow-any policy whenever the FSSO collector is briefly unavailable.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. Add a top-level allow-any policy whenever the FSSO collector is briefly unavailable. The proposed shortcut bypasses the needed control: FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction. The appropriate response is to compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. 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 add a top-level allow-any policy whenever the FSSO collector is briefly unavailable.
Question 280
A regional bank can ping the collector but staff group rules no longer match following a domain trust change. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?
Answer & Explanations
Correct answer: D
This action and check address the alternate operation “For the regional bank deployment: Implement: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly…” instead of the stated acceptance requirement. The matching action is to compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Its confirming test is to correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. 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 compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Its confirming test is to correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
This action and check address the alternate operation “For the regional bank 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 compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Its confirming test is to correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. Implement: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Verify: Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector. This pairing is justified because FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.
FCP - FortiGate 7.6 Administrator (FCP_FGT_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FGT_AD-7.6 Practice Test 30 - 10 Questions (Last Reviewed 23-Oct-2026)