Question 20
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate.
- A successful ping to the hub interface does not establish end-to-end private-network access
- Shared administrator credentials obscure individual change attribution even when policies are technically valid
- Treating IPsec phase-two success as complete reachability overlooks missing routing
- Disabling all certificate verification would undermine the identity-trust boundary instead of repairing it
Explanation
Correct Answer
D:Disabling all certificate verification would undermine the identity-trust boundary instead of repairing it. The planned change can still miss the requirement if this condition is left unresolved. A stale signature verification key prevents valid assertions from being accepted even when users know their passwords.
Incorrect Answers
A:A successful ping to the hub interface does not establish end-to-end private-network access. It addresses a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. 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 disabling all certificate verification would undermine the identity-trust boundary instead of repairing it.
B:Shared administrator credentials obscure individual change attribution even when policies are technically valid. It could be appropriate when one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account. However, that does not resolve the stated condition: a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. A more direct answer is disabling all certificate verification would undermine the identity-trust boundary instead of repairing it.
C:Treating IPsec phase-two success as complete reachability overlooks missing routing. That is a useful action for a different circumstance: the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. 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 disabling all certificate verification would undermine the identity-trust boundary instead of repairing it.
Question 21
Given this incident — A company wants to prevent simultaneous failure of two Internet circuits from the same carrier. — the administrator plans to choose physically and provider-diverse WAN underlays rather than merely naming two SD-WAN members. Which technical principle justifies it?
- Path selection and security inspection are separate controls in FortiOS
- SD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes
- SD-WAN link selection can respond to independent transport failures but cannot eliminate a shared provider dependency
- SD-WAN can distinguish overlay and underlay transport and steer traffic based on intended destination and policy
Explanation
Correct Answer
C:SD-WAN link selection can respond to independent transport failures but cannot eliminate a shared provider dependency. This is why the proposed repair addresses the reported behavior; confirm by checking: A controlled failure of one provider leaves a separately sourced member reachable.
Incorrect Answers
A:Path selection and security inspection are separate controls in FortiOS. The outcome for that step belongs to a branch was built with two SD-WAN members, but a team assumes this alone automatically adds application inspection to client sessions. Here the decisive requirement concerns a company wants to prevent simultaneous failure of two Internet circuits from the same carrier, so sD-WAN link selection can respond to independent transport failures but cannot eliminate a shared provider dependency is the better fit.
B:SD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes. It addresses an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. In the reported environment, the missing behavior instead relates to a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. The relevant choice is sD-WAN link selection can respond to independent transport failures but cannot eliminate a shared provider dependency.
D:SD-WAN can distinguish overlay and underlay transport and steer traffic based on intended destination and policy. It could be appropriate when a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. However, that does not resolve the stated condition: a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. A more direct answer is sD-WAN link selection can respond to independent transport failures but cannot eliminate a shared provider dependency.
Question 22
After the authorized change to review the exemption and narrow it to justified destinations before relying on content-based protection, which result actually demonstrates that this site's requirement is met? Initial issue: A FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules.
- Malicious test content is detected or blocked according to policy without blocking the entire legitimate site category
- A controlled HTTPS test produces appropriate file or malware inspection events without certificate errors
- Relevant test HTTPS downloads receive the intended malware or DLP inspection
- A representative synthetic-sensitive-data upload is restricted and logged by DLP
Explanation
Correct Answer
C:Relevant test HTTPS downloads receive the intended malware or DLP inspection. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:Malicious test content is detected or blocked according to policy without blocking the entire legitimate site category. It addresses a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category. In the reported environment, the missing behavior instead relates to a FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules. The relevant choice is relevant test HTTPS downloads receive the intended malware or DLP inspection.
B:A controlled HTTPS test produces appropriate file or malware inspection events without certificate errors. It could be appropriate when a FortiSASE web policy has a functioning antivirus profile on unencrypted downloads, but it detects only HTTPS domains and cannot inspect malicious downloads inside encrypted sessions. However, that does not resolve the stated condition: a FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules. A more direct answer is relevant test HTTPS downloads receive the intended malware or DLP inspection.
D:A representative synthetic-sensitive-data upload is restricted and logged by DLP. The outcome for that step belongs to a company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications. Here the decisive requirement concerns a FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules, so relevant test HTTPS downloads receive the intended malware or DLP inspection is the better fit.
Question 23
Given this incident — 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. — the administrator plans to pilot FortiSASE remote-client access through security points of presence with the required web security policy. Which technical principle justifies it?
- Service routing and jurisdictional obligations are separate from basic tunnel connectivity
- Available subscription entitlements constrain which managed SASE services can be deployed
- Cloud PoPs apply policy on the user path, independent of the user's physical branch location
- The PoP is where the cloud-delivered access policy evaluates the relevant traffic flow
Explanation
Correct Answer
C:Cloud PoPs apply policy on the user path, independent of the user's physical branch location. This is why the proposed repair addresses the reported behavior; confirm by checking: A remote employee receives the same intended web-filter decision from two distinct locations.
Incorrect Answers
A:Service routing and jurisdictional obligations are separate from basic tunnel connectivity. The outcome for that step belongs to an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision. Here the decisive requirement concerns 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, so cloud PoPs apply policy on the user path, independent of the user's physical branch location is the better fit.
B:Available subscription entitlements constrain which managed SASE services can be deployed. It could be appropriate when a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. However, that does not resolve the stated condition: 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. A more direct answer is cloud PoPs apply policy on the user path, independent of the user's physical branch location.
D:The PoP is where the cloud-delivered access policy evaluates the relevant traffic flow. It addresses a security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally. In the reported environment, the missing behavior instead relates 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. The relevant choice is cloud PoPs apply policy on the user path, independent of the user's physical branch location.
Question 24
After the authorized change to update connector peer information and ensure the new hub endpoint is reachable, which result actually demonstrates that this site's requirement is met? Initial issue: After a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer.
- The tunnel negotiates to the intended new hub endpoint and routes recover
- Both sides learn the intended private route and a permitted remote session reaches the server
- Approved TCP and UDP application tests succeed through the overlay without public exposure
- The private service is accessible to authorized remote users solely via the intended secure connector path
Explanation
Correct Answer
A:The tunnel negotiates to the intended new hub endpoint and routes recover. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:Both sides learn the intended private route and a permitted remote session reaches the server. It addresses the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. In the reported environment, the missing behavior instead relates to after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer. The relevant choice is the tunnel negotiates to the intended new hub endpoint and routes recover.
C:Approved TCP and UDP application tests succeed through the overlay without public exposure. The outcome for that step belongs to an organization needs private TCP and UDP access to multiple office services without publishing public listener ports. Here the decisive requirement concerns after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer, so the tunnel negotiates to the intended new hub endpoint and routes recover is the better fit.
D:The private service is accessible to authorized remote users solely via the intended secure connector path. That is a useful action for a different circumstance: 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. The present case is constrained by after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer; the targeted response is the tunnel negotiates to the intended new hub endpoint and routes recover.
Question 25
For this Fortinet incident, which observation should the engineer collect first to validate the suspected 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.
- Check that emergency packets match the explicit SD-WAN rule and not only an Internet allow rule
- Compare member choices for multiple connections from one client and several different clients
- Inspect per-member jitter and the rule's quality metric/selection status
- Inspect ordered rule matching and the actual matched rule for a billing test flow
Explanation
Correct Answer
A:Check that emergency packets match the explicit SD-WAN rule and not only an Internet allow rule. The observed evidence guides the targeted repair: Add an explicit traffic-matching SD-WAN rule for the emergency application's destination and preferred LTE member.
Incorrect Answers
B:Compare member choices for multiple connections from one client and several different clients. That is a useful action for a different circumstance: the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. 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 check that emergency packets match the explicit SD-WAN rule and not only an Internet allow rule.
C:Inspect per-member jitter and the rule's quality metric/selection status. It addresses video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price. 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 check that emergency packets match the explicit SD-WAN rule and not only an Internet allow rule.
D:Inspect ordered rule matching and the actual matched rule for a billing test flow. The outcome for that step belongs to a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. Here the decisive requirement concerns a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy, so check that emergency packets match the explicit SD-WAN rule and not only an Internet allow rule is the better fit.
Question 26
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A security analyst sees a compliant laptop marked as noncompliant even after remediation of its local antivirus settings.
- A web-filter-only assumption can miss DNS-based activity that never generates a standard web request
- Disabling the compliance rule for the entire tenant would conceal the stale-state problem
- Keeping a blanket deep-inspection exemption for SSO traffic can prevent the designed authentication path
- Disabling content inspection for performance without reviewing IPS requirements removes this detection path
Explanation
Correct Answer
B:Disabling the compliance rule for the entire tenant would conceal the stale-state problem. The planned change can still miss the requirement if this condition is left unresolved. Posture enforcement decisions depend on reported endpoint state; stale or mismapped data can cause incorrect classification.
Incorrect Answers
A:A web-filter-only assumption can miss DNS-based activity that never generates a standard web request. 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: a security analyst sees a compliant laptop marked as noncompliant even after remediation of its local antivirus settings. A more direct answer is disabling the compliance rule for the entire tenant would conceal the stale-state problem.
C:Keeping a blanket deep-inspection exemption for SSO traffic can prevent the designed authentication path. That is a useful action for a different circumstance: an agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain. The present case is constrained by a security analyst sees a compliant laptop marked as noncompliant even after remediation of its local antivirus settings; the targeted response is disabling the compliance rule for the entire tenant would conceal the stale-state problem.
D:Disabling content inspection for performance without reviewing IPS requirements removes this detection path. The outcome for that step belongs to a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. Here the decisive requirement concerns a security analyst sees a compliant laptop marked as noncompliant even after remediation of its local antivirus settings, so disabling the compliance rule for the entire tenant would conceal the stale-state problem is the better fit.
Question 27
A proposed repair is to keep secure Internet access and secure private access forwarding choices distinct in the policy and route design. Why should that repair work in this particular situation? Context: FortiSASE remote clients reach SASE points of presence, yet office users need direct access to the Internet without unnecessarily hairpinning via a corporate hub.
- The SASE security PoP can act as a spoke to a FortiGate hub for protected private networks
- Private access requires separate firewall authorization in addition to tunnel and route reachability
- The SASE architecture supports cloud Internet inspection and specific private application connectivity through connectors
- IPsec establishes transport, but routing must advertise and resolve the private destination networks
Explanation
Correct Answer
C:The SASE architecture supports cloud Internet inspection and specific private application connectivity through connectors. This is why the proposed repair addresses the reported behavior; confirm by checking: Public traffic follows the intended SASE Internet path; private traffic enters the connector overlay.
Incorrect Answers
A:The SASE security PoP can act as a spoke to a FortiGate hub for protected private networks. It addresses a customer wants remote FortiClient users to reach a database behind an existing FortiGate SD-WAN hub rather than exposing the database publicly. In the reported environment, the missing behavior instead relates to fortiSASE remote clients reach SASE points of presence, yet office users need direct access to the Internet without unnecessarily hairpinning via a corporate hub. The relevant choice is the SASE architecture supports cloud Internet inspection and specific private application connectivity through connectors.
B:Private access requires separate firewall authorization in addition to tunnel and route reachability. 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: fortiSASE remote clients reach SASE points of presence, yet office users need direct access to the Internet without unnecessarily hairpinning via a corporate hub. A more direct answer is the SASE architecture supports cloud Internet inspection and specific private application connectivity through connectors.
D:IPsec establishes transport, but routing must advertise and resolve the private destination networks. The outcome for that step belongs to the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. Here the decisive requirement concerns fortiSASE remote clients reach SASE points of presence, yet office users need direct access to the Internet without unnecessarily hairpinning via a corporate hub, so the SASE architecture supports cloud Internet inspection and specific private application connectivity through connectors is the better fit.
Question 28
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A sanctioned collaboration app is allowed, but management wants to prevent an unapproved file transfer action within that SaaS application.
- Inspect both user-group policies and the profile groups attached to each
- Inspect DNS-filter profile configuration and the matching DNS security log
- Inspect the DLP profile match rules and whether the application traffic is decryptable where required
- Inspect inline-CASB application/action criteria and relevant security-event logs
Explanation
Correct Answer
D:Inspect inline-CASB application/action criteria and relevant security-event logs. This check isolates the relevant control before the change. Granular SaaS application controls distinguish an operation within an app from simply permitting the app's domain.
Incorrect Answers
A:Inspect both user-group policies and the profile groups attached to each. It addresses a remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access. In the reported environment, the missing behavior instead relates to a sanctioned collaboration app is allowed, but management wants to prevent an unapproved file transfer action within that SaaS application. The relevant choice is inspect inline-CASB application/action criteria and relevant security-event logs.
B:Inspect DNS-filter profile configuration and the matching DNS security log. 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: a sanctioned collaboration app is allowed, but management wants to prevent an unapproved file transfer action within that SaaS application. A more direct answer is inspect inline-CASB application/action criteria and relevant security-event logs.
C:Inspect the DLP profile match rules and whether the application traffic is decryptable where required. That is a useful action for a different circumstance: a company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications. The present case is constrained by a sanctioned collaboration app is allowed, but management wants to prevent an unapproved file transfer action within that SaaS application; the targeted response is inspect inline-CASB application/action criteria and relevant security-event logs.
Question 29
At a FortiSASE/SD-WAN site, this issue is reported: A company wants to prevent simultaneous failure of two Internet circuits from the same carrier. What is the most direct technical change to address the stated requirement?
- Install a valid default route that resolves through the intended SD-WAN zone or member design
- Use FortiGate SD-WAN health and member monitoring widgets after member and SLA configuration
- Define traffic-matching SD-WAN steering rules, with relevant quality targets and the required firewall permissions
- Choose physically and provider-diverse WAN underlays rather than merely naming two SD-WAN members
Explanation
Correct Answer
D:Choose physically and provider-diverse WAN underlays rather than merely naming two SD-WAN members. SD-WAN link selection can respond to independent transport failures but cannot eliminate a shared provider dependency. The acceptance check should show: A controlled failure of one provider leaves a separately sourced member reachable.
Incorrect Answers
A:Install a valid default route that resolves through the intended SD-WAN zone or member design. It addresses a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations. In the reported environment, the missing behavior instead relates to a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. The relevant choice is choose physically and provider-diverse WAN underlays rather than merely naming two SD-WAN members.
B:Use FortiGate SD-WAN health and member monitoring widgets after member and SLA configuration. That is a useful action for a different circumstance: a new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory. The present case is constrained by a company wants to prevent simultaneous failure of two Internet circuits from the same carrier; the targeted response is choose physically and provider-diverse WAN underlays rather than merely naming two SD-WAN members.
C:Define traffic-matching SD-WAN steering rules, with relevant quality targets and the required firewall permissions. It could be appropriate when an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. However, that does not resolve the stated condition: a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. A more direct answer is choose physically and provider-diverse WAN underlays rather than merely naming two SD-WAN members.
Question 30
During implementation, the administrator observes: An administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. Which intervention targets the described fault rather than an adjacent workflow?
- Use a steering policy with preferred primary member and health-based failover to LTE, rather than unrestricted equal sharing
- Build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate
- Use FortiGate SD-WAN health and member monitoring widgets after member and SLA configuration
- Define traffic-matching SD-WAN steering rules, with relevant quality targets and the required firewall permissions
Explanation
Correct Answer
D:Define traffic-matching SD-WAN steering rules, with relevant quality targets and the required firewall permissions. SD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes. The acceptance check should show: A simulated congested WAN changes eligible conferencing path selection while bulk traffic follows its own rule.
Incorrect Answers
A:Use a steering policy with preferred primary member and health-based failover to LTE, rather than unrestricted equal sharing. That is a useful action for a different circumstance: a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered. The present case is constrained by an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch; the targeted response is define traffic-matching SD-WAN steering rules, with relevant quality targets and the required firewall permissions.
B:Build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate. It addresses a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. In the reported environment, the missing behavior instead relates to an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. The relevant choice is define traffic-matching SD-WAN steering rules, with relevant quality targets and the required firewall permissions.
C:Use FortiGate SD-WAN health and member monitoring widgets after member and SLA configuration. It could be appropriate when a new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory. However, that does not resolve the stated condition: an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. A more direct answer is define traffic-matching SD-WAN steering rules, with relevant quality targets and the required firewall permissions.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests