Question 200
For a change review, the team proposes to confirm FortiClient or SWG traffic steering toward the designated FortiSASE security PoP because: A security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally. Which explanation connects the change to the underlying behavior?
- Cloud PoPs apply policy on the user path, independent of the user's physical branch location
- Individual accountability and scoped permissions improve operational security and auditability
- The PoP is where the cloud-delivered access policy evaluates the relevant traffic flow
- Service routing and jurisdictional obligations are separate from basic tunnel connectivity
Explanation
Correct Answer
C:The PoP is where the cloud-delivered access policy evaluates the relevant traffic flow. This is why the proposed repair addresses the reported behavior; confirm by checking: The user's test flow appears in FortiSASE policy and traffic logs for the expected PoP.
Incorrect Answers
A:Cloud PoPs apply policy on the user path, independent of the user's physical branch location. It addresses a large retailer wants to prove that security policy enforcement for mobile employees is cloud-based rather than tied to their nearest on-premises office firewall. In the reported environment, the missing behavior instead relates to a security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally. The relevant choice is the PoP is where the cloud-delivered access policy evaluates the relevant traffic flow.
B:Individual accountability and scoped permissions improve operational security and auditability. The outcome for that step belongs to one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account. Here the decisive requirement concerns a security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally, so the PoP is where the cloud-delivered access policy evaluates the relevant traffic flow is the better fit.
D:Service routing and jurisdictional obligations are separate from basic tunnel connectivity. It could be appropriate when an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision. However, that does not resolve the stated condition: a security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally. A more direct answer is the PoP is where the cloud-delivered access policy evaluates the relevant traffic flow.
Question 201
The team is troubleshooting the following Fortinet 7.6 deployment: A smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences. Which specific corrective action should be prioritized?
- Use the SD-WAN zone object in the firewall policy instead of attempting to target the individual SD-WAN member
- Assign the new member to that policy's intended zone when the same treatment is appropriate
- Add the correct physical interface as an SD-WAN member and assign it to the intended zone
- Group both SD-WAN members in a common WAN zone for use by the shared firewall policy
Explanation
Correct Answer
D:Group both SD-WAN members in a common WAN zone for use by the shared firewall policy. Zone grouping allows multiple eligible members to share a policy interface object. The acceptance check should show: Sessions over either provider hit the single intended allow policy and retain appropriate inspection.
Incorrect Answers
A:Use the SD-WAN zone object in the firewall policy instead of attempting to target the individual SD-WAN member. 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 smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences. The relevant choice is group both SD-WAN members in a common WAN zone for use by the shared firewall policy.
B:Assign the new member to that policy's intended zone when the same treatment is appropriate. That is a useful action for a different circumstance: a company adds a new 5G interface but its existing WAN firewall policy covers only a named SD-WAN zone containing the older links. 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 group both SD-WAN members in a common WAN zone for use by the shared firewall policy.
C: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 smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences. A more direct answer is group both SD-WAN members in a common WAN zone for use by the shared firewall policy.
Question 202
After the authorized change to switch to a quality-aware strategy with a matching SLA requirement for the application, which result actually demonstrates that this site's requirement is met? Initial issue: A VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor.
- Each test application selects the intended member while both remain authorized by the firewall
- Matching calls select a qualifying WAN during controlled primary-path degradation
- The SaaS service hits its own rule while generic traffic remains under the broad steering rule
- The selected path is the cheapest SLA-compliant member under the current measurements
Explanation
Correct Answer
B:Matching calls select a qualifying WAN during controlled primary-path degradation. This is stronger than a saved configuration because it tests the intended operational result. A link preference by itself does not dynamically guarantee application-level latency or loss quality.
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 VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. A more direct answer is matching calls select a qualifying WAN during controlled primary-path degradation.
C:The SaaS service hits its own rule while generic traffic remains under the broad steering rule. The outcome for that step belongs to a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. Here the decisive requirement concerns a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor, so matching calls select a qualifying WAN during controlled primary-path degradation is the better fit.
D:The selected path is the cheapest SLA-compliant member under the current measurements. That is a useful action for a different circumstance: two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access. The present case is constrained by a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor; the targeted response is matching calls select a qualifying WAN during controlled primary-path degradation.
Question 203
For a change review, the team proposes to verify the source-IP hash selection and choose a different supported balancing method if per-session spreading is required because: The network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. Which explanation connects the change to the underlying behavior?
- SD-WAN steering is independent of the permit policy and can choose links using service-specific matches
- The best-quality strategy compares eligible links by the selected measured quality factor
- Source-IP hashing intentionally associates the same source with a deterministic member selection
- Broad earlier matches can preempt narrower intended steering logic
Explanation
Correct Answer
C:Source-IP hashing intentionally associates the same source with a deterministic member selection. This is why the proposed repair addresses the reported behavior; confirm by checking: Under a session-based distribution rule, new connections can spread independently rather than strictly by source IP.
Incorrect Answers
A:SD-WAN steering is independent of the permit policy and can choose links using service-specific matches. The outcome for that step belongs to a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. Here the decisive requirement concerns the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit, so source-IP hashing intentionally associates the same source with a deterministic member selection is the better fit.
B:The best-quality strategy compares eligible links by the selected measured quality factor. 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 the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. The relevant choice is source-IP hashing intentionally associates the same source with a deterministic member selection.
D:Broad earlier matches can preempt narrower intended steering logic. 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: the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. A more direct answer is source-IP hashing intentionally associates the same source with a deterministic member selection.
Question 204
During implementation, the administrator observes: A branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. Which intervention targets the described fault rather than an adjacent workflow?
- Inspect the affected traffic's matched rule and egress details in SD-WAN/session logs
- Inspect the selected-member information in per-session and SD-WAN rule diagnostics
- Analyze SD-WAN health-check events alongside traffic and member-selection logs for the affected time
- Use SD-WAN traffic logs and member performance/usage views for the same time window
Explanation
Correct Answer
C:Analyze SD-WAN health-check events alongside traffic and member-selection logs for the affected time. Link-quality and steering events describe path changes that physical link state alone may not explain. The configuration alone must be followed by a functioning test: The recorded degradation and selected-member transition correspond to the voice complaint.
Incorrect Answers
A:Inspect the affected traffic's matched rule and egress details in SD-WAN/session logs. The outcome for that step belongs to a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. Here the decisive requirement concerns a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up, so analyze SD-WAN health-check events alongside traffic and member-selection logs for the affected time is the better fit.
B:Inspect the selected-member information in per-session and SD-WAN rule diagnostics. It addresses an SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow. In the reported environment, the missing behavior instead relates to a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. The relevant choice is analyze SD-WAN health-check events alongside traffic and member-selection logs for the affected time.
D:Use SD-WAN traffic logs and member performance/usage views for the same time window. It could be appropriate when a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. However, that does not resolve the stated condition: a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. A more direct answer is analyze SD-WAN health-check events alongside traffic and member-selection logs for the affected time.
Question 205
The team is troubleshooting the following Fortinet 7.6 deployment: A company chooses LDAP as an identity source, but FortiSASE cannot apply a group-based access policy despite successful basic user lookup. Which specific corrective action should be prioritized?
- Deploy and trust the FortiSASE inspection CA certificate on the affected clients according to the approved method
- Update the trusted SAML signing-certificate configuration to the active identity-provider certificate
- Provision the contractor using an agentless Internet proxy policy and omit unrelated private-access grants
- Validate LDAP group retrieval and policy group mapping in addition to directory connectivity
Explanation
Correct Answer
D:Validate LDAP group retrieval and policy group mapping in addition to directory connectivity. Group-based authorization requires that the relevant identity-group attributes are available to the SASE policy. The acceptance check should show: The user is placed in the expected group and matches its targeted allow policy.
Incorrect Answers
A:Deploy and trust the FortiSASE inspection CA certificate on the affected clients according to the approved method. That is a useful action for a different circumstance: users report browser certificate warnings immediately after enabling deep inspection for an agentless secure web gateway. The present case is constrained by a company chooses LDAP as an identity source, but FortiSASE cannot apply a group-based access policy despite successful basic user lookup; the targeted response is validate LDAP group retrieval and policy group mapping in addition to directory connectivity.
B:Update the trusted SAML signing-certificate configuration to the active identity-provider certificate. It could be appropriate when a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. However, that does not resolve the stated condition: a company chooses LDAP as an identity source, but FortiSASE cannot apply a group-based access policy despite successful basic user lookup. A more direct answer is validate LDAP group retrieval and policy group mapping in addition to directory connectivity.
C:Provision the contractor using an agentless Internet proxy policy and omit unrelated private-access grants. It addresses a temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel. In the reported environment, the missing behavior instead relates to a company chooses LDAP as an identity source, but FortiSASE cannot apply a group-based access policy despite successful basic user lookup. The relevant choice is validate LDAP group retrieval and policy group mapping in addition to directory connectivity.
Question 206
Given this incident — An existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change. — the administrator plans to update the affected route and firewall address references for the new private prefix. Which technical principle justifies it?
- SD-WAN selection and possible session reevaluation can differ for established and newly created flows
- Forwarding to a changed destination requires matching route and permission objects regardless of tunnel state
- SD-WAN steering acts within the set of paths that routing can actually resolve
- A change of egress public IP can affect remote-session continuity even when a new path is reachable
Explanation
Correct Answer
B:Forwarding to a changed destination requires matching route and permission objects regardless of tunnel state. It directly explains the need to update the affected route and firewall address references for the new private prefix. The narrow validation is: Traffic to the new prefix follows the overlay and matches the intended allow rule.
Incorrect Answers
A:SD-WAN selection and possible session reevaluation can differ for established and newly created flows. That is a useful action for a different circumstance: a provider outage removes a member's usable path, yet operators continue testing sessions that were established before the outage. The present case is constrained by an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change; the targeted response is forwarding to a changed destination requires matching route and permission objects regardless of tunnel state.
C:SD-WAN steering acts within the set of paths that routing can actually resolve. It could be appropriate when a FortiGate has a manual SD-WAN rule preferring WAN2, but a route lookup for the destination has no usable next hop. However, that does not resolve the stated condition: an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change. A more direct answer is forwarding to a changed destination requires matching route and permission objects regardless of tunnel state.
D:A change of egress public IP can affect remote-session continuity even when a new path is reachable. The outcome for that step belongs to a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. Here the decisive requirement concerns an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change, so forwarding to a changed destination requires matching route and permission objects regardless of tunnel state is the better fit.
Question 207
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? After moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules.
- Branch users reach the hub-hosted application through IPsec while ordinary Internet access uses the local ISP
- Normal traffic uses broadband, but simulated broadband failure makes new eligible flows use LTE
- The policy matches sessions sent through either eligible member of its designated zone
- An allowed session uses an SD-WAN member while the relevant content/security event is logged by its profile
Explanation
Correct Answer
C:The policy matches sessions sent through either eligible member of its designated zone. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:Branch users reach the hub-hosted application through IPsec while ordinary Internet access uses the local ISP. 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: after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules. A more direct answer is the policy matches sessions sent through either eligible member of its designated zone.
B:Normal traffic uses broadband, but simulated broadband failure makes new eligible flows use LTE. It addresses a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered. In the reported environment, the missing behavior instead relates to after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules. The relevant choice is the policy matches sessions sent through either eligible member of its designated zone.
D:An allowed session uses an SD-WAN member while the relevant content/security event is logged by its profile. 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 after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules, so the policy matches sessions sent through either eligible member of its designated zone is the better fit.
Question 208
At a FortiSASE/SD-WAN site, this issue is reported: A configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. What is the most direct technical change to address the stated requirement?
- Use the appropriate Internet Service Database selector within the SD-WAN rule where supported
- Switch to a quality-aware strategy with a matching SLA requirement for the application
- Inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs
- Move or refine the billing rule so the specific matching policy is considered before the broad catchall
Explanation
Correct Answer
D:Move or refine the billing rule so the specific matching policy is considered before the broad catchall. Rule evaluation and match specificity determine which steering action applies to a session. The acceptance check should show: Billing traffic matches the intended narrow rule and the generic rule handles remaining sessions.
Incorrect Answers
A:Use the appropriate Internet Service Database selector within the SD-WAN rule where supported. It addresses an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. In the reported environment, the missing behavior instead relates to a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. The relevant choice is move or refine the billing rule so the specific matching policy is considered before the broad catchall.
B:Switch to a quality-aware strategy with a matching SLA requirement for the application. That is a useful action for a different circumstance: a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. The present case is constrained by a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member; the targeted response is move or refine the billing rule so the specific matching policy is considered before the broad catchall.
C:Inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs. It could be appropriate when no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. However, that does not resolve the stated condition: a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. A more direct answer is move or refine the billing rule so the specific matching policy is considered before the broad catchall.
Question 209
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? An administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list.
- The SaaS service hits its own rule while generic traffic remains under the broad steering rule
- Conference sessions match the dedicated rule while unrelated services do not
- Matching SaaS sessions follow the desired member even as their destination IPs change within the service classification
- Emergency flows use the intended LTE member without rerouting unrelated Web traffic
Explanation
Correct Answer
C:Matching SaaS sessions follow the desired member even as their destination IPs change within the service classification. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:The SaaS service hits its own rule while generic traffic remains under the broad steering rule. The outcome for that step belongs to a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. 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 matching SaaS sessions follow the desired member even as their destination IPs change within the service classification is the better fit.
B:Conference sessions match the dedicated rule while unrelated services do not. 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 an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. The relevant choice is matching SaaS sessions follow the desired member even as their destination IPs change within the service classification.
D:Emergency flows use the intended LTE member without rerouting unrelated Web traffic. It could be appropriate when a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy. 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 matching SaaS sessions follow the desired member even as their destination IPs change within the service classification.
Question 210
The team plans to correct the user/group targeting of the intended endpoint profile and synchronize membership for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile.
- Changing a FortiGate WAN gateway does not influence FortiSASE endpoint-profile assignment
- An accept action alone does not imply all possible security profiles are enabled
- Treating a certificate-only exemption as equivalent to full content inspection is unsafe
- A global profile edit may broaden restrictions beyond the intended population
Explanation
Correct Answer
A:Changing a FortiGate WAN gateway does not influence FortiSASE endpoint-profile assignment. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:An accept action alone does not imply all possible security profiles are enabled. 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 a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile. The relevant choice is changing a FortiGate WAN gateway does not influence FortiSASE endpoint-profile assignment.
C:Treating a certificate-only exemption as equivalent to full content inspection is unsafe. The outcome for that step belongs to a FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules. Here the decisive requirement concerns a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile, so changing a FortiGate WAN gateway does not influence FortiSASE endpoint-profile assignment is the better fit.
D:A global profile edit may broaden restrictions beyond the intended population. That is a useful action for a different circumstance: a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. The present case is constrained by a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile; the targeted response is changing a FortiGate WAN gateway does not influence FortiSASE endpoint-profile assignment.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests