Question 190
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? Security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny.
- Inspect the matched DLP rule, user, application and blocked action
- Inspect the sign-in outcomes, source addresses and account correlation in the audit window
- Search overlapping timestamps, username and application or destination fields in both log types
- Review the cloud application's identified operation and enforcement action
Explanation
Correct Answer
D:Review the cloud application's identified operation and enforcement action. This check isolates the relevant control before the change. Inline SaaS inspection can produce activity-level events distinct from domain-category blocks.
Incorrect Answers
A:Inspect the matched DLP rule, user, application and blocked action. It could be appropriate when an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. However, that does not resolve the stated condition: security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. A more direct answer is review the cloud application's identified operation and enforcement action.
B:Inspect the sign-in outcomes, source addresses and account correlation in the audit window. That is a useful action for a different circumstance: a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. The present case is constrained by security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny; the targeted response is review the cloud application's identified operation and enforcement action.
C:Search overlapping timestamps, username and application or destination fields in both log types. It addresses a FortiSASE security incident spans an employee's proxy session and a possible malware detection one minute later. In the reported environment, the missing behavior instead relates to security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. The relevant choice is review the cloud application's identified operation and enforcement action.
Question 191
The team plans to sync the AD connection and verify the effective user/group-based endpoint-profile assignment for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A company configures an Active Directory group for endpoint profiles, but a recently added user still receives the Default profile.
- An on-premises branch-only firewall rule cannot cover remote sessions that never traverse that branch
- Deleting the Default profile is not a remedy and may be unsupported
- A traffic log showing an allowed website request is not proof of who edited the policy
- Expanding a broad any-to-any rule would unnecessarily widen application access
Explanation
Correct Answer
B:Deleting the Default profile is not a remedy and may be unsupported. The planned change can still miss the requirement if this condition is left unresolved. Endpoint assignment depends on available synchronized directory membership and profile matching.
Incorrect Answers
A:An on-premises branch-only firewall rule cannot cover remote sessions that never traverse that branch. The outcome for that step belongs to a large retailer wants to prove that security policy enforcement for mobile employees is cloud-based rather than tied to their nearest on-premises office firewall. Here the decisive requirement concerns a company configures an Active Directory group for endpoint profiles, but a recently added user still receives the Default profile, so deleting the Default profile is not a remedy and may be unsupported is the better fit.
C:A traffic log showing an allowed website request is not proof of who edited the policy. That is a useful action for a different circumstance: an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. The present case is constrained by a company configures an Active Directory group for endpoint profiles, but a recently added user still receives the Default profile; the targeted response is deleting the Default profile is not a remedy and may be unsupported.
D:Expanding a broad any-to-any rule would unnecessarily widen application access. It could be appropriate when a private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet. However, that does not resolve the stated condition: a company configures an Active Directory group for endpoint profiles, but a recently added user still receives the Default profile. A more direct answer is deleting the Default profile is not a remedy and may be unsupported.
Question 192
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A department asks which user cohort consumed the most bandwidth across FortiSASE Internet access this month.
- Inspect active filters, date limits and the export's documented entry scope
- Inspect report periods, matched category actions and any reporting coverage differences
- Inspect the report's user grouping, time range and byte totals
- Inspect log-forwarding destination, connection status and event receipt in the external system
Explanation
Correct Answer
C:Inspect the report's user grouping, time range and byte totals. The observed evidence guides the targeted repair: Use a user-traffic or usage report filtered to the month and corresponding cohort.
Incorrect Answers
A:Inspect active filters, date limits and the export's documented entry scope. It addresses an analyst exports the currently filtered FortiSASE security-log view but expects every historical event in the tenant to appear in that export. In the reported environment, the missing behavior instead relates to a department asks which user cohort consumed the most bandwidth across FortiSASE Internet access this month. The relevant choice is inspect the report's user grouping, time range and byte totals.
B:Inspect report periods, matched category actions and any reporting coverage differences. 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 a department asks which user cohort consumed the most bandwidth across FortiSASE Internet access this month, so inspect the report's user grouping, time range and byte totals is the better fit.
D:Inspect log-forwarding destination, connection status and event receipt in the external system. It could be appropriate when a regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window. However, that does not resolve the stated condition: a department asks which user cohort consumed the most bandwidth across FortiSASE Internet access this month. A more direct answer is inspect the report's user grouping, time range and byte totals.
Question 193
The team is troubleshooting the following Fortinet 7.6 deployment: The team sees a route via an SD-WAN zone but no actual WAN member is healthy under it. Which specific corrective action should be prioritized?
- Make an overlay-specific zone and reference that zone in a narrow firewall policy for the authorized users
- Treat member and zone configuration as persistent objects and remove them separately only if the design requires it
- Inspect and restore at least one usable member in the zone before expecting forwarded traffic
- Enroll the ISP as a member of an Internet-only SD-WAN zone and define its firewall-policy treatment
Explanation
Correct Answer
C:Inspect and restore at least one usable member in the zone before expecting forwarded traffic. Routing through an SD-WAN zone requires a member capable of carrying traffic after health and reachability checks. The configuration alone must be followed by a functioning test: A restored member carries test packets and is visible in the rule's active selection.
Incorrect Answers
A:Make an overlay-specific zone and reference that zone in a narrow firewall policy for the authorized users. It could be appropriate when a site should limit one overlay circuit to a restricted group of users, unlike unrestricted Internet underlays. However, that does not resolve the stated condition: the team sees a route via an SD-WAN zone but no actual WAN member is healthy under it. A more direct answer is inspect and restore at least one usable member in the zone before expecting forwarded traffic.
B:Treat member and zone configuration as persistent objects and remove them separately only if the design requires it. 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 the team sees a route via an SD-WAN zone but no actual WAN member is healthy under it, so inspect and restore at least one usable member in the zone before expecting forwarded traffic is the better fit.
D:Enroll the ISP as a member of an Internet-only SD-WAN zone and define its firewall-policy treatment. It addresses 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. In the reported environment, the missing behavior instead relates to the team sees a route via an SD-WAN zone but no actual WAN member is healthy under it. The relevant choice is inspect and restore at least one usable member in the zone before expecting forwarded traffic.
Question 194
For a change review, the team proposes to set the rule's supported minimum SLA-meeting member count to two because: The company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. Which explanation connects the change to the underlying behavior?
- Health results depend on the selected probe target and path; an unreachable probe endpoint can create a false failure signal
- The minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA
- This strategy elects the lowest-cost member among links meeting the SLA before considering preference ties
- Passive monitoring derives link quality from existing traversing traffic rather than generating active probes
Explanation
Correct Answer
B:The minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA. It directly explains the need to set the rule's supported minimum SLA-meeting member count to two. The narrow validation is: The rule activates only while at least two members satisfy its required SLA.
Incorrect Answers
A:Health results depend on the selected probe target and path; an unreachable probe endpoint can create a false failure signal. The outcome for that step belongs to a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works. Here the decisive requirement concerns the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule, so the minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA is the better fit.
C:This strategy elects the lowest-cost member among links meeting the SLA before considering preference ties. That is a useful action for a different circumstance: a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements. The present case is constrained by the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule; the targeted response is the minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA.
D:Passive monitoring derives link quality from existing traversing traffic rather than generating active probes. It could be appropriate when a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use. However, that does not resolve the stated condition: the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. A more direct answer is the minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA.
Question 195
Given this incident — An SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow. — the administrator plans to inspect the selected-member information in per-session and SD-WAN rule diagnostics. Which technical principle justifies it?
- Logged rule IDs and application information can demonstrate the policy's actual scope
- Link-quality and steering events describe path changes that physical link state alone may not explain
- Eligibility is a candidate set; the selected path must be determined for the specific traffic instance
- Per-session policy and egress evidence can identify the forwarding decision behind a route change
Explanation
Correct Answer
C:Eligibility is a candidate set; the selected path must be determined for the specific traffic instance. This is why the proposed repair addresses the reported behavior; confirm by checking: The actual traffic log or session record names the intended selected member.
Incorrect Answers
A:Logged rule IDs and application information can demonstrate the policy's actual scope. It could be appropriate when an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. However, that does not resolve the stated condition: an SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow. A more direct answer is eligibility is a candidate set; the selected path must be determined for the specific traffic instance.
B:Link-quality and steering events describe path changes that physical link state alone may not explain. It addresses a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. In the reported environment, the missing behavior instead relates to an SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow. The relevant choice is eligibility is a candidate set; the selected path must be determined for the specific traffic instance.
D:Per-session policy and egress evidence can identify the forwarding decision behind a route change. The outcome for that step belongs to a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. Here the decisive requirement concerns an SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow, so eligibility is a candidate set; the selected path must be determined for the specific traffic instance is the better fit.
Question 196
The team plans to check the FortiSASE RADIUS server settings and shared secret against the server-side client definition for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? RADIUS-backed authentication works for a test account on the directory server but fails for FortiSASE users after onboarding.
- A type not supported for synchronization must not be assumed to appear automatically
- An allow-any Internet policy is not a substitute for private-prefix routing and least-privilege access
- Changing Internet steering rules will not correct a mismatched RADIUS shared secret
- Correct BGP prefixes cannot traverse a tunnel that never establishes
Explanation
Correct Answer
C:Changing Internet steering rules will not correct a mismatched RADIUS shared secret. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:A type not supported for synchronization must not be assumed to appear automatically. It could be appropriate when a central network management program wants address groups and security profile groups shared between on-premise FortiGate and the FortiSASE tenant. However, that does not resolve the stated condition: rADIUS-backed authentication works for a test account on the directory server but fails for FortiSASE users after onboarding. A more direct answer is changing Internet steering rules will not correct a mismatched RADIUS shared secret.
B:An allow-any Internet policy is not a substitute for private-prefix routing and least-privilege access. It addresses a secure private access rollout uses a hub-and-spoke VPN topology and engineers expect private traffic to be accessible without exposing on-prem applications to the public Internet. In the reported environment, the missing behavior instead relates to rADIUS-backed authentication works for a test account on the directory server but fails for FortiSASE users after onboarding. The relevant choice is changing Internet steering rules will not correct a mismatched RADIUS shared secret.
D:Correct BGP prefixes cannot traverse a tunnel that never establishes. The outcome for that step belongs to fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. Here the decisive requirement concerns rADIUS-backed authentication works for a test account on the directory server but fails for FortiSASE users after onboarding, so changing Internet steering rules will not correct a mismatched RADIUS shared secret is the better fit.
Question 197
The team plans to add or correct performance-SLA measurements and reference them in the application steering rule for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit.
- Membership in the overlay zone would produce unintended policy coupling
- Disabling the faulty uplink administratively hides the missing performance-based decision logic
- A passive-only measurement may lack fresh samples when no relevant application sessions exist
- Moving the tunnel without updating affected route and policy references can preserve the outage
Explanation
Correct Answer
B:Disabling the faulty uplink administratively hides the missing performance-based decision logic. The planned change can still miss the requirement if this condition is left unresolved. Physical interface state measures carrier, whereas SLA probes reveal end-to-end latency, jitter and loss.
Incorrect Answers
A:Membership in the overlay zone would produce unintended policy coupling. It could be appropriate when 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. However, that does not resolve the stated condition: a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit. A more direct answer is disabling the faulty uplink administratively hides the missing performance-based decision logic.
C:A passive-only measurement may lack fresh samples when no relevant application sessions exist. The outcome for that step belongs to two WAN interfaces show up, but the network manager needs continuous health information even when no users are active. Here the decisive requirement concerns a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit, so disabling the faulty uplink administratively hides the missing performance-based decision logic is the better fit.
D:Moving the tunnel without updating affected route and policy references can preserve the outage. That is a useful action for a different circumstance: during site migration, the team assigns an overlay tunnel to the ordinary Internet zone, then discovers it is subject to public-web policy handling. The present case is constrained by a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit; the targeted response is disabling the faulty uplink administratively hides the missing performance-based decision logic.
Question 198
Given this incident — A new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy. — the administrator plans to map the user to the correct identity group and check the group condition on the intended access policy. Which technical principle justifies it?
- Identity-based policy assignment depends on group membership, not just successful authentication
- The onboarding mode and policy scope should align to browser-based Internet access rather than broad private routing
- Endpoint profiles can differentiate connection behavior by selected AD or non-AD user groups
- Group-based authorization requires that the relevant identity-group attributes are available to the SASE policy
Explanation
Correct Answer
A:Identity-based policy assignment depends on group membership, not just successful authentication. This is why the proposed repair addresses the reported behavior; confirm by checking: The new starter receives the intended departmental policy after correct group mapping.
Incorrect Answers
B:The onboarding mode and policy scope should align to browser-based Internet access rather than broad private routing. It addresses a temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel. In the reported environment, the missing behavior instead relates to a new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy. The relevant choice is identity-based policy assignment depends on group membership, not just successful authentication.
C:Endpoint profiles can differentiate connection behavior by selected AD or non-AD user groups. The outcome for that step belongs to one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. Here the decisive requirement concerns a new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy, so identity-based policy assignment depends on group membership, not just successful authentication is the better fit.
D:Group-based authorization requires that the relevant identity-group attributes are available to the SASE policy. That is a useful action for a different circumstance: a company chooses LDAP as an identity source, but FortiSASE cannot apply a group-based access policy despite successful basic user lookup. The present case is constrained by a new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy; the targeted response is identity-based policy assignment depends on group membership, not just successful authentication.
Question 199
The team is troubleshooting the following Fortinet 7.6 deployment: The WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry. Which specific corrective action should be prioritized?
- Use Lowest Cost (SLA) steering with relevant performance targets and appropriate member costs
- Change the health-check destination to a representative reachable and permitted probe target
- Reference the intended SLA target explicitly in the rule's steering configuration
- Include both candidate members in the health check where the intended steering decision compares them
Explanation
Correct Answer
D:Include both candidate members in the health check where the intended steering decision compares them. Per-member SLA measurements make alternate-link selection observable and qualified. The acceptance check should show: Both candidate paths show valid quality samples used by the relevant rule.
Incorrect Answers
A:Use Lowest Cost (SLA) steering with relevant performance targets and appropriate member costs. It could be appropriate when a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements. However, that does not resolve the stated condition: the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry. A more direct answer is include both candidate members in the health check where the intended steering decision compares them.
B:Change the health-check destination to a representative reachable and permitted probe target. It addresses a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works. In the reported environment, the missing behavior instead relates to the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry. The relevant choice is include both candidate members in the health check where the intended steering decision compares them.
C:Reference the intended SLA target explicitly in the rule's steering configuration. That is a useful action for a different circumstance: an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit. The present case is constrained by the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry; the targeted response is include both candidate members in the health check where the intended steering decision compares them.
Question 200
For a change review, the team proposes to confirm FortiClient or SWG traffic steering toward the designated FortiSASE security PoP because: A security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally. Which explanation connects the change to the underlying behavior?
- Cloud PoPs apply policy on the user path, independent of the user's physical branch location
- Individual accountability and scoped permissions improve operational security and auditability
- The PoP is where the cloud-delivered access policy evaluates the relevant traffic flow
- Service routing and jurisdictional obligations are separate from basic tunnel connectivity
Explanation
Correct Answer
C:The PoP is where the cloud-delivered access policy evaluates the relevant traffic flow. This is why the proposed repair addresses the reported behavior; confirm by checking: The user's test flow appears in FortiSASE policy and traffic logs for the expected PoP.
Incorrect Answers
A:Cloud PoPs apply policy on the user path, independent of the user's physical branch location. It addresses a large retailer wants to prove that security policy enforcement for mobile employees is cloud-based rather than tied to their nearest on-premises office firewall. In the reported environment, the missing behavior instead relates to a security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally. The relevant choice is the PoP is where the cloud-delivered access policy evaluates the relevant traffic flow.
B:Individual accountability and scoped permissions improve operational security and auditability. The outcome for that step belongs to one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account. Here the decisive requirement concerns a security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally, so the PoP is where the cloud-delivered access policy evaluates the relevant traffic flow is the better fit.
D:Service routing and jurisdictional obligations are separate from basic tunnel connectivity. It could be appropriate when an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision. However, that does not resolve the stated condition: a security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally. A more direct answer is the PoP is where the cloud-delivered access policy evaluates the relevant traffic flow.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests