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 1

Question 1

A FortiOS 7.6 review of a datacenter security boundary reports the following condition: An edge FortiGate accepts HTTPS administration from untrusted WAN addresses although support staff use a dedicated management subnet. The requirement concerns restricted administrator access while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Enable relevant firewall-policy traffic logging and configure a reachable retention destination.
  2. Connect matching dedicated heartbeat interfaces correctly and verify HA heartbeat communication.
  3. Create a restricted administrator profile that grants log access without unneeded configuration rights.
  4. Limit HTTPS administrative access to the intended management interface and approved trusted hosts.

Explanation

Correct Answer

D:

Choosing to limit HTTPS administrative access to the intended management interface and approved trusted hosts 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: try HTTPS from an approved management host and a disallowed internet client and compare access.

Incorrect Answers

A:

Enabling relevant firewall-policy traffic logging and configure a reachable retention destination would focus the new configuration on forward traffic log destination, for which traffic matching an accept policy has no retained records during incident investigation may be a valid concern, but this restricted administrator access configuration has a different failure. Evidence for restricted administrator access requires staff to try HTTPS from an approved management host and a disallowed internet client and compare access; the proposed forward traffic log destination change cannot deliver that restricted administrator access result by itself.

B:

Connecting matching dedicated heartbeat interfaces correctly and verify HA heartbeat communication would focus the new configuration on fgcp heartbeat cabling, for which two same-model cluster members cannot reliably discover one another because heartbeat ports are crossed between devices may be a valid concern, but this restricted administrator access configuration has a different failure. Evidence for restricted administrator access requires staff to try HTTPS from an approved management host and a disallowed internet client and compare access; the proposed fgcp heartbeat cabling change cannot deliver that restricted administrator access result by itself.

C:

Creating a restricted administrator profile that grants log access without unneeded configuration rights would focus the new configuration on least-privilege administrative profiles, for which a help-desk operator only needs to view event logs but is assigned a full configuration administrator profile may be a valid concern, but this restricted administrator access configuration has a different failure. Evidence for restricted administrator access requires staff to try HTTPS from an approved management host and a disallowed internet client and compare access; the proposed least-privilege administrative profiles change cannot deliver that restricted administrator access result by itself.

Question 2

During FortiOS 7.6 operations at an enterprise gateway change window, the evidence is: An edge FortiGate accepts HTTPS administration from untrusted WAN addresses although support staff use a dedicated management subnet. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this restricted administrator access failure?

  1. Enable only administrator login logging while leaving forward-traffic logging disabled.
  2. Use unrelated management ports with no shared HA heartbeat configuration.
  3. Leave HTTPS administration reachable on the public WAN without trusted-host restrictions.
  4. Grant the operator unrestricted super-admin rights for convenience.

Explanation

Correct Answer

C:

The problem arises when administrators leave HTTPS administration reachable on the public WAN without trusted-host restrictions, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to limit HTTPS administrative access to the intended management interface and approved trusted hosts.

Incorrect Answers

A:

The alternative cause involving forward traffic log destination can produce a different failure, for example when traffic matching an accept policy has no retained records during incident investigation; it is not the restricted administrator access case. The more specific error here is the choice to leave HTTPS administration reachable on the public WAN without trusted-host restrictions; check it by attempting to try HTTPS from an approved management host and a disallowed internet client and compare access before making an unrelated forward traffic log destination change.

B:

The alternative cause involving fgcp heartbeat cabling can produce a different failure, for example when two same-model cluster members cannot reliably discover one another because heartbeat ports are crossed between devices; it is not the restricted administrator access case. The more specific error here is the choice to leave HTTPS administration reachable on the public WAN without trusted-host restrictions; check it by attempting to try HTTPS from an approved management host and a disallowed internet client and compare access before making an unrelated fgcp heartbeat cabling change.

D:

The alternative cause involving least-privilege administrative profiles can produce a different failure, for example when a help-desk operator only needs to view event logs but is assigned a full configuration administrator profile; it is not the restricted administrator access case. The more specific error here is the choice to leave HTTPS administration reachable on the public WAN without trusted-host restrictions; check it by attempting to try HTTPS from an approved management host and a disallowed internet client and compare access before making an unrelated least-privilege administrative profiles change.

Question 3

At a redundant regional firewall pair, a FortiGate running FortiOS 7.6 has this observation: An edge FortiGate accepts HTTPS administration from untrusted WAN addresses although support staff use a dedicated management subnet. Investigators confirmed this cause: administrators chose to leave HTTPS administration reachable on the public WAN without trusted-host restrictions. Which action MOST directly corrects the confirmed error?

  1. Limit HTTPS administrative access to the intended management interface and approved trusted hosts.
  2. Enable relevant firewall-policy traffic logging and configure a reachable retention destination.
  3. Connect matching dedicated heartbeat interfaces correctly and verify HA heartbeat communication.
  4. Leave HTTPS administration reachable on the public WAN without trusted-host restrictions.

Explanation

Correct Answer

A:

This addresses restricted administrator access without needlessly weakening separate security or routing controls. Given the observed condition—an edge FortiGate accepts HTTPS administration from untrusted WAN addresses although support staff use a dedicated management subnet—the operator should then try HTTPS from an approved management host and a disallowed internet client and compare access.

Incorrect Answers

B:

Changing the mechanism to enable relevant firewall-policy traffic logging and configure a reachable retention destination could be a sensible correction for forward traffic log destination when traffic matching an accept policy has no retained records during incident investigation. The targeted fix is to limit HTTPS administrative access to the intended management interface and approved trusted hosts; a review of forward traffic log destination would not, by itself, prove that the team can try HTTPS from an approved management host and a disallowed internet client and compare access.

C:

Changing the mechanism to connect matching dedicated heartbeat interfaces correctly and verify HA heartbeat communication could be a sensible correction for fgcp heartbeat cabling when two same-model cluster members cannot reliably discover one another because heartbeat ports are crossed between devices. The targeted fix is to limit HTTPS administrative access to the intended management interface and approved trusted hosts; a review of fgcp heartbeat cabling would not, by itself, prove that the team can try HTTPS from an approved management host and a disallowed internet client and compare access.

D:

The proposal repeats the confirmed restricted administrator access error by choosing to leave HTTPS administration reachable on the public WAN without trusted-host restrictions. A corrective change must instead limit HTTPS administrative access to the intended management interface and approved trusted hosts and then produce the measurable result to try HTTPS from an approved management host and a disallowed internet client and compare access; repeating the failed setting cannot serve as a repair.

Question 4

A FortiOS 7.6 review of a remote-office migration reports the following condition: An edge FortiGate accepts HTTPS administration from untrusted WAN addresses although support staff use a dedicated management subnet. The incident has been fixed, and the owner wants to prevent a recurrence of the restricted administrator access problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for forward traffic log destination changes and an acceptance check that will generate a known allowed session and find its traffic log in the selected storage destination before relevant releases.
  2. Require peer review for least-privilege administrative profiles changes and an acceptance check that will log in with the limited account and confirm logs work while unauthorized configuration changes fail before relevant releases.
  3. Require peer review for restricted administrator access changes and an acceptance check that will try HTTPS from an approved management host and a disallowed internet client and compare access before relevant releases.
  4. Require peer review for fgcp heartbeat cabling changes and an acceptance check that will inspect HA member status and confirm stable heartbeat communication on the designated links before relevant releases.

Explanation

Correct Answer

C:

This change-control gate requires teams to require peer review for restricted administrator access changes and an acceptance check that will try HTTPS from an approved management host and a disallowed internet client and compare access 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 try HTTPS from an approved management host and a disallowed internet client and compare access.

Incorrect Answers

A:

A review gate for forward traffic log destination, such as require peer review for forward traffic log destination changes and an acceptance check that will generate a known allowed session and find its traffic log in the selected storage destination before relevant releases, can be useful where traffic matching an accept policy has no retained records during incident investigation, but it is not the approved restricted administrator access review. The preventive test must enforce that staff will limit HTTPS administrative access to the intended management interface and approved trusted hosts and subsequently can try HTTPS from an approved management host and a disallowed internet client and compare access; the proposed forward traffic log destination gate would not check that same control.

B:

A review gate for least-privilege administrative profiles, such as require peer review for least-privilege administrative profiles changes and an acceptance check that will log in with the limited account and confirm logs work while unauthorized configuration changes fail before relevant releases, can be useful where a help-desk operator only needs to view event logs but is assigned a full configuration administrator profile, but it is not the approved restricted administrator access review. The preventive test must enforce that staff will limit HTTPS administrative access to the intended management interface and approved trusted hosts and subsequently can try HTTPS from an approved management host and a disallowed internet client and compare access; the proposed least-privilege administrative profiles gate would not check that same control.

D:

A review gate for fgcp heartbeat cabling, such as require peer review for fgcp heartbeat cabling changes and an acceptance check that will inspect HA member status and confirm stable heartbeat communication on the designated links before relevant releases, can be useful where two same-model cluster members cannot reliably discover one another because heartbeat ports are crossed between devices, but it is not the approved restricted administrator access review. The preventive test must enforce that staff will limit HTTPS administrative access to the intended management interface and approved trusted hosts and subsequently can try HTTPS from an approved management host and a disallowed internet client and compare access; the proposed fgcp heartbeat cabling gate would not check that same control.

Question 5

During FortiOS 7.6 operations at a monitored business uplink, the evidence is: An edge FortiGate accepts HTTPS administration from untrusted WAN addresses although support staff use a dedicated management subnet. The operator corrected the configuration by choosing to limit HTTPS administrative access to the intended management interface and approved trusted hosts. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Try HTTPS from an approved management host and a disallowed internet client and compare access.
  2. Require peer review for restricted administrator access changes and an acceptance check that will try HTTPS from an approved management host and a disallowed internet client and compare access before relevant releases.
  3. Log in with the limited account and confirm logs work while unauthorized configuration changes fail.
  4. Generate a known allowed session and find its traffic log in the selected storage destination.
  5. Inspect HA member status and confirm stable heartbeat communication on the designated links.

Explanation

Correct Answers

A:

It measures the operational result after the correction to limit HTTPS administrative access to the intended management interface and approved trusted hosts, and it directly checks the reported condition: an edge FortiGate accepts HTTPS administration from untrusted WAN addresses although support staff use a dedicated management subnet. For restricted administrator access, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

B:

The organization already encountered the failure where an edge FortiGate accepts HTTPS administration from untrusted WAN addresses although support staff use a dedicated management subnet, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to try HTTPS from an approved management host and a disallowed internet client and compare access, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

C:

The proposed evidence, to log in with the limited account and confirm logs work while unauthorized configuration changes fail, checks least-privilege administrative profiles in a situation such as a help-desk operator only needs to view event logs but is assigned a full configuration administrator profile, not the required restricted administrator access acceptance. For the affected firewall behavior the directly discriminating check is to try HTTPS from an approved management host and a disallowed internet client and compare access, alongside a review of restricted administrator access rather than least-privilege administrative profiles settings.

D:

The proposed evidence, to generate a known allowed session and find its traffic log in the selected storage destination, checks forward traffic log destination in a situation such as traffic matching an accept policy has no retained records during incident investigation, not the required restricted administrator access acceptance. For the affected firewall behavior the directly discriminating check is to try HTTPS from an approved management host and a disallowed internet client and compare access, alongside a review of restricted administrator access rather than forward traffic log destination settings.

E:

The proposed evidence, to inspect HA member status and confirm stable heartbeat communication on the designated links, checks fgcp heartbeat cabling in a situation such as two same-model cluster members cannot reliably discover one another because heartbeat ports are crossed between devices, not the required restricted administrator access acceptance. For the affected firewall behavior the directly discriminating check is to try HTTPS from an approved management host and a disallowed internet client and compare access, alongside a review of restricted administrator access rather than fgcp heartbeat cabling settings.

Question 6

At an internal application segment, a FortiGate running FortiOS 7.6 has this observation: New branch clients receive no address even though the FortiGate LAN interface is their designated gateway. The requirement concerns initial dhcp service while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Configure reachable DNS resolvers for FortiGate local-out name resolution and test lookup from the device.
  2. Align cluster peers to the same supported firmware and compatible hardware before enrollment.
  3. Configure the analyzer destination and verify device authorization and registration on FortiAnalyzer.
  4. Enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool.

Explanation

Correct Answer

D:

Choosing to enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool 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: renew a branch client lease and check its address, gateway, and server interface.

Incorrect Answers

A:

Configuring reachable DNS resolvers for FortiGate local-out name resolution and test lookup from the device would focus the new configuration on management plane dns resolution, for which fortiGuard ratings and hostname-based update checks fail even though the data-plane WAN route is healthy may be a valid concern, but this initial dhcp service configuration has a different failure. Evidence for initial dhcp service requires staff to renew a branch client lease and check its address, gateway, and server interface; the proposed management plane dns resolution change cannot deliver that initial dhcp service result by itself.

B:

Selecting align cluster peers to the same supported firmware and compatible hardware before enrollment would focus the new configuration on ha firmware parity, for which two intended FGCP peers run incompatible FortiOS builds and fail to form a stable synchronized cluster may be a valid concern, but this initial dhcp service configuration has a different failure. Evidence for initial dhcp service requires staff to renew a branch client lease and check its address, gateway, and server interface; the proposed ha firmware parity change cannot deliver that initial dhcp service result by itself.

C:

Configuring the analyzer destination and verify device authorization and registration on FortiAnalyzer would focus the new configuration on fortianalyzer device registration, for which an external FortiAnalyzer receives no logs after a new FortiGate is provisioned may be a valid concern, but this initial dhcp service configuration has a different failure. Evidence for initial dhcp service requires staff to renew a branch client lease and check its address, gateway, and server interface; the proposed fortianalyzer device registration change cannot deliver that initial dhcp service result by itself.

Question 7

A FortiOS 7.6 review of a hybrid-network deployment reports the following condition: New branch clients receive no address even though the FortiGate LAN interface is their designated gateway. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this initial dhcp service failure?

  1. Change a LAN DHCP lease duration instead of fixing the FortiGate name resolver.
  2. Configure a local syslog facility name but never register the FortiGate with FortiAnalyzer.
  3. Attempt to build an FGCP cluster with mismatched firmware builds and assume automatic conversion.
  4. Enable a DHCP server on the upstream WAN port instead of the branch client interface.

Explanation

Correct Answer

D:

The problem arises when administrators enable a DHCP server on the upstream WAN port instead of the branch client interface, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool.

Incorrect Answers

A:

The alternative cause involving management plane dns resolution can produce a different failure, for example when fortiGuard ratings and hostname-based update checks fail even though the data-plane WAN route is healthy; it is not the initial dhcp service case. The more specific error here is the choice to enable a DHCP server on the upstream WAN port instead of the branch client interface; check it by attempting to renew a branch client lease and check its address, gateway, and server interface before making an unrelated management plane dns resolution change.

B:

The alternative cause involving fortianalyzer device registration can produce a different failure, for example when an external FortiAnalyzer receives no logs after a new FortiGate is provisioned; it is not the initial dhcp service case. The more specific error here is the choice to enable a DHCP server on the upstream WAN port instead of the branch client interface; check it by attempting to renew a branch client lease and check its address, gateway, and server interface before making an unrelated fortianalyzer device registration change.

C:

The alternative cause involving ha firmware parity can produce a different failure, for example when two intended FGCP peers run incompatible FortiOS builds and fail to form a stable synchronized cluster; it is not the initial dhcp service case. The more specific error here is the choice to enable a DHCP server on the upstream WAN port instead of the branch client interface; check it by attempting to renew a branch client lease and check its address, gateway, and server interface before making an unrelated ha firmware parity change.

Question 8

During FortiOS 7.6 operations at an operations incident response, the evidence is: New branch clients receive no address even though the FortiGate LAN interface is their designated gateway. Investigators confirmed this cause: administrators chose to enable a DHCP server on the upstream WAN port instead of the branch client interface. Which action MOST directly corrects the confirmed error?

  1. Enable a DHCP server on the upstream WAN port instead of the branch client interface.
  2. Enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool.
  3. Align cluster peers to the same supported firmware and compatible hardware before enrollment.
  4. Configure the analyzer destination and verify device authorization and registration on FortiAnalyzer.

Explanation

Correct Answer

B:

This addresses initial dhcp service without needlessly weakening separate security or routing controls. Given the observed condition—new branch clients receive no address even though the FortiGate LAN interface is their designated gateway—the operator should then renew a branch client lease and check its address, gateway, and server interface.

Incorrect Answers

A:

The proposal repeats the confirmed initial dhcp service error by choosing to enable a DHCP server on the upstream WAN port instead of the branch client interface. A corrective change must instead enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool and then produce the measurable result to renew a branch client lease and check its address, gateway, and server interface; repeating the failed setting cannot serve as a repair.

C:

Changing the mechanism to align cluster peers to the same supported firmware and compatible hardware before enrollment could be a sensible correction for ha firmware parity when two intended FGCP peers run incompatible FortiOS builds and fail to form a stable synchronized cluster. The targeted fix is to enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool; a review of ha firmware parity would not, by itself, prove that the team can renew a branch client lease and check its address, gateway, and server interface.

D:

Changing the mechanism to configure the analyzer destination and verify device authorization and registration on FortiAnalyzer could be a sensible correction for fortianalyzer device registration when an external FortiAnalyzer receives no logs after a new FortiGate is provisioned. The targeted fix is to enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool; a review of fortianalyzer device registration would not, by itself, prove that the team can renew a branch client lease and check its address, gateway, and server interface.

Question 9

At a network segmentation review, a FortiGate running FortiOS 7.6 has this observation: New branch clients receive no address even though the FortiGate LAN interface is their designated gateway. The incident has been fixed, and the owner wants to prevent a recurrence of the initial dhcp service problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for ha firmware parity changes and an acceptance check that will check cluster membership, firmware identity, and synchronized configuration after alignment before relevant releases.
  2. Require peer review for initial dhcp service changes and an acceptance check that will renew a branch client lease and check its address, gateway, and server interface before relevant releases.
  3. Require peer review for management plane dns resolution changes and an acceptance check that will run a FortiGate-local DNS query and verify update hostname resolution before repeating the rating check before relevant releases.
  4. Require peer review for fortianalyzer device registration changes and an acceptance check that will confirm the device appears as authorized and a test traffic event reaches FortiAnalyzer before relevant releases.

Explanation

Correct Answer

B:

This change-control gate requires teams to require peer review for initial dhcp service changes and an acceptance check that will renew a branch client lease and check its address, gateway, and server interface 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 renew a branch client lease and check its address, gateway, and server interface.

Incorrect Answers

A:

A review gate for ha firmware parity, such as require peer review for ha firmware parity changes and an acceptance check that will check cluster membership, firmware identity, and synchronized configuration after alignment before relevant releases, can be useful where two intended FGCP peers run incompatible FortiOS builds and fail to form a stable synchronized cluster, but it is not the approved initial dhcp service review. The preventive test must enforce that staff will enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool and subsequently can renew a branch client lease and check its address, gateway, and server interface; the proposed ha firmware parity gate would not check that same control.

C:

A review gate for management plane dns resolution, such as require peer review for management plane dns resolution changes and an acceptance check that will run a FortiGate-local DNS query and verify update hostname resolution before repeating the rating check before relevant releases, can be useful where fortiGuard ratings and hostname-based update checks fail even though the data-plane WAN route is healthy, but it is not the approved initial dhcp service review. The preventive test must enforce that staff will enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool and subsequently can renew a branch client lease and check its address, gateway, and server interface; the proposed management plane dns resolution gate would not check that same control.

D:

A review gate for fortianalyzer device registration, such as require peer review for fortianalyzer device registration changes and an acceptance check that will confirm the device appears as authorized and a test traffic event reaches FortiAnalyzer before relevant releases, can be useful where an external FortiAnalyzer receives no logs after a new FortiGate is provisioned, but it is not the approved initial dhcp service review. The preventive test must enforce that staff will enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool and subsequently can renew a branch client lease and check its address, gateway, and server interface; the proposed fortianalyzer device registration gate would not check that same control.

Question 10

A FortiOS 7.6 review of a managed branch perimeter reports the following condition: New branch clients receive no address even though the FortiGate LAN interface is their designated gateway. The operator corrected the configuration by choosing to enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Renew a branch client lease and check its address, gateway, and server interface.
  2. Confirm the device appears as authorized and a test traffic event reaches FortiAnalyzer.
  3. Run a FortiGate-local DNS query and verify update hostname resolution before repeating the rating check.
  4. Require peer review for initial dhcp service changes and an acceptance check that will renew a branch client lease and check its address, gateway, and server interface before relevant releases.
  5. Check cluster membership, firmware identity, and synchronized configuration after alignment.

Explanation

Correct Answers

A:

It measures the operational result after the correction to enable the DHCP server on the correct LAN interface with a nonoverlapping subnet, gateway, and lease pool, and it directly checks the reported condition: new branch clients receive no address even though the FortiGate LAN interface is their designated gateway. For initial dhcp service, 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 new branch clients receive no address even though the FortiGate LAN interface is their designated gateway, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to renew a branch client lease and check its address, gateway, and server interface, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

B:

The proposed evidence, to confirm the device appears as authorized and a test traffic event reaches FortiAnalyzer, checks fortianalyzer device registration in a situation such as an external FortiAnalyzer receives no logs after a new FortiGate is provisioned, not the required initial dhcp service acceptance. For the affected firewall behavior the directly discriminating check is to renew a branch client lease and check its address, gateway, and server interface, alongside a review of initial dhcp service rather than fortianalyzer device registration settings.

C:

The proposed evidence, to run a FortiGate-local DNS query and verify update hostname resolution before repeating the rating check, checks management plane dns resolution in a situation such as fortiGuard ratings and hostname-based update checks fail even though the data-plane WAN route is healthy, not the required initial dhcp service acceptance. For the affected firewall behavior the directly discriminating check is to renew a branch client lease and check its address, gateway, and server interface, alongside a review of initial dhcp service rather than management plane dns resolution settings.

E:

The proposed evidence, to check cluster membership, firmware identity, and synchronized configuration after alignment, checks ha firmware parity in a situation such as two intended FGCP peers run incompatible FortiOS builds and fail to form a stable synchronized cluster, not the required initial dhcp service acceptance. For the affected firewall behavior the directly discriminating check is to renew a branch client lease and check its address, gateway, and server interface, alongside a review of initial dhcp service rather than ha firmware parity settings.

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