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

Question 600

Within an off-site workforce where some endpoints fail compliance verification, the administrator must label endpoints dynamically when a specified local security condition is met without redesigning unrelated services. Which option addresses the goal?

  1. Check endpoint vulnerability severity
  2. Assign compliant endpoint tags to private policies
  3. Build a security posture tag rule
  4. Review the posture tag's allow or deny direction
  5. Use endpoint-profile assignment for managed groups

Explanation

Correct Answer

C:

FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags; that scope directly serves the goal to label endpoints dynamically when a specified local security condition is met in an off-site workforce where some endpoints fail compliance verification. During implementation, the tag logic must accurately represent the actual security requirement rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

Vulnerability-related posture information can be used to classify a risky endpoint for conditional access, a mechanism intended to apply stricter access to devices with high-severity unresolved vulnerabilities rather than the requested ‘Build a security posture tag rule’ control. The stated task instead is to label endpoints dynamically when a specified local security condition is met, and adjusting ‘Check endpoint vulnerability severity’ would not deliver ‘Build a security posture tag rule’. For the ‘Check endpoint vulnerability severity’ alternative to ‘Build a security posture tag rule’, posture signals require recent endpoint scanning and successful telemetry exchange.

B:

Private access policies can use security posture tags as dynamic matching criteria, a mechanism intended to grant sensitive private access only to managed devices meeting specified security conditions rather than the requested ‘Build a security posture tag rule’ control. The stated task instead is to label endpoints dynamically when a specified local security condition is met, and adjusting ‘Assign compliant endpoint tags to private policies’ would not deliver ‘Build a security posture tag rule’. For the ‘Assign compliant endpoint tags to private policies’ alternative to ‘Build a security posture tag rule’, authentication identity and endpoint posture solve different trust checks.

D:

An allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity, a mechanism intended to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint rather than the requested ‘Build a security posture tag rule’ control. The stated task instead is to label endpoints dynamically when a specified local security condition is met, and adjusting ‘Review the posture tag's allow or deny direction’ would not deliver ‘Build a security posture tag rule’. For the ‘Review the posture tag's allow or deny direction’ alternative to ‘Build a security posture tag rule’, define whether a tag means compliant or noncompliant before using it for admission.

E:

Endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives, a mechanism intended to apply a stricter posture and connection configuration to a high-risk user population rather than the requested ‘Build a security posture tag rule’ control. The stated task instead is to label endpoints dynamically when a specified local security condition is met, and adjusting ‘Use endpoint-profile assignment for managed groups’ would not deliver ‘Build a security posture tag rule’. For the ‘Use endpoint-profile assignment for managed groups’ alternative to ‘Build a security posture tag rule’, a cloud traffic policy alone does not deploy settings to FortiClient endpoints.

Question 601

During an authorized lab exercise for an off-site workforce where some endpoints fail compliance verification, a reviewer needs proof the deployment can apply stricter access to devices with high-severity unresolved vulnerabilities. Which observation most directly validates it?

  1. The posture telemetry classifies the device according to antivirus status.
  2. The device's posture classification reflects the configured vulnerability severity.
  3. FortiClient rejects the tunnel according to the configured posture-tag action.
  4. The configured action denies devices carrying the noncompliant tag.

Explanation

Correct Answer

B:

This checks ‘Check endpoint vulnerability severity’ at the correct operational boundary: vulnerability-related posture information can be used to classify a risky endpoint for conditional access. It demonstrates the specific capability to apply stricter access to devices with high-severity unresolved vulnerabilities in an off-site workforce where some endpoints fail compliance verification; deployment should additionally respect the constraint: Posture signals require recent endpoint scanning and successful telemetry exchange.

Incorrect Answers

A:

That observation belongs to ‘Require endpoint antivirus status’, not ‘Check endpoint vulnerability severity’; its purpose is to treat disabled or missing antimalware protection as a noncompliant device condition, the underlying behavior is that a posture rule can evaluate security-product presence or protection state and classify the endpoint. The reviewer is instead verifying ‘Check endpoint vulnerability severity’ for an off-site workforce where some endpoints fail compliance verification, not the evidence produced by ‘Require endpoint antivirus status’.

C:

That observation belongs to ‘Configure pre-connection posture enforcement’, not ‘Check endpoint vulnerability severity’; its purpose is to block an untrusted FortiClient endpoint before it establishes its protected cloud tunnel, the underlying behavior is that a configured pre-connection check can allow or deny a tunnel attempt based on an assigned posture tag. The reviewer is instead verifying ‘Check endpoint vulnerability severity’ for an off-site workforce where some endpoints fail compliance verification, not the evidence produced by ‘Configure pre-connection posture enforcement’.

D:

That observation belongs to ‘Review the posture tag's allow or deny direction’, not ‘Check endpoint vulnerability severity’; its purpose is to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint, the underlying behavior is that an allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity. The reviewer is instead verifying ‘Check endpoint vulnerability severity’ for an off-site workforce where some endpoints fail compliance verification, not the evidence produced by ‘Review the posture tag's allow or deny direction’.

Question 602

In a change-control meeting for a remote access monthly review for the SASE operations team, a colleague challenges the proposed control ‘Compare user traffic volume trends’ for the requirement to find which authenticated population caused a sustained increase in cloud egress. Which explanation accurately describes its behavior?

  1. Time-bound analytics separate incident-period activity from unrelated historical traffic.
  2. Application analytics classify observed traffic into recognizable applications for reporting.
  3. Security analytics can group blocked traffic by destination or policy to reveal recurring patterns.
  4. User traffic analytics aggregate bytes and sessions by identity and time for usage investigation.

Explanation

Correct Answer

D:

‘Compare user traffic volume trends’ is used to find which authenticated population caused a sustained increase in cloud egress in a remote access monthly review for the SASE operations team; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the time-filtered report ranks user or group traffic volume for the affected interval; the rollout must also respect this constraint: Traffic volume alone is not evidence that a session is malicious.

Incorrect Answers

A:

The described behavior is part of ‘Use report time filters for incident scoping’, used to limit an investigation to the period in which an employee reported a cloud access failure instead of the role of ‘Compare user traffic volume trends’. In contrast to ‘Use report time filters for incident scoping’, ‘Compare user traffic volume trends’ follows a different mechanism: user traffic analytics aggregate bytes and sessions by identity and time for usage investigation. Treating ‘Use report time filters for incident scoping’ as equivalent would not address an ISP usage spike is blamed on anonymous traffic without identifying the active user groups in a remote access monthly review for the SASE operations team.

B:

The described behavior is part of ‘Review application usage reports’, used to identify which SaaS or application class dominates inspected remote traffic instead of the role of ‘Compare user traffic volume trends’. In contrast to ‘Review application usage reports’, ‘Compare user traffic volume trends’ follows a different mechanism: user traffic analytics aggregate bytes and sessions by identity and time for usage investigation. Treating ‘Review application usage reports’ as equivalent would not address an ISP usage spike is blamed on anonymous traffic without identifying the active user groups in a remote access monthly review for the SASE operations team.

C:

The described behavior is part of ‘Correlate policy action with destination risk’, used to identify repeated attempts to reach restricted destinations across remote users instead of the role of ‘Compare user traffic volume trends’. In contrast to ‘Correlate policy action with destination risk’, ‘Compare user traffic volume trends’ follows a different mechanism: user traffic analytics aggregate bytes and sessions by identity and time for usage investigation. Treating ‘Correlate policy action with destination risk’ as equivalent would not address an ISP usage spike is blamed on anonymous traffic without identifying the active user groups in a remote access monthly review for the SASE operations team.

Question 603

At a cloud security migration with independent web and private-app policies, a controlled test reveals that users from two departments unexpectedly receive the same unrestricted access policy. Which setting is the strongest first lead?

  1. Investigate: Configure SASE certificate trust
  2. Investigate: Use geolocation-aware access restrictions
  3. Investigate: Assign FortiSASE administrator access
  4. Investigate: Organize SASE users into policy groups

Explanation

Correct Answer

D:

The symptom identifies the missing operational behavior: user groups provide a membership basis for matching different FortiSASE access policies. For a cloud security migration with independent web and private-app policies, a direct diagnostic confirmation would be that group membership and policy matches differ for the two user populations; during repair, authentication source membership must be available for identity-based rule evaluation.

Incorrect Answers

A:

When deep inspection is used, managed endpoints need the appropriate inspection CA trust anchor, which serves the different requirement to avoid TLS warnings and ensure clients trust the cloud security inspection certificate instead of the behavior delivered by ‘Organize SASE users into policy groups’. If that component were misconfigured, a more characteristic finding would be that browsers show certificate warnings when protected HTTPS traffic is inspected; the actual report concerns users from two departments unexpectedly receive the same unrestricted access policy at a cloud security migration with independent web and private-app policies.

B:

Geographic policy criteria can help distinguish traffic by geolocation where FortiSASE policy supports that selection, which serves the different requirement to restrict access from locations outside an organization-approved geographic footprint instead of the behavior delivered by ‘Organize SASE users into policy groups’. If that component were misconfigured, a more characteristic finding would be that remote access occurs from a region that violates the deployment's stated geographic rule; the actual report concerns users from two departments unexpectedly receive the same unrestricted access policy at a cloud security migration with independent web and private-app policies.

C:

Distinct authorized administrators enable accountable management while the original account retains ownership, which serves the different requirement to let a delegated operator manage the cloud configuration without sharing the primary account instead of the behavior delivered by ‘Organize SASE users into policy groups’. If that component were misconfigured, a more characteristic finding would be that routine changes are made using a shared primary login with no individual accountability; the actual report concerns users from two departments unexpectedly receive the same unrestricted access policy at a cloud security migration with independent web and private-app policies.

Question 604

Within a medical office prioritizing stable response times to a hosted patient system, the operator applies the control ‘Select the correct probe server’ as part of an effort to measure user-relevant path health rather than only the nearest ISP hop. Which operating behavior should the team expect?

  1. Health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway.
  2. Passive measurements can obtain link metrics from observed traffic instead of relying solely on synthetic monitoring packets.
  3. The SLA target defines tolerated delay, loss, or jitter against measured health-check values.
  4. Separate health checks can reveal that a circuit reaches one remote service well but another poorly.
  5. A member may be reachable and report alive while failing a stricter SLA target for performance.

Explanation

Correct Answer

A:

‘Select the correct probe server’ is used to measure user-relevant path health rather than only the nearest ISP hop in a medical office prioritizing stable response times to a hosted patient system; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that probe results to the intended external target reflect the actual remote-path problem; the rollout must also respect this constraint: The measurement endpoint must be reliably reachable and appropriate to the application.

Incorrect Answers

B:

The described behavior is part of ‘Use passive WAN health measurement’, used to derive quality observations from actual matched user sessions rather than dedicated probes instead of the role of ‘Select the correct probe server’. In contrast to ‘Use passive WAN health measurement’, ‘Select the correct probe server’ follows a different mechanism: health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway. Treating ‘Use passive WAN health measurement’ as equivalent would not address all circuits reach their gateways but the real remote service path is impaired in a medical office prioritizing stable response times to a hosted patient system.

C:

The described behavior is part of ‘Configure an SLA target for a health check’, used to turn observed quality metrics into a pass-or-fail objective for rule selection instead of the role of ‘Select the correct probe server’. In contrast to ‘Configure an SLA target for a health check’, ‘Select the correct probe server’ follows a different mechanism: health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway. Treating ‘Configure an SLA target for a health check’ as equivalent would not address all circuits reach their gateways but the real remote service path is impaired in a medical office prioritizing stable response times to a hosted patient system.

D:

The described behavior is part of ‘Compare health across multiple SLAs’, used to measure distinct service destinations separately rather than treating the internet as one uniform path instead of the role of ‘Select the correct probe server’. In contrast to ‘Compare health across multiple SLAs’, ‘Select the correct probe server’ follows a different mechanism: health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway. Treating ‘Compare health across multiple SLAs’ as equivalent would not address all circuits reach their gateways but the real remote service path is impaired in a medical office prioritizing stable response times to a hosted patient system.

E:

The described behavior is part of ‘Investigate alive versus SLA-qualified state’, used to distinguish basic connectivity from acceptable application performance instead of the role of ‘Select the correct probe server’. In contrast to ‘Investigate alive versus SLA-qualified state’, ‘Select the correct probe server’ follows a different mechanism: health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway. Treating ‘Investigate alive versus SLA-qualified state’ as equivalent would not address all circuits reach their gateways but the real remote service path is impaired in a medical office prioritizing stable response times to a hosted patient system.

Question 605

At a policy owner determining which protective control stopped a session, the rollout includes the control ‘Inspect web-filter category logs’ to determine whether a website was blocked by category policy rather than by transport failure. Which observed mechanism is consistent with this configuration?

  1. DNS security logs record affected domain requests and configured malicious-domain actions.
  2. Authentication events reveal the login or SSO step at which a FortiSASE user failed to establish identity.
  3. AV logs identify signature or file detections and the security action applied to a session.
  4. Web-filter logs associate an HTTP or HTTPS destination with category evaluation and action.

Explanation

Correct Answer

D:

‘Inspect web-filter category logs’ is used to determine whether a website was blocked by category policy rather than by transport failure in a policy owner determining which protective control stopped a session; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the web-filter event shows the URL category and associated block action; the rollout must also respect this constraint: Category decisions must be distinguished from DNS filter results and generic firewall denies.

Incorrect Answers

A:

The described behavior is part of ‘Inspect DNS-filter threat events’, used to identify blocked malicious name resolution before the browser opens a TCP session instead of the role of ‘Inspect web-filter category logs’. In contrast to ‘Inspect DNS-filter threat events’, ‘Inspect web-filter category logs’ follows a different mechanism: web-filter logs associate an HTTP or HTTPS destination with category evaluation and action. Treating ‘Inspect DNS-filter threat events’ as equivalent would not address a marketing site fails and the team incorrectly assumes the SASE tunnel is down in a policy owner determining which protective control stopped a session.

B:

The described behavior is part of ‘Correlate cloud authentication events’, used to distinguish failed identity sign-in from a denied security profile decision instead of the role of ‘Inspect web-filter category logs’. In contrast to ‘Correlate cloud authentication events’, ‘Inspect web-filter category logs’ follows a different mechanism: web-filter logs associate an HTTP or HTTPS destination with category evaluation and action. Treating ‘Correlate cloud authentication events’ as equivalent would not address a marketing site fails and the team incorrectly assumes the SASE tunnel is down in a policy owner determining which protective control stopped a session.

C:

The described behavior is part of ‘Inspect antivirus detection events’, used to identify which inspected download was blocked for malware and under which policy instead of the role of ‘Inspect web-filter category logs’. In contrast to ‘Inspect antivirus detection events’, ‘Inspect web-filter category logs’ follows a different mechanism: web-filter logs associate an HTTP or HTTPS destination with category evaluation and action. Treating ‘Inspect antivirus detection events’ as equivalent would not address a marketing site fails and the team incorrectly assumes the SASE tunnel is down in a policy owner determining which protective control stopped a session.

Question 606

Within a remote-user design needing both public SaaS and internal subnet access, the administrator must connect remote FortiSASE clients to data-center applications protected behind a FortiGate without redesigning unrelated services. Which option addresses the goal?

  1. Use ZTNA application proxy for a protected TCP app
  2. Use a redundant private-access hub
  3. Integrate branch SD-WAN with FortiSASE on-ramp
  4. Use IPsec transport for the SASE branch connection
  5. Use FortiGate as a private-access hub

Explanation

Correct Answer

E:

FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic; that scope directly serves the goal to connect remote FortiSASE clients to data-center applications protected behind a FortiGate in a remote-user design needing both public SaaS and internal subnet access. During implementation, the protected data-center prefixes need return routes toward FortiSASE clients rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

ZTNA private access targets authorized TCP applications rather than granting generic network reachability, a mechanism intended to publish a narrowly scoped internal TCP application through a FortiGate ZTNA gateway rather than the requested ‘Use FortiGate as a private-access hub’ control. The stated task instead is to connect remote FortiSASE clients to data-center applications protected behind a FortiGate, and adjusting ‘Use ZTNA application proxy for a protected TCP app’ would not deliver ‘Use FortiGate as a private-access hub’. For the ‘Use ZTNA application proxy for a protected TCP app’ alternative to ‘Use FortiGate as a private-access hub’, the FortiGate ZTNA server, access policy, and required client posture must be configured.

B:

Multiple suitably configured SPA hubs can provide a redundant path to private resources, a mechanism intended to maintain access to applications when one data-center gateway or tunnel fails rather than the requested ‘Use FortiGate as a private-access hub’ control. The stated task instead is to connect remote FortiSASE clients to data-center applications protected behind a FortiGate, and adjusting ‘Use a redundant private-access hub’ would not deliver ‘Use FortiGate as a private-access hub’. For the ‘Use a redundant private-access hub’ alternative to ‘Use FortiGate as a private-access hub’, redundancy depends on both routing and policy consistency across hubs.

C:

A supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs, a mechanism intended to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge rather than the requested ‘Use FortiGate as a private-access hub’ control. The stated task instead is to connect remote FortiSASE clients to data-center applications protected behind a FortiGate, and adjusting ‘Integrate branch SD-WAN with FortiSASE on-ramp’ would not deliver ‘Use FortiGate as a private-access hub’. For the ‘Integrate branch SD-WAN with FortiSASE on-ramp’ alternative to ‘Use FortiGate as a private-access hub’, branch integration requires transport reachability and matching on-ramp security policy.

D:

An IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay, a mechanism intended to carry branch traffic securely across an untrusted ISP toward a SASE service edge rather than the requested ‘Use FortiGate as a private-access hub’ control. The stated task instead is to connect remote FortiSASE clients to data-center applications protected behind a FortiGate, and adjusting ‘Use IPsec transport for the SASE branch connection’ would not deliver ‘Use FortiGate as a private-access hub’. For the ‘Use IPsec transport for the SASE branch connection’ alternative to ‘Use FortiGate as a private-access hub’, iKE negotiations and underlay routing must work before traffic steering over the tunnel.

Question 607

In a change-control meeting for a regional hub where live transport measurements do not agree with the user complaint, acceptance testing shows that probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links. Which control should be investigated first?

  1. Investigate: Configure an SLA target for a health check
  2. Investigate: Set jitter SLA threshold
  3. Investigate: Compare health across multiple SLAs
  4. Investigate: Use passive WAN health measurement

Explanation

Correct Answer

A:

The symptom identifies the missing operational behavior: the SLA target defines tolerated delay, loss, or jitter against measured health-check values. For a regional hub where live transport measurements do not agree with the user complaint, a direct diagnostic confirmation would be that the health-check's target reports individual member pass or failure against stated limits; during repair, measurement alone and selecting a traffic-steering target are different steps.

Incorrect Answers

B:

A jitter target compares delay variation with an allowed maximum to qualify or reject a member, which serves the different requirement to avoid a circuit whose packet-delay variation damages live audio instead of the behavior delivered by ‘Configure an SLA target for a health check’. If that component were misconfigured, a more characteristic finding would be that calls become choppy even though mean delay remains acceptable; the actual report concerns probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links at a regional hub where live transport measurements do not agree with the user complaint.

C:

Separate health checks can reveal that a circuit reaches one remote service well but another poorly, which serves the different requirement to measure distinct service destinations separately rather than treating the internet as one uniform path instead of the behavior delivered by ‘Configure an SLA target for a health check’. If that component were misconfigured, a more characteristic finding would be that the administrator assumes one successful probe proves all SaaS destinations are reachable; the actual report concerns probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links at a regional hub where live transport measurements do not agree with the user complaint.

D:

Passive measurements can obtain link metrics from observed traffic instead of relying solely on synthetic monitoring packets, which serves the different requirement to derive quality observations from actual matched user sessions rather than dedicated probes instead of the behavior delivered by ‘Configure an SLA target for a health check’. If that component were misconfigured, a more characteristic finding would be that active probes look healthy but user-path measurements are needed for the actual application flow; the actual report concerns probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links at a regional hub where live transport measurements do not agree with the user complaint.

Question 608

At a private-access application that requires device trust as well as user identity, a support engineer needs to verify that ‘Review the posture tag's allow or deny direction’ is active for the goal to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint. Which observation is decisive?

  1. Registration health and a recent tag update corroborate the current device state.
  2. The posture rule changes endpoint classification when the process stops or resumes.
  3. The device's posture classification reflects the configured vulnerability severity.
  4. The configured action denies devices carrying the noncompliant tag.

Explanation

Correct Answer

D:

This checks ‘Review the posture tag's allow or deny direction’ at the correct operational boundary: an allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity. It demonstrates the specific capability to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint in a private-access application that requires device trust as well as user identity; deployment should additionally respect the constraint: Define whether a tag means compliant or noncompliant before using it for admission.

Incorrect Answers

A:

That observation belongs to ‘Validate fresh endpoint posture telemetry’, not ‘Review the posture tag's allow or deny direction’; its purpose is to avoid relying on stale compliance information after an endpoint stops reporting to management, the underlying behavior is that posture-based enforcement depends on updated FortiClient registration and local security-condition evaluation. The reviewer is instead verifying ‘Review the posture tag's allow or deny direction’ for a private-access application that requires device trust as well as user identity, not the evidence produced by ‘Validate fresh endpoint posture telemetry’.

B:

That observation belongs to ‘Check a required running process’, not ‘Review the posture tag's allow or deny direction’; its purpose is to permit an internal app only when its approved endpoint security agent is running, the underlying behavior is that process-presence conditions can contribute to device posture evaluation where supported. The reviewer is instead verifying ‘Review the posture tag's allow or deny direction’ for a private-access application that requires device trust as well as user identity, not the evidence produced by ‘Check a required running process’.

C:

That observation belongs to ‘Check endpoint vulnerability severity’, not ‘Review the posture tag's allow or deny direction’; its purpose is to apply stricter access to devices with high-severity unresolved vulnerabilities, the underlying behavior is that vulnerability-related posture information can be used to classify a risky endpoint for conditional access. The reviewer is instead verifying ‘Review the posture tag's allow or deny direction’ for a private-access application that requires device trust as well as user identity, not the evidence produced by ‘Check endpoint vulnerability severity’.

Question 609

During an authorized lab exercise for an insurance branch with a real-time application and a bulk-backup workload, the incident notes state that highly interactive traffic follows the higher-latency link though both links are reachable. Which change is most relevant to this symptom?

  1. Investigate: Match service protocol and port
  2. Investigate: Use Best Quality with latency
  3. Investigate: Match destination address in an SD-WAN rule
  4. Investigate: Restrict the candidate member preference list

Explanation

Correct Answer

B:

The symptom identifies the missing operational behavior: Best Quality can rank member quality using latency collected by the designated performance health check. For an insurance branch with a real-time application and a bulk-backup workload, a direct diagnostic confirmation would be that the service's quality factor is latency and the member ordering reflects measured delay; during repair, latency-based ranking does not ensure the lowest commercial ISP bill.

Incorrect Answers

A:

Service matching narrows selection by transport protocol and destination-port criteria, which serves the different requirement to steer a well-defined TCP service without affecting unrelated traffic to the same server instead of the behavior delivered by ‘Use Best Quality with latency’. If that component were misconfigured, a more characteristic finding would be that all traffic to the server uses the special circuit instead of only the target application port; the actual report concerns highly interactive traffic follows the higher-latency link though both links are reachable at an insurance branch with a real-time application and a bulk-backup workload.

C:

Destination-address matching distinguishes route candidates for a specified network target, which serves the different requirement to direct traffic to a particular partner subnet over an overlay while other traffic uses internet DIA instead of the behavior delivered by ‘Use Best Quality with latency’. If that component were misconfigured, a more characteristic finding would be that partner subnet flows accidentally match the generic internet steering policy; the actual report concerns highly interactive traffic follows the higher-latency link though both links are reachable at an insurance branch with a real-time application and a bulk-backup workload.

D:

An explicit member or zone preference limits which eligible paths a matching service may choose, which serves the different requirement to prevent a sensitive service from using an otherwise healthy but unapproved ISP instead of the behavior delivered by ‘Use Best Quality with latency’. If that component were misconfigured, a more characteristic finding would be that a regulated application crosses a third ISP that is healthy but not on its approved transport list; the actual report concerns highly interactive traffic follows the higher-latency link though both links are reachable at an insurance branch with a real-time application and a bulk-backup workload.

Question 610

At a remote call center measuring two ISP paths to the same application target, the change request is to avoid a circuit whose packet-delay variation damages live audio. Which configuration is the most direct fit?

  1. Set jitter SLA threshold
  2. Set latency SLA threshold
  3. Use passive WAN health measurement
  4. Assign the relevant member set to a health check

Explanation

Correct Answer

A:

A jitter target compares delay variation with an allowed maximum to qualify or reject a member; that scope directly serves the goal to avoid a circuit whose packet-delay variation damages live audio in a remote call center measuring two ISP paths to the same application target. During implementation, low average latency alone does not demonstrate satisfactory jitter rather than treating the configuration label as proof of working service.

Incorrect Answers

B:

A latency target makes a member fail that SLA when measured delay exceeds the configured limit, a mechanism intended to exclude paths whose round-trip delay exceeds a real-time application's bound rather than the requested ‘Set jitter SLA threshold’ control. The stated task instead is to avoid a circuit whose packet-delay variation damages live audio, and adjusting ‘Set latency SLA threshold’ would not deliver ‘Set jitter SLA threshold’. For the ‘Set latency SLA threshold’ alternative to ‘Set jitter SLA threshold’, thresholds must be realistic for the probe destination and business application.

C:

Passive measurements can obtain link metrics from observed traffic instead of relying solely on synthetic monitoring packets, a mechanism intended to derive quality observations from actual matched user sessions rather than dedicated probes rather than the requested ‘Set jitter SLA threshold’ control. The stated task instead is to avoid a circuit whose packet-delay variation damages live audio, and adjusting ‘Use passive WAN health measurement’ would not deliver ‘Set jitter SLA threshold’. For the ‘Use passive WAN health measurement’ alternative to ‘Set jitter SLA threshold’, traffic and policy instrumentation must support the passive measurement mechanism.

D:

An SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface, a mechanism intended to compare only the transport members serving a given application class rather than the requested ‘Set jitter SLA threshold’ control. The stated task instead is to avoid a circuit whose packet-delay variation damages live audio, and adjusting ‘Assign the relevant member set to a health check’ would not deliver ‘Set jitter SLA threshold’. For the ‘Assign the relevant member set to a health check’ alternative to ‘Set jitter SLA threshold’, a measured SLA cannot evaluate a member that is not associated with the check.

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