Question 780
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences.
- An overly broad default route must not hide the more-specific private overlay route
- Choosing plain manual priority does not independently enforce the quality targets
- A rule with the best quality strategy cannot repair the absence of any resolvable route
- Creating separate zones is unnecessary unless policy treatment must differ
Explanation
Correct Answer
D:Creating separate zones is unnecessary unless policy treatment must differ. The planned change can still miss the requirement if this condition is left unresolved. Zone grouping allows multiple eligible members to share a policy interface object.
Incorrect Answers
A:An overly broad default route must not hide the more-specific private overlay route. It addresses a branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay. In the reported environment, the missing behavior instead relates to a smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences. The relevant choice is creating separate zones is unnecessary unless policy treatment must differ.
B:Choosing plain manual priority does not independently enforce the quality targets. 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: a smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences. A more direct answer is creating separate zones is unnecessary unless policy treatment must differ.
C:A rule with the best quality strategy cannot repair the absence of any resolvable route. That is a useful action for a different circumstance: a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations. The present case is constrained by a smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences; the targeted response is creating separate zones is unnecessary unless policy treatment must differ.
Question 781
A proposed repair is to inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs. Why should that repair work in this particular situation? Context: No custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member.
- Internet-service identification is designed for recognized services whose destinations may change
- SD-WAN can distribute eligible session load across members according to its balancing method
- Application-aware matching can distinguish a known service from unrelated flows on shared infrastructure
- The implicit rule supplies default member selection when custom rules do not match
Explanation
Correct Answer
D:The implicit rule supplies default member selection when custom rules do not match. It directly explains the need to inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs. The narrow validation is: A test session with no explicit rule match follows the implicit rule's configured algorithm.
Incorrect Answers
A:Internet-service identification is designed for recognized services whose destinations may change. It could be appropriate when an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. However, that does not resolve the stated condition: no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. A more direct answer is the implicit rule supplies default member selection when custom rules do not match.
B:SD-WAN can distribute eligible session load across members according to its balancing method. That is a useful action for a different circumstance: a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. The present case is constrained by no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member; the targeted response is the implicit rule supplies default member selection when custom rules do not match.
C:Application-aware matching can distinguish a known service from unrelated flows on shared infrastructure. It addresses a security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider. In the reported environment, the missing behavior instead relates to no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. The relevant choice is the implicit rule supplies default member selection when custom rules do not match.
Question 782
After the authorized change to use the supported application or Internet-service matching criteria for the intended conference traffic, which result actually demonstrates that this site's requirement is met? Initial issue: A security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider.
- Each test application selects the intended member while both remain authorized by the firewall
- A test session with no explicit rule match follows the implicit rule's configured algorithm
- New payroll sessions choose the configured preferred eligible member
- Conference sessions match the dedicated rule while unrelated services do not
Explanation
Correct Answer
D:Conference sessions match the dedicated rule while unrelated services do not. This is stronger than a saved configuration because it tests the intended operational result. Application-aware matching can distinguish a known service from unrelated flows on shared infrastructure.
Incorrect Answers
A:Each test application selects the intended member while both remain authorized by the firewall. It could be appropriate when a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. However, that does not resolve the stated condition: a security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider. A more direct answer is conference sessions match the dedicated rule while unrelated services do not.
B:A test session with no explicit rule match follows the implicit rule's configured algorithm. That is a useful action for a different circumstance: no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. The present case is constrained by a security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider; the targeted response is conference sessions match the dedicated rule while unrelated services do not.
C:New payroll sessions choose the configured preferred eligible member. It addresses a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services. In the reported environment, the missing behavior instead relates to a security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider. The relevant choice is conference sessions match the dedicated rule while unrelated services do not.
Question 783
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? FortiGate's traffic policy permits VoIP, but its SD-WAN rule is scoped to the wrong source network after a subnet migration.
- Under a session-based distribution rule, new connections can spread independently rather than strictly by source IP
- The SaaS service hits its own rule while generic traffic remains under the broad steering rule
- Matching SaaS sessions follow the desired member even as their destination IPs change within the service classification
- New migrated phones match the voice-steering rule rather than the implicit fallback
Explanation
Correct Answer
D:New migrated phones match the voice-steering rule rather than the implicit fallback. This is stronger than a saved configuration because it tests the intended operational result. The rule only affects sessions satisfying its configured match conditions.
Incorrect Answers
A:Under a session-based distribution rule, new connections can spread independently rather than strictly by source IP. 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 fortiGate's traffic policy permits VoIP, but its SD-WAN rule is scoped to the wrong source network after a subnet migration; the targeted response is new migrated phones match the voice-steering rule rather than the implicit fallback.
B:The SaaS service hits its own rule while generic traffic remains under the broad steering rule. It addresses a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. In the reported environment, the missing behavior instead relates to fortiGate's traffic policy permits VoIP, but its SD-WAN rule is scoped to the wrong source network after a subnet migration. The relevant choice is new migrated phones match the voice-steering rule rather than the implicit fallback.
C:Matching SaaS sessions follow the desired member even as their destination IPs change within the service classification. It could be appropriate when an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. However, that does not resolve the stated condition: fortiGate's traffic policy permits VoIP, but its SD-WAN rule is scoped to the wrong source network after a subnet migration. A more direct answer is new migrated phones match the voice-steering rule rather than the implicit fallback.
Question 784
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered.
- Branch users reach the hub-hosted application through IPsec while ordinary Internet access uses the local ISP
- Internet testing exits locally and private testing resolves through the intended VPN overlay
- Traffic transitions to a qualifying link when the poor circuit crosses its configured SLA bounds
- Normal traffic uses broadband, but simulated broadband failure makes new eligible flows use LTE
Explanation
Correct Answer
D:Normal traffic uses broadband, but simulated broadband failure makes new eligible flows use LTE. This is stronger than a saved configuration because it tests the intended operational result. Member preference combined with failure detection limits routine use of a metered backup path.
Incorrect Answers
A:Branch users reach the hub-hosted application through IPsec while ordinary Internet access uses the local ISP. That is a useful action for a different circumstance: a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. The present case is constrained by a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered; the targeted response is normal traffic uses broadband, but simulated broadband failure makes new eligible flows use LTE.
B:Internet testing exits locally and private testing resolves through the intended VPN overlay. It could be appropriate when a branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay. However, that does not resolve the stated condition: a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered. A more direct answer is normal traffic uses broadband, but simulated broadband failure makes new eligible flows use LTE.
C:Traffic transitions to a qualifying link when the poor circuit crosses its configured SLA bounds. It addresses a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit. In the reported environment, the missing behavior instead relates to a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered. The relevant choice is normal traffic uses broadband, but simulated broadband failure makes new eligible flows use LTE.
Question 785
The team is troubleshooting the following Fortinet 7.6 deployment: An agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain. Which specific corrective action should be prioritized?
- Create or assign a narrowly targeted security profile group to the intended user-group policy
- Attach the required security profile group to the matching Accept policy
- Review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust
- Attach an appropriate web-filter category policy to the matching FortiSASE security profile group
Explanation
Correct Answer
C:Review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust. SWG SSO authentication can depend on deep inspection, and bypass exceptions can interrupt that workflow. The configuration alone must be followed by a functioning test: An SSO session completes while intended web inspection policy remains enforced.
Incorrect Answers
A:Create or assign a narrowly targeted security profile group to the intended user-group policy. 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: an agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain. A more direct answer is review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust.
B:Attach the required security profile group to the matching Accept policy. It addresses 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. 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 review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust.
D:Attach an appropriate web-filter category policy to the matching FortiSASE security profile group. The outcome for that step belongs to employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone. Here the decisive requirement concerns an agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain, so review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust is the better fit.
Question 786
For a change review, the team proposes to add a narrowly scoped firewall-policy permit for the legitimate SASE source and destination as required because: A private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet. Which explanation connects the change to the underlying behavior?
- Private access requires separate firewall authorization in addition to tunnel and route reachability
- The overlay creates protected paths between remote SASE PoPs and hosted private networks
- BGP exchanges reachable private prefixes required by the PoP-to-hub design
- The SASE security PoP can act as a spoke to a FortiGate hub for protected private networks
Explanation
Correct Answer
A:Private access requires separate firewall authorization in addition to tunnel and route reachability. This is why the proposed repair addresses the reported behavior; confirm by checking: The authorized source reaches only its permitted private application and is logged accordingly.
Incorrect Answers
B:The overlay creates protected paths between remote SASE PoPs and hosted private networks. The outcome for that step belongs to 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. 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 private access requires separate firewall authorization in addition to tunnel and route reachability is the better fit.
C:BGP exchanges reachable private prefixes required by the PoP-to-hub design. That is a useful action for a different circumstance: 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. 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 private access requires separate firewall authorization in addition to tunnel and route reachability.
D: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 a private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet. The relevant choice is private access requires separate firewall authorization in addition to tunnel and route reachability.
Question 787
For the stated scenario, what is the most important remaining blind spot after the proposed correction? An internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window.
- Deep-inspection exemptions can interfere with SWG SSO flows under this configuration
- A traffic log showing an allowed website request is not proof of who edited the policy
- One global profile cannot safely encode mutually different group-specific connection permissions
- The tenant's saved configuration alone does not prove every endpoint has received it
Explanation
Correct Answer
B:A traffic log showing an allowed website request is not proof of who edited the policy. The planned change can still miss the requirement if this condition is left unresolved. Change auditing associates security configuration actions with users and times.
Incorrect Answers
A: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: an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. A more direct answer is a traffic log showing an allowed website request is not proof of who edited the policy.
C:One global profile cannot safely encode mutually different group-specific connection permissions. That is a useful action for a different circumstance: one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. The present case is constrained by an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window; the targeted response is a traffic log showing an allowed website request is not proof of who edited the policy.
D:The tenant's saved configuration alone does not prove every endpoint has received it. The outcome for that step belongs to a remote endpoint has FortiClient installed, but the connection profile is stale after the administrator changes the tenant settings. Here the decisive requirement concerns an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window, so a traffic log showing an allowed website request is not proof of who edited the policy is the better fit.
Question 788
After the authorized change to treat member and zone configuration as persistent objects and remove them separately only if the design requires it, which result actually demonstrates that this site's requirement is met? Initial issue: A network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions.
- A single zone policy covers sessions egressing via any eligible member assigned to that zone
- Internet flows use the correct ISP zone and inspection profile without touching private-overlay policies
- A restored member carries test packets and is visible in the rule's active selection
- The members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces
Explanation
Correct Answer
D:The members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces. This is stronger than a saved configuration because it tests the intended operational result. Steering rules select traffic paths; they do not own the underlying interface-to-zone configuration lifecycle.
Incorrect Answers
A:A single zone policy covers sessions egressing via any eligible member assigned to that zone. It addresses a FortiGate using zone-based policies shows the original interface port but the administrator cannot select it as a distinct policy destination. In the reported environment, the missing behavior instead relates to a network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions. The relevant choice is the members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces.
B:Internet flows use the correct ISP zone and inspection profile without touching private-overlay policies. 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 network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions. A more direct answer is the members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces.
C:A restored member carries test packets and is visible in the rule's active selection. That is a useful action for a different circumstance: the team sees a route via an SD-WAN zone but no actual WAN member is healthy under it. The present case is constrained by a network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions; the targeted response is the members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces.
Question 789
A proposed repair is to review live probe status and allow new samples to establish post-maintenance link quality. Why should that repair work in this particular situation? Context: A branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance.
- Health dashboards display measured probe results, not a static certification that a line has been repaired
- Per-member SLA measurements make alternate-link selection observable and qualified
- With equal costs among qualifying links, interface preference determines the selected link
- SLA-driven steering can respond to packet loss, delay or probe failure without physical link-down events
Explanation
Correct Answer
A:Health dashboards display measured probe results, not a static certification that a line has been repaired. This is why the proposed repair addresses the reported behavior; confirm by checking: Fresh monitoring intervals show quality consistent with the restored circuit and the SLA target.
Incorrect Answers
B:Per-member SLA measurements make alternate-link selection observable and qualified. The outcome for that step belongs to the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry. Here the decisive requirement concerns a branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance, so health dashboards display measured probe results, not a static certification that a line has been repaired is the better fit.
C:With equal costs among qualifying links, interface preference determines the selected link. It addresses an operations team sees two SLA-compliant WAN links assigned identical cost values but asks why only the first was elected. In the reported environment, the missing behavior instead relates to a branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance. The relevant choice is health dashboards display measured probe results, not a static certification that a line has been repaired.
D:SLA-driven steering can respond to packet loss, delay or probe failure without physical link-down events. That is a useful action for a different circumstance: a branch reports all SD-WAN sessions failed over after a WAN hiccup, but an engineer only checked the link LED and concluded no impairment. The present case is constrained by a branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance; the targeted response is health dashboards display measured probe results, not a static certification that a line has been repaired.
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.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests