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 47

Question 460

A FortiOS 7.6 review of a managed branch perimeter reports the following condition: Downloads over an inspected protocol are not scanned because the applied AV profile lacks the appropriate protocol settings. The operator corrected the configuration by choosing to configure applicable AV and protocol options for the actual session protocol. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Load-test representative traffic and check IPS process CPU and security coverage together.
  2. Transfer a safe test object through the intended protocol and inspect AV events.
  3. Test an exempt site and an ordinary site and verify different inspection behavior.
  4. Require peer review for antivirus protocol coverage changes and an acceptance check that will transfer a safe test object through the intended protocol and inspect AV events before relevant releases.
  5. Retest the application and confirm unrelated high-risk test signatures remain enforced.

Explanation

Correct Answers

B:

It measures the operational result after the correction to configure applicable AV and protocol options for the actual session protocol, and it directly checks the reported condition: downloads over an inspected protocol are not scanned because the applied AV profile lacks the appropriate protocol settings. For antivirus protocol coverage, 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 downloads over an inspected protocol are not scanned because the applied AV profile lacks the appropriate protocol settings, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to transfer a safe test object through the intended protocol and inspect AV events, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

A:

The proposed evidence, to load-test representative traffic and check IPS process CPU and security coverage together, checks ips cpu resource pressure in a situation such as traffic inspection consumes excessive CPU after a very broad IPS signature set was applied to high-volume flows, not the required antivirus protocol coverage acceptance. For the affected firewall behavior the directly discriminating check is to transfer a safe test object through the intended protocol and inspect AV events, alongside a review of antivirus protocol coverage rather than ips cpu resource pressure settings.

C:

The proposed evidence, to test an exempt site and an ordinary site and verify different inspection behavior, checks sensitive https inspection exemption in a situation such as a compliance policy prohibits decrypting specified financial transactions but still requires encrypted session visibility, not the required antivirus protocol coverage acceptance. For the affected firewall behavior the directly discriminating check is to transfer a safe test object through the intended protocol and inspect AV events, alongside a review of antivirus protocol coverage rather than sensitive https inspection exemption settings.

E:

The proposed evidence, to retest the application and confirm unrelated high-risk test signatures remain enforced, checks ips false positive handling in a situation such as a production application is disrupted by one signature, but disabling the entire IPS profile would expose unrelated threats, not the required antivirus protocol coverage acceptance. For the affected firewall behavior the directly discriminating check is to transfer a safe test object through the intended protocol and inspect AV events, alongside a review of antivirus protocol coverage rather than ips false positive handling settings.

Question 461

During FortiOS 7.6 operations at a datacenter security boundary, the evidence is: A detected malware sample is blocked but security staff cannot associate it with the source session. The requirement concerns antivirus incident trace while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Enable and inspect antivirus logs alongside the matched traffic policy and endpoint details.
  2. Change the targeted IPS signature action to Block under the approved security policy.
  3. Inspect the server certificate identity, name matching, and FortiGate SSL exception handling.
  4. Enable policy-approved decryption and ensure the IPS sensor receives inspectable content.

Explanation

Correct Answer

A:

Choosing to enable and inspect antivirus logs alongside the matched traffic policy and endpoint details 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: replay an approved test object and correlate AV detection, policy ID, and session source.

Incorrect Answers

B:

Selecting change the targeted IPS signature action to Block under the approved security policy would focus the new configuration on ips block versus monitor, for which iPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor may be a valid concern, but this antivirus incident trace configuration has a different failure. Evidence for antivirus incident trace requires staff to replay an approved test object and correlate AV detection, policy ID, and session source; the proposed ips block versus monitor change cannot deliver that antivirus incident trace result by itself.

C:

Inspecting the server certificate identity, name matching, and FortiGate SSL exception handling would focus the new configuration on certificate hostname mismatch, for which users see certificate errors only for one hostname after a proxy inspection change and DNS addresses are otherwise correct may be a valid concern, but this antivirus incident trace configuration has a different failure. Evidence for antivirus incident trace requires staff to replay an approved test object and correlate AV detection, policy ID, and session source; the proposed certificate hostname mismatch change cannot deliver that antivirus incident trace result by itself.

D:

Enabling policy-approved decryption and ensure the IPS sensor receives inspectable content would focus the new configuration on ips on encrypted sessions, for which an encrypted attack payload is not examined by IPS although the IPS sensor is attached to the policy may be a valid concern, but this antivirus incident trace configuration has a different failure. Evidence for antivirus incident trace requires staff to replay an approved test object and correlate AV detection, policy ID, and session source; the proposed ips on encrypted sessions change cannot deliver that antivirus incident trace result by itself.

Question 462

At an enterprise gateway change window, a FortiGate running FortiOS 7.6 has this observation: A detected malware sample is blocked but security staff cannot associate it with the source session. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this antivirus incident trace failure?

  1. Assume IPS can inspect arbitrary ciphertext without the SSL visibility required by the signature.
  2. Leave the signature set to Monitor and treat its log as evidence of dropped traffic.
  3. Search only HA heartbeat logs for a malware block that occurred in data-plane inspection.
  4. Override all mismatched certificates without verifying the presented hostname.

Explanation

Correct Answer

C:

The problem arises when administrators search only HA heartbeat logs for a malware block that occurred in data-plane inspection, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to enable and inspect antivirus logs alongside the matched traffic policy and endpoint details.

Incorrect Answers

A:

The alternative cause involving ips on encrypted sessions can produce a different failure, for example when an encrypted attack payload is not examined by IPS although the IPS sensor is attached to the policy; it is not the antivirus incident trace case. The more specific error here is the choice to search only HA heartbeat logs for a malware block that occurred in data-plane inspection; check it by attempting to replay an approved test object and correlate AV detection, policy ID, and session source before making an unrelated ips on encrypted sessions change.

B:

The alternative cause involving ips block versus monitor can produce a different failure, for example when iPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor; it is not the antivirus incident trace case. The more specific error here is the choice to search only HA heartbeat logs for a malware block that occurred in data-plane inspection; check it by attempting to replay an approved test object and correlate AV detection, policy ID, and session source before making an unrelated ips block versus monitor change.

D:

The alternative cause involving certificate hostname mismatch can produce a different failure, for example when users see certificate errors only for one hostname after a proxy inspection change and DNS addresses are otherwise correct; it is not the antivirus incident trace case. The more specific error here is the choice to search only HA heartbeat logs for a malware block that occurred in data-plane inspection; check it by attempting to replay an approved test object and correlate AV detection, policy ID, and session source before making an unrelated certificate hostname mismatch change.

Question 463

A FortiOS 7.6 review of a redundant regional firewall pair reports the following condition: A detected malware sample is blocked but security staff cannot associate it with the source session. Investigators confirmed this cause: administrators chose to search only HA heartbeat logs for a malware block that occurred in data-plane inspection. Which action MOST directly corrects the confirmed error?

  1. Inspect the server certificate identity, name matching, and FortiGate SSL exception handling.
  2. Search only HA heartbeat logs for a malware block that occurred in data-plane inspection.
  3. Enable policy-approved decryption and ensure the IPS sensor receives inspectable content.
  4. Enable and inspect antivirus logs alongside the matched traffic policy and endpoint details.

Explanation

Correct Answer

D:

This addresses antivirus incident trace without needlessly weakening separate security or routing controls. Given the observed condition—a detected malware sample is blocked but security staff cannot associate it with the source session—the operator should then replay an approved test object and correlate AV detection, policy ID, and session source.

Incorrect Answers

A:

Changing the mechanism to inspect the server certificate identity, name matching, and FortiGate SSL exception handling could be a sensible correction for certificate hostname mismatch when users see certificate errors only for one hostname after a proxy inspection change and DNS addresses are otherwise correct. The targeted fix is to enable and inspect antivirus logs alongside the matched traffic policy and endpoint details; a review of certificate hostname mismatch would not, by itself, prove that the team can replay an approved test object and correlate AV detection, policy ID, and session source.

B:

The proposal repeats the confirmed antivirus incident trace error by choosing to search only HA heartbeat logs for a malware block that occurred in data-plane inspection. A corrective change must instead enable and inspect antivirus logs alongside the matched traffic policy and endpoint details and then produce the measurable result to replay an approved test object and correlate AV detection, policy ID, and session source; repeating the failed setting cannot serve as a repair.

C:

Changing the mechanism to enable policy-approved decryption and ensure the IPS sensor receives inspectable content could be a sensible correction for ips on encrypted sessions when an encrypted attack payload is not examined by IPS although the IPS sensor is attached to the policy. The targeted fix is to enable and inspect antivirus logs alongside the matched traffic policy and endpoint details; a review of ips on encrypted sessions would not, by itself, prove that the team can replay an approved test object and correlate AV detection, policy ID, and session source.

Question 464

During FortiOS 7.6 operations at a remote-office migration, the evidence is: A detected malware sample is blocked but security staff cannot associate it with the source session. The incident has been fixed, and the owner wants to prevent a recurrence of the antivirus incident trace problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for antivirus incident trace changes and an acceptance check that will replay an approved test object and correlate AV detection, policy ID, and session source before relevant releases.
  2. Require peer review for ips on encrypted sessions changes and an acceptance check that will run an authorized encrypted test payload and confirm permitted inspection and IPS result before relevant releases.
  3. Require peer review for certificate hostname mismatch changes and an acceptance check that will connect to a test name with an intentionally mismatched certificate and inspect the logged decision before relevant releases.
  4. Require peer review for ips block versus monitor changes and an acceptance check that will replay a controlled attack indicator and verify the connection is denied with an IPS block log before relevant releases.

Explanation

Correct Answer

A:

This change-control gate requires teams to require peer review for antivirus incident trace changes and an acceptance check that will replay an approved test object and correlate AV detection, policy ID, and session source 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 replay an approved test object and correlate AV detection, policy ID, and session source.

Incorrect Answers

B:

A review gate for ips on encrypted sessions, such as require peer review for ips on encrypted sessions changes and an acceptance check that will run an authorized encrypted test payload and confirm permitted inspection and IPS result before relevant releases, can be useful where an encrypted attack payload is not examined by IPS although the IPS sensor is attached to the policy, but it is not the approved antivirus incident trace review. The preventive test must enforce that staff will enable and inspect antivirus logs alongside the matched traffic policy and endpoint details and subsequently can replay an approved test object and correlate AV detection, policy ID, and session source; the proposed ips on encrypted sessions gate would not check that same control.

C:

A review gate for certificate hostname mismatch, such as require peer review for certificate hostname mismatch changes and an acceptance check that will connect to a test name with an intentionally mismatched certificate and inspect the logged decision before relevant releases, can be useful where users see certificate errors only for one hostname after a proxy inspection change and DNS addresses are otherwise correct, but it is not the approved antivirus incident trace review. The preventive test must enforce that staff will enable and inspect antivirus logs alongside the matched traffic policy and endpoint details and subsequently can replay an approved test object and correlate AV detection, policy ID, and session source; the proposed certificate hostname mismatch gate would not check that same control.

D:

A review gate for ips block versus monitor, such as require peer review for ips block versus monitor changes and an acceptance check that will replay a controlled attack indicator and verify the connection is denied with an IPS block log before relevant releases, can be useful where iPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor, but it is not the approved antivirus incident trace review. The preventive test must enforce that staff will enable and inspect antivirus logs alongside the matched traffic policy and endpoint details and subsequently can replay an approved test object and correlate AV detection, policy ID, and session source; the proposed ips block versus monitor gate would not check that same control.

Question 465

At a monitored business uplink, a FortiGate running FortiOS 7.6 has this observation: A detected malware sample is blocked but security staff cannot associate it with the source session. The operator corrected the configuration by choosing to enable and inspect antivirus logs alongside the matched traffic policy and endpoint details. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Require peer review for antivirus incident trace changes and an acceptance check that will replay an approved test object and correlate AV detection, policy ID, and session source before relevant releases.
  2. Replay a controlled attack indicator and verify the connection is denied with an IPS block log.
  3. Replay an approved test object and correlate AV detection, policy ID, and session source.
  4. Run an authorized encrypted test payload and confirm permitted inspection and IPS result.
  5. Connect to a test name with an intentionally mismatched certificate and inspect the logged decision.

Explanation

Correct Answers

A:

The organization already encountered the failure where a detected malware sample is blocked but security staff cannot associate it with the source session, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to replay an approved test object and correlate AV detection, policy ID, and session source, this gate checks future revisions without claiming that the current configuration is permanently correct.

C:

It measures the operational result after the correction to enable and inspect antivirus logs alongside the matched traffic policy and endpoint details, and it directly checks the reported condition: a detected malware sample is blocked but security staff cannot associate it with the source session. For antivirus incident trace, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

B:

The proposed evidence, to replay a controlled attack indicator and verify the connection is denied with an IPS block log, checks ips block versus monitor in a situation such as iPS logs a critical exploit signature but the connection remains permitted because the signature action is Monitor, not the required antivirus incident trace acceptance. For the affected firewall behavior the directly discriminating check is to replay an approved test object and correlate AV detection, policy ID, and session source, alongside a review of antivirus incident trace rather than ips block versus monitor settings.

D:

The proposed evidence, to run an authorized encrypted test payload and confirm permitted inspection and IPS result, checks ips on encrypted sessions in a situation such as an encrypted attack payload is not examined by IPS although the IPS sensor is attached to the policy, not the required antivirus incident trace acceptance. For the affected firewall behavior the directly discriminating check is to replay an approved test object and correlate AV detection, policy ID, and session source, alongside a review of antivirus incident trace rather than ips on encrypted sessions settings.

E:

The proposed evidence, to connect to a test name with an intentionally mismatched certificate and inspect the logged decision, checks certificate hostname mismatch in a situation such as users see certificate errors only for one hostname after a proxy inspection change and DNS addresses are otherwise correct, not the required antivirus incident trace acceptance. For the affected firewall behavior the directly discriminating check is to replay an approved test object and correlate AV detection, policy ID, and session source, alongside a review of antivirus incident trace rather than certificate hostname mismatch settings.

Question 466

A FortiOS 7.6 review of an internal application segment reports the following condition: Large archives traverse the firewall without expected deep scanning due to configured buffer or file-size limits. The requirement concerns file size inspection limits while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Profile IPS workload and scope sensor signatures to required threats while keeping mandatory protection.
  2. Configure the supported Protecting SSL Server profile with the server certificate and matching inbound policy.
  3. Validate FortiGuard IPS database updates and the security profile's active signature filtering.
  4. Review AV inspection-size limits and select a policy for oversize files consistent with risk requirements.

Explanation

Correct Answer

D:

Choosing to review AV inspection-size limits and select a policy for oversize files consistent with risk requirements 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: send safe files around the configured size threshold and inspect scan or oversize actions.

Incorrect Answers

A:

Selecting profile IPS workload and scope sensor signatures to required threats while keeping mandatory protection would focus the new configuration on ips cpu resource pressure, for which traffic inspection consumes excessive CPU after a very broad IPS signature set was applied to high-volume flows may be a valid concern, but this file size inspection limits configuration has a different failure. Evidence for file size inspection limits requires staff to send safe files around the configured size threshold and inspect scan or oversize actions; the proposed ips cpu resource pressure change cannot deliver that file size inspection limits result by itself.

B:

Configuring the supported Protecting SSL Server profile with the server certificate and matching inbound policy would focus the new configuration on inbound encrypted server protection, for which an internal HTTPS server published through the firewall needs inbound payload inspection, not just outbound certificate metadata may be a valid concern, but this file size inspection limits configuration has a different failure. Evidence for file size inspection limits requires staff to send safe files around the configured size threshold and inspect scan or oversize actions; the proposed inbound encrypted server protection change cannot deliver that file size inspection limits result by itself.

C:

Selecting validate FortiGuard IPS database updates and the security profile's active signature filtering would focus the new configuration on fortiguard ips update checks, for which a newly published protection is absent from a firewall using an outdated IPS signature database may be a valid concern, but this file size inspection limits configuration has a different failure. Evidence for file size inspection limits requires staff to send safe files around the configured size threshold and inspect scan or oversize actions; the proposed fortiguard ips update checks change cannot deliver that file size inspection limits result by itself.

Question 467

During FortiOS 7.6 operations at a hybrid-network deployment, the evidence is: Large archives traverse the firewall without expected deep scanning due to configured buffer or file-size limits. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this file size inspection limits failure?

  1. Increase a routing administrative distance without addressing oversize AV scanning behavior.
  2. Apply an outbound certificate-inspection profile and assume it decrypts inbound server payloads.
  3. Replace the VPN phase-two selector instead of updating IPS intelligence.
  4. Disable all inspection and declare resource issues fixed without validating required security controls.

Explanation

Correct Answer

A:

The problem arises when administrators increase a routing administrative distance without addressing oversize AV scanning behavior, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to review AV inspection-size limits and select a policy for oversize files consistent with risk requirements.

Incorrect Answers

B:

The alternative cause involving inbound encrypted server protection can produce a different failure, for example when an internal HTTPS server published through the firewall needs inbound payload inspection, not just outbound certificate metadata; it is not the file size inspection limits case. The more specific error here is the choice to increase a routing administrative distance without addressing oversize AV scanning behavior; check it by attempting to send safe files around the configured size threshold and inspect scan or oversize actions before making an unrelated inbound encrypted server protection change.

C:

The alternative cause involving fortiguard ips update checks can produce a different failure, for example when a newly published protection is absent from a firewall using an outdated IPS signature database; it is not the file size inspection limits case. The more specific error here is the choice to increase a routing administrative distance without addressing oversize AV scanning behavior; check it by attempting to send safe files around the configured size threshold and inspect scan or oversize actions before making an unrelated fortiguard ips update checks change.

D:

The alternative cause involving ips cpu resource pressure can produce a different failure, for example when traffic inspection consumes excessive CPU after a very broad IPS signature set was applied to high-volume flows; it is not the file size inspection limits case. The more specific error here is the choice to increase a routing administrative distance without addressing oversize AV scanning behavior; check it by attempting to send safe files around the configured size threshold and inspect scan or oversize actions before making an unrelated ips cpu resource pressure change.

Question 468

At an operations incident response, a FortiGate running FortiOS 7.6 has this observation: Large archives traverse the firewall without expected deep scanning due to configured buffer or file-size limits. Investigators confirmed this cause: administrators chose to increase a routing administrative distance without addressing oversize AV scanning behavior. Which action MOST directly corrects the confirmed error?

  1. Validate FortiGuard IPS database updates and the security profile's active signature filtering.
  2. Increase a routing administrative distance without addressing oversize AV scanning behavior.
  3. Configure the supported Protecting SSL Server profile with the server certificate and matching inbound policy.
  4. Review AV inspection-size limits and select a policy for oversize files consistent with risk requirements.

Explanation

Correct Answer

D:

This addresses file size inspection limits without needlessly weakening separate security or routing controls. Given the observed condition—large archives traverse the firewall without expected deep scanning due to configured buffer or file-size limits—the operator should then send safe files around the configured size threshold and inspect scan or oversize actions.

Incorrect Answers

A:

Changing the mechanism to validate FortiGuard IPS database updates and the security profile's active signature filtering could be a sensible correction for fortiguard ips update checks when a newly published protection is absent from a firewall using an outdated IPS signature database. The targeted fix is to review AV inspection-size limits and select a policy for oversize files consistent with risk requirements; a review of fortiguard ips update checks would not, by itself, prove that the team can send safe files around the configured size threshold and inspect scan or oversize actions.

B:

The proposal repeats the confirmed file size inspection limits error by choosing to increase a routing administrative distance without addressing oversize AV scanning behavior. A corrective change must instead review AV inspection-size limits and select a policy for oversize files consistent with risk requirements and then produce the measurable result to send safe files around the configured size threshold and inspect scan or oversize actions; repeating the failed setting cannot serve as a repair.

C:

Changing the mechanism to configure the supported Protecting SSL Server profile with the server certificate and matching inbound policy could be a sensible correction for inbound encrypted server protection when an internal HTTPS server published through the firewall needs inbound payload inspection, not just outbound certificate metadata. The targeted fix is to review AV inspection-size limits and select a policy for oversize files consistent with risk requirements; a review of inbound encrypted server protection would not, by itself, prove that the team can send safe files around the configured size threshold and inspect scan or oversize actions.

Question 469

A FortiOS 7.6 review of a network segmentation review reports the following condition: Large archives traverse the firewall without expected deep scanning due to configured buffer or file-size limits. The incident has been fixed, and the owner wants to prevent a recurrence of the file size inspection limits problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for file size inspection limits changes and an acceptance check that will send safe files around the configured size threshold and inspect scan or oversize actions before relevant releases.
  2. Require peer review for inbound encrypted server protection changes and an acceptance check that will connect to the published service and verify payload inspection with the correct local certificate before relevant releases.
  3. Require peer review for fortiguard ips update checks changes and an acceptance check that will check the IPS signature database timestamp and presence of the intended test signature before relevant releases.
  4. Require peer review for ips cpu resource pressure changes and an acceptance check that will load-test representative traffic and check IPS process CPU and security coverage together before relevant releases.

Explanation

Correct Answer

A:

This change-control gate requires teams to require peer review for file size inspection limits changes and an acceptance check that will send safe files around the configured size threshold and inspect scan or oversize actions 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 send safe files around the configured size threshold and inspect scan or oversize actions.

Incorrect Answers

B:

A review gate for inbound encrypted server protection, such as require peer review for inbound encrypted server protection changes and an acceptance check that will connect to the published service and verify payload inspection with the correct local certificate before relevant releases, can be useful where an internal HTTPS server published through the firewall needs inbound payload inspection, not just outbound certificate metadata, but it is not the approved file size inspection limits review. The preventive test must enforce that staff will review AV inspection-size limits and select a policy for oversize files consistent with risk requirements and subsequently can send safe files around the configured size threshold and inspect scan or oversize actions; the proposed inbound encrypted server protection gate would not check that same control.

C:

A review gate for fortiguard ips update checks, such as require peer review for fortiguard ips update checks changes and an acceptance check that will check the IPS signature database timestamp and presence of the intended test signature before relevant releases, can be useful where a newly published protection is absent from a firewall using an outdated IPS signature database, but it is not the approved file size inspection limits review. The preventive test must enforce that staff will review AV inspection-size limits and select a policy for oversize files consistent with risk requirements and subsequently can send safe files around the configured size threshold and inspect scan or oversize actions; the proposed fortiguard ips update checks gate would not check that same control.

D:

A review gate for ips cpu resource pressure, such as require peer review for ips cpu resource pressure changes and an acceptance check that will load-test representative traffic and check IPS process CPU and security coverage together before relevant releases, can be useful where traffic inspection consumes excessive CPU after a very broad IPS signature set was applied to high-volume flows, but it is not the approved file size inspection limits review. The preventive test must enforce that staff will review AV inspection-size limits and select a policy for oversize files consistent with risk requirements and subsequently can send safe files around the configured size threshold and inspect scan or oversize actions; the proposed ips cpu resource pressure gate would not check that same control.

Question 470

During FortiOS 7.6 operations at a managed branch perimeter, the evidence is: Large archives traverse the firewall without expected deep scanning due to configured buffer or file-size limits. The operator corrected the configuration by choosing to review AV inspection-size limits and select a policy for oversize files consistent with risk requirements. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Load-test representative traffic and check IPS process CPU and security coverage together.
  2. Connect to the published service and verify payload inspection with the correct local certificate.
  3. Send safe files around the configured size threshold and inspect scan or oversize actions.
  4. Require peer review for file size inspection limits changes and an acceptance check that will send safe files around the configured size threshold and inspect scan or oversize actions before relevant releases.
  5. Check the IPS signature database timestamp and presence of the intended test signature.

Explanation

Correct Answers

C:

It measures the operational result after the correction to review AV inspection-size limits and select a policy for oversize files consistent with risk requirements, and it directly checks the reported condition: large archives traverse the firewall without expected deep scanning due to configured buffer or file-size limits. For file size inspection limits, 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 large archives traverse the firewall without expected deep scanning due to configured buffer or file-size limits, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to send safe files around the configured size threshold and inspect scan or oversize actions, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

A:

The proposed evidence, to load-test representative traffic and check IPS process CPU and security coverage together, checks ips cpu resource pressure in a situation such as traffic inspection consumes excessive CPU after a very broad IPS signature set was applied to high-volume flows, not the required file size inspection limits acceptance. For the affected firewall behavior the directly discriminating check is to send safe files around the configured size threshold and inspect scan or oversize actions, alongside a review of file size inspection limits rather than ips cpu resource pressure settings.

B:

The proposed evidence, to connect to the published service and verify payload inspection with the correct local certificate, checks inbound encrypted server protection in a situation such as an internal HTTPS server published through the firewall needs inbound payload inspection, not just outbound certificate metadata, not the required file size inspection limits acceptance. For the affected firewall behavior the directly discriminating check is to send safe files around the configured size threshold and inspect scan or oversize actions, alongside a review of file size inspection limits rather than inbound encrypted server protection settings.

E:

The proposed evidence, to check the IPS signature database timestamp and presence of the intended test signature, checks fortiguard ips update checks in a situation such as a newly published protection is absent from a firewall using an outdated IPS signature database, not the required file size inspection limits acceptance. For the affected firewall behavior the directly discriminating check is to send safe files around the configured size threshold and inspect scan or oversize actions, alongside a review of file size inspection limits rather than fortiguard ips update checks settings.

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