Question 10
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: During branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider.
- Check the SD-WAN member list and each interface's administrative and operational state
- Check the backup member's acquired address, gateway reachability and route state
- Examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names
- Examine an identified conference flow and verify which SD-WAN rule it matches
Explanation
Correct Answer
B:Check the backup member's acquired address, gateway reachability and route state. This check isolates the relevant control before the change. An Ethernet carrier signal does not establish layer-3 underlay reachability needed for the SD-WAN path.
Incorrect Answers
A:Check the SD-WAN member list and each interface's administrative and operational state. It could be appropriate when 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. However, that does not resolve the stated condition: during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider. A more direct answer is check the backup member's acquired address, gateway reachability and route state.
C:Examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names. That is a useful action for a different circumstance: a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. The present case is constrained by during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider; the targeted response is check the backup member's acquired address, gateway reachability and route state.
D:Examine an identified conference flow and verify which SD-WAN rule it matches. The outcome for that step belongs to an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. Here the decisive requirement concerns during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider, so check the backup member's acquired address, gateway reachability and route state is the better fit.
Question 11
During implementation, the administrator observes: 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. Which intervention targets the described fault rather than an adjacent workflow?
- Inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics
- Keep the more-specific private route toward the tunnel while using default Internet reachability for public traffic
- Check SNAT and session behavior when rerouting across WAN members, not only link quality
- Compare route prefix length and actual routing preference for the specific destination before changing SD-WAN rules
Explanation
Correct Answer
A:Inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics. Active-session evidence shows which path was actually used, not only which paths were configured. The configuration alone must be followed by a functioning test: The session record shows the intended tunnel and matching permit rule during a successful request.
Incorrect Answers
B:Keep the more-specific private route toward the tunnel while using default Internet reachability for public traffic. It addresses a branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination. In the reported environment, the missing behavior instead relates to 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 relevant choice is inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics.
C:Check SNAT and session behavior when rerouting across WAN members, not only link quality. 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 SD-WAN operator wants to prove that a payment session left through the correct tunnel after an incident, rather than infer from routes alone, so inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics is the better fit.
D:Compare route prefix length and actual routing preference for the specific destination before changing SD-WAN rules. That is a useful action for a different circumstance: an SD-WAN hub learns a private route over BGP but the branch still uses a competing less-specific static path for one destination. The present case is constrained by 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 targeted response is inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics.
Question 12
The team plans to add an explicit traffic-matching SD-WAN rule for the emergency application's destination and preferred LTE member for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy.
- An established IPsec security association alone does not prove the necessary BGP routes exist
- Creating duplicate static routes does not make a degraded link satisfy a performance objective
- An allow policy with broad destination 'all' is not an SD-WAN member-selection rule
- Steering alone cannot resolve a mistaken destination prefix or absent BGP route
Explanation
Correct Answer
C:An allow policy with broad destination 'all' is not an SD-WAN member-selection rule. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:An established IPsec security association alone does not prove the necessary BGP routes exist. The outcome for that step belongs to 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. Here the decisive requirement concerns a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy, so an allow policy with broad destination 'all' is not an SD-WAN member-selection rule is the better fit.
B:Creating duplicate static routes does not make a degraded link satisfy a performance objective. It addresses an administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing. In the reported environment, the missing behavior instead relates to a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy. The relevant choice is an allow policy with broad destination 'all' is not an SD-WAN member-selection rule.
D:Steering alone cannot resolve a mistaken destination prefix or absent BGP route. It could be appropriate when an SD-WAN hub learns a private route over BGP but the branch still uses a competing less-specific static path for one destination. However, that does not resolve the stated condition: a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy. A more direct answer is an allow policy with broad destination 'all' is not an SD-WAN member-selection rule.
Question 13
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions.
- Inspect the endpoint vulnerability results and the matched compliance posture tag on a test device
- Inspect assigned groups and effective profile for a pilot and a nonpilot device
- Inspect the endpoint's reported protection state and matched compliance rule
- Check user-group membership, intended profile priority and effective endpoint assignment
Explanation
Correct Answer
C:Inspect the endpoint's reported protection state and matched compliance rule. The observed evidence guides the targeted repair: Configure the supported endpoint compliance or posture criteria and associate them with the appropriate access treatment.
Incorrect Answers
A:Inspect the endpoint vulnerability results and the matched compliance posture tag on a test device. It could be appropriate when a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. However, that does not resolve the stated condition: a company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions. A more direct answer is inspect the endpoint's reported protection state and matched compliance rule.
B:Inspect assigned groups and effective profile for a pilot and a nonpilot device. It addresses an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. In the reported environment, the missing behavior instead relates to a company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions. The relevant choice is inspect the endpoint's reported protection state and matched compliance rule.
D:Check user-group membership, intended profile priority and effective endpoint assignment. The outcome for that step belongs to a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile. Here the decisive requirement concerns a company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions, so inspect the endpoint's reported protection state and matched compliance rule is the better fit.
Question 14
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A company wants to prevent simultaneous failure of two Internet circuits from the same carrier.
- Compare active link health and the rule's selected member for normal flows
- Examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names
- Review the route lookup for a representative public destination and the next-hop resolution
- Inspect the policy's destination interface and the assigned zone of that WAN member
Explanation
Correct Answer
B:Examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names. This check isolates the relevant control before the change. SD-WAN link selection can respond to independent transport failures but cannot eliminate a shared provider dependency.
Incorrect Answers
A:Compare active link health and the rule's selected member for normal flows. 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 a company wants to prevent simultaneous failure of two Internet circuits from the same carrier; the targeted response is examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names.
C:Review the route lookup for a representative public destination and the next-hop resolution. It could be appropriate when a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations. However, that does not resolve the stated condition: a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. A more direct answer is examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names.
D:Inspect the policy's destination interface and the assigned zone of that WAN member. The outcome for that step belongs 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. Here the decisive requirement concerns a company wants to prevent simultaneous failure of two Internet circuits from the same carrier, so examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names is the better fit.
Question 15
Given this incident — An employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. — the administrator plans to review DLP or relevant inline SaaS security events for the sensitive-content match. Which technical principle justifies it?
- An IPS event records traffic behavior matching a threat signature, not simply route choice
- Inline SaaS inspection can produce activity-level events distinct from domain-category blocks
- Web-filter events concern destination categorization, while IPS events concern detected intrusion patterns
- DLP incidents identify content-rule enforcement distinct from simple URL or authentication failures
Explanation
Correct Answer
D:DLP incidents identify content-rule enforcement distinct from simple URL or authentication failures. It directly explains the need to review DLP or relevant inline SaaS security events for the sensitive-content match. The narrow validation is: A DLP event links the restricted content pattern to the denied upload.
Incorrect Answers
A:An IPS event records traffic behavior matching a threat signature, not simply route choice. It could be appropriate when a remote client receives an intrusion-prevention alert while accessing an internal application through SASE. However, that does not resolve the stated condition: an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. A more direct answer is dLP incidents identify content-rule enforcement distinct from simple URL or authentication failures.
B:Inline SaaS inspection can produce activity-level events distinct from domain-category blocks. It addresses security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. In the reported environment, the missing behavior instead relates to an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. The relevant choice is dLP incidents identify content-rule enforcement distinct from simple URL or authentication failures.
C:Web-filter events concern destination categorization, while IPS events concern detected intrusion patterns. That is a useful action for a different circumstance: users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event. The present case is constrained by an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block; the targeted response is dLP incidents identify content-rule enforcement distinct from simple URL or authentication failures.
Question 16
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A company wants to prevent simultaneous failure of two Internet circuits from the same carrier.
- Checking only Ethernet link state would miss end-to-end packet loss
- Moving the tunnel without updating affected route and policy references can preserve the outage
- Trying to solve policy match by changing member weight leaves the wrong policy interface untouched
- Two virtual members mapped to the same failed provider do not deliver true transport diversity
Explanation
Correct Answer
D:Two virtual members mapped to the same failed provider do not deliver true transport diversity. The planned change can still miss the requirement if this condition is left unresolved. SD-WAN link selection can respond to independent transport failures but cannot eliminate a shared provider dependency.
Incorrect Answers
A:Checking only Ethernet link state would miss end-to-end packet loss. It could be appropriate when a remote kiosk experiences intermittent missing packets despite its interface staying up. However, that does not resolve the stated condition: a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. A more direct answer is two virtual members mapped to the same failed provider do not deliver true transport diversity.
B:Moving the tunnel without updating affected route and policy references can preserve the outage. It addresses during site migration, the team assigns an overlay tunnel to the ordinary Internet zone, then discovers it is subject to public-web policy handling. In the reported environment, the missing behavior instead relates to a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. The relevant choice is two virtual members mapped to the same failed provider do not deliver true transport diversity.
C:Trying to solve policy match by changing member weight leaves the wrong policy interface untouched. That is a useful action for a different circumstance: a FortiGate using zone-based policies shows the original interface port but the administrator cannot select it as a distinct policy destination. The present case is constrained by a company wants to prevent simultaneous failure of two Internet circuits from the same carrier; the targeted response is two virtual members mapped to the same failed provider do not deliver true transport diversity.
Question 17
After the authorized change to tie the supported compliance or posture result to an appropriately scoped private-access policy decision, which result actually demonstrates that this site's requirement is met? Initial issue: Security wants a noncompliant laptop to be unable to access protected company applications until it passes device checks.
- The test application is denied for a deliberately noncompliant device and permitted after remediation
- A representative non-exempt user is restricted while the authorized exception remains functional
- A patched test endpoint receives the compliant tag while a deliberately vulnerable test endpoint receives the intended restriction
- Only pilot devices receive the new requirements while other users retain their prior settings
Explanation
Correct Answer
A:The test application is denied for a deliberately noncompliant device and permitted after remediation. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:A representative non-exempt user is restricted while the authorized exception remains functional. That is a useful action for a different circumstance: one employee group is permitted removable media use while everyone else must be restricted by endpoint policy. The present case is constrained by security wants a noncompliant laptop to be unable to access protected company applications until it passes device checks; the targeted response is the test application is denied for a deliberately noncompliant device and permitted after remediation.
C:A patched test endpoint receives the compliant tag while a deliberately vulnerable test endpoint receives the intended restriction. It addresses a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. In the reported environment, the missing behavior instead relates to security wants a noncompliant laptop to be unable to access protected company applications until it passes device checks. The relevant choice is the test application is denied for a deliberately noncompliant device and permitted after remediation.
D:Only pilot devices receive the new requirements while other users retain their prior settings. The outcome for that step belongs to an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. Here the decisive requirement concerns security wants a noncompliant laptop to be unable to access protected company applications until it passes device checks, so the test application is denied for a deliberately noncompliant device and permitted after remediation is the better fit.
Question 18
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? An SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow.
- Inspect time-aligned per-member bytes or sessions and the corresponding flow log fields
- Review the payment session's egress and rule ID instead of only the SLA dashboard
- Inspect transaction timestamps and log status on both sides of the impairment
- Inspect traffic classification, rule ID and source/destination fields for both cohorts
Explanation
Correct Answer
B:Review the payment session's egress and rule ID instead of only the SLA dashboard. This check isolates the relevant control before the change. Eligibility is a candidate set; the selected path must be determined for the specific traffic instance.
Incorrect Answers
A:Inspect time-aligned per-member bytes or sessions and the corresponding flow log fields. That is a useful action for a different circumstance: a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. The present case is constrained by an SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow; the targeted response is review the payment session's egress and rule ID instead of only the SLA dashboard.
C:Inspect transaction timestamps and log status on both sides of the impairment. It could be appropriate when a branch rollout claims reliable failover because the WAN link state changed, but the business owner wants proof that application transactions continued. However, that does not resolve the stated condition: an SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow. A more direct answer is review the payment session's egress and rule ID instead of only the SLA dashboard.
D:Inspect traffic classification, rule ID and source/destination fields for both cohorts. The outcome for that step belongs to an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. Here the decisive requirement concerns an SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow, so review the payment session's egress and rule ID instead of only the SLA dashboard is the better fit.
Question 19
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? Management wants to compare blocked website trends by user group and demonstrate that the change was not only a temporary increase in total web traffic.
- Reporting only aggregate successful Internet sessions does not answer a group-specific blocking question
- A device-wide bandwidth chart does not identify one transaction's rule match
- A login success event does not prove why an uploaded file was blocked
- A rule configuration screenshot alone is weaker than observed matched-session behavior
Explanation
Correct Answer
A:Reporting only aggregate successful Internet sessions does not answer a group-specific blocking question. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:A device-wide bandwidth chart does not identify one transaction's rule match. 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 management wants to compare blocked website trends by user group and demonstrate that the change was not only a temporary increase in total web traffic, so reporting only aggregate successful Internet sessions does not answer a group-specific blocking question is the better fit.
C:A login success event does not prove why an uploaded file was blocked. It addresses an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. In the reported environment, the missing behavior instead relates to management wants to compare blocked website trends by user group and demonstrate that the change was not only a temporary increase in total web traffic. The relevant choice is reporting only aggregate successful Internet sessions does not answer a group-specific blocking question.
D:A rule configuration screenshot alone is weaker than observed matched-session behavior. That is a useful action for a different circumstance: an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. The present case is constrained by management wants to compare blocked website trends by user group and demonstrate that the change was not only a temporary increase in total web traffic; the targeted response is reporting only aggregate successful Internet sessions does not answer a group-specific blocking question.
Question 20
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate.
- A successful ping to the hub interface does not establish end-to-end private-network access
- Shared administrator credentials obscure individual change attribution even when policies are technically valid
- Treating IPsec phase-two success as complete reachability overlooks missing routing
- Disabling all certificate verification would undermine the identity-trust boundary instead of repairing it
Explanation
Correct Answer
D:Disabling all certificate verification would undermine the identity-trust boundary instead of repairing it. The planned change can still miss the requirement if this condition is left unresolved. A stale signature verification key prevents valid assertions from being accepted even when users know their passwords.
Incorrect Answers
A:A successful ping to the hub interface does not establish end-to-end private-network access. It addresses a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. In the reported environment, the missing behavior instead relates to a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. The relevant choice is disabling all certificate verification would undermine the identity-trust boundary instead of repairing it.
B:Shared administrator credentials obscure individual change attribution even when policies are technically valid. It could be appropriate when one tenant has different security teams for Internet access and private-app policy, but all configuration changes are currently performed by a shared account. However, that does not resolve the stated condition: a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. A more direct answer is disabling all certificate verification would undermine the identity-trust boundary instead of repairing it.
C:Treating IPsec phase-two success as complete reachability overlooks missing routing. That is a useful action for a different circumstance: the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. The present case is constrained by a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate; the targeted response is disabling all certificate verification would undermine the identity-trust boundary instead of repairing it.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests