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.
Question 31
The team plans to inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? No custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member.
- Deleting all custom rules does not disable the implicit fallback behavior
- A link SLA tweak cannot explain a route that already wins or loses on routing preference
- A static route table screenshot alone cannot establish past per-session forwarding
- Assuming every established TCP session seamlessly survives a path or SNAT address change is unsafe
Explanation
Correct Answer
A:Deleting all custom rules does not disable the implicit fallback behavior. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:A link SLA tweak cannot explain a route that already wins or loses on routing preference. The outcome for that step belongs to a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks. Here the decisive requirement concerns no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member, so deleting all custom rules does not disable the implicit fallback behavior is the better fit.
C:A static route table screenshot alone cannot establish past per-session forwarding. That is a useful action for a different circumstance: an SD-WAN operator wants to prove that a payment session left through the correct tunnel after an incident, rather than infer from routes alone. 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 deleting all custom rules does not disable the implicit fallback behavior.
D:Assuming every established TCP session seamlessly survives a path or SNAT address change is unsafe. It addresses a provider outage removes a member's usable path, yet operators continue testing sessions that were established before the outage. 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 deleting all custom rules does not disable the implicit fallback behavior.
Question 32
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? After a data-center maintenance event, a configured rule remains disabled because its minimum number of SLA-passing members is three but only two are healthy.
- A perfect application match still fails without valid forwarding reachability
- Simply rearranging interface preference does not satisfy an unmet numerical minimum
- Changing an SD-WAN member weight cannot overturn an explicit deny policy
- An established IPsec security association alone does not prove the necessary BGP routes exist
Explanation
Correct Answer
B:Simply rearranging interface preference does not satisfy an unmet numerical minimum. The planned change can still miss the requirement if this condition is left unresolved. The minimum SLA-meeting members constraint gates rule activation independently of individual link health.
Incorrect Answers
A:A perfect application match still fails without valid forwarding reachability. It could be appropriate when an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. However, that does not resolve the stated condition: after a data-center maintenance event, a configured rule remains disabled because its minimum number of SLA-passing members is three but only two are healthy. A more direct answer is simply rearranging interface preference does not satisfy an unmet numerical minimum.
C:Changing an SD-WAN member weight cannot overturn an explicit deny policy. The outcome for that step belongs to a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. Here the decisive requirement concerns after a data-center maintenance event, a configured rule remains disabled because its minimum number of SLA-passing members is three but only two are healthy, so simply rearranging interface preference does not satisfy an unmet numerical minimum is the better fit.
D:An established IPsec security association alone does not prove the necessary BGP routes exist. That is a useful action for a different circumstance: 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. The present case is constrained by after a data-center maintenance event, a configured rule remains disabled because its minimum number of SLA-passing members is three but only two are healthy; the targeted response is simply rearranging interface preference does not satisfy an unmet numerical minimum.
Question 33
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member.
- Sessions over either provider hit the single intended allow policy and retain appropriate inspection
- A controlled failure of the first tunnel leads private traffic through the second while preserving policy matching
- The members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces
- The ISP interface is listed as a member and selected by a matching SD-WAN rule
Explanation
Correct Answer
D:The ISP interface is listed as a member and selected by a matching SD-WAN rule. This is stronger than a saved configuration because it tests the intended operational result. Creating the zone alone does not enroll physical or tunnel interfaces as SD-WAN members.
Incorrect Answers
A:Sessions over either provider hit the single intended allow policy and retain appropriate inspection. It addresses a smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences. In the reported environment, the missing behavior instead relates to a FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member. The relevant choice is the ISP interface is listed as a member and selected by a matching SD-WAN rule.
B:A controlled failure of the first tunnel leads private traffic through the second while preserving policy matching. That is a useful action for a different circumstance: a branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy. The present case is constrained by a FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member; the targeted response is the ISP interface is listed as a member and selected by a matching SD-WAN rule.
C:The members remain documented, and any changed steering behavior is attributable to rule lookup rather than vanished interfaces. It could be appropriate when a network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions. However, that does not resolve the stated condition: a FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member. A more direct answer is the ISP interface is listed as a member and selected by a matching SD-WAN rule.
Question 34
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use.
- The monitor updates quality statistics as application sessions traverse the selected WAN
- The logged SLA failure aligns with the observed traffic path change
- The voice rule avoids the noncompliant path when another compliant member is available
- Changing measured quality produces a corresponding member-selection change for the voice rule
Explanation
Correct Answer
A:The monitor updates quality statistics as application sessions traverse the selected WAN. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:The logged SLA failure aligns with the observed traffic path change. 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 metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use; the targeted response is the monitor updates quality statistics as application sessions traverse the selected WAN.
C:The voice rule avoids the noncompliant path when another compliant member is available. It addresses an SD-WAN operator sees a link marked alive but the performance SLA map shows it misses the configured voice target. In the reported environment, the missing behavior instead relates to a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use. The relevant choice is the monitor updates quality statistics as application sessions traverse the selected WAN.
D:Changing measured quality produces a corresponding member-selection change for the voice rule. The outcome for that step belongs to an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit. Here the decisive requirement concerns a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use, so the monitor updates quality statistics as application sessions traverse the selected WAN is the better fit.
Question 35
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? 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.
- Merely increasing physical interface speed does not create application-aware path selection
- A dashboard cannot show meaningful SLA quality when no health-check target is configured
- An old dashboard screenshot cannot prove current performance after a carrier change
- Membership in the overlay zone would produce unintended policy coupling
Explanation
Correct Answer
D:Membership in the overlay zone would produce unintended policy coupling. The planned change can still miss the requirement if this condition is left unresolved. Independent zone grouping enables separate Internet and private-overlay security policy paths.
Incorrect Answers
A:Merely increasing physical interface speed does not create application-aware path selection. That is a useful action for a different circumstance: an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. The present case is constrained by 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; the targeted response is membership in the overlay zone would produce unintended policy coupling.
B:A dashboard cannot show meaningful SLA quality when no health-check target is configured. 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: 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. A more direct answer is membership in the overlay zone would produce unintended policy coupling.
C:An old dashboard screenshot cannot prove current performance after a carrier change. It addresses a branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance. In the reported environment, the missing behavior instead relates to a deployment requires public Internet from a third ISP, and the operator wants to manage it independently without applying the private overlay's IPS policy. The relevant choice is membership in the overlay zone would produce unintended policy coupling.
Question 36
For the stated scenario, what is the most important remaining blind spot after the proposed correction? An administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams.
- Instructing users to ignore all certificate warnings would hide genuine TLS risks
- A global profile edit may broaden restrictions beyond the intended population
- Cloning a profile without checking its assignment can cause undesired broad enforcement
- An SD-WAN jitter threshold does not classify phishing websites
Explanation
Correct Answer
C:Cloning a profile without checking its assignment can cause undesired broad enforcement. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Instructing users to ignore all certificate warnings would hide genuine TLS risks. It addresses a browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions. In the reported environment, the missing behavior instead relates to an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. The relevant choice is cloning a profile without checking its assignment can cause undesired broad enforcement.
B:A global profile edit may broaden restrictions beyond the intended population. 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 administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. A more direct answer is cloning a profile without checking its assignment can cause undesired broad enforcement.
D:An SD-WAN jitter threshold does not classify phishing websites. 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 administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams, so cloning a profile without checking its assignment can cause undesired broad enforcement is the better fit.
Question 37
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor.
- Inspect ordered rule matching and the actual matched rule for a billing test flow
- Inspect the implicit or explicit rule's balance algorithm and the member session counters
- Check the manual strategy setting alongside measured SLA health on each WAN
- Inspect the traffic's identified service/application and the rule's match criteria
Explanation
Correct Answer
C:Check the manual strategy setting alongside measured SLA health on each WAN. The observed evidence guides the targeted repair: Switch to a quality-aware strategy with a matching SLA requirement for the application.
Incorrect Answers
A:Inspect ordered rule matching and the actual matched rule for a billing test flow. It addresses a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. In the reported environment, the missing behavior instead relates to a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. The relevant choice is check the manual strategy setting alongside measured SLA health on each WAN.
B:Inspect the implicit or explicit rule's balance algorithm and the member session counters. The outcome for that step belongs to a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. 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 check the manual strategy setting alongside measured SLA health on each WAN is the better fit.
D:Inspect the traffic's identified service/application and the rule's match criteria. It could be appropriate when 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. 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 check the manual strategy setting alongside measured SLA health on each WAN.
Question 38
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription.
- Review policy mandates against the tenant's actual allowed service regions and logging arrangements
- Inspect whether the target object type is supported and the synchronization reports success
- Inspect administrative identity, assigned scope and change history for the affected settings
- Inspect the tenant's active subscriptions and whether the required capability is included
Explanation
Correct Answer
D:Inspect the tenant's active subscriptions and whether the required capability is included. This check isolates the relevant control before the change. Available subscription entitlements constrain which managed SASE services can be deployed.
Incorrect Answers
A:Review policy mandates against the tenant's actual allowed service regions and logging arrangements. 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 SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. A more direct answer is inspect the tenant's active subscriptions and whether the required capability is included.
B:Inspect whether the target object type is supported and the synchronization reports success. That is a useful action for a different circumstance: a central network management program wants address groups and security profile groups shared between on-premise FortiGate and the FortiSASE tenant. The present case is constrained by a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription; the targeted response is inspect the tenant's active subscriptions and whether the required capability is included.
C:Inspect administrative identity, assigned scope and change history for the affected settings. It addresses one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account. In the reported environment, the missing behavior instead relates to a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. The relevant choice is inspect the tenant's active subscriptions and whether the required capability is included.
Question 39
For a change review, the team proposes to validate LDAP group retrieval and policy group mapping in addition to directory connectivity because: A company chooses LDAP as an identity source, but FortiSASE cannot apply a group-based access policy despite successful basic user lookup. Which explanation connects the change to the underlying behavior?
- SAML supports federated sign-on using identity assertions rather than a second stand-alone password store
- Endpoint profiles can differentiate connection behavior by selected AD or non-AD user groups
- Group-based authorization requires that the relevant identity-group attributes are available to the SASE policy
- RADIUS authentication requires consistent server addressing, client trust and shared-secret parameters
Explanation
Correct Answer
C:Group-based authorization requires that the relevant identity-group attributes are available to the SASE policy. This is why the proposed repair addresses the reported behavior; confirm by checking: The user is placed in the expected group and matches its targeted allow policy.
Incorrect Answers
A:SAML supports federated sign-on using identity assertions rather than a second stand-alone password store. It could be appropriate when a corporation already authenticates its employees with an enterprise SAML identity provider and wants single sign-on for FortiSASE user access. 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 group-based authorization requires that the relevant identity-group attributes are available to the SASE policy.
B:Endpoint profiles can differentiate connection behavior by selected AD or non-AD user groups. The outcome for that step belongs to one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. Here the decisive requirement concerns a company chooses LDAP as an identity source, but FortiSASE cannot apply a group-based access policy despite successful basic user lookup, so group-based authorization requires that the relevant identity-group attributes are available to the SASE policy is the better fit.
D:RADIUS authentication requires consistent server addressing, client trust and shared-secret parameters. It addresses rADIUS-backed authentication works for a test account on the directory server but fails for FortiSASE users after onboarding. 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 group-based authorization requires that the relevant identity-group attributes are available to the SASE policy.
Question 40
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance.
- Inspect whether the monitored service has sufficient real sessions to supply passive samples
- Examine loss percentages over probe intervals and compare with the accepted threshold
- Compare measured jitter for each member with the voice SLA target rather than only checking packet loss
- Inspect most recent probe measurements and sample timing on the affected member
Explanation
Correct Answer
D:Inspect most recent probe measurements and sample timing on the affected member. This check isolates the relevant control before the change. Health dashboards display measured probe results, not a static certification that a line has been repaired.
Incorrect Answers
A:Inspect whether the monitored service has sufficient real sessions to supply passive samples. It could be appropriate when a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use. However, that does not resolve the stated condition: a branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance. A more direct answer is inspect most recent probe measurements and sample timing on the affected member.
B:Examine loss percentages over probe intervals and compare with the accepted threshold. It addresses a remote kiosk experiences intermittent missing packets despite its interface staying up. 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 inspect most recent probe measurements and sample timing on the affected member.
C:Compare measured jitter for each member with the voice SLA target rather than only checking packet loss. That is a useful action for a different circumstance: a voice application performs poorly with high jitter even though packet loss is low on both WANs. 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 inspect most recent probe measurements and sample timing on the affected member.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests