Question 730
The team plans to analyze SD-WAN health-check events alongside traffic and member-selection logs for the affected time for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up.
- Manually exporting a dashboard once does not meet a recurring reporting requirement
- Treating every blocked website as an IPS exploit event misclassifies the cause
- An interface-up log cannot establish which member carried a specific session
- Treating all errors as virus detections can send responders down the wrong path
Explanation
Correct Answer
C:An interface-up log cannot establish which member carried a specific session. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Manually exporting a dashboard once does not meet a recurring reporting requirement. The outcome for that step belongs to the compliance manager needs the same user-traffic report delivered every Monday without an operator manually rerunning it. Here the decisive requirement concerns a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up, so an interface-up log cannot establish which member carried a specific session is the better fit.
B:Treating every blocked website as an IPS exploit event misclassifies the cause. It addresses users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event. In the reported environment, the missing behavior instead relates to a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. The relevant choice is an interface-up log cannot establish which member carried a specific session.
D:Treating all errors as virus detections can send responders down the wrong path. It could be appropriate when a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. However, that does not resolve the stated condition: a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. A more direct answer is an interface-up log cannot establish which member carried a specific session.
Question 731
The team plans to use an appropriate load-balancing strategy and verify how the selected algorithm distributes sessions for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link.
- A static route table screenshot alone cannot establish past per-session forwarding
- Keeping the retired address object can deny traffic even when VPN negotiation succeeds
- A perfect application match still fails without valid forwarding reachability
- Best-quality steering may prefer a single superior path rather than share load
Explanation
Correct Answer
D:Best-quality steering may prefer a single superior path rather than share load. The planned change can still miss the requirement if this condition is left unresolved. SD-WAN can distribute eligible session load across members according to its balancing method.
Incorrect Answers
A:A static route table screenshot alone cannot establish past per-session forwarding. That is a useful action for a different circumstance: an SD-WAN operator wants to prove that a payment session left through the correct tunnel after an incident, rather than infer from routes alone. The present case is constrained by a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link; the targeted response is best-quality steering may prefer a single superior path rather than share load.
B:Keeping the retired address object can deny traffic even when VPN negotiation succeeds. It could be appropriate when an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change. However, that does not resolve the stated condition: a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. A more direct answer is best-quality steering may prefer a single superior path rather than share load.
C:A perfect application match still fails without valid forwarding reachability. It addresses an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. In the reported environment, the missing behavior instead relates to a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. The relevant choice is best-quality steering may prefer a single superior path rather than share load.
Question 732
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations.
- A rule with the best quality strategy cannot repair the absence of any resolvable route
- Changing jitter thresholds when both already pass will not explain a deterministic equal-cost tie
- Deleting a rule may expose the implicit steering behavior instead of disabling SD-WAN globally
- Setting the minimum above the number of installed healthy members can disable the rule entirely
Explanation
Correct Answer
A:A rule with the best quality strategy cannot repair the absence of any resolvable route. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:Changing jitter thresholds when both already pass will not explain a deterministic equal-cost tie. That is a useful action for a different circumstance: an operations team sees two SLA-compliant WAN links assigned identical cost values but asks why only the first was elected. The present case is constrained by a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations; the targeted response is a rule with the best quality strategy cannot repair the absence of any resolvable route.
C:Deleting a rule may expose the implicit steering behavior instead of disabling SD-WAN globally. The outcome for that step belongs to a network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions. Here the decisive requirement concerns a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations, so a rule with the best quality strategy cannot repair the absence of any resolvable route is the better fit.
D:Setting the minimum above the number of installed healthy members can disable the rule entirely. It addresses the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. In the reported environment, the missing behavior instead relates to a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations. The relevant choice is a rule with the best quality strategy cannot repair the absence of any resolvable route.
Question 733
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: Two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access.
- Inspect the implicit or explicit rule's balance algorithm and the member session counters
- Check the manual strategy setting alongside measured SLA health on each WAN
- Compare cost settings with the qualifying SLA result for both members
- Check source address on an actual session and compare with the rule source selector
Explanation
Correct Answer
C:Compare cost settings with the qualifying SLA result for both members. The observed evidence guides the targeted repair: Configure Lowest Cost (SLA) steering with real member costs and the SaaS SLA target.
Incorrect Answers
A:Inspect the implicit or explicit rule's balance algorithm and the member session counters. It could be appropriate when a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. However, that does not resolve the stated condition: two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access. A more direct answer is compare cost settings with the qualifying SLA result for both members.
B:Check the manual strategy setting alongside measured SLA health on each WAN. The outcome for that step belongs to a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. Here the decisive requirement concerns two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access, so compare cost settings with the qualifying SLA result for both members is the better fit.
D:Check source address on an actual session and compare with the rule source selector. It addresses fortiGate's traffic policy permits VoIP, but its SD-WAN rule is scoped to the wrong source network after a subnet migration. In the reported environment, the missing behavior instead relates to two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access. The relevant choice is compare cost settings with the qualifying SLA result for both members.
Question 734
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? Two WAN interfaces show up, but the network manager needs continuous health information even when no users are active.
- A passive-only measurement may lack fresh samples when no relevant application sessions exist
- Trying to solve policy match by changing member weight leaves the wrong policy interface untouched
- Keeping both members in one shared zone prevents policy separation solely by member identity
- A rule with the best quality strategy cannot repair the absence of any resolvable route
Explanation
Correct Answer
A:A passive-only measurement may lack fresh samples when no relevant application sessions exist. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:Trying to solve policy match by changing member weight leaves the wrong policy interface untouched. It addresses a FortiGate using zone-based policies shows the original interface port but the administrator cannot select it as a distinct policy destination. In the reported environment, the missing behavior instead relates to two WAN interfaces show up, but the network manager needs continuous health information even when no users are active. The relevant choice is a passive-only measurement may lack fresh samples when no relevant application sessions exist.
C:Keeping both members in one shared zone prevents policy separation solely by member identity. That is a useful action for a different circumstance: a branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic. The present case is constrained by two WAN interfaces show up, but the network manager needs continuous health information even when no users are active; the targeted response is a passive-only measurement may lack fresh samples when no relevant application sessions exist.
D:A rule with the best quality strategy cannot repair the absence of any resolvable route. The outcome for that step belongs to a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations. Here the decisive requirement concerns two WAN interfaces show up, but the network manager needs continuous health information even when no users are active, so a passive-only measurement may lack fresh samples when no relevant application sessions exist is the better fit.
Question 735
A proposed repair is to correct the user/group targeting of the intended endpoint profile and synchronize membership. Why should that repair work in this particular situation? Context: A sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile.
- Vulnerability-aware device posture can restrict endpoints independently of the user identity check
- Posture enforcement decisions depend on reported endpoint state; stale or mismapped data can cause incorrect classification
- Posture checks are useful only when their result affects the relevant access enforcement path
- Endpoint profiles are assigned to AD or non-AD groups based on their configured match conditions
Explanation
Correct Answer
D:Endpoint profiles are assigned to AD or non-AD groups based on their configured match conditions. It directly explains the need to correct the user/group targeting of the intended endpoint profile and synchronize membership. The narrow validation is: The test client receives the departmental profile and the expected security controls.
Incorrect Answers
A:Vulnerability-aware device posture can restrict endpoints independently of the user identity check. It could be appropriate when a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. However, that does not resolve the stated condition: a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile. A more direct answer is endpoint profiles are assigned to AD or non-AD groups based on their configured match conditions.
B:Posture enforcement decisions depend on reported endpoint state; stale or mismapped data can cause incorrect classification. It addresses a security analyst sees a compliant laptop marked as noncompliant even after remediation of its local antivirus settings. In the reported environment, the missing behavior instead relates to a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile. The relevant choice is endpoint profiles are assigned to AD or non-AD groups based on their configured match conditions.
C:Posture checks are useful only when their result affects the relevant access enforcement path. That is a useful action for a different circumstance: security wants a noncompliant laptop to be unable to access protected company applications until it passes device checks. The present case is constrained by a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile; the targeted response is endpoint profiles are assigned to AD or non-AD groups based on their configured match conditions.
Question 736
A proposed repair is to use a steering policy with preferred primary member and health-based failover to LTE, rather than unrestricted equal sharing. Why should that repair work in this particular situation? Context: A retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered.
- SD-WAN can distinguish overlay and underlay transport and steer traffic based on intended destination and policy
- Member preference combined with failure detection limits routine use of a metered backup path
- FortiGate logically groups SD-WAN members into zones and uses zones as policy interfaces
- SD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes
Explanation
Correct Answer
B:Member preference combined with failure detection limits routine use of a metered backup path. It directly explains the need to use a steering policy with preferred primary member and health-based failover to LTE, rather than unrestricted equal sharing. The narrow validation is: Normal traffic uses broadband, but simulated broadband failure makes new eligible flows use LTE.
Incorrect Answers
A:SD-WAN can distinguish overlay and underlay transport and steer traffic based on intended destination and policy. The outcome for that step belongs to a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. Here the decisive requirement concerns a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered, so member preference combined with failure detection limits routine use of a metered backup path is the better fit.
C:FortiGate logically groups SD-WAN members into zones and uses zones as policy interfaces. It could be appropriate when after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules. However, that does not resolve the stated condition: a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered. A more direct answer is member preference combined with failure detection limits routine use of a metered backup path.
D:SD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes. That is a useful action for a different circumstance: an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. The present case is constrained by a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered; the targeted response is member preference combined with failure detection limits routine use of a metered backup path.
Question 737
At a FortiSASE/SD-WAN site, this issue is reported: Management wants to compare blocked website trends by user group and demonstrate that the change was not only a temporary increase in total web traffic. What is the most direct technical change to address the stated requirement?
- Generate a filtered security or usage report with the relevant block category, user grouping and comparable time windows
- Use an appropriate periodic report for the summary and drill down to the underlying time-filtered logs for evidence
- Compare relevant web-filter security events across defined before-and-after reporting periods
- Configure supported secure log forwarding to the authorized external logging destination and validate receipt
Explanation
Correct Answer
A:Generate a filtered security or usage report with the relevant block category, user grouping and comparable time windows. Grouping by both user and enforcement action helps separate policy behavior from raw request volume. The configuration alone must be followed by a functioning test: The report shows blocked-event trends per cohort alongside enough traffic context to interpret the change.
Incorrect Answers
B:Use an appropriate periodic report for the summary and drill down to the underlying time-filtered logs for evidence. That is a useful action for a different circumstance: a quarterly audit asks for a summary of FortiSASE security events and the ability to investigate one anomalous period in detail. The present case is constrained by management wants to compare blocked website trends by user group and demonstrate that the change was not only a temporary increase in total web traffic; the targeted response is generate a filtered security or usage report with the relevant block category, user grouping and comparable time windows.
C:Compare relevant web-filter security events across defined before-and-after reporting periods. The outcome for that step belongs to a security officer needs proof that web-category policy violations increased after a recent configuration change. Here the decisive requirement concerns management wants to compare blocked website trends by user group and demonstrate that the change was not only a temporary increase in total web traffic, so generate a filtered security or usage report with the relevant block category, user grouping and comparable time windows is the better fit.
D:Configure supported secure log forwarding to the authorized external logging destination and validate receipt. It addresses a regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window. In the reported environment, the missing behavior instead relates to management wants to compare blocked website trends by user group and demonstrate that the change was not only a temporary increase in total web traffic. The relevant choice is generate a filtered security or usage report with the relevant block category, user grouping and comparable time windows.
Question 738
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A deployment requires public Internet from a third ISP, and the operator wants to manage it independently without applying the private overlay's IPS policy.
- Check the SD-WAN member inventory and assigned zone for the ISP port
- Check the new member zone and the firewall security profile group applied to that zone
- Inspect the two VPN interfaces' zone assignments and overlay routing entries
- Inspect member and zone entries after the rule has been removed
Explanation
Correct Answer
B:Check the new member zone and the firewall security profile group applied to that zone. This check isolates the relevant control before the change. Independent zone grouping enables separate Internet and private-overlay security policy paths.
Incorrect Answers
A:Check the SD-WAN member inventory and assigned zone for the ISP port. It could be appropriate when a FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member. However, that does not resolve the stated condition: a deployment requires public Internet from a third ISP, and the operator wants to manage it independently without applying the private overlay's IPS policy. A more direct answer is check the new member zone and the firewall security profile group applied to that zone.
C:Inspect the two VPN interfaces' zone assignments and overlay routing entries. The outcome for that step belongs to two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout. Here the decisive requirement concerns a deployment requires public Internet from a third ISP, and the operator wants to manage it independently without applying the private overlay's IPS policy, so check the new member zone and the firewall security profile group applied to that zone is the better fit.
D:Inspect member and zone entries after the rule has been removed. That is a useful action for a different circumstance: a network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions. The present case is constrained by a deployment requires public Internet from a third ISP, and the operator wants to manage it independently without applying the private overlay's IPS policy; the targeted response is check the new member zone and the firewall security profile group applied to that zone.
Question 739
For a change review, the team proposes to constrain the pilot profile to a narrowly defined test user or endpoint group because: An administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. Which explanation connects the change to the underlying behavior?
- Posture checks are useful only when their result affects the relevant access enforcement path
- Profiles must be scoped to their target populations to avoid unintended fleet-wide change
- Endpoint posture requirements differentiate compliant and noncompliant devices independently of user authentication
- A compliant posture can require both running antivirus and connected management telemetry
Explanation
Correct Answer
B:Profiles must be scoped to their target populations to avoid unintended fleet-wide change. It directly explains the need to constrain the pilot profile to a narrowly defined test user or endpoint group. The narrow validation is: Only pilot devices receive the new requirements while other users retain their prior settings.
Incorrect Answers
A:Posture checks are useful only when their result affects the relevant access enforcement path. It could be appropriate when security wants a noncompliant laptop to be unable to access protected company applications until it passes device checks. However, that does not resolve the stated condition: an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. A more direct answer is profiles must be scoped to their target populations to avoid unintended fleet-wide change.
C:Endpoint posture requirements differentiate compliant and noncompliant devices independently of user authentication. That is a useful action for a different circumstance: a company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions. The present case is constrained by an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams; the targeted response is profiles must be scoped to their target populations to avoid unintended fleet-wide change.
D:A compliant posture can require both running antivirus and connected management telemetry. The outcome for that step belongs to a managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service. Here the decisive requirement concerns an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams, so profiles must be scoped to their target populations to avoid unintended fleet-wide change is the better fit.
Question 740
For a change review, the team proposes to review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust because: An agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain. Which explanation connects the change to the underlying behavior?
- Profile-group selection at policy level can differentiate inspection by user cohort
- SWG SSO authentication can depend on deep inspection, and bypass exceptions can interrupt that workflow
- DNS filtering can enforce policy based on name resolution queries, complementing web URL checks
- Categorization filters web destinations by content classification instead of treating all hosts at one IP equally
Explanation
Correct Answer
B:SWG SSO authentication can depend on deep inspection, and bypass exceptions can interrupt that workflow. It directly explains the need to review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust. The narrow validation is: An SSO session completes while intended web inspection policy remains enforced.
Incorrect Answers
A:Profile-group selection at policy level can differentiate inspection by user cohort. That is a useful action for a different circumstance: a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. The present case is constrained by an agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain; the targeted response is sWG SSO authentication can depend on deep inspection, and bypass exceptions can interrupt that workflow.
C:DNS filtering can enforce policy based on name resolution queries, complementing web URL checks. It could be appropriate when a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests. However, that does not resolve the stated condition: an agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain. A more direct answer is sWG SSO authentication can depend on deep inspection, and bypass exceptions can interrupt that workflow.
D:Categorization filters web destinations by content classification instead of treating all hosts at one IP equally. The outcome for that step belongs to employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone. Here the decisive requirement concerns an agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain, so sWG SSO authentication can depend on deep inspection, and bypass exceptions can interrupt that workflow is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests