Question 550
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? Following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub.
- Check applicable policy routes and their conditions for the sample source/destination
- Compare route lookup for the private server prefix and for an external destination
- Inspect the route lookup for a specific protected subnet and its policy match
- Inspect the traffic log policy ID and action for the denied session
Explanation
Correct Answer
C:Inspect the route lookup for a specific protected subnet and its policy match. The observed evidence guides the targeted repair: Install or correct the private route to resolve through the proper overlay zone and enforce its firewall policy.
Incorrect Answers
A:Check applicable policy routes and their conditions for the sample source/destination. It addresses an internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule. In the reported environment, the missing behavior instead relates to following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub. The relevant choice is inspect the route lookup for a specific protected subnet and its policy match.
B:Compare route lookup for the private server prefix and for an external destination. The outcome for that step belongs to a branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination. Here the decisive requirement concerns following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub, so inspect the route lookup for a specific protected subnet and its policy match is the better fit.
D:Inspect the traffic log policy ID and action for the denied session. It could be appropriate when a security operator finds an SD-WAN rule showing the expected preferred member, yet a web session is denied at the firewall. However, that does not resolve the stated condition: following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub. A more direct answer is inspect the route lookup for a specific protected subnet and its policy match.
Question 551
At a FortiSASE/SD-WAN site, this issue is reported: A security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. What is the most direct technical change to address the stated requirement?
- Create or assign a narrowly targeted security profile group to the intended user-group policy
- Review the exemption and narrow it to justified destinations before relying on content-based protection
- Apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events
- Review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust
Explanation
Correct Answer
C:Apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events. Intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation. The configuration alone must be followed by a functioning test: A controlled security test produces the expected IPS event or block decision.
Incorrect Answers
A:Create or assign a narrowly targeted security profile group to the intended user-group policy. 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 security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. The relevant choice is apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events.
B:Review the exemption and narrow it to justified destinations before relying on content-based protection. The outcome for that step belongs to a FortiSASE inspection policy protects web downloads but remote staff use encrypted traffic exempted from all deep inspection rules. Here the decisive requirement concerns a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE, so apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events is the better fit.
D:Review unsupported exemptions and configure a compatible deep-inspection policy and endpoint certificate trust. 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 security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. A more direct answer is apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events.
Question 552
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks.
- Compare session source translation and external public IP before and after the switchover
- Inspect the routing table and gateway or tunnel resolution for the destination
- Check competing route entries and chosen FIB next hop for the exact destination
- Run route lookup and firewall-policy matching against the new application address
Explanation
Correct Answer
C:Check competing route entries and chosen FIB next hop for the exact destination. The observed evidence guides the targeted repair: Inspect longest-prefix, administrative distance and route resolution for the affected address first.
Incorrect Answers
A: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 FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks. A more direct answer is check competing route entries and chosen FIB next hop for the exact destination.
B:Inspect the routing table and gateway or tunnel resolution for the destination. The outcome for that step belongs to a FortiGate has a manual SD-WAN rule preferring WAN2, but a route lookup for the destination has no usable next hop. Here the decisive requirement concerns a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks, so check competing route entries and chosen FIB next hop for the exact destination is the better fit.
D:Run route lookup and firewall-policy matching against the new application address. It addresses an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change. In the reported environment, the missing behavior instead relates to a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks. The relevant choice is check competing route entries and chosen FIB next hop for the exact destination.
Question 553
The team plans to inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? 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.
- A static route table screenshot alone cannot establish past per-session forwarding
- A generic implicit rule cannot enforce the specific payroll preference when a suitable custom rule is required
- A broad provider subnet alone may cause unintended traffic to share the conference path
- A static rule definition alone cannot show the dynamic decision made for an affected session
Explanation
Correct Answer
A:A static route table screenshot alone cannot establish past per-session forwarding. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:A generic implicit rule cannot enforce the specific payroll preference when a suitable custom rule is required. That is a useful action for a different circumstance: a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services. The present case is constrained by an SD-WAN operator wants to prove that a payment session left through the correct tunnel after an incident, rather than infer from routes alone; the targeted response is a static route table screenshot alone cannot establish past per-session forwarding.
C:A broad provider subnet alone may cause unintended traffic to share the conference path. The outcome for that step belongs to a security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider. Here the decisive requirement concerns an SD-WAN operator wants to prove that a payment session left through the correct tunnel after an incident, rather than infer from routes alone, so a static route table screenshot alone cannot establish past per-session forwarding is the better fit.
D:A static rule definition alone cannot show the dynamic decision made for an affected session. 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 an SD-WAN operator wants to prove that a payment session left through the correct tunnel after an incident, rather than infer from routes alone. The relevant choice is a static route table screenshot alone cannot establish past per-session forwarding.
Question 554
The team is troubleshooting the following Fortinet 7.6 deployment: An administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams. Which specific corrective action should be prioritized?
- Investigate the independent telemetry-connectivity posture condition instead of treating antivirus alone as full compliance
- Refresh endpoint posture reporting and verify the rule's effective match data before relaxing policy
- Constrain the pilot profile to a narrowly defined test user or endpoint group
- Stage the baseline through a limited pilot group and validate enforcement before broader rollout
Explanation
Correct Answer
C:Constrain the pilot profile to a narrowly defined test user or endpoint group. Profiles must be scoped to their target populations to avoid unintended fleet-wide change. The configuration alone must be followed by a functioning test: Only pilot devices receive the new requirements while other users retain their prior settings.
Incorrect Answers
A:Investigate the independent telemetry-connectivity posture condition instead of treating antivirus alone as full compliance. It could be appropriate when a managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service. 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 constrain the pilot profile to a narrowly defined test user or endpoint group.
B: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 administrator copies a strict endpoint profile for a pilot but accidentally applies it to the whole tenant, disrupting unrelated teams, so constrain the pilot profile to a narrowly defined test user or endpoint group is the better fit.
D:Stage the baseline through a limited pilot group and validate enforcement before broader rollout. It addresses an organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once. 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 constrain the pilot profile to a narrowly defined test user or endpoint group.
Question 555
The team plans to apply DNS-filter settings where supported to the relevant FortiSASE policy profile for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests.
- A successful SSO login does not erase high-severity vulnerability findings
- Successful SAML authentication alone does not prove acceptable endpoint security posture
- A web-filter-only assumption can miss DNS-based activity that never generates a standard web request
- An inventory dashboard that reports posture without enforcing it does not satisfy conditional-access goals
Explanation
Correct Answer
C:A web-filter-only assumption can miss DNS-based activity that never generates a standard web request. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:A successful SSO login does not erase high-severity vulnerability findings. The outcome for that step belongs to a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. Here the decisive requirement concerns a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests, so a web-filter-only assumption can miss DNS-based activity that never generates a standard web request is the better fit.
B:Successful SAML authentication alone does not prove acceptable endpoint security posture. It addresses a company requires an endpoint to have a working antivirus product before it may receive the normal remote-access permissions. In the reported environment, the missing behavior instead relates to a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests. The relevant choice is a web-filter-only assumption can miss DNS-based activity that never generates a standard web request.
D:An inventory dashboard that reports posture without enforcing it does not satisfy conditional-access goals. It could be appropriate when security wants a noncompliant laptop to be unable to access protected company applications until it passes device checks. However, that does not resolve the stated condition: a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests. A more direct answer is a web-filter-only assumption can miss DNS-based activity that never generates a standard web request.
Question 556
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A service provider reuses a FortiGate SD-WAN hub for FortiSASE SPA and wants to confirm BGP is functioning, not only an IPsec phase-one tunnel.
- Inspect BGP neighbor state and the expected route in the routing table
- Inspect the denied session's source/destination and matching FortiGate policy ID
- Inspect advertised prefixes and active routes from both hub connections
- Inspect the connector's configured peer and IKE negotiation destination during connection attempts
Explanation
Correct Answer
A:Inspect BGP neighbor state and the expected route in the routing table. The observed evidence guides the targeted repair: Validate BGP adjacency and learned private routes across the tunnel.
Incorrect Answers
B:Inspect the denied session's source/destination and matching FortiGate policy ID. That is a useful action for a different circumstance: a private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet. The present case is constrained by a service provider reuses a FortiGate SD-WAN hub for FortiSASE SPA and wants to confirm BGP is functioning, not only an IPsec phase-one tunnel; the targeted response is inspect BGP neighbor state and the expected route in the routing table.
C:Inspect advertised prefixes and active routes from both hub connections. The outcome for that step belongs to an organization adds a second FortiGate hub for resilience but has not defined which private prefixes each hub advertises. Here the decisive requirement concerns a service provider reuses a FortiGate SD-WAN hub for FortiSASE SPA and wants to confirm BGP is functioning, not only an IPsec phase-one tunnel, so inspect BGP neighbor state and the expected route in the routing table is the better fit.
D:Inspect the connector's configured peer and IKE negotiation destination during connection attempts. It addresses after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer. In the reported environment, the missing behavior instead relates to a service provider reuses a FortiGate SD-WAN hub for FortiSASE SPA and wants to confirm BGP is functioning, not only an IPsec phase-one tunnel. The relevant choice is inspect BGP neighbor state and the expected route in the routing table.
Question 557
During implementation, the administrator observes: A remote client receives an intrusion-prevention alert while accessing an internal application through SASE. Which intervention targets the described fault rather than an adjacent workflow?
- Inspect relevant antivirus or file-security events in FortiSASE security logs
- Review DLP or relevant inline SaaS security events for the sensitive-content match
- Inspect the IPS detection event and its signature/action details before modifying access policy
- Filter FortiSASE threat events by user identity, policy and time interval
Explanation
Correct Answer
C:Inspect the IPS detection event and its signature/action details before modifying access policy. An IPS event records traffic behavior matching a threat signature, not simply route choice. The configuration alone must be followed by a functioning test: The report identifies the triggered IPS signature and whether traffic was blocked or monitored.
Incorrect Answers
A:Inspect relevant antivirus or file-security events in FortiSASE security logs. It could be appropriate when a FortiSASE user reports that a malicious attachment was blocked, but the security team needs to know which threat control acted. However, that does not resolve the stated condition: a remote client receives an intrusion-prevention alert while accessing an internal application through SASE. A more direct answer is inspect the IPS detection event and its signature/action details before modifying access policy.
B:Review DLP or relevant inline SaaS security events for the sensitive-content match. The outcome for that step belongs to an employee attempts to upload a restricted customer record to a collaboration app and receives a policy block. Here the decisive requirement concerns a remote client receives an intrusion-prevention alert while accessing an internal application through SASE, so inspect the IPS detection event and its signature/action details before modifying access policy is the better fit.
D:Filter FortiSASE threat events by user identity, policy and time interval. It addresses a security-event dashboard shows a sharp increase in malicious-web detections, but analysts cannot identify the affected users. In the reported environment, the missing behavior instead relates to a remote client receives an intrusion-prevention alert while accessing an internal application through SASE. The relevant choice is inspect the IPS detection event and its signature/action details before modifying access policy.
Question 558
At a FortiSASE/SD-WAN site, this issue is reported: Two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout. What is the most direct technical change to address the stated requirement?
- Make an overlay-specific zone and reference that zone in a narrow firewall policy for the authorized users
- Create an overlay-only SD-WAN zone and place the two VPN tunnel interfaces within it
- Treat member and zone configuration as persistent objects and remove them separately only if the design requires it
- Reassign the overlay member to a dedicated private zone and align routing and policy scope
Explanation
Correct Answer
B:Create an overlay-only SD-WAN zone and place the two VPN tunnel interfaces within it. Member zoning can separate overlay transports from Internet underlays for policy matching. The acceptance check should show: Private traffic may steer between overlays while the Internet firewall policy still targets underlays.
Incorrect Answers
A:Make an overlay-specific zone and reference that zone in a narrow firewall policy for the authorized users. It could be appropriate when a site should limit one overlay circuit to a restricted group of users, unlike unrestricted Internet underlays. However, that does not resolve the stated condition: two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout. A more direct answer is create an overlay-only SD-WAN zone and place the two VPN tunnel interfaces within it.
C:Treat member and zone configuration as persistent objects and remove them separately only if the design requires it. The outcome for that step belongs to a network operator assumes deleting an SD-WAN rule also deletes the shared zone's member definitions. Here the decisive requirement concerns two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout, so create an overlay-only SD-WAN zone and place the two VPN tunnel interfaces within it is the better fit.
D:Reassign the overlay member to a dedicated private zone and align routing and policy scope. That is a useful action for a different circumstance: during site migration, the team assigns an overlay tunnel to the ordinary Internet zone, then discovers it is subject to public-web policy handling. The present case is constrained by two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout; the targeted response is create an overlay-only SD-WAN zone and place the two VPN tunnel interfaces within it.
Question 559
The team plans to inspect and reconcile policy routing with SD-WAN route and rule evaluation before predicting the egress member for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? An internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule.
- Simply rearranging interface preference does not satisfy an unmet numerical minimum
- Ignoring a matching policy route can lead to false conclusions about SD-WAN rule behavior
- A manual-only priority rule would not use the defined cost comparison in the same way
- Source-based hashing should not be represented as a guarantee of per-connection even balance for one user
Explanation
Correct Answer
B:Ignoring a matching policy route can lead to false conclusions about SD-WAN rule behavior. The planned change can still miss the requirement if this condition is left unresolved. Policy routes can affect forwarding independently of ordinary destination route and member preference.
Incorrect Answers
A:Simply rearranging interface preference does not satisfy an unmet numerical minimum. The outcome for that step belongs to after a data-center maintenance event, a configured rule remains disabled because its minimum number of SLA-passing members is three but only two are healthy. Here the decisive requirement concerns an internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule, so ignoring a matching policy route can lead to false conclusions about SD-WAN rule behavior is the better fit.
C:A manual-only priority rule would not use the defined cost comparison in the same way. That is a useful action for a different circumstance: two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access. The present case is constrained by an internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule; the targeted response is ignoring a matching policy route can lead to false conclusions about SD-WAN rule behavior.
D:Source-based hashing should not be represented as a guarantee of per-connection even balance for one user. 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 internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule. A more direct answer is ignoring a matching policy route can lead to false conclusions about SD-WAN rule behavior.
Question 560
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: 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.
- Check the SD-WAN member list and each interface's administrative and operational state
- Inspect whether the VPN tunnel is established and whether routes to private prefixes use the overlay zone
- Inspect probe results and confirm whether the rule actually references their SLA target
- Inspect the session's policy match and the outbound interface named in the effective policy
Explanation
Correct Answer
A:Check the SD-WAN member list and each interface's administrative and operational state. The observed evidence guides the targeted repair: Add both WAN interfaces as SD-WAN members in an appropriate zone before defining the steering rule.
Incorrect Answers
B:Inspect whether the VPN tunnel is established and whether routes to private prefixes use the overlay zone. That is a useful action for a different circumstance: 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 present case is constrained by 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 targeted response is check the SD-WAN member list and each interface's administrative and operational state.
C:Inspect probe results and confirm whether the rule actually references their SLA target. The outcome for that step belongs to a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit. Here the decisive requirement concerns 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, so check the SD-WAN member list and each interface's administrative and operational state is the better fit.
D:Inspect the session's policy match and the outbound interface named in the effective policy. 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 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 relevant choice is check the SD-WAN member list and each interface's administrative and operational state.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests