Question 280
For the stated scenario, what is the most important remaining blind spot after the proposed correction? One group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily.
- Changing application-user SAML claims cannot repair an unreachable IPsec peer endpoint
- A tunnel being up in one direction does not prove reply routing or security state are correct
- One global profile cannot safely encode mutually different group-specific connection permissions
- Shared administrator credentials obscure individual change attribution even when policies are technically valid
Explanation
Correct Answer
C:One global profile cannot safely encode mutually different group-specific connection permissions. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Changing application-user SAML claims cannot repair an unreachable IPsec peer endpoint. It could be appropriate when after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer. 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 one global profile cannot safely encode mutually different group-specific connection permissions.
B:A tunnel being up in one direction does not prove reply routing or security state are correct. The outcome for that step belongs to a remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path. 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 one global profile cannot safely encode mutually different group-specific connection permissions is the better fit.
D:Shared administrator credentials obscure individual change attribution even when policies are technically valid. 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 one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. The relevant choice is one global profile cannot safely encode mutually different group-specific connection permissions.
Question 281
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? An administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams.
- Access follows the intended policy only after the agent reports both required posture conditions
- Updated endpoint state passes the required security check without weakening the baseline
- The test client receives the departmental profile and the expected security controls
- Only pilot devices receive the new requirements while other users retain their prior settings
Explanation
Correct Answer
D:Only pilot devices receive the new requirements while other users retain their prior settings. This is stronger than a saved configuration because it tests the intended operational result. Profiles must be scoped to their target populations to avoid unintended fleet-wide change.
Incorrect Answers
A:Access follows the intended policy only after the agent reports both required posture conditions. It addresses a managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service. 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 only pilot devices receive the new requirements while other users retain their prior settings.
B:Updated endpoint state passes the required security check without weakening the baseline. That is a useful action for a different circumstance: a security analyst sees a compliant laptop marked as noncompliant even after remediation of its local antivirus settings. The present case is constrained by an administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams; the targeted response is only pilot devices receive the new requirements while other users retain their prior settings.
C:The test client receives the departmental profile and the expected security controls. It could be appropriate when a sales employee installs FortiClient but remains assigned the Default endpoint profile rather than the required departmental protection profile. 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 only pilot devices receive the new requirements while other users retain their prior settings.
Question 282
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? Video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price.
- Assuming every established TCP session seamlessly survives a path or SNAT address change is unsafe
- Lowest Cost (SLA) mode could prefer a cheaper merely compliant path rather than the best jitter
- Increasing probe timeout does not fix a gateway that no longer exists
- A broad default route does not replace a missing specific private-network route
Explanation
Correct Answer
B:Lowest Cost (SLA) mode could prefer a cheaper merely compliant path rather than the best jitter. The planned change can still miss the requirement if this condition is left unresolved. The best-quality strategy compares eligible links by the selected measured quality factor.
Incorrect Answers
A:Assuming every established TCP session seamlessly survives a path or SNAT address change is unsafe. The outcome for that step belongs to a provider outage removes a member's usable path, yet operators continue testing sessions that were established before the outage. Here the decisive requirement concerns video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price, so lowest Cost (SLA) mode could prefer a cheaper merely compliant path rather than the best jitter is the better fit.
C:Increasing probe timeout does not fix a gateway that no longer exists. That is a useful action for a different circumstance: a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member. The present case is constrained by video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price; the targeted response is lowest Cost (SLA) mode could prefer a cheaper merely compliant path rather than the best jitter.
D:A broad default route does not replace a missing specific private-network route. It could be appropriate when a branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination. However, that does not resolve the stated condition: video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price. A more direct answer is lowest Cost (SLA) mode could prefer a cheaper merely compliant path rather than the best jitter.
Question 283
At a FortiSASE/SD-WAN site, this issue is reported: A bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. What is the most direct technical change to address the stated requirement?
- Complete the backup interface's appropriate DHCP or static IP configuration and gateway settings
- Build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate
- Add both WAN interfaces as SD-WAN members in an appropriate zone before defining the steering rule
- Reference the intended SD-WAN zone for traffic-policy control rather than individual members when using the SD-WAN design
Explanation
Correct Answer
B:Build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate. SD-WAN can distinguish overlay and underlay transport and steer traffic based on intended destination and policy. The acceptance check should show: Branch users reach the hub-hosted application through IPsec while ordinary Internet access uses the local ISP.
Incorrect Answers
A:Complete the backup interface's appropriate DHCP or static IP configuration and gateway settings. The outcome for that step belongs to during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider. Here the decisive requirement concerns a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly, so build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate is the better fit.
C:Add both WAN interfaces as SD-WAN members in an appropriate zone before defining the steering rule. 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: a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. A more direct answer is build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate.
D:Reference the intended SD-WAN zone for traffic-policy control rather than individual members when using the SD-WAN design. That is a useful action for a different circumstance: after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules. The present case is constrained by a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly; the targeted response is build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate.
Question 284
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A team wants to identify which ISP path was used by a specific session before a provider outage.
- Inspect time-aligned per-member bytes or sessions and the corresponding flow log fields
- Inspect traffic classification, rule ID and source/destination fields for both cohorts
- Filter logs by source, destination, time and relevant rule or session identifiers
- Inspect session source, destination, timestamps, policy and egress member
Explanation
Correct Answer
D:Inspect session source, destination, timestamps, policy and egress member. This check isolates the relevant control before the change. Historical logs preserve forwarding decisions from the event time while current routing may differ.
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 a team wants to identify which ISP path was used by a specific session before a provider outage; the targeted response is inspect session source, destination, timestamps, policy and egress member.
B:Inspect traffic classification, rule ID and source/destination fields for both cohorts. It could be appropriate when an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. However, that does not resolve the stated condition: a team wants to identify which ISP path was used by a specific session before a provider outage. A more direct answer is inspect session source, destination, timestamps, policy and egress member.
C:Filter logs by source, destination, time and relevant rule or session identifiers. It addresses a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. In the reported environment, the missing behavior instead relates to a team wants to identify which ISP path was used by a specific session before a provider outage. The relevant choice is inspect session source, destination, timestamps, policy and egress member.
Question 285
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A remote kiosk experiences intermittent missing packets despite its interface staying up.
- The lower-cost compliant link is selected; a lower-cost failing link does not automatically win
- The kiosk's new sessions move toward a qualifying member when the original exceeds loss tolerance
- The reachable target produces valid health samples on both correctly functioning circuits
- After an authorized order swap, new eligible flows select the newly preferred equal-cost member
Explanation
Correct Answer
B:The kiosk's new sessions move toward a qualifying member when the original exceeds loss tolerance. This is stronger than a saved configuration because it tests the intended operational result. SLA loss checks can disqualify a degraded path even when the physical carrier remains established.
Incorrect Answers
A:The lower-cost compliant link is selected; a lower-cost failing link does not automatically win. 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 remote kiosk experiences intermittent missing packets despite its interface staying up, so the kiosk's new sessions move toward a qualifying member when the original exceeds loss tolerance is the better fit.
C:The reachable target produces valid health samples on both correctly functioning circuits. 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 remote kiosk experiences intermittent missing packets despite its interface staying up; the targeted response is the kiosk's new sessions move toward a qualifying member when the original exceeds loss tolerance.
D:After an authorized order swap, new eligible flows select the newly preferred equal-cost member. It could be appropriate when an operations team sees two SLA-compliant WAN links assigned identical cost values but asks why only the first was elected. However, that does not resolve the stated condition: a remote kiosk experiences intermittent missing packets despite its interface staying up. A more direct answer is the kiosk's new sessions move toward a qualifying member when the original exceeds loss tolerance.
Question 286
At a FortiSASE/SD-WAN site, this issue is reported: 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. What is the most direct technical change to address the stated requirement?
- Correlate SLA health-check events with member selection and session logs around the incident time
- Configure an active performance SLA with a reachable probe server on both members
- Distinguish link availability from SLA compliance and review the rule's qualifying-member selection
- Change the health-check destination to a representative reachable and permitted probe target
Explanation
Correct Answer
A:Correlate SLA health-check events with member selection and session logs around the incident time. SLA-driven steering can respond to packet loss, delay or probe failure without physical link-down events. The configuration alone must be followed by a functioning test: The logged SLA failure aligns with the observed traffic path change.
Incorrect Answers
B:Configure an active performance SLA with a reachable probe server on both members. 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 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 targeted response is correlate SLA health-check events with member selection and session logs around the incident time.
C:Distinguish link availability from SLA compliance and review the rule's qualifying-member selection. The outcome for that step belongs to an SD-WAN operator sees a link marked alive but the performance SLA map shows it misses the configured voice target. Here the decisive requirement concerns 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, so correlate SLA health-check events with member selection and session logs around the incident time is the better fit.
D:Change the health-check destination to a representative reachable and permitted probe target. It addresses a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works. In the reported environment, the missing behavior instead relates to 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 relevant choice is correlate SLA health-check events with member selection and session logs around the incident time.
Question 287
After the authorized change to move or refine the billing rule so the specific matching policy is considered before the broad catchall, which result actually demonstrates that this site's requirement is met? Initial issue: A configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member.
- Billing traffic matches the intended narrow rule and the generic rule handles remaining sessions
- New matching calls are steered toward the better-performing member under the configured metric
- The member change correlates with a documented SLA or eligibility change, not guesswork about policy order
- New payroll sessions choose the configured preferred eligible member
Explanation
Correct Answer
A:Billing traffic matches the intended narrow rule and the generic rule handles remaining sessions. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:New matching calls are steered toward the better-performing member under the configured metric. That is a useful action for a different circumstance: video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price. 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 billing traffic matches the intended narrow rule and the generic rule handles remaining sessions.
C: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 configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. The relevant choice is billing traffic matches the intended narrow rule and the generic rule handles remaining sessions.
D:New payroll sessions choose the configured preferred eligible member. The outcome for that step belongs to a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services. 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 billing traffic matches the intended narrow rule and the generic rule handles remaining sessions is the better fit.
Question 288
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit.
- Inspect the session's policy match and the outbound interface named in the effective policy
- Examine an identified conference flow and verify which SD-WAN rule it matches
- Examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names
- Inspect probe results and confirm whether the rule actually references their SLA target
Explanation
Correct Answer
D:Inspect probe results and confirm whether the rule actually references their SLA target. This check isolates the relevant control before the change. Physical interface state measures carrier, whereas SLA probes reveal end-to-end latency, jitter and loss.
Incorrect Answers
A:Inspect the session's policy match and the outbound interface named in the effective policy. That is a useful action for a different circumstance: 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. 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 inspect probe results and confirm whether the rule actually references their SLA target.
B:Examine an identified conference flow and verify which SD-WAN rule it matches. It addresses an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. 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 inspect probe results and confirm whether the rule actually references their SLA target.
C:Examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names. It could be appropriate when a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. However, that does not resolve the stated condition: a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit. A more direct answer is inspect probe results and confirm whether the rule actually references their SLA target.
Question 289
Given this incident — 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 administrator plans to enroll the ISP as a member of an Internet-only SD-WAN zone and define its firewall-policy treatment. Which technical principle justifies it?
- An SD-WAN zone is the logical policy interface, so wrong zone placement affects treatment of sessions
- Zones provide policy-level grouping, making distinct inspection by transport class possible
- Independent zone grouping enables separate Internet and private-overlay security policy paths
- Creating the zone alone does not enroll physical or tunnel interfaces as SD-WAN members
Explanation
Correct Answer
C:Independent zone grouping enables separate Internet and private-overlay security policy paths. This is why the proposed repair addresses the reported behavior; confirm by checking: Internet flows use the correct ISP zone and inspection profile without touching private-overlay policies.
Incorrect Answers
A:An SD-WAN zone is the logical policy interface, so wrong zone placement affects treatment of sessions. 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 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 independent zone grouping enables separate Internet and private-overlay security policy paths.
B:Zones provide policy-level grouping, making distinct inspection by transport class possible. 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: 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 independent zone grouping enables separate Internet and private-overlay security policy paths.
D:Creating the zone alone does not enroll physical or tunnel interfaces as SD-WAN members. The outcome for that step belongs to a FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member. Here the decisive requirement concerns 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, so independent zone grouping enables separate Internet and private-overlay security policy paths is the better fit.
Question 290
Given this incident — A helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. — the administrator plans to inspect the affected traffic's matched rule and egress details in SD-WAN/session logs. Which technical principle justifies it?
- Per-session policy and egress evidence can identify the forwarding decision behind a route change
- Historical logs preserve forwarding decisions from the event time while current routing may differ
- The causal clue comes from the chronology of health, route and traffic decisions rather than any one counter
- Usage visibility distinguishes aggregate demand from per-member forwarding behavior
Explanation
Correct Answer
A:Per-session policy and egress evidence can identify the forwarding decision behind a route change. This is why the proposed repair addresses the reported behavior; confirm by checking: The log records the expected rule and the backup-member selection for that transaction.
Incorrect Answers
B:Historical logs preserve forwarding decisions from the event time while current routing may differ. That is a useful action for a different circumstance: a team wants to identify which ISP path was used by a specific session before a provider outage. 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 per-session policy and egress evidence can identify the forwarding decision behind a route change.
C:The causal clue comes from the chronology of health, route and traffic decisions rather than any one counter. The outcome for that step belongs to an operator says a VPN application keeps failing over but cannot show whether the trigger was packet loss or a routing change. 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 per-session policy and egress evidence can identify the forwarding decision behind a route change is the better fit.
D:Usage visibility distinguishes aggregate demand from per-member forwarding behavior. It addresses a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. In the reported environment, the missing behavior instead relates to a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. The relevant choice is per-session policy and egress evidence can identify the forwarding decision behind a route change.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests