Question 300
The team plans to define traffic-matching SD-WAN steering rules, with relevant quality targets and the required firewall permissions for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? An administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch.
- An old dashboard screenshot cannot prove current performance after a carrier change
- A new member in an unrelated zone may be selected by routing but denied by the policy scope
- Keeping both members in one shared zone prevents policy separation solely by member identity
- Merely increasing physical interface speed does not create application-aware path selection
Explanation
Correct Answer
D:Merely increasing physical interface speed does not create application-aware path selection. The planned change can still miss the requirement if this condition is left unresolved. SD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes.
Incorrect Answers
A:An old dashboard screenshot cannot prove current performance after a carrier change. That is a useful action for a different circumstance: a branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance. 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 merely increasing physical interface speed does not create application-aware path selection.
B:A new member in an unrelated zone may be selected by routing but denied by the policy scope. It addresses a company adds a new 5G interface but its existing WAN firewall policy covers only a named SD-WAN zone containing the older links. 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 merely increasing physical interface speed does not create application-aware path selection.
C:Keeping both members in one shared zone prevents policy separation solely by member identity. It could be appropriate when a branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic. 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 merely increasing physical interface speed does not create application-aware path selection.
Question 301
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic.
- Inspect zone membership and the permit rule's source and destination interface constraints
- Compare the 5G member's zone with the destination zone in the active allow policy
- Review the member-to-zone mapping and the source/destination zone in each security rule
- Inspect whether the interface is enrolled as an SD-WAN member and which zone is referenced by the policy
Explanation
Correct Answer
C:Review the member-to-zone mapping and the source/destination zone in each security rule. The observed evidence guides the targeted repair: Place the MPLS and Internet members in distinct SD-WAN zones and target each zone in the appropriate policy.
Incorrect Answers
A:Inspect zone membership and the permit rule's source and destination interface constraints. The outcome for that step belongs to a site should limit one overlay circuit to a restricted group of users, unlike unrestricted Internet underlays. Here the decisive requirement concerns a branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic, so review the member-to-zone mapping and the source/destination zone in each security rule is the better fit.
B:Compare the 5G member's zone with the destination zone in the active allow policy. It could be appropriate when a company adds a new 5G interface but its existing WAN firewall policy covers only a named SD-WAN zone containing the older links. However, that does not resolve the stated condition: a branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic. A more direct answer is review the member-to-zone mapping and the source/destination zone in each security rule.
D:Inspect whether the interface is enrolled as an SD-WAN member and which zone is referenced by the policy. 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 branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic. The relevant choice is review the member-to-zone mapping and the source/destination zone in each security rule.
Question 302
A proposed repair is to enable an appropriate antivirus inspection profile on the traffic's allow security profile group. Why should that repair work in this particular situation? Context: A remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category.
- Profile-group selection at policy level can differentiate inspection by user cohort
- Intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation
- Antivirus scanning targets malicious content, which may reside on otherwise acceptable sites
- DNS filtering can enforce policy based on name resolution queries, complementing web URL checks
Explanation
Correct Answer
C:Antivirus scanning targets malicious content, which may reside on otherwise acceptable sites. This is why the proposed repair addresses the reported behavior; confirm by checking: Malicious test content is detected or blocked according to policy without blocking the entire legitimate site category.
Incorrect Answers
A:Profile-group selection at policy level can differentiate inspection by user cohort. It addresses a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. In the reported environment, the missing behavior instead relates to a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category. The relevant choice is antivirus scanning targets malicious content, which may reside on otherwise acceptable sites.
B:Intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation. It could be appropriate when a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. However, that does not resolve the stated condition: a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category. A more direct answer is antivirus scanning targets malicious content, which may reside on otherwise acceptable sites.
D:DNS filtering can enforce policy based on name resolution queries, complementing web URL checks. The outcome for that step belongs to a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests. Here the decisive requirement concerns a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category, so antivirus scanning targets malicious content, which may reside on otherwise acceptable sites is the better fit.
Question 303
After the authorized change to choose physically and provider-diverse WAN underlays rather than merely naming two SD-WAN members, which result actually demonstrates that this site's requirement is met? Initial issue: A company wants to prevent simultaneous failure of two Internet circuits from the same carrier.
- A controlled failure of one provider leaves a separately sourced member reachable
- Branch users reach the hub-hosted application through IPsec while ordinary Internet access uses the local ISP
- Both circuits appear as selectable members and a test flow follows the matching steering rule
- Operators see per-member health and selection changes during a controlled path impairment test
Explanation
Correct Answer
A:A controlled failure of one provider leaves a separately sourced member reachable. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:Branch users reach the hub-hosted application through IPsec while ordinary Internet access uses the local ISP. 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 a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. The relevant choice is a controlled failure of one provider leaves a separately sourced member reachable.
C:Both circuits appear as selectable members and a test flow follows the matching steering rule. The outcome for that step belongs 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. Here the decisive requirement concerns a company wants to prevent simultaneous failure of two Internet circuits from the same carrier, so a controlled failure of one provider leaves a separately sourced member reachable is the better fit.
D:Operators see per-member health and selection changes during a controlled path impairment test. That is a useful action for a different circumstance: a new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory. 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 a controlled failure of one provider leaves a separately sourced member reachable.
Question 304
After the authorized change to attach the required security profile group to the matching Accept policy, which result actually demonstrates that this site's requirement is met? Initial issue: A remote-user security policy is set to Accept but the administrator expects an IPS profile to be active without having attached a profile group.
- A controlled session produces the intended IPS inspection event under the associated policy
- Only the intended group triggers the stricter web-filter behavior in logged tests
- Only the targeted cohort receives the block, and other approved users retain expected access
- An identified application action produces the intended monitor or block event while basic permitted access remains available
Explanation
Correct Answer
A:A controlled session produces the intended IPS inspection event under the associated policy. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:Only the intended group triggers the stricter web-filter behavior in logged tests. The outcome for that step belongs to a remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access. Here the decisive requirement concerns a remote-user security policy is set to Accept but the administrator expects an IPS profile to be active without having attached a profile group, so a controlled session produces the intended IPS inspection event under the associated policy is the better fit.
C:Only the targeted cohort receives the block, and other approved users retain expected access. 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 remote-user security policy is set to Accept but the administrator expects an IPS profile to be active without having attached a profile group; the targeted response is a controlled session produces the intended IPS inspection event under the associated policy.
D:An identified application action produces the intended monitor or block event while basic permitted access remains available. It addresses a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service. In the reported environment, the missing behavior instead relates to a remote-user security policy is set to Accept but the administrator expects an IPS profile to be active without having attached a profile group. The relevant choice is a controlled session produces the intended IPS inspection event under the associated policy.
Question 305
At a FortiSASE/SD-WAN site, this issue is reported: An organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once. What is the most direct technical change to address the stated requirement?
- Stage the baseline through a limited pilot group and validate enforcement before broader rollout
- Constrain the pilot profile to a narrowly defined test user or endpoint group
- Refresh endpoint posture reporting and verify the rule's effective match data before relaxing policy
- Investigate the independent telemetry-connectivity posture condition instead of treating antivirus alone as full compliance
Explanation
Correct Answer
A:Stage the baseline through a limited pilot group and validate enforcement before broader rollout. Targeted endpoint profile or compliance assignments support controlled policy changes. The configuration alone must be followed by a functioning test: The pilot group enforces the new control without changing the nonpilot cohort's access.
Incorrect Answers
B:Constrain the pilot profile to a narrowly defined test user or endpoint group. 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 an organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once. The relevant choice is stage the baseline through a limited pilot group and validate enforcement before broader rollout.
C:Refresh endpoint posture reporting and verify the rule's effective match data before relaxing policy. The outcome for that step belongs to a security analyst sees a compliant laptop marked as noncompliant even after remediation of its local antivirus settings. Here the decisive requirement concerns an organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once, so stage the baseline through a limited pilot group and validate enforcement before broader rollout is the better fit.
D:Investigate the independent telemetry-connectivity posture condition instead of treating antivirus alone as full compliance. That is a useful action for a different circumstance: a managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service. The present case is constrained by an organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once; the targeted response is stage the baseline through a limited pilot group and validate enforcement before broader rollout.
Question 306
For a change review, the team proposes to create and assign different endpoint profiles with the corresponding allowed disconnect behavior because: One group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. Which explanation connects the change to the underlying behavior?
- A managed installer and assigned profile reduce configuration drift between new endpoint installations
- Endpoint profiles can differentiate connection behavior by selected AD or non-AD user groups
- A stale signature verification key prevents valid assertions from being accepted even when users know their passwords
- Identity-based policy assignment depends on group membership, not just successful authentication
Explanation
Correct Answer
B:Endpoint profiles can differentiate connection behavior by selected AD or non-AD user groups. It directly explains the need to create and assign different endpoint profiles with the corresponding allowed disconnect behavior. The narrow validation is: Standard staff cannot disconnect, while the approved IT group has the intended exception.
Incorrect Answers
A:A managed installer and assigned profile reduce configuration drift between new endpoint installations. The outcome for that step belongs to a support team wants to distribute an approved managed FortiClient installer to a new device population, with consistent connection settings. Here the decisive requirement concerns one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily, so endpoint profiles can differentiate connection behavior by selected AD or non-AD user groups is the better fit.
C:A stale signature verification key prevents valid assertions from being accepted even when users know their passwords. That is a useful action for a different circumstance: a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. The present case is constrained by one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily; the targeted response is endpoint profiles can differentiate connection behavior by selected AD or non-AD user groups.
D:Identity-based policy assignment depends on group membership, not just successful authentication. It could be appropriate when a new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy. However, that does not resolve the stated condition: one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. A more direct answer is endpoint profiles can differentiate connection behavior by selected AD or non-AD user groups.
Question 307
After the authorized change to inspect the selected-member information in per-session and SD-WAN rule diagnostics, which result actually demonstrates that this site's requirement is met? Initial issue: 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 actual traffic log or session record names the intended selected member
- Only approved application sessions match the specialized rule in a controlled test
- The incident session record identifies the ISP path active before the outage
- The recorded degradation and selected-member transition correspond to the voice complaint
Explanation
Correct Answer
A:The actual traffic log or session record names the intended selected member. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:Only approved application sessions match the specialized rule in a controlled test. 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 the actual traffic log or session record names the intended selected member is the better fit.
C:The incident session record identifies the ISP path active before the outage. It addresses a team wants to identify which ISP path was used by a specific session before a provider outage. In the reported environment, the missing behavior instead relates to 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 relevant choice is the actual traffic log or session record names the intended selected member.
D:The recorded degradation and selected-member transition correspond to the voice complaint. That is a useful action for a different circumstance: a branch user reports intermittent voice interruptions, but the manager only has a log of which WAN interface was administratively up. 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 the actual traffic log or session record names the intended selected member.
Question 308
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? During branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider.
- A sourced probe from the backup interface reaches the provider gateway and test external destinations
- Operators see per-member health and selection changes during a controlled path impairment test
- A new external session finds a default route and egresses on an eligible SD-WAN member
- The policy matches sessions sent through either eligible member of its designated zone
Explanation
Correct Answer
A:A sourced probe from the backup interface reaches the provider gateway and test external destinations. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:Operators see per-member health and selection changes during a controlled path impairment test. That is a useful action for a different circumstance: a new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory. 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 a sourced probe from the backup interface reaches the provider gateway and test external destinations.
C:A new external session finds a default route and egresses on an eligible SD-WAN member. It addresses a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations. In the reported environment, the missing behavior instead relates to during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider. The relevant choice is a sourced probe from the backup interface reaches the provider gateway and test external destinations.
D:The policy matches sessions sent through either eligible member of its designated zone. 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 during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider, so a sourced probe from the backup interface reaches the provider gateway and test external destinations is the better fit.
Question 309
A proposed repair is to add or correct performance-SLA measurements and reference them in the application steering rule. Why should that repair work in this particular situation? Context: A support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit.
- Physical interface state measures carrier, whereas SLA probes reveal end-to-end latency, jitter and loss
- The firewall policy is a separate permission decision from member selection; a valid SD-WAN path does not itself allow sessions
- SD-WAN views tie member selection to quality data rather than only link-up state
- Steering can choose only among configured members; simply having two interfaces with addresses does not make them SD-WAN candidates
Explanation
Correct Answer
A:Physical interface state measures carrier, whereas SLA probes reveal end-to-end latency, jitter and loss. This is why the proposed repair addresses the reported behavior; confirm by checking: Traffic transitions to a qualifying link when the poor circuit crosses its configured SLA bounds.
Incorrect Answers
B:The firewall policy is a separate permission decision from member selection; a valid SD-WAN path does not itself allow sessions. It addresses a newly installed branch has healthy ISP links and an SD-WAN zone, yet LAN clients cannot browse because the existing allow policy targets only a former WAN interface. In the reported environment, the missing behavior instead relates to a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit. The relevant choice is physical interface state measures carrier, whereas SLA probes reveal end-to-end latency, jitter and loss.
C:SD-WAN views tie member selection to quality data rather than only link-up state. The outcome for that step belongs to a new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory. Here the decisive requirement concerns a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit, so physical interface state measures carrier, whereas SLA probes reveal end-to-end latency, jitter and loss is the better fit.
D:Steering can choose only among configured members; simply having two interfaces with addresses does not make them SD-WAN candidates. That is a useful action for a different circumstance: 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 present case is constrained by a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit; the targeted response is physical interface state measures carrier, whereas SLA probes reveal end-to-end latency, jitter and loss.
Question 310
After the authorized change to correct the member gateway and dependent routing configuration to match the currently assigned underlay, which result actually demonstrates that this site's requirement is met? Initial issue: A WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router.
- Internet test flows use a reachable next hop and health probes recover
- The session record shows the intended tunnel and matching permit rule during a successful request
- The hub routing table contains the expected reachable prefixes across the overlay
- The repaired member is both routed and SLA-qualified when its measured performance meets the target
Explanation
Correct Answer
A:Internet test flows use a reachable next hop and health probes recover. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:The session record shows the intended tunnel and matching permit rule during a successful request. It addresses 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. In the reported environment, the missing behavior instead relates to a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. The relevant choice is internet test flows use a reachable next hop and health probes recover.
C:The hub routing table contains the expected reachable prefixes across the overlay. 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 a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router; the targeted response is internet test flows use a reachable next hop and health probes recover.
D:The repaired member is both routed and SLA-qualified when its measured performance meets the target. The outcome for that step belongs to an administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing. Here the decisive requirement concerns a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router, so internet test flows use a reachable next hop and health probes recover is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests