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 31

Question 300

At a managed branch perimeter, a FortiGate running FortiOS 7.6 has this observation: FSSO identifies the employee correctly but an allow rule restricted to a group never matches. The operator corrected the configuration by choosing to align FSSO group mapping and firewall policy source-user group with the approved directory group. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Inspect the egress route and matching policy ID for the test session.
  2. 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.
  3. Test Finance and guest sources against the same destination and record selected policies.
  4. Terminate or renew an authorized test session and inspect its new policy match.
  5. Inspect the user's resolved group membership and selected policy during a new session.

Explanation

Correct Answers

B:

The organization already encountered the failure where fSSO identifies the employee correctly but an allow rule restricted to a group never matches, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to inspect the user's resolved group membership and selected policy during a new session, this gate checks future revisions without claiming that the current configuration is permanently correct.

E:

It measures the operational result after the correction to align FSSO group mapping and firewall policy source-user group with the approved directory group, and it directly checks the reported condition: fSSO identifies the employee correctly but an allow rule restricted to a group never matches. For fsso policy group matching, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

A:

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 fsso policy group matching acceptance. For the affected firewall behavior the directly discriminating check is to inspect the user's resolved group membership and selected policy during a new session, alongside a review of fsso policy group matching rather than outgoing interface mismatch settings.

C:

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 fsso policy group matching acceptance. For the affected firewall behavior the directly discriminating check is to inspect the user's resolved group membership and selected policy during a new session, alongside a review of fsso policy group matching rather than source address selection settings.

D:

The proposed evidence, to terminate or renew an authorized test session and inspect its new policy match, checks after-change session testing in a situation such as an amended firewall policy does not affect a pre-existing long-lived session and the team mistakes it for a new-flow policy defect, not the required fsso policy group matching acceptance. For the affected firewall behavior the directly discriminating check is to inspect the user's resolved group membership and selected policy during a new session, alongside a review of fsso policy group matching rather than after-change session testing settings.

Question 301

A FortiOS 7.6 review of a datacenter security boundary reports the following condition: Two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user. The requirement concerns stale fsso ip mapping while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Implement least-privilege intersegment policies for the approved source, destination, and service.
  2. Review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings.
  3. Apply the correct schedule to the scoped firewall policy and verify times in device timezone.
  4. Use a destination address object limited to the approved server or service address.

Explanation

Correct Answer

B:

Choosing to review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings 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: reassign a test IP to a new user and verify FSSO identity updates correctly.

Incorrect Answers

A:

Selecting implement least-privilege intersegment policies for the approved source, destination, and service would focus the new configuration on east-west segmentation, for which a shared office segment can unexpectedly access privileged management services across an internal firewall boundary may be a valid concern, but this stale fsso ip mapping configuration has a different failure. Evidence for stale fsso ip mapping requires staff to reassign a test IP to a new user and verify FSSO identity updates correctly; the proposed east-west segmentation change cannot deliver that stale fsso ip mapping result by itself.

C:

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 stale fsso ip mapping configuration has a different failure. Evidence for stale fsso ip mapping requires staff to reassign a test IP to a new user and verify FSSO identity updates correctly; the proposed schedule-limited access change cannot deliver that stale fsso ip mapping result by itself.

D:

Using a destination address object limited to the approved server or service address would focus the new configuration on destination object scope, for which a branch policy must allow access to one application server without opening the entire datacenter subnet may be a valid concern, but this stale fsso ip mapping configuration has a different failure. Evidence for stale fsso ip mapping requires staff to reassign a test IP to a new user and verify FSSO identity updates correctly; the proposed destination object scope change cannot deliver that stale fsso ip mapping result by itself.

Question 302

During FortiOS 7.6 operations at an enterprise gateway change window, the evidence is: Two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this stale fsso ip mapping failure?

  1. Retain an old IP-to-user mapping indefinitely after a different user takes the address.
  2. Use a single unrestricted internal-to-internal permit policy across all VLANs.
  3. Use an always schedule for traffic that should be restricted to work hours.
  4. Replace the application destination with the complete datacenter subnet.

Explanation

Correct Answer

A:

The problem arises when administrators retain an old IP-to-user mapping indefinitely after a different user takes the address, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings.

Incorrect Answers

B:

The alternative cause involving east-west segmentation can produce a different failure, for example when a shared office segment can unexpectedly access privileged management services across an internal firewall boundary; it is not the stale fsso ip mapping case. The more specific error here is the choice to retain an old IP-to-user mapping indefinitely after a different user takes the address; check it by attempting to reassign a test IP to a new user and verify FSSO identity updates correctly before making an unrelated east-west segmentation change.

C:

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 stale fsso ip mapping case. The more specific error here is the choice to retain an old IP-to-user mapping indefinitely after a different user takes the address; check it by attempting to reassign a test IP to a new user and verify FSSO identity updates correctly before making an unrelated schedule-limited access change.

D:

The alternative cause involving destination object scope can produce a different failure, for example when a branch policy must allow access to one application server without opening the entire datacenter subnet; it is not the stale fsso ip mapping case. The more specific error here is the choice to retain an old IP-to-user mapping indefinitely after a different user takes the address; check it by attempting to reassign a test IP to a new user and verify FSSO identity updates correctly before making an unrelated destination object scope change.

Question 303

At a redundant regional firewall pair, a FortiGate running FortiOS 7.6 has this observation: Two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user. Investigators confirmed this cause: administrators chose to retain an old IP-to-user mapping indefinitely after a different user takes the address. Which action MOST directly corrects the confirmed error?

  1. Use a destination address object limited to the approved server or service address.
  2. Review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings.
  3. Retain an old IP-to-user mapping indefinitely after a different user takes the address.
  4. Implement least-privilege intersegment policies for the approved source, destination, and service.

Explanation

Correct Answer

B:

This addresses stale fsso ip mapping without needlessly weakening separate security or routing controls. Given the observed condition—two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user—the operator should then reassign a test IP to a new user and verify FSSO identity updates correctly.

Incorrect Answers

A:

Changing the mechanism to use a destination address object limited to the approved server or service address could be a sensible correction for destination object scope when a branch policy must allow access to one application server without opening the entire datacenter subnet. The targeted fix is to review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings; a review of destination object scope would not, by itself, prove that the team can reassign a test IP to a new user and verify FSSO identity updates correctly.

C:

The proposal repeats the confirmed stale fsso ip mapping error by choosing to retain an old IP-to-user mapping indefinitely after a different user takes the address. A corrective change must instead review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings and then produce the measurable result to reassign a test IP to a new user and verify FSSO identity updates correctly; repeating the failed setting cannot serve as a repair.

D:

Changing the mechanism to implement least-privilege intersegment policies for the approved source, destination, and service could be a sensible correction for east-west segmentation when a shared office segment can unexpectedly access privileged management services across an internal firewall boundary. The targeted fix is to review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings; a review of east-west segmentation would not, by itself, prove that the team can reassign a test IP to a new user and verify FSSO identity updates correctly.

Question 304

A FortiOS 7.6 review of a remote-office migration reports the following condition: Two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user. The incident has been fixed, and the owner wants to prevent a recurrence of the stale fsso ip mapping problem. Which future change-control rule is MOST appropriate?

  1. 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.
  2. Require peer review for east-west segmentation changes and an acceptance check that will probe an authorized application port and an unauthorized management port across segments before relevant releases.
  3. Require peer review for destination object scope changes and an acceptance check that will attempt connections to the approved server and a neighboring unauthorized server before relevant releases.
  4. 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.

Explanation

Correct Answer

D:

This change-control gate requires teams to 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, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to reassign a test IP to a new user and verify FSSO identity updates correctly.

Incorrect Answers

A:

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 stale fsso ip mapping review. The preventive test must enforce that staff will review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings and subsequently can reassign a test IP to a new user and verify FSSO identity updates correctly; the proposed schedule-limited access gate would not check that same control.

B:

A review gate for east-west segmentation, such as require peer review for east-west segmentation changes and an acceptance check that will probe an authorized application port and an unauthorized management port across segments before relevant releases, can be useful where a shared office segment can unexpectedly access privileged management services across an internal firewall boundary, but it is not the approved stale fsso ip mapping review. The preventive test must enforce that staff will review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings and subsequently can reassign a test IP to a new user and verify FSSO identity updates correctly; the proposed east-west segmentation gate would not check that same control.

C:

A review gate for destination object scope, such as require peer review for destination object scope changes and an acceptance check that will attempt connections to the approved server and a neighboring unauthorized server before relevant releases, can be useful where a branch policy must allow access to one application server without opening the entire datacenter subnet, but it is not the approved stale fsso ip mapping review. The preventive test must enforce that staff will review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings and subsequently can reassign a test IP to a new user and verify FSSO identity updates correctly; the proposed destination object scope gate would not check that same control.

Question 305

During FortiOS 7.6 operations at a monitored business uplink, the evidence is: Two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user. The operator corrected the configuration by choosing to review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Test the same permitted source and service inside and outside the schedule.
  2. Attempt connections to the approved server and a neighboring unauthorized server.
  3. Reassign a test IP to a new user and verify FSSO identity updates correctly.
  4. Probe an authorized application port and an unauthorized management port across segments.
  5. 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.

Explanation

Correct Answers

C:

It measures the operational result after the correction to review FSSO logoff, timeout, and IP reuse handling to retire stale identity mappings, and it directly checks the reported condition: two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user. For stale fsso ip mapping, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

E:

The organization already encountered the failure where two people use the same reassigned workstation address and the firewall still associates the IP with the earlier user, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to reassign a test IP to a new user and verify FSSO identity updates correctly, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

A:

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 stale fsso ip mapping acceptance. For the affected firewall behavior the directly discriminating check is to reassign a test IP to a new user and verify FSSO identity updates correctly, alongside a review of stale fsso ip mapping rather than schedule-limited access settings.

B:

The proposed evidence, to attempt connections to the approved server and a neighboring unauthorized server, checks destination object scope in a situation such as a branch policy must allow access to one application server without opening the entire datacenter subnet, not the required stale fsso ip mapping acceptance. For the affected firewall behavior the directly discriminating check is to reassign a test IP to a new user and verify FSSO identity updates correctly, alongside a review of stale fsso ip mapping rather than destination object scope settings.

D:

The proposed evidence, to probe an authorized application port and an unauthorized management port across segments, checks east-west segmentation in a situation such as a shared office segment can unexpectedly access privileged management services across an internal firewall boundary, not the required stale fsso ip mapping acceptance. For the affected firewall behavior the directly discriminating check is to reassign a test IP to a new user and verify FSSO identity updates correctly, alongside a review of stale fsso ip mapping rather than east-west segmentation settings.

Question 306

At an internal application segment, a FortiGate running FortiOS 7.6 has this observation: A multi-domain organization sees group membership only from headquarters while remote domain-controller logons are missing. The requirement concerns fsso across domain sites while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Configure approved DC monitoring or collectors for all relevant logon sources and group mappings.
  2. Correct source address objects and match conditions to distinguish Finance and guest networks.
  3. Define and apply the correct TCP service object for the actual application port.
  4. Enable the appropriate source NAT on the matching outbound firewall policy.

Explanation

Correct Answer

A:

Choosing to configure approved DC monitoring or collectors for all relevant logon sources and group mappings 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: log on from each supported domain site and verify resolved identities in the FortiGate FSSO table.

Incorrect Answers

B:

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 fsso across domain sites configuration has a different failure. Evidence for fsso across domain sites requires staff to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table; the proposed source address selection change cannot deliver that fsso across domain sites result by itself.

C:

Selecting define and apply the correct TCP service object for the actual application port would focus the new configuration on service port matching, for which a new internal HTTPS application uses TCP 8443 but its firewall rule permits only standard TCP 443 may be a valid concern, but this fsso across domain sites configuration has a different failure. Evidence for fsso across domain sites requires staff to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table; the proposed service port matching change cannot deliver that fsso across domain sites result by itself.

D:

Enabling the appropriate source NAT on the matching outbound firewall policy would focus the new configuration on per-policy source nat, for which outbound branch clients require internet egress through the WAN interface address but see unroutable private source addresses upstream may be a valid concern, but this fsso across domain sites configuration has a different failure. Evidence for fsso across domain sites requires staff to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table; the proposed per-policy source nat change cannot deliver that fsso across domain sites result by itself.

Question 307

A FortiOS 7.6 review of a hybrid-network deployment reports the following condition: A multi-domain organization sees group membership only from headquarters while remote domain-controller logons are missing. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this fsso across domain sites failure?

  1. Assume the HTTPS service object always covers every custom TLS port.
  2. Use an all-sources address object for a Finance-only access rule.
  3. Disable source NAT on the only outbound policy even though the upstream network cannot route private sources.
  4. Monitor only one domain controller and assume all branch logons are discovered automatically.

Explanation

Correct Answer

D:

The problem arises when administrators monitor only one domain controller and assume all branch logons are discovered automatically, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to configure approved DC monitoring or collectors for all relevant logon sources and group mappings.

Incorrect Answers

A:

The alternative cause involving service port matching can produce a different failure, for example when a new internal HTTPS application uses TCP 8443 but its firewall rule permits only standard TCP 443; it is not the fsso across domain sites case. The more specific error here is the choice to monitor only one domain controller and assume all branch logons are discovered automatically; check it by attempting to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table before making an unrelated service port matching change.

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 fsso across domain sites case. The more specific error here is the choice to monitor only one domain controller and assume all branch logons are discovered automatically; check it by attempting to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table before making an unrelated source address selection change.

C:

The alternative cause involving per-policy source nat can produce a different failure, for example when outbound branch clients require internet egress through the WAN interface address but see unroutable private source addresses upstream; it is not the fsso across domain sites case. The more specific error here is the choice to monitor only one domain controller and assume all branch logons are discovered automatically; check it by attempting to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table before making an unrelated per-policy source nat change.

Question 308

During FortiOS 7.6 operations at an operations incident response, the evidence is: A multi-domain organization sees group membership only from headquarters while remote domain-controller logons are missing. Investigators confirmed this cause: administrators chose to monitor only one domain controller and assume all branch logons are discovered automatically. Which action MOST directly corrects the confirmed error?

  1. Monitor only one domain controller and assume all branch logons are discovered automatically.
  2. Enable the appropriate source NAT on the matching outbound firewall policy.
  3. Define and apply the correct TCP service object for the actual application port.
  4. Configure approved DC monitoring or collectors for all relevant logon sources and group mappings.

Explanation

Correct Answer

D:

This addresses fsso across domain sites without needlessly weakening separate security or routing controls. Given the observed condition—a multi-domain organization sees group membership only from headquarters while remote domain-controller logons are missing—the operator should then log on from each supported domain site and verify resolved identities in the FortiGate FSSO table.

Incorrect Answers

A:

The proposal repeats the confirmed fsso across domain sites error by choosing to monitor only one domain controller and assume all branch logons are discovered automatically. A corrective change must instead configure approved DC monitoring or collectors for all relevant logon sources and group mappings and then produce the measurable result to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table; repeating the failed setting cannot serve as a repair.

B:

Changing the mechanism to enable the appropriate source NAT on the matching outbound firewall policy could be a sensible correction for per-policy source nat when outbound branch clients require internet egress through the WAN interface address but see unroutable private source addresses upstream. The targeted fix is to configure approved DC monitoring or collectors for all relevant logon sources and group mappings; a review of per-policy source nat would not, by itself, prove that the team can log on from each supported domain site and verify resolved identities in the FortiGate FSSO table.

C:

Changing the mechanism to define and apply the correct TCP service object for the actual application port could be a sensible correction for service port matching when a new internal HTTPS application uses TCP 8443 but its firewall rule permits only standard TCP 443. The targeted fix is to configure approved DC monitoring or collectors for all relevant logon sources and group mappings; a review of service port matching would not, by itself, prove that the team can log on from each supported domain site and verify resolved identities in the FortiGate FSSO table.

Question 309

At a network segmentation review, a FortiGate running FortiOS 7.6 has this observation: A multi-domain organization sees group membership only from headquarters while remote domain-controller logons are missing. The incident has been fixed, and the owner wants to prevent a recurrence of the fsso across domain sites problem. Which future change-control rule is MOST appropriate?

  1. 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.
  2. Require peer review for per-policy source nat changes and an acceptance check that will capture egress packets and verify public source translation for a test client before relevant releases.
  3. Require peer review for fsso across domain sites changes and an acceptance check that will log on from each supported domain site and verify resolved identities in the FortiGate FSSO table before relevant releases.
  4. Require peer review for service port matching changes and an acceptance check that will check a TCP 8443 test session against service and policy match results before relevant releases.

Explanation

Correct Answer

C:

This change-control gate requires teams to require peer review for fsso across domain sites changes and an acceptance check that will log on from each supported domain site and verify resolved identities in the FortiGate FSSO table 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 log on from each supported domain site and verify resolved identities in the FortiGate FSSO table.

Incorrect Answers

A:

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 fsso across domain sites review. The preventive test must enforce that staff will configure approved DC monitoring or collectors for all relevant logon sources and group mappings and subsequently can log on from each supported domain site and verify resolved identities in the FortiGate FSSO table; the proposed source address selection gate would not check that same control.

B:

A review gate for per-policy source nat, such as require peer review for per-policy source nat changes and an acceptance check that will capture egress packets and verify public source translation for a test client before relevant releases, can be useful where outbound branch clients require internet egress through the WAN interface address but see unroutable private source addresses upstream, but it is not the approved fsso across domain sites review. The preventive test must enforce that staff will configure approved DC monitoring or collectors for all relevant logon sources and group mappings and subsequently can log on from each supported domain site and verify resolved identities in the FortiGate FSSO table; the proposed per-policy source nat gate would not check that same control.

D:

A review gate for service port matching, such as require peer review for service port matching changes and an acceptance check that will check a TCP 8443 test session against service and policy match results before relevant releases, can be useful where a new internal HTTPS application uses TCP 8443 but its firewall rule permits only standard TCP 443, but it is not the approved fsso across domain sites review. The preventive test must enforce that staff will configure approved DC monitoring or collectors for all relevant logon sources and group mappings and subsequently can log on from each supported domain site and verify resolved identities in the FortiGate FSSO table; the proposed service port matching gate would not check that same control.

Question 310

A FortiOS 7.6 review of a managed branch perimeter reports the following condition: A multi-domain organization sees group membership only from headquarters while remote domain-controller logons are missing. The operator corrected the configuration by choosing to configure approved DC monitoring or collectors for all relevant logon sources and group mappings. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Capture egress packets and verify public source translation for a test client.
  2. Test Finance and guest sources against the same destination and record selected policies.
  3. Require peer review for fsso across domain sites changes and an acceptance check that will log on from each supported domain site and verify resolved identities in the FortiGate FSSO table before relevant releases.
  4. Log on from each supported domain site and verify resolved identities in the FortiGate FSSO table.
  5. Check a TCP 8443 test session against service and policy match results.

Explanation

Correct Answers

C:

The organization already encountered the failure where a multi-domain organization sees group membership only from headquarters while remote domain-controller logons are missing, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table, this gate checks future revisions without claiming that the current configuration is permanently correct.

D:

It measures the operational result after the correction to configure approved DC monitoring or collectors for all relevant logon sources and group mappings, and it directly checks the reported condition: a multi-domain organization sees group membership only from headquarters while remote domain-controller logons are missing. For fsso across domain sites, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

A:

The proposed evidence, to capture egress packets and verify public source translation for a test client, checks per-policy source nat in a situation such as outbound branch clients require internet egress through the WAN interface address but see unroutable private source addresses upstream, not the required fsso across domain sites acceptance. For the affected firewall behavior the directly discriminating check is to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table, alongside a review of fsso across domain sites rather than per-policy source nat settings.

B:

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 fsso across domain sites acceptance. For the affected firewall behavior the directly discriminating check is to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table, alongside a review of fsso across domain sites rather than source address selection settings.

E:

The proposed evidence, to check a TCP 8443 test session against service and policy match results, checks service port matching in a situation such as a new internal HTTPS application uses TCP 8443 but its firewall rule permits only standard TCP 443, not the required fsso across domain sites acceptance. For the affected firewall behavior the directly discriminating check is to log on from each supported domain site and verify resolved identities in the FortiGate FSSO table, alongside a review of fsso across domain sites rather than service port matching settings.

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