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 35

Question 340

A FortiOS 7.6 review of a managed branch perimeter reports the following condition: An internal HTTPS server published through the firewall needs inbound payload inspection, not just outbound certificate metadata. The operator corrected the configuration by choosing to configure the supported Protecting SSL Server profile with the server certificate and matching inbound policy. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Test permitted sibling domains and the prohibited host against the revised filter.
  2. Connect to the published service and verify payload inspection with the correct local certificate.
  3. Browse controlled allowed and blocked category sites and inspect the web-filter category log.
  4. Reproduce the denied request and correlate the web filter log with session policy.
  5. 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.

Explanation

Correct Answers

B:

It measures the operational result after the correction to configure the supported Protecting SSL Server profile with the server certificate and matching inbound policy, and it directly checks the reported condition: an internal HTTPS server published through the firewall needs inbound payload inspection, not just outbound certificate metadata. For inbound encrypted server protection, 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 an internal HTTPS server published through the firewall needs inbound payload inspection, not just outbound certificate metadata, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to connect to the published service and verify payload inspection with the correct local certificate, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

A:

The proposed evidence, to test permitted sibling domains and the prohibited host against the revised filter, checks url filter pattern scope in a situation such as a broad URL pattern blocks unrelated subdomains that were meant to remain accessible, not the required inbound encrypted server protection acceptance. For the affected firewall behavior the directly discriminating check is to connect to the published service and verify payload inspection with the correct local certificate, alongside a review of inbound encrypted server protection rather than url filter pattern scope settings.

C:

The proposed evidence, to browse controlled allowed and blocked category sites and inspect the web-filter category log, checks fortiguard category action in a situation such as a school permits generic learning sites but must block the gambling category across managed browsers, not the required inbound encrypted server protection acceptance. For the affected firewall behavior the directly discriminating check is to connect to the published service and verify payload inspection with the correct local certificate, alongside a review of inbound encrypted server protection rather than fortiguard category action settings.

D:

The proposed evidence, to reproduce the denied request and correlate the web filter log with session policy, checks web filter incident evidence in a situation such as a user reports a denied web request but analysts inspect only a generic system event list, not the required inbound encrypted server protection acceptance. For the affected firewall behavior the directly discriminating check is to connect to the published service and verify payload inspection with the correct local certificate, alongside a review of inbound encrypted server protection rather than web filter incident evidence settings.

Question 341

During FortiOS 7.6 operations at a datacenter security boundary, the evidence is: An IPS policy logs TCP 443 sessions but cannot observe a malicious payload that remains encrypted end to end. The requirement concerns encrypted threat inspection requirement while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic.
  2. Configure a scoped static URL filter entry for the hostname and attach the profile to the traffic policy.
  3. Configure a limited authorized web profile override with group and duration constraints.
  4. Use an application control profile with appropriate application signatures on the matching firewall policy.

Explanation

Correct Answer

A:

Choosing to configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic 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 a harmless synthetic payload over approved TLS inspection and inspect IPS visibility.

Incorrect Answers

B:

Configuring a scoped static URL filter entry for the hostname and attach the profile to the traffic policy would focus the new configuration on static url filtering, for which an exact malicious hostname must be denied while other sites in the same FortiGuard category stay allowed may be a valid concern, but this encrypted threat inspection requirement configuration has a different failure. Evidence for encrypted threat inspection requirement requires staff to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility; the proposed static url filtering change cannot deliver that encrypted threat inspection requirement result by itself.

C:

Configuring a limited authorized web profile override with group and duration constraints would focus the new configuration on user web filter override, for which staff with an approved temporary exception still cannot access a blocked research category may be a valid concern, but this encrypted threat inspection requirement configuration has a different failure. Evidence for encrypted threat inspection requirement requires staff to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility; the proposed user web filter override change cannot deliver that encrypted threat inspection requirement result by itself.

D:

Using an application control profile with appropriate application signatures on the matching firewall policy would focus the new configuration on application signature identification, for which a policy blocks TCP ports but an unwanted application moves across permitted ports and remains accessible may be a valid concern, but this encrypted threat inspection requirement configuration has a different failure. Evidence for encrypted threat inspection requirement requires staff to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility; the proposed application signature identification change cannot deliver that encrypted threat inspection requirement result by itself.

Question 342

At an enterprise gateway change window, a FortiGate running FortiOS 7.6 has this observation: An IPS policy logs TCP 443 sessions but cannot observe a malicious payload that remains encrypted end to end. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this encrypted threat inspection requirement failure?

  1. Set every blocked web category to Allow permanently for all users to serve one exception.
  2. Block the entire broad FortiGuard category when only one hostname is prohibited.
  3. Assume an IPS signature can always inspect encrypted HTTP content without any TLS decryption.
  4. Treat port blocking alone as equivalent to application-aware control for all protocols.

Explanation

Correct Answer

C:

The problem arises when administrators assume an IPS signature can always inspect encrypted HTTP content without any TLS decryption, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic.

Incorrect Answers

A:

The alternative cause involving user web filter override can produce a different failure, for example when staff with an approved temporary exception still cannot access a blocked research category; it is not the encrypted threat inspection requirement case. The more specific error here is the choice to assume an IPS signature can always inspect encrypted HTTP content without any TLS decryption; check it by attempting to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility before making an unrelated user web filter override change.

B:

The alternative cause involving static url filtering can produce a different failure, for example when an exact malicious hostname must be denied while other sites in the same FortiGuard category stay allowed; it is not the encrypted threat inspection requirement case. The more specific error here is the choice to assume an IPS signature can always inspect encrypted HTTP content without any TLS decryption; check it by attempting to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility before making an unrelated static url filtering change.

D:

The alternative cause involving application signature identification can produce a different failure, for example when a policy blocks TCP ports but an unwanted application moves across permitted ports and remains accessible; it is not the encrypted threat inspection requirement case. The more specific error here is the choice to assume an IPS signature can always inspect encrypted HTTP content without any TLS decryption; check it by attempting to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility before making an unrelated application signature identification change.

Question 343

A FortiOS 7.6 review of a redundant regional firewall pair reports the following condition: An IPS policy logs TCP 443 sessions but cannot observe a malicious payload that remains encrypted end to end. Investigators confirmed this cause: administrators chose to assume an IPS signature can always inspect encrypted HTTP content without any TLS decryption. Which action MOST directly corrects the confirmed error?

  1. Configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic.
  2. Configure a limited authorized web profile override with group and duration constraints.
  3. Use an application control profile with appropriate application signatures on the matching firewall policy.
  4. Assume an IPS signature can always inspect encrypted HTTP content without any TLS decryption.

Explanation

Correct Answer

A:

This addresses encrypted threat inspection requirement without needlessly weakening separate security or routing controls. Given the observed condition—an IPS policy logs TCP 443 sessions but cannot observe a malicious payload that remains encrypted end to end—the operator should then replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility.

Incorrect Answers

B:

Changing the mechanism to configure a limited authorized web profile override with group and duration constraints could be a sensible correction for user web filter override when staff with an approved temporary exception still cannot access a blocked research category. The targeted fix is to configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic; a review of user web filter override would not, by itself, prove that the team can replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility.

C:

Changing the mechanism to use an application control profile with appropriate application signatures on the matching firewall policy could be a sensible correction for application signature identification when a policy blocks TCP ports but an unwanted application moves across permitted ports and remains accessible. The targeted fix is to configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic; a review of application signature identification would not, by itself, prove that the team can replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility.

D:

The proposal repeats the confirmed encrypted threat inspection requirement error by choosing to assume an IPS signature can always inspect encrypted HTTP content without any TLS decryption. A corrective change must instead configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic and then produce the measurable result to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility; repeating the failed setting cannot serve as a repair.

Question 344

During FortiOS 7.6 operations at a remote-office migration, the evidence is: An IPS policy logs TCP 443 sessions but cannot observe a malicious payload that remains encrypted end to end. The incident has been fixed, and the owner wants to prevent a recurrence of the encrypted threat inspection requirement problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for static url filtering changes and an acceptance check that will request the prohibited hostname and an allowed peer and compare URL-filter actions before relevant releases.
  2. Require peer review for application signature identification changes and an acceptance check that will run a permitted test of the target app on another port and inspect the application event before relevant releases.
  3. Require peer review for encrypted threat inspection requirement changes and an acceptance check that will replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility before relevant releases.
  4. Require peer review for user web filter override changes and an acceptance check that will test the authorized exception account and an ordinary user before and after override expiry before relevant releases.

Explanation

Correct Answer

C:

This change-control gate requires teams to require peer review for encrypted threat inspection requirement changes and an acceptance check that will replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility 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 a harmless synthetic payload over approved TLS inspection and inspect IPS visibility.

Incorrect Answers

A:

A review gate for static url filtering, such as require peer review for static url filtering changes and an acceptance check that will request the prohibited hostname and an allowed peer and compare URL-filter actions before relevant releases, can be useful where an exact malicious hostname must be denied while other sites in the same FortiGuard category stay allowed, but it is not the approved encrypted threat inspection requirement review. The preventive test must enforce that staff will configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic and subsequently can replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility; the proposed static url filtering gate would not check that same control.

B:

A review gate for application signature identification, such as require peer review for application signature identification changes and an acceptance check that will run a permitted test of the target app on another port and inspect the application event before relevant releases, can be useful where a policy blocks TCP ports but an unwanted application moves across permitted ports and remains accessible, but it is not the approved encrypted threat inspection requirement review. The preventive test must enforce that staff will configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic and subsequently can replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility; the proposed application signature identification gate would not check that same control.

D:

A review gate for user web filter override, such as require peer review for user web filter override changes and an acceptance check that will test the authorized exception account and an ordinary user before and after override expiry before relevant releases, can be useful where staff with an approved temporary exception still cannot access a blocked research category, but it is not the approved encrypted threat inspection requirement review. The preventive test must enforce that staff will configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic and subsequently can replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility; the proposed user web filter override gate would not check that same control.

Question 345

At a monitored business uplink, a FortiGate running FortiOS 7.6 has this observation: An IPS policy logs TCP 443 sessions but cannot observe a malicious payload that remains encrypted end to end. The operator corrected the configuration by choosing to configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Require peer review for encrypted threat inspection requirement changes and an acceptance check that will replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility before relevant releases.
  2. Replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility.
  3. Request the prohibited hostname and an allowed peer and compare URL-filter actions.
  4. Run a permitted test of the target app on another port and inspect the application event.
  5. Test the authorized exception account and an ordinary user before and after override expiry.

Explanation

Correct Answers

A:

The organization already encountered the failure where an IPS policy logs TCP 443 sessions but cannot observe a malicious payload that remains encrypted end to end, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility, this gate checks future revisions without claiming that the current configuration is permanently correct.

B:

It measures the operational result after the correction to configure authorized deep inspection so the relevant security profiles can inspect the permitted decrypted traffic, and it directly checks the reported condition: an IPS policy logs TCP 443 sessions but cannot observe a malicious payload that remains encrypted end to end. For encrypted threat inspection requirement, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.

Incorrect Answers

C:

The proposed evidence, to request the prohibited hostname and an allowed peer and compare URL-filter actions, checks static url filtering in a situation such as an exact malicious hostname must be denied while other sites in the same FortiGuard category stay allowed, not the required encrypted threat inspection requirement acceptance. For the affected firewall behavior the directly discriminating check is to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility, alongside a review of encrypted threat inspection requirement rather than static url filtering settings.

D:

The proposed evidence, to run a permitted test of the target app on another port and inspect the application event, checks application signature identification in a situation such as a policy blocks TCP ports but an unwanted application moves across permitted ports and remains accessible, not the required encrypted threat inspection requirement acceptance. For the affected firewall behavior the directly discriminating check is to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility, alongside a review of encrypted threat inspection requirement rather than application signature identification settings.

E:

The proposed evidence, to test the authorized exception account and an ordinary user before and after override expiry, checks user web filter override in a situation such as staff with an approved temporary exception still cannot access a blocked research category, not the required encrypted threat inspection requirement acceptance. For the affected firewall behavior the directly discriminating check is to replay a harmless synthetic payload over approved TLS inspection and inspect IPS visibility, alongside a review of encrypted threat inspection requirement rather than user web filter override settings.

Question 346

A FortiOS 7.6 review of an internal application segment reports the following condition: A deep-inspection profile exists but the production policy still references no-inspection. The requirement concerns ssl profile policy attachment while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?

  1. Apply a narrowly scoped application control override for the approved signature while retaining category policy.
  2. Enable web filtering with the correct profile on the firewall policy used by the sessions.
  3. Attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow.
  4. Replace the broad pattern with the specific supported hostname or path match appropriate to the requirement.

Explanation

Correct Answer

C:

Choosing to attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow 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: verify the policy ID and selected SSL profile during a controlled HTTPS test.

Incorrect Answers

A:

Applying a narrowly scoped application control override for the approved signature while retaining category policy would focus the new configuration on application control category override, for which a broad application category is blocked but one approved business app in that category needs a specific exception may be a valid concern, but this ssl profile policy attachment configuration has a different failure. Evidence for ssl profile policy attachment requires staff to verify the policy ID and selected SSL profile during a controlled HTTPS test; the proposed application control category override change cannot deliver that ssl profile policy attachment result by itself.

B:

Enabling web filtering with the correct profile on the firewall policy used by the sessions would focus the new configuration on web filter profile on policy, for which a URL block exists in a profile but the matching traffic policy does not apply that web profile may be a valid concern, but this ssl profile policy attachment configuration has a different failure. Evidence for ssl profile policy attachment requires staff to verify the policy ID and selected SSL profile during a controlled HTTPS test; the proposed web filter profile on policy change cannot deliver that ssl profile policy attachment result by itself.

D:

Selecting replace the broad pattern with the specific supported hostname or path match appropriate to the requirement would focus the new configuration on url filter pattern scope, for which a broad URL pattern blocks unrelated subdomains that were meant to remain accessible may be a valid concern, but this ssl profile policy attachment configuration has a different failure. Evidence for ssl profile policy attachment requires staff to verify the policy ID and selected SSL profile during a controlled HTTPS test; the proposed url filter pattern scope change cannot deliver that ssl profile policy attachment result by itself.

Question 347

During FortiOS 7.6 operations at a hybrid-network deployment, the evidence is: A deep-inspection profile exists but the production policy still references no-inspection. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this ssl profile policy attachment failure?

  1. Keep a wildcard pattern that matches more hosts than the documented deny list.
  2. Create a new SSL inspection object without applying it to the matching policy.
  3. Apply the web-filter profile to an unused rule and assume it governs all web sessions.
  4. Allow the entire blocked application category to accommodate one business application.

Explanation

Correct Answer

B:

The problem arises when administrators create a new SSL inspection object without applying it to the matching policy, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow.

Incorrect Answers

A:

The alternative cause involving url filter pattern scope can produce a different failure, for example when a broad URL pattern blocks unrelated subdomains that were meant to remain accessible; it is not the ssl profile policy attachment case. The more specific error here is the choice to create a new SSL inspection object without applying it to the matching policy; check it by attempting to verify the policy ID and selected SSL profile during a controlled HTTPS test before making an unrelated url filter pattern scope change.

C:

The alternative cause involving web filter profile on policy can produce a different failure, for example when a URL block exists in a profile but the matching traffic policy does not apply that web profile; it is not the ssl profile policy attachment case. The more specific error here is the choice to create a new SSL inspection object without applying it to the matching policy; check it by attempting to verify the policy ID and selected SSL profile during a controlled HTTPS test before making an unrelated web filter profile on policy change.

D:

The alternative cause involving application control category override can produce a different failure, for example when a broad application category is blocked but one approved business app in that category needs a specific exception; it is not the ssl profile policy attachment case. The more specific error here is the choice to create a new SSL inspection object without applying it to the matching policy; check it by attempting to verify the policy ID and selected SSL profile during a controlled HTTPS test before making an unrelated application control category override change.

Question 348

At an operations incident response, a FortiGate running FortiOS 7.6 has this observation: A deep-inspection profile exists but the production policy still references no-inspection. Investigators confirmed this cause: administrators chose to create a new SSL inspection object without applying it to the matching policy. Which action MOST directly corrects the confirmed error?

  1. Attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow.
  2. Enable web filtering with the correct profile on the firewall policy used by the sessions.
  3. Create a new SSL inspection object without applying it to the matching policy.
  4. Apply a narrowly scoped application control override for the approved signature while retaining category policy.

Explanation

Correct Answer

A:

This addresses ssl profile policy attachment without needlessly weakening separate security or routing controls. Given the observed condition—a deep-inspection profile exists but the production policy still references no-inspection—the operator should then verify the policy ID and selected SSL profile during a controlled HTTPS test.

Incorrect Answers

B:

Changing the mechanism to enable web filtering with the correct profile on the firewall policy used by the sessions could be a sensible correction for web filter profile on policy when a URL block exists in a profile but the matching traffic policy does not apply that web profile. The targeted fix is to attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow; a review of web filter profile on policy would not, by itself, prove that the team can verify the policy ID and selected SSL profile during a controlled HTTPS test.

C:

The proposal repeats the confirmed ssl profile policy attachment error by choosing to create a new SSL inspection object without applying it to the matching policy. A corrective change must instead attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow and then produce the measurable result to verify the policy ID and selected SSL profile during a controlled HTTPS test; repeating the failed setting cannot serve as a repair.

D:

Changing the mechanism to apply a narrowly scoped application control override for the approved signature while retaining category policy could be a sensible correction for application control category override when a broad application category is blocked but one approved business app in that category needs a specific exception. The targeted fix is to attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow; a review of application control category override would not, by itself, prove that the team can verify the policy ID and selected SSL profile during a controlled HTTPS test.

Question 349

A FortiOS 7.6 review of a network segmentation review reports the following condition: A deep-inspection profile exists but the production policy still references no-inspection. The incident has been fixed, and the owner wants to prevent a recurrence of the ssl profile policy attachment problem. Which future change-control rule is MOST appropriate?

  1. Require peer review for ssl profile policy attachment changes and an acceptance check that will verify the policy ID and selected SSL profile during a controlled HTTPS test before relevant releases.
  2. Require peer review for application control category override changes and an acceptance check that will test the approved app and another app in the category and inspect respective actions before relevant releases.
  3. Require peer review for url filter pattern scope changes and an acceptance check that will test permitted sibling domains and the prohibited host against the revised filter before relevant releases.
  4. Require peer review for web filter profile on policy changes and an acceptance check that will find the matching firewall policy and its web filter event for a controlled prohibited URL before relevant releases.

Explanation

Correct Answer

A:

This change-control gate requires teams to require peer review for ssl profile policy attachment changes and an acceptance check that will verify the policy ID and selected SSL profile during a controlled HTTPS test before relevant releases, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to verify the policy ID and selected SSL profile during a controlled HTTPS test.

Incorrect Answers

B:

A review gate for application control category override, such as require peer review for application control category override changes and an acceptance check that will test the approved app and another app in the category and inspect respective actions before relevant releases, can be useful where a broad application category is blocked but one approved business app in that category needs a specific exception, but it is not the approved ssl profile policy attachment review. The preventive test must enforce that staff will attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow and subsequently can verify the policy ID and selected SSL profile during a controlled HTTPS test; the proposed application control category override gate would not check that same control.

C:

A review gate for url filter pattern scope, such as require peer review for url filter pattern scope changes and an acceptance check that will test permitted sibling domains and the prohibited host against the revised filter before relevant releases, can be useful where a broad URL pattern blocks unrelated subdomains that were meant to remain accessible, but it is not the approved ssl profile policy attachment review. The preventive test must enforce that staff will attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow and subsequently can verify the policy ID and selected SSL profile during a controlled HTTPS test; the proposed url filter pattern scope gate would not check that same control.

D:

A review gate for web filter profile on policy, such as require peer review for web filter profile on policy changes and an acceptance check that will find the matching firewall policy and its web filter event for a controlled prohibited URL before relevant releases, can be useful where a URL block exists in a profile but the matching traffic policy does not apply that web profile, but it is not the approved ssl profile policy attachment review. The preventive test must enforce that staff will attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow and subsequently can verify the policy ID and selected SSL profile during a controlled HTTPS test; the proposed web filter profile on policy gate would not check that same control.

Question 350

During FortiOS 7.6 operations at a managed branch perimeter, the evidence is: A deep-inspection profile exists but the production policy still references no-inspection. The operator corrected the configuration by choosing to attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.

  1. Verify the policy ID and selected SSL profile during a controlled HTTPS test.
  2. Find the matching firewall policy and its web filter event for a controlled prohibited URL.
  3. Test the approved app and another app in the category and inspect respective actions.
  4. Test permitted sibling domains and the prohibited host against the revised filter.
  5. Require peer review for ssl profile policy attachment changes and an acceptance check that will verify the policy ID and selected SSL profile during a controlled HTTPS test before relevant releases.

Explanation

Correct Answers

A:

It measures the operational result after the correction to attach the intended SSL/SSH inspection profile to the firewall policy actually carrying the flow, and it directly checks the reported condition: a deep-inspection profile exists but the production policy still references no-inspection. For ssl profile policy attachment, 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 a deep-inspection profile exists but the production policy still references no-inspection, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to verify the policy ID and selected SSL profile during a controlled HTTPS test, this gate checks future revisions without claiming that the current configuration is permanently correct.

Incorrect Answers

B:

The proposed evidence, to find the matching firewall policy and its web filter event for a controlled prohibited URL, checks web filter profile on policy in a situation such as a URL block exists in a profile but the matching traffic policy does not apply that web profile, not the required ssl profile policy attachment acceptance. For the affected firewall behavior the directly discriminating check is to verify the policy ID and selected SSL profile during a controlled HTTPS test, alongside a review of ssl profile policy attachment rather than web filter profile on policy settings.

C:

The proposed evidence, to test the approved app and another app in the category and inspect respective actions, checks application control category override in a situation such as a broad application category is blocked but one approved business app in that category needs a specific exception, not the required ssl profile policy attachment acceptance. For the affected firewall behavior the directly discriminating check is to verify the policy ID and selected SSL profile during a controlled HTTPS test, alongside a review of ssl profile policy attachment rather than application control category override settings.

D:

The proposed evidence, to test permitted sibling domains and the prohibited host against the revised filter, checks url filter pattern scope in a situation such as a broad URL pattern blocks unrelated subdomains that were meant to remain accessible, not the required ssl profile policy attachment acceptance. For the affected firewall behavior the directly discriminating check is to verify the policy ID and selected SSL profile during a controlled HTTPS test, alongside a review of ssl profile policy attachment rather than url filter pattern scope settings.

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