Question 390
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? FortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub.
- An IPsec tunnel becomes established and remains stable before private-app traffic tests
- The internal name resolves to the correct private address and the application connects over SPA
- The remote private destination is learned from the intended hub and forwarded over the VPN
- Each approved hub has consistent overlay and routing settings after verified deployment
Explanation
Correct Answer
A:An IPsec tunnel becomes established and remains stable before private-app traffic tests. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:The internal name resolves to the correct private address and the application connects over SPA. It addresses a remote user can reach an internal server by private IP but not by its internal hostname through the SPA connection. In the reported environment, the missing behavior instead relates to fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. The relevant choice is an IPsec tunnel becomes established and remains stable before private-app traffic tests.
C:The remote private destination is learned from the intended hub and forwarded over the VPN. 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 fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub; the targeted response is an IPsec tunnel becomes established and remains stable before private-app traffic tests.
D:Each approved hub has consistent overlay and routing settings after verified deployment. The outcome for that step belongs to a company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites. Here the decisive requirement concerns fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub, so an IPsec tunnel becomes established and remains stable before private-app traffic tests is the better fit.
Question 391
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision.
- Inspect per-member jitter and the rule's quality metric/selection status
- Compare member choices for multiple connections from one client and several different clients
- Inspect ordered rule matching and the actual matched rule for a billing test flow
- Compare which application or destination condition each matching rule contains
Explanation
Correct Answer
D:Compare which application or destination condition each matching rule contains. This check isolates the relevant control before the change. SD-WAN steering is independent of the permit policy and can choose links using service-specific matches.
Incorrect Answers
A: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 policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. The relevant choice is compare which application or destination condition each matching rule contains.
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 policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision; the targeted response is compare which application or destination condition each matching rule contains.
C:Inspect ordered rule matching and the actual matched rule for a billing test flow. It could be appropriate when a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. However, that does not resolve the stated condition: a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. A more direct answer is compare which application or destination condition each matching rule contains.
Question 392
For a change review, the team proposes to distinguish link availability from SLA compliance and review the rule's qualifying-member selection because: An SD-WAN operator sees a link marked alive but the performance SLA map shows it misses the configured voice target. Which explanation connects the change to the underlying behavior?
- A live transport can fail an application's quality threshold without becoming administratively down
- With equal costs among qualifying links, interface preference determines the selected link
- The minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA
- Active probes create measurement traffic independently of client session demand
Explanation
Correct Answer
A:A live transport can fail an application's quality threshold without becoming administratively down. This is why the proposed repair addresses the reported behavior; confirm by checking: The voice rule avoids the noncompliant path when another compliant member is available.
Incorrect Answers
B: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 an SD-WAN operator sees a link marked alive but the performance SLA map shows it misses the configured voice target. The relevant choice is a live transport can fail an application's quality threshold without becoming administratively down.
C:The minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA. The outcome for that step belongs to the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. Here the decisive requirement concerns an SD-WAN operator sees a link marked alive but the performance SLA map shows it misses the configured voice target, so a live transport can fail an application's quality threshold without becoming administratively down is the better fit.
D:Active probes create measurement traffic independently of client session demand. That is a useful action for a different circumstance: two WAN interfaces show up, but the network manager needs continuous health information even when no users are active. The present case is constrained by an SD-WAN operator sees a link marked alive but the performance SLA map shows it misses the configured voice target; the targeted response is a live transport can fail an application's quality threshold without becoming administratively down.
Question 393
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link.
- New eligible backup sessions spread across both members in line with the chosen algorithm
- The member change correlates with a documented SLA or eligibility change, not guesswork about policy order
- Conference sessions match the dedicated rule while unrelated services do not
- Matching calls select a qualifying WAN during controlled primary-path degradation
Explanation
Correct Answer
A:New eligible backup sessions spread across both members in line with the chosen algorithm. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:The member change correlates with a documented SLA or eligibility change, not guesswork about policy order. It addresses an IT team monitors a policy's configuration text but still cannot explain why a selected member changed during a short quality incident. In the reported environment, the missing behavior instead relates to a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. The relevant choice is new eligible backup sessions spread across both members in line with the chosen algorithm.
C:Conference sessions match the dedicated rule while unrelated services do not. That is a useful action for a different circumstance: 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 present case is constrained by a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link; the targeted response is new eligible backup sessions spread across both members in line with the chosen algorithm.
D:Matching calls select a qualifying WAN during controlled primary-path degradation. The outcome for that step belongs to a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. Here the decisive requirement concerns a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link, so new eligible backup sessions spread across both members in line with the chosen algorithm is the better fit.
Question 394
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable.
- Inspect the client telemetry connection and the resulting compliant or noncompliant posture tag
- Inspect how the policy evaluates the missing field and distinguish unknown from failed conditions
- Inspect assigned groups and effective profile for a pilot and a nonpilot device
- Check user-group membership, intended profile priority and effective endpoint assignment
Explanation
Correct Answer
B:Inspect how the policy evaluates the missing field and distinguish unknown from failed conditions. This check isolates the relevant control before the change. Conditional access decisions must use the actual required posture attributes and rule logic.
Incorrect Answers
A:Inspect the client telemetry connection and the resulting compliant or noncompliant posture tag. The outcome for that step belongs to a managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service. Here the decisive requirement concerns a department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable, so inspect how the policy evaluates the missing field and distinguish unknown from failed conditions is the better fit.
C:Inspect assigned groups and effective profile for a pilot and a nonpilot device. It could be appropriate when an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. However, that does not resolve the stated condition: a department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable. A more direct answer is inspect how the policy evaluates the missing field and distinguish unknown from failed conditions.
D:Check user-group membership, intended profile priority and effective endpoint assignment. That is a useful action for a different circumstance: a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile. The present case is constrained by a department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable; the targeted response is inspect how the policy evaluates the missing field and distinguish unknown from failed conditions.
Question 395
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A new branch has two internet circuits configured as ordinary FortiGate interfaces, but no SD-WAN members exist; the owner wants policy-based path steering.
- The second tunnel still requires a route and operational VPN establishment; zone assignment alone is not sufficient
- A static route pointing to a zone does not automatically populate that zone with members
- A firewall policy or route that omits the SD-WAN zone can still prevent forwarding
- A latency-only SLA may miss variable packet-arrival spacing
Explanation
Correct Answer
C:A firewall policy or route that omits the SD-WAN zone can still prevent forwarding. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:The second tunnel still requires a route and operational VPN establishment; zone assignment alone is not sufficient. It could be appropriate when a branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy. However, that does not resolve the stated condition: a new branch has two internet circuits configured as ordinary FortiGate interfaces, but no SD-WAN members exist; the owner wants policy-based path steering. A more direct answer is a firewall policy or route that omits the SD-WAN zone can still prevent forwarding.
B:A static route pointing to a zone does not automatically populate that zone with members. It addresses a FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member. In the reported environment, the missing behavior instead relates to a new branch has two internet circuits configured as ordinary FortiGate interfaces, but no SD-WAN members exist; the owner wants policy-based path steering. The relevant choice is a firewall policy or route that omits the SD-WAN zone can still prevent forwarding.
D:A latency-only SLA may miss variable packet-arrival spacing. The outcome for that step belongs to a voice application performs poorly with high jitter even though packet loss is low on both WANs. Here the decisive requirement concerns a new branch has two internet circuits configured as ordinary FortiGate interfaces, but no SD-WAN members exist; the owner wants policy-based path steering, so a firewall policy or route that omits the SD-WAN zone can still prevent forwarding is the better fit.
Question 396
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? An existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change.
- Deleting all custom rules does not disable the implicit fallback behavior
- Best-quality steering may prefer a single superior path rather than share load
- Keeping the retired address object can deny traffic even when VPN negotiation succeeds
- Changing the firewall policy action alone does not select the distinct outbound members
Explanation
Correct Answer
C:Keeping the retired address object can deny traffic even when VPN negotiation succeeds. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Deleting all custom rules does not disable the implicit fallback behavior. It addresses no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. In the reported environment, the missing behavior instead relates to an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change. The relevant choice is keeping the retired address object can deny traffic even when VPN negotiation succeeds.
B:Best-quality steering may prefer a single superior path rather than share load. It could be appropriate when a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. 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 keeping the retired address object can deny traffic even when VPN negotiation succeeds.
D:Changing the firewall policy action alone does not select the distinct outbound members. 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 an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change, so keeping the retired address object can deny traffic even when VPN negotiation succeeds is the better fit.
Question 397
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change.
- Assuming a single filtered-screen export includes all tenant history can omit relevant evidence
- A device-wide bandwidth chart does not identify one transaction's rule match
- Manually exporting a dashboard once does not meet a recurring reporting requirement
- Changing SD-WAN member priority does not explain an application-layer intrusion signature
Explanation
Correct Answer
B:A device-wide bandwidth chart does not identify one transaction's rule match. The planned change can still miss the requirement if this condition is left unresolved. Per-session policy and egress evidence can identify the forwarding decision behind a route change.
Incorrect Answers
A:Assuming a single filtered-screen export includes all tenant history can omit relevant evidence. It could be appropriate when an analyst exports the currently filtered FortiSASE security-log view but expects every historical event in the tenant to appear in that export. However, that does not resolve the stated condition: a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. A more direct answer is a device-wide bandwidth chart does not identify one transaction's rule match.
C:Manually exporting a dashboard once does not meet a recurring reporting requirement. The outcome for that step belongs to the compliance manager needs the same user-traffic report delivered every Monday without an operator manually rerunning it. Here the decisive requirement concerns a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change, so a device-wide bandwidth chart does not identify one transaction's rule match is the better fit.
D:Changing SD-WAN member priority does not explain an application-layer intrusion signature. That is a useful action for a different circumstance: a remote client receives an intrusion-prevention alert while accessing an internal application through SASE. The present case is constrained by a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change; the targeted response is a device-wide bandwidth chart does not identify one transaction's rule match.
Question 398
During implementation, the administrator observes: One tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account. Which intervention targets the described fault rather than an adjacent workflow?
- Inspect administrative event and change records for the FortiSASE tenant
- Verify and apply the required FortiSASE license entitlement for the selected deployment before enabling the features
- Use individual named administrator identities and appropriate delegated roles rather than sharing credentials
- Pilot FortiSASE remote-client access through security points of presence with the required web security policy
Explanation
Correct Answer
C:Use individual named administrator identities and appropriate delegated roles rather than sharing credentials. Individual accountability and scoped permissions improve operational security and auditability. The configuration alone must be followed by a functioning test: A test change is attributable to a named authorized administrator with the expected rights.
Incorrect Answers
A:Inspect administrative event and change records for the FortiSASE tenant. It could be appropriate when an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. However, that does not resolve the stated condition: one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account. A more direct answer is use individual named administrator identities and appropriate delegated roles rather than sharing credentials.
B:Verify and apply the required FortiSASE license entitlement for the selected deployment before enabling the features. The outcome for that step belongs to a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. Here the decisive requirement concerns one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account, so use individual named administrator identities and appropriate delegated roles rather than sharing credentials is the better fit.
D:Pilot FortiSASE remote-client access through security points of presence with the required web security policy. 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 one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account. The relevant choice is use individual named administrator identities and appropriate delegated roles rather than sharing credentials.
Question 399
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member.
- Compare cost settings with the qualifying SLA result for both members
- Inspect ordered rule matching and the actual matched rule for a billing test flow
- Check source address on an actual session and compare with the rule source selector
- Review implicit strategy and active member selection for the unmatched test session
Explanation
Correct Answer
B:Inspect ordered rule matching and the actual matched rule for a billing test flow. This check isolates the relevant control before the change. Rule evaluation and match specificity determine which steering action applies to a session.
Incorrect Answers
A:Compare cost settings with the qualifying SLA result for both members. 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 configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member; the targeted response is inspect ordered rule matching and the actual matched rule for a billing test flow.
C:Check source address on an actual session and compare with the rule source selector. It could be appropriate when fortiGate's traffic policy permits VoIP, but its SD-WAN rule is scoped to the wrong source network after a subnet migration. 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 inspect ordered rule matching and the actual matched rule for a billing test flow.
D:Review implicit strategy and active member selection for the unmatched test session. The outcome for that step belongs to no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. Here the decisive requirement concerns a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member, so inspect ordered rule matching and the actual matched rule for a billing test flow is the better fit.
Question 400
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A voice application performs poorly with high jitter even though packet loss is low on both WANs.
- Compare measured jitter for each member with the voice SLA target rather than only checking packet loss
- Inspect configured member costs, measured SLA target results and the selected rule
- Check probe reachability along each member before attributing failure to transport quality
- Check how many members actually meet the target and the configured minimum for that rule
Explanation
Correct Answer
A:Compare measured jitter for each member with the voice SLA target rather than only checking packet loss. The observed evidence guides the targeted repair: Define a jitter SLA threshold and reference that health target in the voice steering rule.
Incorrect Answers
B:Inspect configured member costs, measured SLA target results and the selected rule. The outcome for that step belongs to a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements. Here the decisive requirement concerns a voice application performs poorly with high jitter even though packet loss is low on both WANs, so compare measured jitter for each member with the voice SLA target rather than only checking packet loss is the better fit.
C:Check probe reachability along each member before attributing failure to transport quality. That is a useful action for a different circumstance: a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works. The present case is constrained by a voice application performs poorly with high jitter even though packet loss is low on both WANs; the targeted response is compare measured jitter for each member with the voice SLA target rather than only checking packet loss.
D:Check how many members actually meet the target and the configured minimum for that rule. It addresses the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. In the reported environment, the missing behavior instead relates to a voice application performs poorly with high jitter even though packet loss is low on both WANs. The relevant choice is compare measured jitter for each member with the voice SLA target rather than only checking packet loss.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests