Question 600
The team is troubleshooting the following Fortinet 7.6 deployment: A remote endpoint has FortiClient installed, but the connection profile is stale after the administrator changes the tenant settings. Which specific corrective action should be prioritized?
- Trigger the supported endpoint-profile update and verify the client receives the current managed configuration
- Configure and test the supported SAML identity provider integration and user-group claims
- Validate LDAP group retrieval and policy group mapping in addition to directory connectivity
- Configure the supported SWG SSO policy with required deep SSL inspection and trusted CA handling
Explanation
Correct Answer
A:Trigger the supported endpoint-profile update and verify the client receives the current managed configuration. Managed agent settings must be synchronized to endpoints before new parameters can govern connections. The configuration alone must be followed by a functioning test: After synchronization, the client uses the newly approved tunnel and security settings.
Incorrect Answers
B:Configure and test the supported SAML identity provider integration and user-group claims. That is a useful action for a different circumstance: a corporation already authenticates its employees with an enterprise SAML identity provider and wants single sign-on for FortiSASE user access. The present case is constrained by a remote endpoint has FortiClient installed, but the connection profile is stale after the administrator changes the tenant settings; the targeted response is trigger the supported endpoint-profile update and verify the client receives the current managed configuration.
C:Validate LDAP group retrieval and policy group mapping in addition to directory connectivity. The outcome for that step belongs to a company chooses LDAP as an identity source, but FortiSASE cannot apply a group-based access policy despite successful basic user lookup. Here the decisive requirement concerns a remote endpoint has FortiClient installed, but the connection profile is stale after the administrator changes the tenant settings, so trigger the supported endpoint-profile update and verify the client receives the current managed configuration is the better fit.
D:Configure the supported SWG SSO policy with required deep SSL inspection and trusted CA handling. It addresses the SASE team expects users to authenticate through SWG SSO but the configured policy uses certificate inspection only. In the reported environment, the missing behavior instead relates to a remote endpoint has FortiClient installed, but the connection profile is stale after the administrator changes the tenant settings. The relevant choice is trigger the supported endpoint-profile update and verify the client receives the current managed configuration.
Question 601
During implementation, the administrator observes: A branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy. Which intervention targets the described fault rather than an adjacent workflow?
- Add the correct physical interface as an SD-WAN member and assign it to the intended zone
- Attach the additional tunnel member to the existing correctly scoped overlay SD-WAN zone
- Use the SD-WAN zone object in the firewall policy instead of attempting to target the individual SD-WAN member
- Enroll the ISP as a member of an Internet-only SD-WAN zone and define its firewall-policy treatment
Explanation
Correct Answer
B:Attach the additional tunnel member to the existing correctly scoped overlay SD-WAN zone. A shared overlay zone makes the same firewall policy interface cover multiple tunnels. The acceptance check should show: A controlled failure of the first tunnel leads private traffic through the second while preserving policy matching.
Incorrect Answers
A:Add the correct physical interface as an SD-WAN member and assign it to the intended zone. 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 branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy. A more direct answer is attach the additional tunnel member to the existing correctly scoped overlay SD-WAN zone.
C:Use the SD-WAN zone object in the firewall policy instead of attempting to target the individual SD-WAN member. That is a useful action for a different circumstance: a FortiGate using zone-based policies shows the original interface port but the administrator cannot select it as a distinct policy destination. The present case is constrained by a branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy; the targeted response is attach the additional tunnel member to the existing correctly scoped overlay SD-WAN zone.
D:Enroll the ISP as a member of an Internet-only SD-WAN zone and define its firewall-policy treatment. The outcome for that step belongs to 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. Here the decisive requirement concerns a branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy, so attach the additional tunnel member to the existing correctly scoped overlay SD-WAN zone is the better fit.
Question 602
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? An agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain.
- Only the targeted cohort receives the block, and other approved users retain expected access
- A controlled security test produces the expected IPS event or block decision
- Blocked-domain resolution attempts follow the configured DNS policy and produce expected events
- An SSO session completes while intended web inspection policy remains enforced
Explanation
Correct Answer
D:An SSO session completes while intended web inspection policy remains enforced. This is stronger than a saved configuration because it tests the intended operational result. SWG SSO authentication can depend on deep inspection, and bypass exceptions can interrupt that workflow.
Incorrect Answers
A:Only the targeted cohort receives the block, and other approved users retain expected access. It addresses a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. In the reported environment, the missing behavior instead relates to an agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain. The relevant choice is an SSO session completes while intended web inspection policy remains enforced.
B:A controlled security test produces the expected IPS event or block decision. That is a useful action for a different circumstance: a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. 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 an SSO session completes while intended web inspection policy remains enforced.
C:Blocked-domain resolution attempts follow the configured DNS policy and produce expected events. 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 an SSO session completes while intended web inspection policy remains enforced.
Question 603
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks.
- A new allowed test flow uses the selected member and logs the intended permit policy
- Route lookup consistently identifies the intended next hop before SD-WAN member selection is analyzed
- The corrected interface reaches its first hop and the remote SLA server
- Fresh connections successfully establish through the chosen ISP's correct translated source
Explanation
Correct Answer
B:Route lookup consistently identifies the intended next hop before SD-WAN member selection is analyzed. This is stronger than a saved configuration because it tests the intended operational result. The forwarding route decision must be understood before diagnosing member-level quality steering.
Incorrect Answers
A:A new allowed test flow uses the selected member and logs the intended permit policy. It could be appropriate when a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. However, that does not resolve the stated condition: a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks. A more direct answer is route lookup consistently identifies the intended next hop before SD-WAN member selection is analyzed.
C:The corrected interface reaches its first hop and the remote SLA server. The outcome for that step belongs to a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member. Here the decisive requirement concerns a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks, so route lookup consistently identifies the intended next hop before SD-WAN member selection is analyzed is the better fit.
D:Fresh connections successfully establish through the chosen ISP's correct translated source. That is a useful action for a different circumstance: a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. The present case is constrained by a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks; the targeted response is route lookup consistently identifies the intended next hop before SD-WAN member selection is analyzed.
Question 604
The team plans to use a defined SD-WAN rule and inspect its selected member against current health and match criteria for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session.
- A health widget showing both links alive does not establish which policy matched the session
- Passive measurement may be uninformative for an idle site and should not be assumed equivalent to active probing
- A static route pointing to a zone does not automatically populate that zone with members
- Member priority by itself cannot enforce which source identities may enter the restricted overlay
Explanation
Correct Answer
A:A health widget showing both links alive does not establish which policy matched the session. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:Passive measurement may be uninformative for an idle site and should not be assumed equivalent to active probing. That is a useful action for a different circumstance: a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use. The present case is constrained by a branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session; the targeted response is a health widget showing both links alive does not establish which policy matched the session.
C:A static route pointing to a zone does not automatically populate that zone with members. The outcome for that step belongs to a FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member. Here the decisive requirement concerns a branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session, so a health widget showing both links alive does not establish which policy matched the session is the better fit.
D:Member priority by itself cannot enforce which source identities may enter the restricted overlay. It addresses a site should limit one overlay circuit to a restricted group of users, unlike unrestricted Internet underlays. In the reported environment, the missing behavior instead relates to a branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session. The relevant choice is a health widget showing both links alive does not establish which policy matched the session.
Question 605
The team is troubleshooting the following Fortinet 7.6 deployment: A private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet. Which specific corrective action should be prioritized?
- Correct return-path routing and stateful policy consistency for private applications over SPA
- Add a narrowly scoped firewall-policy permit for the legitimate SASE source and destination as required
- Configure and validate internal DNS resolution and any required DNS redirection for private domains
- Validate BGP adjacency and learned private routes across the tunnel
Explanation
Correct Answer
B:Add a narrowly scoped firewall-policy permit for the legitimate SASE source and destination as required. Private access requires separate firewall authorization in addition to tunnel and route reachability. The acceptance check should show: The authorized source reaches only its permitted private application and is logged accordingly.
Incorrect Answers
A:Correct return-path routing and stateful policy consistency for private applications over SPA. The outcome for that step belongs to a remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path. Here the decisive requirement concerns a private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet, so add a narrowly scoped firewall-policy permit for the legitimate SASE source and destination as required is the better fit.
C:Configure and validate internal DNS resolution and any required DNS redirection for private domains. That is a useful action for a different circumstance: a remote user can reach an internal server by private IP but not by its internal hostname through the SPA connection. The present case is constrained by a private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet; the targeted response is add a narrowly scoped firewall-policy permit for the legitimate SASE source and destination as required.
D:Validate BGP adjacency and learned private routes across the tunnel. It could be appropriate when a service provider reuses a FortiGate SD-WAN hub for FortiSASE SPA and wants to confirm BGP is functioning, not only an IPsec phase-one tunnel. However, that does not resolve the stated condition: a private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet. A more direct answer is add a narrowly scoped firewall-policy permit for the legitimate SASE source and destination as required.
Question 606
After the authorized change to inspect the affected traffic's matched rule and egress details in SD-WAN/session logs, which result actually demonstrates that this site's requirement is met? Initial issue: A helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change.
- The sequence shows whether SLA failure preceded path selection or a route event caused it
- The selected member and traffic increase are attributable to the actual logged sessions
- The log records the expected rule and the backup-member selection for that transaction
- New authorized transactions complete over the backup path during failure testing
Explanation
Correct Answer
C:The log records the expected rule and the backup-member selection for that transaction. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:The sequence shows whether SLA failure preceded path selection or a route event caused it. It could be appropriate when an operator says a VPN application keeps failing over but cannot show whether the trigger was packet loss or a routing change. However, that does not resolve the stated condition: a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. A more direct answer is the log records the expected rule and the backup-member selection for that transaction.
B:The selected member and traffic increase are attributable to the actual logged sessions. It addresses a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. In the reported environment, the missing behavior instead relates to a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. The relevant choice is the log records the expected rule and the backup-member selection for that transaction.
D:New authorized transactions complete over the backup path during failure testing. The outcome for that step belongs to a branch rollout claims reliable failover because the WAN link state changed, but the business owner wants proof that application transactions continued. Here the decisive requirement concerns a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change, so the log records the expected rule and the backup-member selection for that transaction is the better fit.
Question 607
For the stated scenario, what is the most important remaining blind spot after the proposed correction? Employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone.
- An SD-WAN jitter threshold does not classify phishing websites
- Assuming an unknown attribute always means compliant can expose protected resources
- An inventory dashboard that reports posture without enforcing it does not satisfy conditional-access goals
- A successful SSO login does not erase high-severity vulnerability findings
Explanation
Correct Answer
A:An SD-WAN jitter threshold does not classify phishing websites. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:Assuming an unknown attribute always means compliant can expose protected resources. The outcome for that step belongs to a department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable. Here the decisive requirement concerns employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone, so an SD-WAN jitter threshold does not classify phishing websites is the better fit.
C:An inventory dashboard that reports posture without enforcing it does not satisfy conditional-access goals. 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 employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone; the targeted response is an SD-WAN jitter threshold does not classify phishing websites.
D:A successful SSO login does not erase high-severity vulnerability findings. It addresses a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. In the reported environment, the missing behavior instead relates to employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone. The relevant choice is an SD-WAN jitter threshold does not classify phishing websites.
Question 608
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: During an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary.
- Inspect report category, action filters, group attribution and period lengths
- Inspect active filters, date limits and the export's documented entry scope
- Inspect report generation timeframe and corresponding event-log availability
- Inspect report filters, selected dates and data sources before running it
Explanation
Correct Answer
D:Inspect report filters, selected dates and data sources before running it. This check isolates the relevant control before the change. On-demand generation allows a targeted investigation without waiting for the next scheduled run.
Incorrect Answers
A:Inspect report category, action filters, group attribution and period lengths. It addresses 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. In the reported environment, the missing behavior instead relates to during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary. The relevant choice is inspect report filters, selected dates and data sources before running it.
B:Inspect active filters, date limits and the export's documented entry scope. It could be appropriate when an analyst exports the currently filtered FortiSASE security-log view but expects every historical event in the tenant to appear in that export. However, that does not resolve the stated condition: during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary. A more direct answer is inspect report filters, selected dates and data sources before running it.
C:Inspect report generation timeframe and corresponding event-log availability. 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 during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary; the targeted response is inspect report filters, selected dates and data sources before running it.
Question 609
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable.
- Instructing users to ignore all certificate warnings would hide genuine TLS risks
- An accept action alone does not imply all possible security profiles are enabled
- A broad DNS deny would eliminate the service rather than implement action-level monitoring
- Assuming an unknown attribute always means compliant can expose protected resources
Explanation
Correct Answer
D:Assuming an unknown attribute always means compliant can expose protected resources. The planned change can still miss the requirement if this condition is left unresolved. Conditional access decisions must use the actual required posture attributes and rule logic.
Incorrect Answers
A:Instructing users to ignore all certificate warnings would hide genuine TLS risks. It addresses a browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions. In the reported environment, the missing behavior instead relates to a department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable. The relevant choice is assuming an unknown attribute always means compliant can expose protected resources.
B:An accept action alone does not imply all possible security profiles are enabled. That is a useful action for a different circumstance: a remote-user security policy is set to Accept but the administrator expects an IPS profile to be active without having attached a profile group. The present case is constrained by a department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable; the targeted response is assuming an unknown attribute always means compliant can expose protected resources.
C:A broad DNS deny would eliminate the service rather than implement action-level monitoring. It could be appropriate when a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service. However, that does not resolve the stated condition: a department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable. A more direct answer is assuming an unknown attribute always means compliant can expose protected resources.
Question 610
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy.
- The SaaS service hits its own rule while generic traffic remains under the broad steering rule
- New matching calls are steered toward the better-performing member under the configured metric
- Billing traffic matches the intended narrow rule and the generic rule handles remaining sessions
- Emergency flows use the intended LTE member without rerouting unrelated Web traffic
Explanation
Correct Answer
D:Emergency flows use the intended LTE member without rerouting unrelated Web traffic. This is stronger than a saved configuration because it tests the intended operational result. An ordinary allow policy decides permission; the steering rule determines eligible egress selection for matched traffic.
Incorrect Answers
A:The SaaS service hits its own rule while generic traffic remains under the broad steering rule. It could be appropriate when a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. However, that does not resolve the stated condition: a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy. A more direct answer is emergency flows use the intended LTE member without rerouting unrelated Web traffic.
B:New matching calls are steered toward the better-performing member under the configured metric. That is a useful action for a different circumstance: video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price. The present case is constrained by a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy; the targeted response is emergency flows use the intended LTE member without rerouting unrelated Web traffic.
C:Billing traffic matches the intended narrow rule and the generic rule handles remaining sessions. It addresses a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. In the reported environment, the missing behavior instead relates to a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy. The relevant choice is emergency flows use the intended LTE member without rerouting unrelated Web traffic.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests