Practice Exams:

Fortinet NSE5_SSE_AD-7.6 Dumps

EXAM: Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator
Verified By Experts
Premium Bundle
$49.99

NSE5_SSE_AD-7.6 Premium ETE File


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

Fortinet NSE5_SSE_AD-7.6 Practice Test 76

Question 750

A university sees high encrypted traffic from a research user and must distinguish legitimate data transfer from suspicious exfiltration. Suppose the team follows this shortcut instead: Block every remote user who generates a high traffic volume without inspecting business backup or update behavior. What is the most likely direct security or operational consequence?

  1. Security controls are weakened even though the missing evidence was only a reporting or scope problem
  2. Legitimate workflows are interrupted while the actual suspicious destination may remain uninvestigated
  3. The wrong root cause is reported and the relevant service or firewall policy defect remains
  4. The affected application continues to use the wrong transport although aggregate throughput appears normal

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. In the stated case: A university sees high encrypted traffic from a research user and must distinguish legitimate data transfer from suspicious exfiltration. The relevant consequence is: Legitimate workflows are interrupted while the actual suspicious destination may remain uninvestigated. The control that prevents it is: Analyze FortiSASE user traffic and security events for abnormal destinations, excessive denials or policy changes before taking scoped action.

B.

Legitimate workflows are interrupted while the actual suspicious destination may remain uninvestigated. This is the risk in the stated situation: A university sees high encrypted traffic from a research user and must distinguish legitimate data transfer from suspicious exfiltration. The risky shortcut is: Block every remote user who generates a high traffic volume without inspecting business backup or update behavior. Prevent it by: Analyze FortiSASE user traffic and security events for abnormal destinations, excessive denials or policy changes before taking scoped action.

C.

This failure concerns another scenario: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. In the stated case: A university sees high encrypted traffic from a research user and must distinguish legitimate data transfer from suspicious exfiltration. The relevant consequence is: Legitimate workflows are interrupted while the actual suspicious destination may remain uninvestigated. The control that prevents it is: Analyze FortiSASE user traffic and security events for abnormal destinations, excessive denials or policy changes before taking scoped action.

D.

This failure concerns another scenario: A retailer's checkout packets traverse LTE even after a fiber preference rule is added. In the stated case: A university sees high encrypted traffic from a research user and must distinguish legitimate data transfer from suspicious exfiltration. The relevant consequence is: Legitimate workflows are interrupted while the actual suspicious destination may remain uninvestigated. The control that prevents it is: Analyze FortiSASE user traffic and security events for abnormal destinations, excessive denials or policy changes before taking scoped action.

Question 751

A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Filter FortiSASE security logs by user, time, web category, policy and action to identify why a specific allowed business destination failed
  2. Investigate FortiSASE antivirus or IPS detection logs together with matching remote user sessions and their policy profiles
  3. Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred
  4. Analyze FortiSASE user traffic and security events for abnormal destinations, excessive denials or policy changes before taking scoped action

Answer & Explanations

Correct answer: C

A.

This action is appropriate in a different case: A university professor cannot access one licensed research website even though FortiClient shows connected. There, the reason is: A remote user can authenticate and tunnel successfully while cloud web filtering denies a site by category; tunnel uptime is not proof of permitted URL access. The current case is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The appropriate response is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

B.

This action is appropriate in a different case: A financial analyst's file download fails and the FortiSASE log identifies a malware profile rather than a login error. There, the reason is: A malicious-content event may be generated by an inspection engine after the access policy allowed the session, so a generic traffic block interpretation can mislead remediation. The current case is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The appropriate response is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

C.

Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred. The technical reason is: A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected. The stated condition is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. Confirm the result by: Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status.

D.

This action is appropriate in a different case: An MSP observes a remote sales laptop contacting an unfamiliar cloud address repeatedly overnight. There, the reason is: An unusual high-volume destination is a signal for investigation, not automatic proof of compromise; user identity, timestamps and matching protections matter. The current case is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The appropriate response is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

Question 752

A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. A Fortinet administrator recommends: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred. Which technical process explanation best justifies that recommendation?

  1. An unusual high-volume destination is a signal for investigation, not automatic proof of compromise; user identity, timestamps and matching protections matter
  2. A member's SLA degradation and a flow's selected egress are separate observations; correlating their timestamps identifies whether steering reacted to a measured impairment
  3. FortiOS routing diagnostics can distinguish expected service intent from actual effective path, especially when a generic rule precedes the intended specific one
  4. A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected

Answer & Explanations

Correct answer: D

A.

This principle explains a different technical intervention: Analyze FortiSASE user traffic and security events for abnormal destinations, excessive denials or policy changes before taking scoped action. It applies to: An MSP observes a remote sales laptop contacting an unfamiliar cloud address repeatedly overnight. The actual case is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The mechanism relevant here is: A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected.

B.

This principle explains a different technical intervention: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application. It applies to: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The actual case is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The mechanism relevant here is: A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected.

C.

This principle explains a different technical intervention: Use the available SD-WAN monitoring and traffic log fields to determine which service rule and path actually handled a selected session. It applies to: A retailer's checkout packets traverse LTE even after a fiber preference rule is added. The actual case is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The mechanism relevant here is: A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected.

D.

A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected. That mechanism explains the decision: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred. In the reported situation: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. Confirmation requires: Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status.

Question 753

A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status
  2. Run one approved target application and verify its service ID, matched address selectors and member change after adjustment
  3. Plot measured quality for the approved service window and compare call failures with actual probe breaches
  4. Reproduce a denied web session and correlate its selected member, firewall policy ID and NAT result

Answer & Explanations

Correct answer: A

A.

Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status. This check directly tests: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred. The underlying behavior is: A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected. The case is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event.

B.

This observation would verify a different remedy: Use the available SD-WAN monitoring and traffic log fields to determine which service rule and path actually handled a selected session. That remedy applies to: A retailer's checkout packets traverse LTE even after a fiber preference rule is added. The present condition is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. To assess it, check: Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status.

C.

This observation would verify a different remedy: Compare SD-WAN loss, latency and jitter over representative peak periods rather than a single recent sample. That remedy applies to: A call center's afternoon voice quality collapses while midnight WAN tests are healthy. The present condition is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. To assess it, check: Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status.

D.

This observation would verify a different remedy: Investigate firewall policy decisions independently when SD-WAN logs report that a healthy eligible member was chosen for a blocked application. That remedy applies to: A hospital's remote support connection selects the correct member but is rejected by the traffic policy. The present condition is: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. To assess it, check: Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status.

Question 754

A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. Which apparently convenient shortcut would most directly undermine the required control?

  1. Change SD-WAN member priority to fix a request denied by security policy
  2. Disable SASE filtering because the dashboard shows zero threats during a short time window
  3. Apply a global deny because one aggregate report lists a risky category without identifying the affected users
  4. Buy an additional WAN circuit only because the aggregate report shows a high monthly byte total

Answer & Explanations

Correct answer: B

A.

This proposed shortcut concerns a separate case: A hospital's remote support connection selects the correct member but is rejected by the traffic policy. The risk in this question concerns: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. Here the unsafe shortcut is: Disable SASE filtering because the dashboard shows zero threats during a short time window. Use this response instead: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

B.

Disable SASE filtering because the dashboard shows zero threats during a short time window. This shortcut is unsafe for: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The resulting failure can be: Security controls are weakened even though the missing evidence was only a reporting or scope problem. The safer response is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

C.

This proposed shortcut concerns a separate case: A hospital needs a summary of clinician and contractor cloud browsing exceptions without exposing all employee details. The risk in this question concerns: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. Here the unsafe shortcut is: Disable SASE filtering because the dashboard shows zero threats during a short time window. Use this response instead: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

D.

This proposed shortcut concerns a separate case: A call center wants evidence whether its backup internet actually carried normal traffic during peak hours. The risk in this question concerns: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. Here the unsafe shortcut is: Disable SASE filtering because the dashboard shows zero threats during a short time window. Use this response instead: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

Question 755

A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. Suppose the team follows this shortcut instead: Disable SASE filtering because the dashboard shows zero threats during a short time window. What is the most likely direct security or operational consequence?

  1. Capacity spend rises without resolving actual loss, jitter or incorrect service selection
  2. Noncompliant devices retain inappropriate access and compliance reporting becomes misleading
  3. Security controls are weakened even though the missing evidence was only a reporting or scope problem
  4. Persistent unaddressed threats remain despite improved dashboard presentation

Answer & Explanations

Correct answer: C

A.

This failure concerns another scenario: A call center wants evidence whether its backup internet actually carried normal traffic during peak hours. In the stated case: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The relevant consequence is: Security controls are weakened even though the missing evidence was only a reporting or scope problem. The control that prevents it is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

B.

This failure concerns another scenario: A finance manager sees remote web activity but wants proof employees met endpoint patch rules for sensitive SaaS access. In the stated case: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The relevant consequence is: Security controls are weakened even though the missing evidence was only a reporting or scope problem. The control that prevents it is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

C.

Security controls are weakened even though the missing evidence was only a reporting or scope problem. This is the risk in the stated situation: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The risky shortcut is: Disable SASE filtering because the dashboard shows zero threats during a short time window. Prevent it by: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

D.

This failure concerns another scenario: An MSP notices repeated phishing detections across several remote users and needs to prioritize remediation. In the stated case: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The relevant consequence is: Security controls are weakened even though the missing evidence was only a reporting or scope problem. The control that prevents it is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

Question 756

A retail operations analyst thinks all inspection stopped because yesterday's report is empty. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Compare SD-WAN loss, latency and jitter over representative peak periods rather than a single recent sample
  2. Investigate firewall policy decisions independently when SD-WAN logs report that a healthy eligible member was chosen for a blocked application
  3. Generate scoped FortiSASE user-traffic reports and compare application, destination and security-action trends over a representative reporting period
  4. Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred

Answer & Explanations

Correct answer: D

A.

This action is appropriate in a different case: A call center's afternoon voice quality collapses while midnight WAN tests are healthy. There, the reason is: Link quality can deteriorate during regular business peaks without going completely down, so one normal off-peak reading does not establish SLA readiness. The current case is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The appropriate response is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

B.

This action is appropriate in a different case: A hospital's remote support connection selects the correct member but is rejected by the traffic policy. There, the reason is: SD-WAN logs explain steering, whereas FortiOS security traffic logs explain authorization and content enforcement; neither record type alone describes all packet decisions. The current case is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The appropriate response is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

C.

This action is appropriate in a different case: A hospital needs a summary of clinician and contractor cloud browsing exceptions without exposing all employee details. There, the reason is: Reports aggregate observed user activity, whereas an individual policy decision must still be confirmed from the underlying session and profile logs. The current case is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The appropriate response is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

D.

Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred. The technical reason is: A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected. The stated condition is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. Confirm the result by: Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status.

Question 757

A retail operations analyst thinks all inspection stopped because yesterday's report is empty. A Fortinet administrator recommends: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred. Which technical process explanation best justifies that recommendation?

  1. A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected
  2. Reports aggregate observed user activity, whereas an individual policy decision must still be confirmed from the underlying session and profile logs
  3. Historical bandwidth and selected-member counts reveal sustained congestion and imbalanced usage but cannot alone identify why a single packet was blocked
  4. A user may appear in traffic reports yet fail a private application policy because a separate posture or group condition is not met

Answer & Explanations

Correct answer: A

A.

A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected. That mechanism explains the decision: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred. In the reported situation: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. Confirmation requires: Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status.

B.

This principle explains a different technical intervention: Generate scoped FortiSASE user-traffic reports and compare application, destination and security-action trends over a representative reporting period. It applies to: A hospital needs a summary of clinician and contractor cloud browsing exceptions without exposing all employee details. The actual case is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The mechanism relevant here is: A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected.

C.

This principle explains a different technical intervention: Review FortiOS or FortiManager SD-WAN member usage reports alongside ISP bandwidth and business demand to plan capacity adjustments. It applies to: A call center wants evidence whether its backup internet actually carried normal traffic during peak hours. The actual case is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The mechanism relevant here is: A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected.

D.

This principle explains a different technical intervention: Combine FortiSASE endpoint compliance summaries with connection and security event reports to explain whether users were blocked by posture, identity or destination filtering. It applies to: A finance manager sees remote web activity but wants proof employees met endpoint patch rules for sensitive SaaS access. The actual case is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The mechanism relevant here is: A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected.

Question 758

A retail operations analyst thinks all inspection stopped because yesterday's report is empty. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Test one noncompliant endpoint and one compliant endpoint, then trace policy verdict and the appropriate report category
  2. Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status
  3. Select one repeated alert class, inspect source event details and confirm the expected result after a scoped correction
  4. Reproduce a safe controlled web request and match the exact filtered URL event and relevant user policy

Answer & Explanations

Correct answer: B

A.

This observation would verify a different remedy: Combine FortiSASE endpoint compliance summaries with connection and security event reports to explain whether users were blocked by posture, identity or destination filtering. That remedy applies to: A finance manager sees remote web activity but wants proof employees met endpoint patch rules for sensitive SaaS access. The present condition is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. To assess it, check: Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status.

B.

Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status. This check directly tests: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred. The underlying behavior is: A narrow time range or wrong event category may hide valid cloud records, while an ingest fault can delay reporting without proving traffic was unprotected. The case is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty.

C.

This observation would verify a different remedy: Review FortiSASE threat and traffic trend reports for repeated incidents, then return to raw logs to verify signatures, users, policy and remediation outcome. That remedy applies to: An MSP notices repeated phishing detections across several remote users and needs to prioritize remediation. The present condition is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. To assess it, check: Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status.

D.

This observation would verify a different remedy: Filter FortiSASE security logs by user, time, web category, policy and action to identify why a specific allowed business destination failed. That remedy applies to: A university professor cannot access one licensed research website even though FortiClient shows connected. The present condition is: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. To assess it, check: Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status.

Question 759

A retail operations analyst thinks all inspection stopped because yesterday's report is empty. Which apparently convenient shortcut would most directly undermine the required control?

  1. Disable the entire tenant's web filtering because a single business site is falsely categorized
  2. Remove all intrusion and malware inspection for a user after mistaking one blocked file for identity failure
  3. Disable SASE filtering because the dashboard shows zero threats during a short time window
  4. Block every remote user who generates a high traffic volume without inspecting business backup or update behavior

Answer & Explanations

Correct answer: C

A.

This proposed shortcut concerns a separate case: A university professor cannot access one licensed research website even though FortiClient shows connected. The risk in this question concerns: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. Here the unsafe shortcut is: Disable SASE filtering because the dashboard shows zero threats during a short time window. Use this response instead: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

B.

This proposed shortcut concerns a separate case: A financial analyst's file download fails and the FortiSASE log identifies a malware profile rather than a login error. The risk in this question concerns: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. Here the unsafe shortcut is: Disable SASE filtering because the dashboard shows zero threats during a short time window. Use this response instead: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

C.

Disable SASE filtering because the dashboard shows zero threats during a short time window. This shortcut is unsafe for: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The resulting failure can be: Security controls are weakened even though the missing evidence was only a reporting or scope problem. The safer response is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

D.

This proposed shortcut concerns a separate case: An MSP observes a remote sales laptop contacting an unfamiliar cloud address repeatedly overnight. The risk in this question concerns: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. Here the unsafe shortcut is: Disable SASE filtering because the dashboard shows zero threats during a short time window. Use this response instead: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

Question 760

A retail operations analyst thinks all inspection stopped because yesterday's report is empty. Suppose the team follows this shortcut instead: Disable SASE filtering because the dashboard shows zero threats during a short time window. What is the most likely direct security or operational consequence?

  1. Legitimate workflows are interrupted while the actual suspicious destination may remain uninvestigated
  2. The wrong root cause is reported and the relevant service or firewall policy defect remains
  3. The affected application continues to use the wrong transport although aggregate throughput appears normal
  4. Security controls are weakened even though the missing evidence was only a reporting or scope problem

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: An MSP observes a remote sales laptop contacting an unfamiliar cloud address repeatedly overnight. In the stated case: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The relevant consequence is: Security controls are weakened even though the missing evidence was only a reporting or scope problem. The control that prevents it is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

B.

This failure concerns another scenario: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. In the stated case: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The relevant consequence is: Security controls are weakened even though the missing evidence was only a reporting or scope problem. The control that prevents it is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

C.

This failure concerns another scenario: A retailer's checkout packets traverse LTE even after a fiber preference rule is added. In the stated case: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The relevant consequence is: Security controls are weakened even though the missing evidence was only a reporting or scope problem. The control that prevents it is: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

D.

Security controls are weakened even though the missing evidence was only a reporting or scope problem. This is the risk in the stated situation: A retail operations analyst thinks all inspection stopped because yesterday's report is empty. The risky shortcut is: Disable SASE filtering because the dashboard shows zero threats during a short time window. Prevent it by: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred.

Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests