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 69

Question 680

A hospital uses managed computers shared across staff roles and must restrict one private clinical application by actual user. Suppose the team follows this shortcut instead: Grant sensitive finance application access to every compliant device regardless of the signed-in account. What is the most likely direct security or operational consequence?

  1. A compromised endpoint passes the supposed antivirus gate while protection is stopped
  2. Unmanaged or risky devices obtain unnecessary access throughout the organization
  3. All user devices lose an important access protection while the stale reporting problem remains
  4. Users outside the authorized business role inherit sensitive application privileges

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A bank's remote contractor installs the required agent but disables real-time endpoint protection. In the stated case: A hospital uses managed computers shared across staff roles and must restrict one private clinical application by actual user. The relevant consequence is: Users outside the authorized business role inherit sensitive application privileges. The control that prevents it is: Apply endpoint compliance checks together with appropriate authenticated user-group access rules rather than assuming one substitutes for the other.

B.

This failure concerns another scenario: A hospital must briefly support one controlled diagnostic laptop that lacks a standard patch while all other endpoints remain gated. In the stated case: A hospital uses managed computers shared across staff roles and must restrict one private clinical application by actual user. The relevant consequence is: Users outside the authorized business role inherit sensitive application privileges. The control that prevents it is: Apply endpoint compliance checks together with appropriate authenticated user-group access rules rather than assuming one substitutes for the other.

C.

This failure concerns another scenario: A bank's newly patched laptop remains blocked because FortiSASE has not received its updated compliance state. In the stated case: A hospital uses managed computers shared across staff roles and must restrict one private clinical application by actual user. The relevant consequence is: Users outside the authorized business role inherit sensitive application privileges. The control that prevents it is: Apply endpoint compliance checks together with appropriate authenticated user-group access rules rather than assuming one substitutes for the other.

D.

Users outside the authorized business role inherit sensitive application privileges. This is the risk in the stated situation: A hospital uses managed computers shared across staff roles and must restrict one private clinical application by actual user. The risky shortcut is: Grant sensitive finance application access to every compliant device regardless of the signed-in account. Prevent it by: Apply endpoint compliance checks together with appropriate authenticated user-group access rules rather than assuming one substitutes for the other.

Question 681

A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application
  2. Use the available SD-WAN monitoring and traffic log fields to determine which service rule and path actually handled a selected session
  3. Compare SD-WAN loss, latency and jitter over representative peak periods rather than a single recent sample
  4. Investigate firewall policy decisions independently when SD-WAN logs report that a healthy eligible member was chosen for a blocked application

Answer & Explanations

Correct answer: A

A.

Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application. The technical reason is: 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. The stated condition is: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. Confirm the result by: Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface.

B.

This action is appropriate in a different case: A retailer's checkout packets traverse LTE even after a fiber preference rule is added. There, the reason is: FortiOS routing diagnostics can distinguish expected service intent from actual effective path, especially when a generic rule precedes the intended specific one. The current case is: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The appropriate response is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

C.

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 support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The appropriate response is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

D.

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 support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The appropriate response is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

Question 682

A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. A Fortinet administrator recommends: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application. Which technical process explanation best justifies that recommendation?

  1. SD-WAN logs explain steering, whereas FortiOS security traffic logs explain authorization and content enforcement; neither record type alone describes all packet decisions
  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. 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
  4. 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

Answer & Explanations

Correct answer: B

A.

This principle explains a different technical intervention: Investigate firewall policy decisions independently when SD-WAN logs report that a healthy eligible member was chosen for a blocked application. It applies to: A hospital's remote support connection selects the correct member but is rejected by the traffic policy. The actual case is: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The mechanism relevant here is: 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.

B.

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. That mechanism explains the decision: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application. In the reported situation: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. Confirmation requires: Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface.

C.

This principle explains a different technical intervention: Filter FortiSASE security logs by user, time, web category, policy and action to identify why a specific allowed business destination failed. It applies to: A university professor cannot access one licensed research website even though FortiClient shows connected. The actual case is: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The mechanism relevant here is: 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.

D.

This principle explains a different technical intervention: Investigate FortiSASE antivirus or IPS detection logs together with matching remote user sessions and their policy profiles. It applies to: A financial analyst's file download fails and the FortiSASE log identifies a malware profile rather than a login error. The actual case is: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The mechanism relevant here is: 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.

Question 683

A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Use an approved nonharmful test indicator and correlate user, content signature and action with the actual session
  2. Compare suspect and known-good user activity using the same policy and confirm any enforcement adjustment with a safe repeat test
  3. Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface
  4. Generate an approved test URL event and find it in broad then precise log searches while checking cloud service status

Answer & Explanations

Correct answer: C

A.

This observation would verify a different remedy: Investigate FortiSASE antivirus or IPS detection logs together with matching remote user sessions and their policy profiles. That remedy applies to: A financial analyst's file download fails and the FortiSASE log identifies a malware profile rather than a login error. The present condition is: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. To assess it, check: Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface.

B.

This observation would verify a different remedy: Analyze FortiSASE user traffic and security events for abnormal destinations, excessive denials or policy changes before taking scoped action. That remedy applies to: An MSP observes a remote sales laptop contacting an unfamiliar cloud address repeatedly overnight. The present condition is: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. To assess it, check: Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface.

C.

Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface. This check directly tests: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application. The underlying behavior is: 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. The case is: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes.

D.

This observation would verify a different remedy: Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred. That remedy applies to: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The present condition is: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. To assess it, check: Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface.

Question 684

A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. Which apparently convenient shortcut would most directly undermine the required control?

  1. Disable SASE filtering because the dashboard shows zero threats during a short time window
  2. Apply a global deny because one aggregate report lists a risky category without identifying the affected users
  3. Buy an additional WAN circuit only because the aggregate report shows a high monthly byte total
  4. Attribute a cloud app outage to an ISP solely because one link's utilization chart is high

Answer & Explanations

Correct answer: D

A.

This proposed shortcut concerns a separate case: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. The risk in this question concerns: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. Here the unsafe shortcut is: Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. Use this response instead: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

B.

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 support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. Here the unsafe shortcut is: Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. Use this response instead: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

C.

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 support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. Here the unsafe shortcut is: Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. Use this response instead: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

D.

Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. This shortcut is unsafe for: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The resulting failure can be: The wrong root cause is reported and the relevant service or firewall policy defect remains. The safer response is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

Question 685

A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. Suppose the team follows this shortcut instead: Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. What is the most likely direct security or operational consequence?

  1. The wrong root cause is reported and the relevant service or firewall policy defect remains
  2. Capacity spend rises without resolving actual loss, jitter or incorrect service selection
  3. Noncompliant devices retain inappropriate access and compliance reporting becomes misleading
  4. Persistent unaddressed threats remain despite improved dashboard presentation

Answer & Explanations

Correct answer: A

A.

The wrong root cause is reported and the relevant service or firewall policy defect remains. This is the risk in the stated situation: A support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The risky shortcut is: Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. Prevent it by: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

B.

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 support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The relevant consequence is: The wrong root cause is reported and the relevant service or firewall policy defect remains. The control that prevents it is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

C.

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 support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The relevant consequence is: The wrong root cause is reported and the relevant service or firewall policy defect remains. The control that prevents it is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

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 support desk sees poor voice calls and needs to determine whether a degraded WAN caused route changes. The relevant consequence is: The wrong root cause is reported and the relevant service or firewall policy defect remains. The control that prevents it is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

Question 686

An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Analyze FortiSASE user traffic and security events for abnormal destinations, excessive denials or policy changes before taking scoped action
  2. Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application
  3. Check FortiSASE log filters, event type, user and tenant scope, timestamps and service health before concluding security inspection never occurred
  4. Generate scoped FortiSASE user-traffic reports and compare application, destination and security-action trends over a representative reporting period

Answer & Explanations

Correct answer: B

A.

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: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The appropriate response is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

B.

Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application. The technical reason is: 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. The stated condition is: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. Confirm the result by: Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface.

C.

This action is appropriate in a different case: A hospital SOC selects the wrong user group and sees no cloud threat logs for a known pilot event. There, the 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 current case is: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The appropriate response is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

D.

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: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The appropriate response is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

Question 687

An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. A Fortinet administrator recommends: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application. Which technical process explanation best justifies that recommendation?

  1. Reports aggregate observed user activity, whereas an individual policy decision must still be confirmed from the underlying session and profile logs
  2. Historical bandwidth and selected-member counts reveal sustained congestion and imbalanced usage but cannot alone identify why a single packet was blocked
  3. 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
  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: C

A.

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: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The mechanism relevant here is: 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.

B.

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: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The mechanism relevant here is: 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.

C.

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. That mechanism explains the decision: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application. In the reported situation: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. Confirmation requires: Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface.

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: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The mechanism relevant here is: 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.

Question 688

An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. 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. Select one repeated alert class, inspect source event details and confirm the expected result after a scoped correction
  3. Run one approved target application and verify its service ID, matched address selectors and member change after adjustment
  4. Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface

Answer & Explanations

Correct answer: D

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: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. To assess it, check: Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface.

B.

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: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. To assess it, check: Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface.

C.

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: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. To assess it, check: Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface.

D.

Capture a failed and healthy pilot connection with SLA state, SD-WAN service ID and actual outgoing interface. This check directly tests: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application. The underlying behavior is: 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. The case is: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service.

Question 689

An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. Which apparently convenient shortcut would most directly undermine the required control?

  1. Attribute a cloud app outage to an ISP solely because one link's utilization chart is high
  2. Count only total SD-WAN traffic volume and declare the specialized priority rule effective
  3. Erase an intermittent WAN incident after one successful midnight ping test
  4. Change SD-WAN member priority to fix a request denied by security policy

Answer & Explanations

Correct answer: A

A.

Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. This shortcut is unsafe for: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The resulting failure can be: The wrong root cause is reported and the relevant service or firewall policy defect remains. The safer response is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

B.

This proposed shortcut concerns a separate case: A retailer's checkout packets traverse LTE even after a fiber preference rule is added. The risk in this question concerns: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. Here the unsafe shortcut is: Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. Use this response instead: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

C.

This proposed shortcut concerns a separate case: A call center's afternoon voice quality collapses while midnight WAN tests are healthy. The risk in this question concerns: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. Here the unsafe shortcut is: Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. Use this response instead: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

D.

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: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. Here the unsafe shortcut is: Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. Use this response instead: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

Question 690

An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. Suppose the team follows this shortcut instead: Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. What is the most likely direct security or operational consequence?

  1. The application remains blocked while unnecessary path changes disrupt other services
  2. The wrong root cause is reported and the relevant service or firewall policy defect remains
  3. Prohibited categories become accessible to unrelated remote users
  4. Dangerous payloads pass uninspected while the original account is otherwise authorized

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A hospital's remote support connection selects the correct member but is rejected by the traffic policy. In the stated case: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The relevant consequence is: The wrong root cause is reported and the relevant service or firewall policy defect remains. The control that prevents it is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

B.

The wrong root cause is reported and the relevant service or firewall policy defect remains. This is the risk in the stated situation: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The risky shortcut is: Attribute a cloud app outage to an ISP solely because one link's utilization chart is high. Prevent it by: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

C.

This failure concerns another scenario: A university professor cannot access one licensed research website even though FortiClient shows connected. In the stated case: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The relevant consequence is: The wrong root cause is reported and the relevant service or firewall policy defect remains. The control that prevents it is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

D.

This failure concerns another scenario: A financial analyst's file download fails and the FortiSASE log identifies a malware profile rather than a login error. In the stated case: An ecommerce branch suspects a link outage but session logs show every affected flow matched an unrelated service. The relevant consequence is: The wrong root cause is reported and the relevant service or firewall policy defect remains. The control that prevents it is: Analyze FortiOS SD-WAN health-check events alongside traffic-session member selection for an affected application.

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