Question 490
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? An organization needs private TCP and UDP access to multiple office services without publishing public listener ports.
- An IPsec tunnel becomes established and remains stable before private-app traffic tests
- Approved TCP and UDP application tests succeed through the overlay without public exposure
- The private service is accessible to authorized remote users solely via the intended secure connector path
- A remote session completes request and response through the intended protected private path
Explanation
Correct Answer
B:Approved TCP and UDP application tests succeed through the overlay without public exposure. This is stronger than a saved configuration because it tests the intended operational result. SPA via hub overlays carries private application traffic through encrypted controlled connectivity.
Incorrect Answers
A:An IPsec tunnel becomes established and remains stable before private-app traffic tests. That is a useful action for a different circumstance: fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. The present case is constrained by an organization needs private TCP and UDP access to multiple office services without publishing public listener ports; the targeted response is approved TCP and UDP application tests succeed through the overlay without public exposure.
C:The private service is accessible to authorized remote users solely via the intended secure connector path. It could be appropriate when a secure private access rollout uses a hub-and-spoke VPN topology and engineers expect private traffic to be accessible without exposing on-prem applications to the public Internet. However, that does not resolve the stated condition: an organization needs private TCP and UDP access to multiple office services without publishing public listener ports. A more direct answer is approved TCP and UDP application tests succeed through the overlay without public exposure.
D:A remote session completes request and response through the intended protected private path. 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 an organization needs private TCP and UDP access to multiple office services without publishing public listener ports, so approved TCP and UDP application tests succeed through the overlay without public exposure is the better fit.
Question 491
After the authorized change to enroll the ISP as a member of an Internet-only SD-WAN zone and define its firewall-policy treatment, which result actually demonstrates that this site's requirement is met? Initial issue: 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.
- Internet flows use the correct ISP zone and inspection profile without touching private-overlay policies
- Private application traffic matches the intended overlay policy after the zone correction
- A restored member carries test packets and is visible in the rule's active selection
- 5G failover sessions match the same policy as other members in that zone
Explanation
Correct Answer
A:Internet flows use the correct ISP zone and inspection profile without touching private-overlay policies. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:Private application traffic matches the intended overlay policy after the zone correction. The outcome for that step belongs to during site migration, the team assigns an overlay tunnel to the ordinary Internet zone, then discovers it is subject to public-web policy handling. 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 internet flows use the correct ISP zone and inspection profile without touching private-overlay policies is the better fit.
C:A restored member carries test packets and is visible in the rule's active selection. It addresses the team sees a route via an SD-WAN zone but no actual WAN member is healthy under it. 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 internet flows use the correct ISP zone and inspection profile without touching private-overlay policies.
D:5G failover sessions match the same policy as other members in that zone. That is a useful action for a different circumstance: a company adds a new 5G interface but its existing WAN firewall policy covers only a named SD-WAN zone containing the older links. The present case is constrained by 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 targeted response is internet flows use the correct ISP zone and inspection profile without touching private-overlay policies.
Question 492
During implementation, the administrator observes: A remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. Which intervention targets the described fault rather than an adjacent workflow?
- Assign distinct FortiSASE endpoint profiles to the appropriate user groups with their intended device controls
- Define the intended compliance predicates explicitly and test missing-value behavior in the supported posture engine
- Correct the user/group targeting of the intended endpoint profile and synchronize membership
- Define the supported endpoint vulnerability or posture-tag condition and enforce it in the private-access policy
Explanation
Correct Answer
D:Define the supported endpoint vulnerability or posture-tag condition and enforce it in the private-access policy. Vulnerability-aware device posture can restrict endpoints independently of the user identity check. The acceptance check should show: A patched test endpoint receives the compliant tag while a deliberately vulnerable test endpoint receives the intended restriction.
Incorrect Answers
A:Assign distinct FortiSASE endpoint profiles to the appropriate user groups with their intended device controls. It addresses one employee group is permitted removable media use while everyone else must be restricted by endpoint policy. In the reported environment, the missing behavior instead relates to a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. The relevant choice is define the supported endpoint vulnerability or posture-tag condition and enforce it in the private-access policy.
B:Define the intended compliance predicates explicitly and test missing-value behavior in the supported posture engine. That is a useful action for a different circumstance: a department wants a policy to block access only when a specific compliance property is missing, not whenever any endpoint telemetry field is unavailable. The present case is constrained by a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications; the targeted response is define the supported endpoint vulnerability or posture-tag condition and enforce it in the private-access policy.
C:Correct the user/group targeting of the intended endpoint profile and synchronize membership. 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: a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. A more direct answer is define the supported endpoint vulnerability or posture-tag condition and enforce it in the private-access policy.
Question 493
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? An existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change.
- Run route lookup and firewall-policy matching against the new application address
- Review the session table entry for the payment flow, including interfaces and translation
- Check the route table for 0.0.0.0/0 and the selected member's gateway
- Inspect IPsec state, BGP neighbor status and advertised/received prefixes
Explanation
Correct Answer
A:Run route lookup and firewall-policy matching against the new application address. The observed evidence guides the targeted repair: Update the affected route and firewall address references for the new private prefix.
Incorrect Answers
B:Review the session table entry for the payment flow, including interfaces and translation. 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 an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change. The relevant choice is run route lookup and firewall-policy matching against the new application address.
C:Check the route table for 0.0.0.0/0 and the selected member's gateway. The outcome for that step belongs to an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. Here the decisive requirement concerns an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change, so run route lookup and firewall-policy matching against the new application address is the better fit.
D:Inspect IPsec state, BGP neighbor status and advertised/received prefixes. 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 an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change; the targeted response is run route lookup and firewall-policy matching against the new application address.
Question 494
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall.
- Check the route table for 0.0.0.0/0 and the selected member's gateway
- Compare session source translation and external public IP before and after the switchover
- Examine the exact prefix match, route source and resolved next hop for the affected destination
- Inspect the traffic log policy ID and action for the denied session
Explanation
Correct Answer
D:Inspect the traffic log policy ID and action for the denied session. This check isolates the relevant control before the change. Routing and steering determine path availability, while firewall policy decides whether traffic is permitted.
Incorrect Answers
A:Check the route table for 0.0.0.0/0 and the selected member's gateway. That is a useful action for a different circumstance: an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. The present case is constrained by a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall; the targeted response is inspect the traffic log policy ID and action for the denied session.
B:Compare session source translation and external public IP before and after the switchover. It could be appropriate when a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. However, that does not resolve the stated condition: a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. A more direct answer is inspect the traffic log policy ID and action for the denied session.
C:Examine the exact prefix match, route source and resolved next hop for the affected destination. It addresses an SD-WAN hub learns a private route over BGP but the branch still uses a competing less-specific static path for one destination. In the reported environment, the missing behavior instead relates to a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. The relevant choice is inspect the traffic log policy ID and action for the denied session.
Question 495
For a change review, the team proposes to filter FortiSASE threat events by user identity, policy and time interval because: A security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users. Which explanation connects the change to the underlying behavior?
- DLP incidents identify content-rule enforcement distinct from simple URL or authentication failures
- Failed logins are identity events and need separate interpretation from content-inspection threats
- Cross-log correlation can connect permitted sessions with subsequent security inspection events
- Attribution requires security-event context rather than relying on tenant-wide totals
Explanation
Correct Answer
D:Attribution requires security-event context rather than relying on tenant-wide totals. It directly explains the need to filter FortiSASE threat events by user identity, policy and time interval. The narrow validation is: The analyst can name the impacted users and the associated verified threat events.
Incorrect Answers
A:DLP incidents identify content-rule enforcement distinct from simple URL or authentication failures. It could be appropriate when an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. However, that does not resolve the stated condition: a security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users. A more direct answer is attribution requires security-event context rather than relying on tenant-wide totals.
B:Failed logins are identity events and need separate interpretation from content-inspection threats. That is a useful action for a different circumstance: a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. The present case is constrained by a security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users; the targeted response is attribution requires security-event context rather than relying on tenant-wide totals.
C:Cross-log correlation can connect permitted sessions with subsequent security inspection events. It addresses a FortiSASE security incident spans an employee's proxy session and a possible malware detection one minute later. In the reported environment, the missing behavior instead relates to a security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users. The relevant choice is attribution requires security-event context rather than relying on tenant-wide totals.
Question 496
After the authorized change to inspect application-control or inline-CASB security logs and the matched action, which result actually demonstrates that this site's requirement is met? Initial issue: Security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny.
- The incident report accurately distinguishes failed-authentication patterns from malware findings
- The report identifies the triggered IPS signature and whether traffic was blocked or monitored
- The log identifies the disallowed in-app action while permitted app sessions remain visible
- The evidence identifies whether the threat event belongs to the same user's session context
Explanation
Correct Answer
C:The log identifies the disallowed in-app action while permitted app sessions remain visible. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:The incident report accurately distinguishes failed-authentication patterns from malware findings. It addresses a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. In the reported environment, the missing behavior instead relates to security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. The relevant choice is the log identifies the disallowed in-app action while permitted app sessions remain visible.
B:The report identifies the triggered IPS signature and whether traffic was blocked or monitored. 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: security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. A more direct answer is the log identifies the disallowed in-app action while permitted app sessions remain visible.
D:The evidence identifies whether the threat event belongs to the same user's session context. The outcome for that step belongs to a FortiSASE security incident spans an employee's proxy session and a possible malware detection one minute later. Here the decisive requirement concerns security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny, so the log identifies the disallowed in-app action while permitted app sessions remain visible is the better fit.
Question 497
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users.
- Filter by user, timestamp and the test file's detected event category
- Inspect the sign-in outcomes, source addresses and account correlation in the audit window
- Inspect distinct affected identities and matched event categories in that window
- Search overlapping timestamps, username and application or destination fields in both log types
Explanation
Correct Answer
C:Inspect distinct affected identities and matched event categories in that window. The observed evidence guides the targeted repair: Filter FortiSASE threat events by user identity, policy and time interval.
Incorrect Answers
A:Filter by user, timestamp and the test file's detected event category. The outcome for that step belongs to a FortiSASE user reports that a malicious attachment was blocked, but the security team needs to know which threat control acted. Here the decisive requirement concerns a security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users, so inspect distinct affected identities and matched event categories in that window is the better fit.
B:Inspect the sign-in outcomes, source addresses and account correlation in the audit window. It addresses a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. In the reported environment, the missing behavior instead relates to a security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users. The relevant choice is inspect distinct affected identities and matched event categories in that window.
D:Search overlapping timestamps, username and application or destination fields in both log types. It could be appropriate when a FortiSASE security incident spans an employee's proxy session and a possible malware detection one minute later. However, that does not resolve the stated condition: a security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users. A more direct answer is inspect distinct affected identities and matched event categories in that window.
Question 498
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? An administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list.
- Compare member choices for multiple connections from one client and several different clients
- Check that emergency packets match the explicit SD-WAN rule and not only an Internet allow rule
- Compare which application or destination condition each matching rule contains
- Inspect the service classification in logs and the selected Internet-service rule criterion
Explanation
Correct Answer
D:Inspect the service classification in logs and the selected Internet-service rule criterion. This check isolates the relevant control before the change. Internet-service identification is designed for recognized services whose destinations may change.
Incorrect Answers
A:Compare member choices for multiple connections from one client and several different clients. It could be appropriate when the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. However, that does not resolve the stated condition: an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. A more direct answer is inspect the service classification in logs and the selected Internet-service rule criterion.
B:Check that emergency packets match the explicit SD-WAN rule and not only an Internet allow rule. That is a useful action for a different circumstance: 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 present case is constrained by an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list; the targeted response is inspect the service classification in logs and the selected Internet-service rule criterion.
C:Compare which application or destination condition each matching rule contains. It addresses a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. In the reported environment, the missing behavior instead relates to an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. The relevant choice is inspect the service classification in logs and the selected Internet-service rule criterion.
Question 499
Given this incident — A public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works. — the administrator plans to change the health-check destination to a representative reachable and permitted probe target. Which technical principle justifies it?
- The minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA
- Health results depend on the selected probe target and path; an unreachable probe endpoint can create a false failure signal
- Measured SLA state affects a rule only when that rule's selection logic actually uses it
- Health dashboards display measured probe results, not a static certification that a line has been repaired
Explanation
Correct Answer
B:Health results depend on the selected probe target and path; an unreachable probe endpoint can create a false failure signal. It directly explains the need to change the health-check destination to a representative reachable and permitted probe target. The narrow validation is: The reachable target produces valid health samples on both correctly functioning circuits.
Incorrect Answers
A:The minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA. That is a useful action for a different circumstance: the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. The present case is constrained by a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works; the targeted response is health results depend on the selected probe target and path; an unreachable probe endpoint can create a false failure signal.
C:Measured SLA state affects a rule only when that rule's selection logic actually uses it. It could be appropriate when an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit. However, that does not resolve the stated condition: a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works. A more direct answer is health results depend on the selected probe target and path; an unreachable probe endpoint can create a false failure signal.
D:Health dashboards display measured probe results, not a static certification that a line has been repaired. The outcome for that step belongs to a branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance. Here the decisive requirement concerns a public probe address is blocked by the provider on one interface, causing its SLA to report failed while real application traffic works, so health results depend on the selected probe target and path; an unreachable probe endpoint can create a false failure signal is the better fit.
Question 500
The team is troubleshooting the following Fortinet 7.6 deployment: The company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. Which specific corrective action should be prioritized?
- Inspect interface preference order for the Lowest Cost (SLA) rule
- Change the health-check destination to a representative reachable and permitted probe target
- Set the rule's supported minimum SLA-meeting member count to two
- Configure a latency target in the performance SLA and bind it to the call-center rule
Explanation
Correct Answer
C:Set the rule's supported minimum SLA-meeting member count to two. The minimum-member parameter prevents a rule from taking effect unless enough members satisfy its SLA. The configuration alone must be followed by a functioning test: The rule activates only while at least two members satisfy its required SLA.
Incorrect Answers
A:Inspect interface preference order for the Lowest Cost (SLA) rule. 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: the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. A more direct answer is set the rule's supported minimum SLA-meeting member count to two.
B: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 the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule. The relevant choice is set the rule's supported minimum SLA-meeting member count to two.
D:Configure a latency target in the performance SLA and bind it to the call-center rule. The outcome for that step belongs to a call-center SLA must avoid any WAN link whose one-way delay is above an agreed threshold. Here the decisive requirement concerns the company requires two healthy members to be available before activating a certain high-availability SD-WAN rule, so set the rule's supported minimum SLA-meeting member count to two is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests