Practice Exams:

Fortinet NSE4_FGT_AD-7.6 Dumps

EXAM: Fortinet NSE 4 - FortiOS 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

NSE4_FGT_AD-7.6 Premium ETE File


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

Fortinet NSE4_FGT_AD-7.6 Practice Test 27

Question 260

During FortiOS 7.6 operations at a managed branch perimeter, the evidence is: A policy uses an LDAP group but user authentication fails because the bind identity and directory connection are wrong. The operator corrected the configuration by choosing to validate directory reachability, LDAP bind credentials, and group lookup mapping on FortiGate. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Generate the protocol session and verify identity resolution without browser interaction.
  2. Inspect the egress route and matching policy ID for the test session.
  3. Require peer review for remote ldap authentication changes and an acceptance check that will run an LDAP server authentication test and check the intended user-group mapping before relevant releases.
  4. Sign in on a test workstation and inspect collector events and FortiGate identity mapping.
  5. Run an LDAP server authentication test and check the intended user-group mapping.

Explanation

Correct Answers

C:

The organization already encountered the failure where a policy uses an LDAP group but user authentication fails because the bind identity and directory connection are wrong, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to run an LDAP server authentication test and check the intended user-group mapping, this gate checks future revisions without claiming that the current configuration is permanently correct.

E:

It measures the operational result after the correction to validate directory reachability, LDAP bind credentials, and group lookup mapping on FortiGate, and it directly checks the reported condition: a policy uses an LDAP group but user authentication fails because the bind identity and directory connection are wrong. For remote ldap authentication, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

A:

The proposed evidence, to generate the protocol session and verify identity resolution without browser interaction, checks passive versus active auth in a situation such as a device using a noninteractive legacy protocol cannot satisfy a browser-based captive portal policy, not the required remote ldap authentication acceptance. For the affected firewall behavior the directly discriminating check is to run an LDAP server authentication test and check the intended user-group mapping, alongside a review of remote ldap authentication rather than passive versus active auth settings.

B:

The proposed evidence, to inspect the egress route and matching policy ID for the test session, checks outgoing interface mismatch in a situation such as a host reaches the firewall but its traffic does not match an otherwise permissive policy because routing selects a different egress interface, not the required remote ldap authentication acceptance. For the affected firewall behavior the directly discriminating check is to run an LDAP server authentication test and check the intended user-group mapping, alongside a review of remote ldap authentication rather than outgoing interface mismatch settings.

D:

The proposed evidence, to sign in on a test workstation and inspect collector events and FortiGate identity mapping, checks fsso domain controller event capture in a situation such as a user's workstation sign-in is never reflected in FSSO even though the collector is configured on the firewall, not the required remote ldap authentication acceptance. For the affected firewall behavior the directly discriminating check is to run an LDAP server authentication test and check the intended user-group mapping, alongside a review of remote ldap authentication rather than fsso domain controller event capture settings.

Question 261

At a datacenter security boundary, a FortiGate running FortiOS 7.6 has this observation: An administrator configured a RADIUS server but all authentication attempts receive integrity-related rejects. The requirement concerns radius shared secret while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Apply the correct schedule to the scoped firewall policy and verify times in device timezone.
  2. Align FSSO group mapping and firewall policy source-user group with the approved directory group.
  3. Verify FSSO collector connectivity, group filtering, and user IP logon collection.
  4. Ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server.

Explanation

Correct Answer

D:

Choosing to ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server changes the component implicated by that observation, rather than masking the symptom through a different firewall feature. Operators can substantiate the choice by carrying out this test: inspect RADIUS server logs and repeat a successful controlled authentication test.

Incorrect Answers

A:

Applying the correct schedule to the scoped firewall policy and verify times in device timezone would focus the new configuration on schedule-limited access, for which an allowed contractor service must be available only during the approved maintenance window may be a valid concern, but this radius shared secret configuration has a different failure. Evidence for radius shared secret requires staff to inspect RADIUS server logs and repeat a successful controlled authentication test; the proposed schedule-limited access change cannot deliver that radius shared secret result by itself.

B:

Selecting align FSSO group mapping and firewall policy source-user group with the approved directory group would focus the new configuration on fsso policy group matching, for which fSSO identifies the employee correctly but an allow rule restricted to a group never matches may be a valid concern, but this radius shared secret configuration has a different failure. Evidence for radius shared secret requires staff to inspect RADIUS server logs and repeat a successful controlled authentication test; the proposed fsso policy group matching change cannot deliver that radius shared secret result by itself.

C:

Verifying FSSO collector connectivity, group filtering, and user IP logon collection would focus the new configuration on fsso collector connectivity, for which domain sign-ins work but FortiGate receives no mapped user IP identities from the deployed FSSO collector may be a valid concern, but this radius shared secret configuration has a different failure. Evidence for radius shared secret requires staff to inspect RADIUS server logs and repeat a successful controlled authentication test; the proposed fsso collector connectivity change cannot deliver that radius shared secret result by itself.

Question 262

A FortiOS 7.6 review of an enterprise gateway change window reports the following condition: An administrator configured a RADIUS server but all authentication attempts receive integrity-related rejects. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this radius shared secret failure?

  1. Keep mismatched RADIUS shared secrets and expect the username alone to authenticate.
  2. Use an always schedule for traffic that should be restricted to work hours.
  3. Use a different directory group in the policy than the one exported by FSSO.
  4. Point policy logs to FortiAnalyzer instead of diagnosing the FSSO collector channel.

Explanation

Correct Answer

A:

The problem arises when administrators keep mismatched RADIUS shared secrets and expect the username alone to authenticate, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server.

Incorrect Answers

B:

The alternative cause involving schedule-limited access can produce a different failure, for example when an allowed contractor service must be available only during the approved maintenance window; it is not the radius shared secret case. The more specific error here is the choice to keep mismatched RADIUS shared secrets and expect the username alone to authenticate; check it by attempting to inspect RADIUS server logs and repeat a successful controlled authentication test before making an unrelated schedule-limited access change.

C:

The alternative cause involving fsso policy group matching can produce a different failure, for example when fSSO identifies the employee correctly but an allow rule restricted to a group never matches; it is not the radius shared secret case. The more specific error here is the choice to keep mismatched RADIUS shared secrets and expect the username alone to authenticate; check it by attempting to inspect RADIUS server logs and repeat a successful controlled authentication test before making an unrelated fsso policy group matching change.

D:

The alternative cause involving fsso collector connectivity can produce a different failure, for example when domain sign-ins work but FortiGate receives no mapped user IP identities from the deployed FSSO collector; it is not the radius shared secret case. The more specific error here is the choice to keep mismatched RADIUS shared secrets and expect the username alone to authenticate; check it by attempting to inspect RADIUS server logs and repeat a successful controlled authentication test before making an unrelated fsso collector connectivity change.

Question 263

During FortiOS 7.6 operations at a redundant regional firewall pair, the evidence is: An administrator configured a RADIUS server but all authentication attempts receive integrity-related rejects. Investigators confirmed this cause: administrators chose to keep mismatched RADIUS shared secrets and expect the username alone to authenticate. Which action MOST directly corrects the confirmed error?

  1. Ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server.
  2. Align FSSO group mapping and firewall policy source-user group with the approved directory group.
  3. Apply the correct schedule to the scoped firewall policy and verify times in device timezone.
  4. Keep mismatched RADIUS shared secrets and expect the username alone to authenticate.

Explanation

Correct Answer

A:

This addresses radius shared secret without needlessly weakening separate security or routing controls. Given the observed condition—an administrator configured a RADIUS server but all authentication attempts receive integrity-related rejects—the operator should then inspect RADIUS server logs and repeat a successful controlled authentication test.

Incorrect Answers

B:

Changing the mechanism to align FSSO group mapping and firewall policy source-user group with the approved directory group could be a sensible correction for fsso policy group matching when fSSO identifies the employee correctly but an allow rule restricted to a group never matches. The targeted fix is to ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server; a review of fsso policy group matching would not, by itself, prove that the team can inspect RADIUS server logs and repeat a successful controlled authentication test.

C:

Changing the mechanism to apply the correct schedule to the scoped firewall policy and verify times in device timezone could be a sensible correction for schedule-limited access when an allowed contractor service must be available only during the approved maintenance window. The targeted fix is to ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server; a review of schedule-limited access would not, by itself, prove that the team can inspect RADIUS server logs and repeat a successful controlled authentication test.

D:

The proposal repeats the confirmed radius shared secret error by choosing to keep mismatched RADIUS shared secrets and expect the username alone to authenticate. A corrective change must instead ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server and then produce the measurable result to inspect RADIUS server logs and repeat a successful controlled authentication test; repeating the failed setting cannot serve as a repair.

Question 264

At a remote-office migration, a FortiGate running FortiOS 7.6 has this observation: An administrator configured a RADIUS server but all authentication attempts receive integrity-related rejects. The incident has been fixed, and the owner wants to prevent a recurrence of the radius shared secret problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for fsso policy group matching changes and an acceptance check that will inspect the user's resolved group membership and selected policy during a new session before relevant releases.
  2. Require peer review for schedule-limited access changes and an acceptance check that will test the same permitted source and service inside and outside the schedule before relevant releases.
  3. Require peer review for fsso collector connectivity changes and an acceptance check that will check the live FSSO user/IP table after a fresh domain logon before relevant releases.
  4. Require peer review for radius shared secret changes and an acceptance check that will inspect RADIUS server logs and repeat a successful controlled authentication test before relevant releases.

Explanation

Correct Answer

D:

This change-control gate requires teams to require peer review for radius shared secret changes and an acceptance check that will inspect RADIUS server logs and repeat a successful controlled authentication test before relevant releases, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to inspect RADIUS server logs and repeat a successful controlled authentication test.

Incorrect Answers

A:

A review gate for fsso policy group matching, such as require peer review for fsso policy group matching changes and an acceptance check that will inspect the user's resolved group membership and selected policy during a new session before relevant releases, can be useful where fSSO identifies the employee correctly but an allow rule restricted to a group never matches, but it is not the approved radius shared secret review. The preventive test must enforce that staff will ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server and subsequently can inspect RADIUS server logs and repeat a successful controlled authentication test; the proposed fsso policy group matching gate would not check that same control.

B:

A review gate for schedule-limited access, such as require peer review for schedule-limited access changes and an acceptance check that will test the same permitted source and service inside and outside the schedule before relevant releases, can be useful where an allowed contractor service must be available only during the approved maintenance window, but it is not the approved radius shared secret review. The preventive test must enforce that staff will ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server and subsequently can inspect RADIUS server logs and repeat a successful controlled authentication test; the proposed schedule-limited access gate would not check that same control.

C:

A review gate for fsso collector connectivity, such as require peer review for fsso collector connectivity changes and an acceptance check that will check the live FSSO user/IP table after a fresh domain logon before relevant releases, can be useful where domain sign-ins work but FortiGate receives no mapped user IP identities from the deployed FSSO collector, but it is not the approved radius shared secret review. The preventive test must enforce that staff will ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server and subsequently can inspect RADIUS server logs and repeat a successful controlled authentication test; the proposed fsso collector connectivity gate would not check that same control.

Question 265

A FortiOS 7.6 review of a monitored business uplink reports the following condition: An administrator configured a RADIUS server but all authentication attempts receive integrity-related rejects. The operator corrected the configuration by choosing to ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Inspect RADIUS server logs and repeat a successful controlled authentication test.
  2. Inspect the user's resolved group membership and selected policy during a new session.
  3. Test the same permitted source and service inside and outside the schedule.
  4. Require peer review for radius shared secret changes and an acceptance check that will inspect RADIUS server logs and repeat a successful controlled authentication test before relevant releases.
  5. Check the live FSSO user/IP table after a fresh domain logon.

Explanation

Correct Answers

A:

It measures the operational result after the correction to ensure the same RADIUS shared secret and client identity are configured on FortiGate and the server, and it directly checks the reported condition: an administrator configured a RADIUS server but all authentication attempts receive integrity-related rejects. For radius shared secret, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

D:

The organization already encountered the failure where an administrator configured a RADIUS server but all authentication attempts receive integrity-related rejects, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to inspect RADIUS server logs and repeat a successful controlled authentication test, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

B:

The proposed evidence, to inspect the user's resolved group membership and selected policy during a new session, checks fsso policy group matching in a situation such as fSSO identifies the employee correctly but an allow rule restricted to a group never matches, not the required radius shared secret acceptance. For the affected firewall behavior the directly discriminating check is to inspect RADIUS server logs and repeat a successful controlled authentication test, alongside a review of radius shared secret rather than fsso policy group matching settings.

C:

The proposed evidence, to test the same permitted source and service inside and outside the schedule, checks schedule-limited access in a situation such as an allowed contractor service must be available only during the approved maintenance window, not the required radius shared secret acceptance. For the affected firewall behavior the directly discriminating check is to inspect RADIUS server logs and repeat a successful controlled authentication test, alongside a review of radius shared secret rather than schedule-limited access settings.

E:

The proposed evidence, to check the live FSSO user/IP table after a fresh domain logon, checks fsso collector connectivity in a situation such as domain sign-ins work but FortiGate receives no mapped user IP identities from the deployed FSSO collector, not the required radius shared secret acceptance. For the affected firewall behavior the directly discriminating check is to inspect RADIUS server logs and repeat a successful controlled authentication test, alongside a review of radius shared secret rather than fsso collector connectivity settings.

Question 266

During FortiOS 7.6 operations at an internal application segment, the evidence is: Guest browsing is permitted without a user identity prompt despite a requirement for interactive firewall authentication. The requirement concerns captive portal policy while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Correct source address objects and match conditions to distinguish Finance and guest networks.
  2. Ensure the selected FSSO DC agent or event collection path observes the relevant domain logons.
  3. Apply supported firewall authentication and captive portal requirements to the applicable guest policy.
  4. Review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings.

Explanation

Correct Answer

C:

Choosing to apply supported firewall authentication and captive portal requirements to the applicable guest policy changes the component implicated by that observation, rather than masking the symptom through a different firewall feature. Operators can substantiate the choice by carrying out this test: connect a new guest session and verify an interactive auth flow and identity-tagged log.

Incorrect Answers

A:

Selecting correct source address objects and match conditions to distinguish Finance and guest networks would focus the new configuration on source address selection, for which an internal Finance subnet is denied while an overly broad allow policy accidentally permits a guest subnet may be a valid concern, but this captive portal policy configuration has a different failure. Evidence for captive portal policy requires staff to connect a new guest session and verify an interactive auth flow and identity-tagged log; the proposed source address selection change cannot deliver that captive portal policy result by itself.

B:

Selecting ensure the selected FSSO DC agent or event collection path observes the relevant domain logons would focus the new configuration on fsso domain controller event capture, for which a user's workstation sign-in is never reflected in FSSO even though the collector is configured on the firewall may be a valid concern, but this captive portal policy configuration has a different failure. Evidence for captive portal policy requires staff to connect a new guest session and verify an interactive auth flow and identity-tagged log; the proposed fsso domain controller event capture change cannot deliver that captive portal policy result by itself.

D:

Reviewing FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings would focus the new configuration on stale fsso ip mapping, for which two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user may be a valid concern, but this captive portal policy configuration has a different failure. Evidence for captive portal policy requires staff to connect a new guest session and verify an interactive auth flow and identity-tagged log; the proposed stale fsso ip mapping change cannot deliver that captive portal policy result by itself.

Question 267

At a hybrid-network deployment, a FortiGate running FortiOS 7.6 has this observation: Guest browsing is permitted without a user identity prompt despite a requirement for interactive firewall authentication. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this captive portal policy failure?

  1. Enable only unauthenticated allow traffic and assume that creates a user login portal.
  2. Use an all-sources address object for a Finance-only access rule.
  3. Retain an old IP-to-user mapping indefinitely after a different user takes the address.
  4. Assume the FSSO collector can infer user identity without any working DC logon collection.

Explanation

Correct Answer

A:

The problem arises when administrators enable only unauthenticated allow traffic and assume that creates a user login portal, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to apply supported firewall authentication and captive portal requirements to the applicable guest policy.

Incorrect Answers

B:

The alternative cause involving source address selection can produce a different failure, for example when an internal Finance subnet is denied while an overly broad allow policy accidentally permits a guest subnet; it is not the captive portal policy case. The more specific error here is the choice to enable only unauthenticated allow traffic and assume that creates a user login portal; check it by attempting to connect a new guest session and verify an interactive auth flow and identity-tagged log before making an unrelated source address selection change.

C:

The alternative cause involving stale fsso ip mapping can produce a different failure, for example when two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user; it is not the captive portal policy case. The more specific error here is the choice to enable only unauthenticated allow traffic and assume that creates a user login portal; check it by attempting to connect a new guest session and verify an interactive auth flow and identity-tagged log before making an unrelated stale fsso ip mapping change.

D:

The alternative cause involving fsso domain controller event capture can produce a different failure, for example when a user's workstation sign-in is never reflected in FSSO even though the collector is configured on the firewall; it is not the captive portal policy case. The more specific error here is the choice to enable only unauthenticated allow traffic and assume that creates a user login portal; check it by attempting to connect a new guest session and verify an interactive auth flow and identity-tagged log before making an unrelated fsso domain controller event capture change.

Question 268

A FortiOS 7.6 review of an operations incident response reports the following condition: Guest browsing is permitted without a user identity prompt despite a requirement for interactive firewall authentication. Investigators confirmed this cause: administrators chose to enable only unauthenticated allow traffic and assume that creates a user login portal. Which action MOST directly corrects the confirmed error?

  1. Enable only unauthenticated allow traffic and assume that creates a user login portal.
  2. Review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings.
  3. Correct source address objects and match conditions to distinguish Finance and guest networks.
  4. Apply supported firewall authentication and captive portal requirements to the applicable guest policy.

Explanation

Correct Answer

D:

This addresses captive portal policy without needlessly weakening separate security or routing controls. Given the observed condition—guest browsing is permitted without a user identity prompt despite a requirement for interactive firewall authentication—the operator should then connect a new guest session and verify an interactive auth flow and identity-tagged log.

Incorrect Answers

A:

The proposal repeats the confirmed captive portal policy error by choosing to enable only unauthenticated allow traffic and assume that creates a user login portal. A corrective change must instead apply supported firewall authentication and captive portal requirements to the applicable guest policy and then produce the measurable result to connect a new guest session and verify an interactive auth flow and identity-tagged log; repeating the failed setting cannot serve as a repair.

B:

Changing the mechanism to review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings could be a sensible correction for stale fsso ip mapping when two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user. The targeted fix is to apply supported firewall authentication and captive portal requirements to the applicable guest policy; a review of stale fsso ip mapping would not, by itself, prove that the team can connect a new guest session and verify an interactive auth flow and identity-tagged log.

C:

Changing the mechanism to correct source address objects and match conditions to distinguish Finance and guest networks could be a sensible correction for source address selection when an internal Finance subnet is denied while an overly broad allow policy accidentally permits a guest subnet. The targeted fix is to apply supported firewall authentication and captive portal requirements to the applicable guest policy; a review of source address selection would not, by itself, prove that the team can connect a new guest session and verify an interactive auth flow and identity-tagged log.

Question 269

During FortiOS 7.6 operations at a network segmentation review, the evidence is: Guest browsing is permitted without a user identity prompt despite a requirement for interactive firewall authentication. The incident has been fixed, and the owner wants to prevent a recurrence of the captive portal policy problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for fsso domain controller event capture changes and an acceptance check that will sign in on a test workstation and inspect collector events and FortiGate identity mapping before relevant releases.
  2. Require peer review for captive portal policy changes and an acceptance check that will connect a new guest session and verify an interactive auth flow and identity-tagged log before relevant releases.
  3. Require peer review for stale fsso ip mapping changes and an acceptance check that will reassign a test IP to a new user and verify FSSO identity updates correctly before relevant releases.
  4. Require peer review for source address selection changes and an acceptance check that will test Finance and guest sources against the same destination and record selected policies before relevant releases.

Explanation

Correct Answer

B:

This change-control gate requires teams to require peer review for captive portal policy changes and an acceptance check that will connect a new guest session and verify an interactive auth flow and identity-tagged log before relevant releases, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to connect a new guest session and verify an interactive auth flow and identity-tagged log.

Incorrect Answers

A:

A review gate for fsso domain controller event capture, such as require peer review for fsso domain controller event capture changes and an acceptance check that will sign in on a test workstation and inspect collector events and FortiGate identity mapping before relevant releases, can be useful where a user's workstation sign-in is never reflected in FSSO even though the collector is configured on the firewall, but it is not the approved captive portal policy review. The preventive test must enforce that staff will apply supported firewall authentication and captive portal requirements to the applicable guest policy and subsequently can connect a new guest session and verify an interactive auth flow and identity-tagged log; the proposed fsso domain controller event capture gate would not check that same control.

C:

A review gate for stale fsso ip mapping, such as require peer review for stale fsso ip mapping changes and an acceptance check that will reassign a test IP to a new user and verify FSSO identity updates correctly before relevant releases, can be useful where two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user, but it is not the approved captive portal policy review. The preventive test must enforce that staff will apply supported firewall authentication and captive portal requirements to the applicable guest policy and subsequently can connect a new guest session and verify an interactive auth flow and identity-tagged log; the proposed stale fsso ip mapping gate would not check that same control.

D:

A review gate for source address selection, such as require peer review for source address selection changes and an acceptance check that will test Finance and guest sources against the same destination and record selected policies before relevant releases, can be useful where an internal Finance subnet is denied while an overly broad allow policy accidentally permits a guest subnet, but it is not the approved captive portal policy review. The preventive test must enforce that staff will apply supported firewall authentication and captive portal requirements to the applicable guest policy and subsequently can connect a new guest session and verify an interactive auth flow and identity-tagged log; the proposed source address selection gate would not check that same control.

Question 270

At a managed branch perimeter, a FortiGate running FortiOS 7.6 has this observation: Guest browsing is permitted without a user identity prompt despite a requirement for interactive firewall authentication. The operator corrected the configuration by choosing to apply supported firewall authentication and captive portal requirements to the applicable guest policy. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Sign in on a test workstation and inspect collector events and FortiGate identity mapping.
  2. Require peer review for captive portal policy changes and an acceptance check that will connect a new guest session and verify an interactive auth flow and identity-tagged log before relevant releases.
  3. Connect a new guest session and verify an interactive auth flow and identity-tagged log.
  4. Test Finance and guest sources against the same destination and record selected policies.
  5. Reassign a test IP to a new user and verify FSSO identity updates correctly.

Explanation

Correct Answers

B:

The organization already encountered the failure where guest browsing is permitted without a user identity prompt despite a requirement for interactive firewall authentication, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to connect a new guest session and verify an interactive auth flow and identity-tagged log, this gate checks future revisions without claiming that the current configuration is permanently correct.

C:

It measures the operational result after the correction to apply supported firewall authentication and captive portal requirements to the applicable guest policy, and it directly checks the reported condition: guest browsing is permitted without a user identity prompt despite a requirement for interactive firewall authentication. For captive portal policy, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

A:

The proposed evidence, to sign in on a test workstation and inspect collector events and FortiGate identity mapping, checks fsso domain controller event capture in a situation such as a user's workstation sign-in is never reflected in FSSO even though the collector is configured on the firewall, not the required captive portal policy acceptance. For the affected firewall behavior the directly discriminating check is to connect a new guest session and verify an interactive auth flow and identity-tagged log, alongside a review of captive portal policy rather than fsso domain controller event capture settings.

D:

The proposed evidence, to test Finance and guest sources against the same destination and record selected policies, checks source address selection in a situation such as an internal Finance subnet is denied while an overly broad allow policy accidentally permits a guest subnet, not the required captive portal policy acceptance. For the affected firewall behavior the directly discriminating check is to connect a new guest session and verify an interactive auth flow and identity-tagged log, alongside a review of captive portal policy rather than source address selection settings.

E:

The proposed evidence, to reassign a test IP to a new user and verify FSSO identity updates correctly, checks stale fsso ip mapping in a situation such as two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user, not the required captive portal policy acceptance. For the affected firewall behavior the directly discriminating check is to connect a new guest session and verify an interactive auth flow and identity-tagged log, alongside a review of captive portal policy rather than stale fsso ip mapping settings.

Fortinet NSE 4 - FortiOS 7.6 Administrator (NSE4_FGT_AD-7.6) Practice Tests