Question 790
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? 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.
- Inspect the applied inline-CASB profile and the event details of a test user action
- Inspect the policy action and Profile Group selection for a representative allowed session
- Inspect the effective web-filter profile and category action for the test URL
- Inspect policy rule order, matching user group and attached security profile group
Explanation
Correct Answer
B:Inspect the policy action and Profile Group selection for a representative allowed session. This check isolates the relevant control before the change. FortiSASE applies selected inspection components through profile groups associated with eligible policies.
Incorrect Answers
A:Inspect the applied inline-CASB profile and the event details of a test user action. That is a useful action for a different circumstance: a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service. The present case is constrained by 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 targeted response is inspect the policy action and Profile Group selection for a representative allowed session.
C:Inspect the effective web-filter profile and category action for the test URL. 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 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, so inspect the policy action and Profile Group selection for a representative allowed session is the better fit.
D:Inspect policy rule order, matching user group and attached security profile group. It could be appropriate when a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. However, that does not resolve the stated condition: 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. A more direct answer is inspect the policy action and Profile Group selection for a representative allowed session.
Question 791
For the stated scenario, what is the most important remaining blind spot after the proposed correction? FortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub.
- Disabling all certificate verification would undermine the identity-trust boundary instead of repairing it
- Deep-inspection exemptions can interfere with SWG SSO flows under this configuration
- Giving everyone the top administrative role would bypass the separation-of-duties goal
- Correct BGP prefixes cannot traverse a tunnel that never establishes
Explanation
Correct Answer
D:Correct BGP prefixes cannot traverse a tunnel that never establishes. The planned change can still miss the requirement if this condition is left unresolved. The SPA overlay depends on a functioning encrypted PoP-to-hub transport.
Incorrect Answers
A:Disabling all certificate verification would undermine the identity-trust boundary instead of repairing it. It addresses a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. In the reported environment, the missing behavior instead relates to fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. The relevant choice is correct BGP prefixes cannot traverse a tunnel that never establishes.
B:Deep-inspection exemptions can interfere with SWG SSO flows under this configuration. It could be appropriate when the SASE team expects users to authenticate through SWG SSO but the configured policy uses certificate inspection only. However, that does not resolve the stated condition: fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. A more direct answer is correct BGP prefixes cannot traverse a tunnel that never establishes.
C:Giving everyone the top administrative role would bypass the separation-of-duties goal. That is a useful action for a different circumstance: a company needs administrators to troubleshoot access policies without allowing every operator to change identity sources or global settings. The present case is constrained by fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub; the targeted response is correct BGP prefixes cannot traverse a tunnel that never establishes.
Question 792
After the authorized change to update the trusted SAML signing-certificate configuration to the active identity-provider certificate, which result actually demonstrates that this site's requirement is met? Initial issue: A customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate.
- The test assertion validates and the user signs in with the expected claims
- A valid corporate user signs in and receives the SASE policy assigned to the asserted group
- A test SWG SSO user authenticates successfully and follows the intended proxy policy
- Newly enrolled devices receive the proper tenant registration and endpoint connection profile
Explanation
Correct Answer
A:The test assertion validates and the user signs in with the expected claims. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:A valid corporate user signs in and receives the SASE policy assigned to the asserted group. It addresses a corporation already authenticates its employees with an enterprise SAML identity provider and wants single sign-on for FortiSASE user access. In the reported environment, the missing behavior instead relates to a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. The relevant choice is the test assertion validates and the user signs in with the expected claims.
C:A test SWG SSO user authenticates successfully and follows the intended proxy policy. That is a useful action for a different circumstance: the SASE team expects users to authenticate through SWG SSO but the configured policy uses certificate inspection only. The present case is constrained by a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate; the targeted response is the test assertion validates and the user signs in with the expected claims.
D:Newly enrolled devices receive the proper tenant registration and endpoint connection profile. The outcome for that step belongs to a support team wants to distribute an approved managed FortiClient installer to a new device population, with consistent connection settings. Here the decisive requirement concerns a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate, so the test assertion validates and the user signs in with the expected claims is the better fit.
Question 793
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A security officer needs proof that web-category policy violations increased after a recent configuration change.
- A domain deny would block the service as a whole and not demonstrate operation-level control
- Changing SD-WAN member priority does not explain an application-layer intrusion signature
- A device-wide bandwidth chart does not identify one transaction's rule match
- Comparing windows of different length without normalization can exaggerate apparent growth
Explanation
Correct Answer
D:Comparing windows of different length without normalization can exaggerate apparent growth. The planned change can still miss the requirement if this condition is left unresolved. Time-window comparison can distinguish a real category-policy trend from a single cumulative count.
Incorrect Answers
A:A domain deny would block the service as a whole and not demonstrate operation-level control. That is a useful action for a different circumstance: security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. The present case is constrained by a security officer needs proof that web-category policy violations increased after a recent configuration change; the targeted response is comparing windows of different length without normalization can exaggerate apparent growth.
B:Changing SD-WAN member priority does not explain an application-layer intrusion signature. It addresses a remote client receives an intrusion-prevention alert while accessing an internal application through SASE. In the reported environment, the missing behavior instead relates to a security officer needs proof that web-category policy violations increased after a recent configuration change. The relevant choice is comparing windows of different length without normalization can exaggerate apparent growth.
C:A device-wide bandwidth chart does not identify one transaction's rule match. It could be appropriate when a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. However, that does not resolve the stated condition: a security officer needs proof that web-category policy violations increased after a recent configuration change. A more direct answer is comparing windows of different length without normalization can exaggerate apparent growth.
Question 794
After the authorized change to configure FortiSASE secure private access through the existing SD-WAN hub using the supported connector integration, which result actually demonstrates that this site's requirement is met? Initial issue: A customer wants remote FortiClient users to reach a database behind an existing FortiGate SD-WAN hub rather than exposing the database publicly.
- The authorized source reaches only its permitted private application and is logged accordingly
- A remote user reaches the private database through the protected PoP-to-hub path
- The remote user reaches the target server subnet through the hub with a matching allowed policy
- Failing one hub leaves required private routes reachable over the approved alternate hub
Explanation
Correct Answer
B:A remote user reaches the private database through the protected PoP-to-hub path. This is stronger than a saved configuration because it tests the intended operational result. The SASE security PoP can act as a spoke to a FortiGate hub for protected private networks.
Incorrect Answers
A:The authorized source reaches only its permitted private application and is logged accordingly. 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 customer wants remote FortiClient users to reach a database behind an existing FortiGate SD-WAN hub rather than exposing the database publicly. A more direct answer is a remote user reaches the private database through the protected PoP-to-hub path.
C:The remote user reaches the target server subnet through the hub with a matching allowed policy. The outcome for that step belongs to a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. Here the decisive requirement concerns a customer wants remote FortiClient users to reach a database behind an existing FortiGate SD-WAN hub rather than exposing the database publicly, so a remote user reaches the private database through the protected PoP-to-hub path is the better fit.
D:Failing one hub leaves required private routes reachable over the approved alternate hub. That is a useful action for a different circumstance: an organization adds a second FortiGate hub for resilience but has not defined which private prefixes each hub advertises. The present case is constrained by a customer wants remote FortiClient users to reach a database behind an existing FortiGate SD-WAN hub rather than exposing the database publicly; the targeted response is a remote user reaches the private database through the protected PoP-to-hub path.
Question 795
The team is troubleshooting the following Fortinet 7.6 deployment: A workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops. Which specific corrective action should be prioritized?
- Deploy and trust the FortiSASE inspection CA certificate on the affected clients according to the approved method
- Map the user to the correct identity group and check the group condition on the intended access policy
- Deploy FortiClient using a supported FortiSASE-managed endpoint profile and connect users in agent-based mode
- Provision the contractor using an agentless Internet proxy policy and omit unrelated private-access grants
Explanation
Correct Answer
C:Deploy FortiClient using a supported FortiSASE-managed endpoint profile and connect users in agent-based mode. FortiClient is the endpoint agent that steers the chosen remote traffic and receives managed connection settings. The configuration alone must be followed by a functioning test: A pilot laptop connects to FortiSASE and its Internet sessions appear under the intended user policy.
Incorrect Answers
A:Deploy and trust the FortiSASE inspection CA certificate on the affected clients according to the approved method. It addresses users report browser certificate warnings immediately after enabling deep inspection for an agentless secure web gateway. In the reported environment, the missing behavior instead relates to a workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops. The relevant choice is deploy FortiClient using a supported FortiSASE-managed endpoint profile and connect users in agent-based mode.
B:Map the user to the correct identity group and check the group condition on the intended access policy. The outcome for that step belongs to a new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy. Here the decisive requirement concerns a workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops, so deploy FortiClient using a supported FortiSASE-managed endpoint profile and connect users in agent-based mode is the better fit.
D:Provision the contractor using an agentless Internet proxy policy and omit unrelated private-access grants. It could be appropriate when a temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel. However, that does not resolve the stated condition: a workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops. A more direct answer is deploy FortiClient using a supported FortiSASE-managed endpoint profile and connect users in agent-based mode.
Question 796
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? One tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account.
- Inspect administrative identity, assigned scope and change history for the affected settings
- Filter administrative events to the policy and time of the alleged change
- Review the affected administrator account's assigned role and effective allowed actions
- Inspect integration status and the exact security profile or object covered by synchronization
Explanation
Correct Answer
A:Inspect administrative identity, assigned scope and change history for the affected settings. The observed evidence guides the targeted repair: Use individual named administrator identities and appropriate delegated roles rather than sharing credentials.
Incorrect Answers
B:Filter administrative events to the policy and time of the alleged change. The outcome for that step belongs to an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. Here the decisive requirement concerns one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account, so inspect administrative identity, assigned scope and change history for the affected settings is the better fit.
C:Review the affected administrator account's assigned role and effective allowed actions. It addresses a company needs administrators to troubleshoot access policies without allowing every operator to change identity sources or global settings. In the reported environment, the missing behavior instead relates 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. The relevant choice is inspect administrative identity, assigned scope and change history for the affected settings.
D:Inspect integration status and the exact security profile or object covered by synchronization. That is a useful action for a different circumstance: fortiSASE configuration is being centrally managed, but changes made in FortiManager do not appear in the remote tenant. The present case is constrained by one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account; the targeted response is inspect administrative identity, assigned scope and change history for the affected settings.
Question 797
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works.
- A health widget showing both links alive does not establish which policy matched the session
- A firewall policy or route that omits the SD-WAN zone can still prevent forwarding
- A single target failure should not be misdiagnosed as universal WAN unavailability
- Two virtual members mapped to the same failed provider do not deliver true transport diversity
Explanation
Correct Answer
C:A single target failure should not be misdiagnosed as universal WAN unavailability. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:A health widget showing both links alive does not establish which policy matched the session. It addresses a branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session. In the reported environment, the missing behavior instead relates to a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works. The relevant choice is a single target failure should not be misdiagnosed as universal WAN unavailability.
B:A firewall policy or route that omits the SD-WAN zone can still prevent forwarding. The outcome for that step belongs to a new branch has two internet circuits configured as ordinary FortiGate interfaces, but no SD-WAN members exist; the owner wants policy-based path steering. Here the decisive requirement concerns a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works, so a single target failure should not be misdiagnosed as universal WAN unavailability is the better fit.
D:Two virtual members mapped to the same failed provider do not deliver true transport diversity. It could be appropriate when a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. However, that does not resolve the stated condition: a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works. A more direct answer is a single target failure should not be misdiagnosed as universal WAN unavailability.
Question 798
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category.
- Inspect the effective web-filter profile and category action for the test URL
- Inspect the profile-group AV settings and the log for a safe simulated malware-detection test
- Inspect the policy action and Profile Group selection for a representative allowed session
- Inspect the DLP profile match rules and whether the application traffic is decryptable where required
Explanation
Correct Answer
B:Inspect the profile-group AV settings and the log for a safe simulated malware-detection test. This check isolates the relevant control before the change. Antivirus scanning targets malicious content, which may reside on otherwise acceptable sites.
Incorrect Answers
A:Inspect the effective web-filter profile and category action for the test URL. That is a useful action for a different circumstance: employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone. The present case is constrained by a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category; the targeted response is inspect the profile-group AV settings and the log for a safe simulated malware-detection test.
C:Inspect the policy action and Profile Group selection for a representative allowed session. The outcome for that step belongs to 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. Here the decisive requirement concerns a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category, so inspect the profile-group AV settings and the log for a safe simulated malware-detection test is the better fit.
D:Inspect the DLP profile match rules and whether the application traffic is decryptable where required. It could be appropriate when a company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications. However, that does not resolve the stated condition: a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category. A more direct answer is inspect the profile-group AV settings and the log for a safe simulated malware-detection test.
Question 799
The team plans to use the appropriate Internet Service Database selector within the SD-WAN rule where supported for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? An administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list.
- Creating duplicate static routes does not make a degraded link satisfy a performance objective
- A static single-IP address can age out as the cloud service shifts endpoints
- Changing an SD-WAN member weight cannot overturn an explicit deny policy
- Changing a security profile cannot resolve an unreachable WAN gateway
Explanation
Correct Answer
B:A static single-IP address can age out as the cloud service shifts endpoints. The planned change can still miss the requirement if this condition is left unresolved. Internet-service identification is designed for recognized services whose destinations may change.
Incorrect Answers
A:Creating duplicate static routes does not make a degraded link satisfy a performance objective. The outcome for that step belongs to an administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing. Here the decisive requirement concerns an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list, so a static single-IP address can age out as the cloud service shifts endpoints is the better fit.
C:Changing an SD-WAN member weight cannot overturn an explicit deny policy. That is a useful action for a different circumstance: a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. The present case is constrained by an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list; the targeted response is a static single-IP address can age out as the cloud service shifts endpoints.
D:Changing a security profile cannot resolve an unreachable WAN gateway. It could be appropriate when a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. However, that does not resolve the stated condition: an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. A more direct answer is a static single-IP address can age out as the cloud service shifts endpoints.
Question 800
At a FortiSASE/SD-WAN site, this issue is reported: A WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. What is the most direct technical change to address the stated requirement?
- Troubleshoot BGP neighbor establishment and route advertisement over the SPA overlay
- Compare route prefix length and actual routing preference for the specific destination before changing SD-WAN rules
- Correct the upstream gateway next hop and verify reachability from that member
- Correct the member gateway and dependent routing configuration to match the currently assigned underlay
Explanation
Correct Answer
D:Correct the member gateway and dependent routing configuration to match the currently assigned underlay. A usable member requires a valid layer-3 next hop, not just a physically active interface. The acceptance check should show: Internet test flows use a reachable next hop and health probes recover.
Incorrect Answers
A:Troubleshoot BGP neighbor establishment and route advertisement over the SPA overlay. It addresses remote users can reach an SASE security PoP, but the FortiGate SD-WAN hub never learns the private prefix it should send toward that PoP. In the reported environment, the missing behavior instead relates to a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. The relevant choice is correct the member gateway and dependent routing configuration to match the currently assigned underlay.
B:Compare route prefix length and actual routing preference for the specific destination before changing SD-WAN rules. It could be appropriate when an SD-WAN hub learns a private route over BGP but the branch still uses a competing less-specific static path for one destination. However, that does not resolve the stated condition: a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. A more direct answer is correct the member gateway and dependent routing configuration to match the currently assigned underlay.
C:Correct the upstream gateway next hop and verify reachability from that member. That is a useful action for a different circumstance: a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member. The present case is constrained by a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router; the targeted response is correct the member gateway and dependent routing configuration to match the currently assigned underlay.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests