Question 340
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service.
- Inspect deep-inspection mode, exemption entries and the affected SSO session failure
- Inspect the DLP profile match rules and whether the application traffic is decryptable where required
- Inspect the applied inline-CASB profile and the event details of a test user action
- Inspect the presented certificate chain and local trusted CA store
Explanation
Correct Answer
C:Inspect the applied inline-CASB profile and the event details of a test user action. The observed evidence guides the targeted repair: Use application control with inline-CASB capability in the relevant FortiSASE inspection profile.
Incorrect Answers
A:Inspect deep-inspection mode, exemption entries and the affected SSO session failure. It could be appropriate when an agentless SWG with SSO must inspect HTTPS but has a certificate-inspection exception for every authentication domain. However, that does not resolve the stated condition: a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service. A more direct answer is inspect the applied inline-CASB profile and the event details of a test user action.
B:Inspect the DLP profile match rules and whether the application traffic is decryptable where required. It addresses a company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications. In the reported environment, the missing behavior instead relates to a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service. The relevant choice is inspect the applied inline-CASB profile and the event details of a test user action.
D:Inspect the presented certificate chain and local trusted CA store. The outcome for that step belongs to a browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions. Here the decisive requirement concerns a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service, so inspect the applied inline-CASB profile and the event details of a test user action is the better fit.
Question 341
After the authorized change to compare relevant web-filter security events across defined before-and-after reporting periods, which result actually demonstrates that this site's requirement is met? Initial issue: A security officer needs proof that web-category policy violations increased after a recent configuration change.
- The resulting report shows comparable event trends with the change timestamp documented
- Representative traffic and security events arrive at the approved collector with consistent timestamps
- The summary's anomalous interval can be reconciled with its individual security events
- The report shows blocked-event trends per cohort alongside enough traffic context to interpret the change
Explanation
Correct Answer
A:The resulting report shows comparable event trends with the change timestamp documented. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:Representative traffic and security events arrive at the approved collector with consistent timestamps. The outcome for that step belongs to a regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window. Here the decisive requirement concerns a security officer needs proof that web-category policy violations increased after a recent configuration change, so the resulting report shows comparable event trends with the change timestamp documented is the better fit.
C:The summary's anomalous interval can be reconciled with its individual security events. It addresses a quarterly audit asks for a summary of FortiSASE security events and the ability to investigate one anomalous period in detail. In the reported environment, the missing behavior instead relates to a security officer needs proof that web-category policy violations increased after a recent configuration change. The relevant choice is the resulting report shows comparable event trends with the change timestamp documented.
D:The report shows blocked-event trends per cohort alongside enough traffic context to interpret the change. That is a useful action for a different circumstance: 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 present case is constrained by a security officer needs proof that web-category policy violations increased after a recent configuration change; the targeted response is the resulting report shows comparable event trends with the change timestamp documented.
Question 342
During implementation, the administrator observes: A branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session. Which intervention targets the described fault rather than an adjacent workflow?
- Use a defined SD-WAN rule and inspect its selected member against current health and match criteria
- Update the intended LAN-to-Internet firewall policy to use the configured SD-WAN zone, with source NAT if the design requires it
- Apply the required security profiles to the matching allow firewall policy independently of SD-WAN member setup
- Build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate
Explanation
Correct Answer
A:Use a defined SD-WAN rule and inspect its selected member against current health and match criteria. A specific steering rule explains the egress decision more reliably than assuming interface order alone. The configuration alone must be followed by a functioning test: The rule ID and selected member align with actual session-forwarding evidence.
Incorrect Answers
B:Update the intended LAN-to-Internet firewall policy to use the configured SD-WAN zone, with source NAT if the design requires it. The outcome for that step belongs to 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. Here the decisive requirement concerns a branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session, so use a defined SD-WAN rule and inspect its selected member against current health and match criteria is the better fit.
C:Apply the required security profiles to the matching allow firewall policy independently of SD-WAN member setup. That is a useful action for a different circumstance: a branch was built with two SD-WAN members, but a team assumes this alone automatically adds application inspection to client sessions. The present case is constrained by a branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session; the targeted response is use a defined SD-WAN rule and inspect its selected member against current health and match criteria.
D:Build a routed IPsec overlay member for private destinations and keep Internet underlay steering separate. It addresses a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. In the reported environment, the missing behavior instead relates to a branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session. The relevant choice is use a defined SD-WAN rule and inspect its selected member against current health and match criteria.
Question 343
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops.
- An authenticated browser session reaches permitted web destinations through the SASE gateway and creates logs
- The new starter receives the intended departmental policy after correct group mapping
- The test assertion validates and the user signs in with the expected claims
- A pilot laptop connects to FortiSASE and its Internet sessions appear under the intended user policy
Explanation
Correct Answer
D:A pilot laptop connects to FortiSASE and its Internet sessions appear under the intended user policy. This is stronger than a saved configuration because it tests the intended operational result. FortiClient is the endpoint agent that steers the chosen remote traffic and receives managed connection settings.
Incorrect Answers
A:An authenticated browser session reaches permitted web destinations through the SASE gateway and creates logs. It addresses external contractors cannot install FortiClient, but they must use secure browser access through a managed gateway. In the reported environment, the missing behavior instead relates to a workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops. The relevant choice is a pilot laptop connects to FortiSASE and its Internet sessions appear under the intended user policy.
B:The new starter receives the intended departmental policy after correct group mapping. That is a useful action for a different circumstance: a new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy. The present case is constrained by a workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops; the targeted response is a pilot laptop connects to FortiSASE and its Internet sessions appear under the intended user policy.
C:The test assertion validates and the user signs in with the expected claims. It could be appropriate when a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. However, that does not resolve the stated condition: a workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops. A more direct answer is a pilot laptop connects to FortiSASE and its Internet sessions appear under the intended user policy.
Question 344
For the stated scenario, what is the most important remaining blind spot after the proposed correction? Users report browser certificate warnings immediately after enabling deep inspection for an agentless secure web gateway.
- A successful ping to the hub interface does not establish end-to-end private-network access
- Ignoring CA trust prompts can break HTTPS access despite valid SSO credentials
- An ordinary Internet access policy at the SASE PoP does not automatically create private-site connectivity
- Assuming every local FortiManager setting automatically maps to FortiSASE can mislead the rollout
Explanation
Correct Answer
B:Ignoring CA trust prompts can break HTTPS access despite valid SSO credentials. The planned change can still miss the requirement if this condition is left unresolved. TLS inspection re-signs server certificates; client trust must cover the inspection CA.
Incorrect Answers
A:A successful ping to the hub interface does not establish end-to-end private-network access. That is a useful action for a different circumstance: a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. The present case is constrained by users report browser certificate warnings immediately after enabling deep inspection for an agentless secure web gateway; the targeted response is ignoring CA trust prompts can break HTTPS access despite valid SSO credentials.
C:An ordinary Internet access policy at the SASE PoP does not automatically create private-site connectivity. It could be appropriate when a customer wants remote FortiClient users to reach a database behind an existing FortiGate SD-WAN hub rather than exposing the database publicly. However, that does not resolve the stated condition: users report browser certificate warnings immediately after enabling deep inspection for an agentless secure web gateway. A more direct answer is ignoring CA trust prompts can break HTTPS access despite valid SSO credentials.
D:Assuming every local FortiManager setting automatically maps to FortiSASE can mislead the rollout. The outcome for that step belongs to fortiSASE configuration is being centrally managed, but changes made in FortiManager do not appear in the remote tenant. Here the decisive requirement concerns users report browser certificate warnings immediately after enabling deep inspection for an agentless secure web gateway, so ignoring CA trust prompts can break HTTPS access despite valid SSO credentials is the better fit.
Question 345
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member.
- Inspect IPsec state, BGP neighbor status and advertised/received prefixes
- Inspect the route lookup for a specific protected subnet and its policy match
- Inspect current DHCP lease, gateway resolution and affected static-route next hop
- Check ARP or route resolution for the configured gateway before the remote probe destination
Explanation
Correct Answer
D:Check ARP or route resolution for the configured gateway before the remote probe destination. This check isolates the relevant control before the change. Health probes cannot succeed through an unreachable gateway even if their target is valid.
Incorrect Answers
A:Inspect IPsec state, BGP neighbor status and advertised/received prefixes. It addresses 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. In the reported environment, the missing behavior instead relates to a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member. The relevant choice is check ARP or route resolution for the configured gateway before the remote probe destination.
B:Inspect the route lookup for a specific protected subnet and its policy match. That is a useful action for a different circumstance: following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub. The present case is constrained by a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member; the targeted response is check ARP or route resolution for the configured gateway before the remote probe destination.
C:Inspect current DHCP lease, gateway resolution and affected static-route next hop. It could be appropriate when a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. However, that does not resolve the stated condition: a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member. A more direct answer is check ARP or route resolution for the configured gateway before the remote probe destination.
Question 346
A proposed repair is to use application control with inline-CASB capability in the relevant FortiSASE inspection profile. Why should that repair work in this particular situation? Context: A legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service.
- Categorization filters web destinations by content classification instead of treating all hosts at one IP equally
- Profile-group selection at policy level can differentiate inspection by user cohort
- Security profile groups bundle inspection settings and can be selected per eligible traffic policy
- Inline application-aware controls can distinguish activity within supported cloud applications rather than only domain access
Explanation
Correct Answer
D:Inline application-aware controls can distinguish activity within supported cloud applications rather than only domain access. It directly explains the need to use application control with inline-CASB capability in the relevant FortiSASE inspection profile. The narrow validation is: An identified application action produces the intended monitor or block event while basic permitted access remains available.
Incorrect Answers
A:Categorization filters web destinations by content classification instead of treating all hosts at one IP equally. That is a useful action for a different circumstance: employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone. The present case is constrained by a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service; the targeted response is inline application-aware controls can distinguish activity within supported cloud applications rather than only domain access.
B: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 legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service. The relevant choice is inline application-aware controls can distinguish activity within supported cloud applications rather than only domain access.
C:Security profile groups bundle inspection settings and can be selected per eligible traffic policy. It could be appropriate when a remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access. However, that does not resolve the stated condition: a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service. A more direct answer is inline application-aware controls can distinguish activity within supported cloud applications rather than only domain access.
Question 347
At a FortiSASE/SD-WAN site, this issue is reported: An SD-WAN operator sees a rule reporting two eligible members but wants to confirm which member was actually used for a payment flow. What is the most direct technical change to address the stated requirement?
- Inspect the affected traffic's matched rule and egress details in SD-WAN/session logs
- Analyze SD-WAN health-check events alongside traffic and member-selection logs for the affected time
- Filter traffic logs by the dedicated rule and compare matching and nonmatching application sessions
- Inspect the selected-member information in per-session and SD-WAN rule diagnostics
Explanation
Correct Answer
D:Inspect the selected-member information in per-session and SD-WAN rule diagnostics. Eligibility is a candidate set; the selected path must be determined for the specific traffic instance. The acceptance check should show: The actual traffic log or session record names the intended selected member.
Incorrect Answers
A:Inspect the affected traffic's matched rule and egress details in SD-WAN/session logs. 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 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 inspect the selected-member information in per-session and SD-WAN rule diagnostics.
B:Analyze SD-WAN health-check events alongside traffic and member-selection logs for the affected time. 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 inspect the selected-member information in per-session and SD-WAN rule diagnostics.
C:Filter traffic logs by the dedicated rule and compare matching and nonmatching application sessions. 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: 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 inspect the selected-member information in per-session and SD-WAN rule diagnostics.
Question 348
A proposed repair is to reference the intended SLA target explicitly in the rule's steering configuration. Why should that repair work in this particular situation? Context: An administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit.
- Health results depend on the selected probe target and path; an unreachable probe endpoint can create a false failure signal
- Passive monitoring derives link quality from existing traversing traffic rather than generating active probes
- Measured SLA state affects a rule only when that rule's selection logic actually uses it
- With equal costs among qualifying links, interface preference determines the selected link
Explanation
Correct Answer
C:Measured SLA state affects a rule only when that rule's selection logic actually uses it. This is why the proposed repair addresses the reported behavior; confirm by checking: Changing measured quality produces a corresponding member-selection change for the voice rule.
Incorrect Answers
A:Health results depend on the selected probe target and path; an unreachable probe endpoint can create a false failure signal. 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 an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit. The relevant choice is measured SLA state affects a rule only when that rule's selection logic actually uses it.
B:Passive monitoring derives link quality from existing traversing traffic rather than generating active probes. The outcome for that step belongs to a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use. Here the decisive requirement concerns an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit, so measured SLA state affects a rule only when that rule's selection logic actually uses it is the better fit.
D:With equal costs among qualifying links, interface preference determines the selected link. 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: an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit. A more direct answer is measured SLA state affects a rule only when that rule's selection logic actually uses it.
Question 349
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory.
- A dashboard cannot show meaningful SLA quality when no health-check target is configured
- A backup interface absent from monitoring should not be assumed SLA compliant merely because it is up
- Member priority by itself cannot enforce which source identities may enter the restricted overlay
- A static route pointing to a zone does not automatically populate that zone with members
Explanation
Correct Answer
A:A dashboard cannot show meaningful SLA quality when no health-check target is configured. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:A backup interface absent from monitoring should not be assumed SLA compliant merely because it is up. That is a useful action for a different circumstance: the WAN team configured a performance SLA only for the preferred link; the backup has no comparable quality telemetry. The present case is constrained by a new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory; the targeted response is a dashboard cannot show meaningful SLA quality when no health-check target is configured.
C:Member priority by itself cannot enforce which source identities may enter the restricted overlay. 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 new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory, so a dashboard cannot show meaningful SLA quality when no health-check target is configured is the better fit.
D: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 deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory. The relevant choice is a dashboard cannot show meaningful SLA quality when no health-check target is configured.
Question 350
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? A remote-work tenant plans to reuse common web-filter and IPS profiles across hundreds of users, with only selected groups receiving additional controls.
- Inspect the tenant's active subscriptions and whether the required capability is included
- Inspect policy-to-profile-group binding for two user cohorts with different requirements
- Review policy mandates against the tenant's actual allowed service regions and logging arrangements
- Check actual PoP assignment and network path latency from representative users in the affected area
Explanation
Correct Answer
B:Inspect policy-to-profile-group binding for two user cohorts with different requirements. This check isolates the relevant control before the change. A profile group provides centrally defined inspection behavior that can be selected by relevant policies.
Incorrect Answers
A:Inspect the tenant's active subscriptions and whether the required capability is included. It could be appropriate when a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. However, that does not resolve the stated condition: a remote-work tenant plans to reuse common web-filter and IPS profiles across hundreds of users, with only selected groups receiving additional controls. A more direct answer is inspect policy-to-profile-group binding for two user cohorts with different requirements.
C:Review policy mandates against the tenant's actual allowed service regions and logging arrangements. That is a useful action for a different circumstance: an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision. The present case is constrained by a remote-work tenant plans to reuse common web-filter and IPS profiles across hundreds of users, with only selected groups receiving additional controls; the targeted response is inspect policy-to-profile-group binding for two user cohorts with different requirements.
D:Check actual PoP assignment and network path latency from representative users in the affected area. The outcome for that step belongs to the SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband. Here the decisive requirement concerns a remote-work tenant plans to reuse common web-filter and IPS profiles across hundreds of users, with only selected groups receiving additional controls, so inspect policy-to-profile-group binding for two user cohorts with different requirements is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests