Question 360
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination.
- Best-quality steering may prefer a single superior path rather than share load
- A broad default route does not replace a missing specific private-network route
- A manual-only priority rule would not use the defined cost comparison in the same way
- A broad provider subnet alone may cause unintended traffic to share the conference path
Explanation
Correct Answer
B:A broad default route does not replace a missing specific private-network route. The planned change can still miss the requirement if this condition is left unresolved. Longest-prefix matching normally distinguishes specific private application networks from the default route.
Incorrect Answers
A:Best-quality steering may prefer a single superior path rather than share load. That is a useful action for a different circumstance: a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. The present case is constrained by a branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination; the targeted response is a broad default route does not replace a missing specific private-network route.
C:A manual-only priority rule would not use the defined cost comparison in the same way. It could be appropriate when two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access. However, that does not resolve the stated condition: a branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination. A more direct answer is a broad default route does not replace a missing specific private-network route.
D: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 a branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination, so a broad default route does not replace a missing specific private-network route is the better fit.
Question 361
Given this incident — A remote user can reach an internal server by private IP but not by its internal hostname through the SPA connection. — the administrator plans to configure and validate internal DNS resolution and any required DNS redirection for private domains. Which technical principle justifies it?
- Name resolution is separate from overlay routing and may require explicit private-domain handling
- The SPA overlay depends on a functioning encrypted PoP-to-hub transport
- Peer addressing must match the current hub for an IPsec overlay to negotiate correctly
- A multi-hub design requires coherent routing as well as tunnel availability to maintain private reachability
Explanation
Correct Answer
A:Name resolution is separate from overlay routing and may require explicit private-domain handling. This is why the proposed repair addresses the reported behavior; confirm by checking: The internal name resolves to the correct private address and the application connects over SPA.
Incorrect Answers
B:The SPA overlay depends on a functioning encrypted PoP-to-hub transport. 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 a remote user can reach an internal server by private IP but not by its internal hostname through the SPA connection; the targeted response is name resolution is separate from overlay routing and may require explicit private-domain handling.
C:Peer addressing must match the current hub for an IPsec overlay to negotiate correctly. The outcome for that step belongs to after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer. Here the decisive requirement concerns a remote user can reach an internal server by private IP but not by its internal hostname through the SPA connection, so name resolution is separate from overlay routing and may require explicit private-domain handling is the better fit.
D:A multi-hub design requires coherent routing as well as tunnel availability to maintain private reachability. It addresses an organization adds a second FortiGate hub for resilience but has not defined which private prefixes each hub advertises. In the reported environment, the missing behavior instead relates to a remote user can reach an internal server by private IP but not by its internal hostname through the SPA connection. The relevant choice is name resolution is separate from overlay routing and may require explicit private-domain handling.
Question 362
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? No custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member.
- Compare member choices for multiple connections from one client and several different clients
- Inspect the rule ID attached to a test SaaS session and the order of all eligible rules
- Review implicit strategy and active member selection for the unmatched test session
- Compare which application or destination condition each matching rule contains
Explanation
Correct Answer
C:Review implicit strategy and active member selection for the unmatched test session. The observed evidence guides the targeted repair: Inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs.
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: no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. A more direct answer is review implicit strategy and active member selection for the unmatched test session.
B:Inspect the rule ID attached to a test SaaS session and the order of all eligible rules. It addresses a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. In the reported environment, the missing behavior instead relates to no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. The relevant choice is review implicit strategy and active member selection for the unmatched test session.
D:Compare which application or destination condition each matching rule contains. The outcome for that step belongs to a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. Here the decisive requirement concerns no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member, so review implicit strategy and active member selection for the unmatched test session is the better fit.
Question 363
The team plans to attach the additional tunnel member to the existing correctly scoped overlay SD-WAN zone for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy.
- Zone membership does not prove a chosen route or traffic permission by itself
- The second tunnel still requires a route and operational VPN establishment; zone assignment alone is not sufficient
- Two virtual members mapped to the same failed provider do not deliver true transport diversity
- A latency-only SLA may miss variable packet-arrival spacing
Explanation
Correct Answer
B:The second tunnel still requires a route and operational VPN establishment; zone assignment alone is not sufficient. The planned change can still miss the requirement if this condition is left unresolved. A shared overlay zone makes the same firewall policy interface cover multiple tunnels.
Incorrect Answers
A:Zone membership does not prove a chosen route or traffic permission by itself. The outcome for that step belongs to after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules. Here the decisive requirement concerns a branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy, so the second tunnel still requires a route and operational VPN establishment; zone assignment alone is not sufficient is the better fit.
C:Two virtual members mapped to the same failed provider do not deliver true transport diversity. 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 branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy. A more direct answer is the second tunnel still requires a route and operational VPN establishment; zone assignment alone is not sufficient.
D:A latency-only SLA may miss variable packet-arrival spacing. That is a useful action for a different circumstance: a voice application performs poorly with high jitter even though packet loss is low on both WANs. The present case is constrained by a branch adds a second private tunnel but wants existing overlay policies to apply without duplicating every individual-tunnel policy; the targeted response is the second tunnel still requires a route and operational VPN establishment; zone assignment alone is not sufficient.
Question 364
A proposed repair is to use FortiSASE SPA with a supported FortiGate hub connection for the approved private network prefixes. Why should that repair work in this particular situation? Context: An organization needs private TCP and UDP access to multiple office services without publishing public listener ports.
- The SASE architecture supports cloud Internet inspection and specific private application connectivity through connectors
- The SPA overlay depends on a functioning encrypted PoP-to-hub transport
- IPsec establishes transport, but routing must advertise and resolve the private destination networks
- SPA via hub overlays carries private application traffic through encrypted controlled connectivity
Explanation
Correct Answer
D:SPA via hub overlays carries private application traffic through encrypted controlled connectivity. It directly explains the need to use FortiSASE SPA with a supported FortiGate hub connection for the approved private network prefixes. The narrow validation is: Approved TCP and UDP application tests succeed through the overlay without public exposure.
Incorrect Answers
A:The SASE architecture supports cloud Internet inspection and specific private application connectivity through connectors. That is a useful action for a different circumstance: fortiSASE remote clients reach SASE points of presence, yet office users need direct access to the Internet without unnecessarily hairpinning via a corporate 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 sPA via hub overlays carries private application traffic through encrypted controlled connectivity.
B:The SPA overlay depends on a functioning encrypted PoP-to-hub transport. It could be appropriate when fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. 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 sPA via hub overlays carries private application traffic through encrypted controlled connectivity.
C:IPsec establishes transport, but routing must advertise and resolve the private destination networks. It addresses the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. In the reported environment, the missing behavior instead relates to an organization needs private TCP and UDP access to multiple office services without publishing public listener ports. The relevant choice is sPA via hub overlays carries private application traffic through encrypted controlled connectivity.
Question 365
After the authorized change to apply an appropriately scoped IPS profile to the authorized traffic and review the resulting threat events, which result actually demonstrates that this site's requirement is met? Initial issue: A security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE.
- An identified application action produces the intended monitor or block event while basic permitted access remains available
- Only the intended group triggers the stricter web-filter behavior in logged tests
- Malicious test content is detected or blocked according to policy without blocking the entire legitimate site category
- A controlled security test produces the expected IPS event or block decision
Explanation
Correct Answer
D:A controlled security test produces the expected IPS event or block decision. This is stronger than a saved configuration because it tests the intended operational result. Intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation.
Incorrect Answers
A:An identified application action produces the intended monitor or block event while basic permitted access remains available. That is a useful action for a different circumstance: a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service. The present case is constrained by a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE; the targeted response is a controlled security test produces the expected IPS event or block decision.
B:Only the intended group triggers the stricter web-filter behavior in logged tests. It addresses a remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access. 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 a controlled security test produces the expected IPS event or block decision.
C:Malicious test content is detected or blocked according to policy without blocking the entire legitimate site category. It could be appropriate when a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category. 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 a controlled security test produces the expected IPS event or block decision.
Question 366
A proposed repair is to make an overlay-specific zone and reference that zone in a narrow firewall policy for the authorized users. Why should that repair work in this particular situation? Context: A site should limit one overlay circuit to a restricted group of users, unlike unrestricted Internet underlays.
- Routing through an SD-WAN zone requires a member capable of carrying traffic after health and reachability checks
- An SD-WAN zone is the logical policy interface, so wrong zone placement affects treatment of sessions
- Policies can be scoped to SD-WAN zones and source identities, rather than depending on interface naming conventions
- Member zoning can separate overlay transports from Internet underlays for policy matching
Explanation
Correct Answer
C:Policies can be scoped to SD-WAN zones and source identities, rather than depending on interface naming conventions. This is why the proposed repair addresses the reported behavior; confirm by checking: Only intended users establish sessions over the overlay while other flows follow permitted Internet policies.
Incorrect Answers
A:Routing through an SD-WAN zone requires a member capable of carrying traffic after health and reachability checks. 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 site should limit one overlay circuit to a restricted group of users, unlike unrestricted Internet underlays. The relevant choice is policies can be scoped to SD-WAN zones and source identities, rather than depending on interface naming conventions.
B:An SD-WAN zone is the logical policy interface, so wrong zone placement affects treatment of sessions. 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 site should limit one overlay circuit to a restricted group of users, unlike unrestricted Internet underlays, so policies can be scoped to SD-WAN zones and source identities, rather than depending on interface naming conventions is the better fit.
D:Member zoning can separate overlay transports from Internet underlays for policy matching. It could be appropriate when two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout. However, that does not resolve the stated condition: a site should limit one overlay circuit to a restricted group of users, unlike unrestricted Internet underlays. A more direct answer is policies can be scoped to SD-WAN zones and source identities, rather than depending on interface naming conventions.
Question 367
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity.
- Using the prior week's scheduled report may omit the relevant incident
- A chart without accessible underlying event details cannot independently explain the suspected incident
- The backup link being alive does not by itself prove the application still works
- Treating all errors as virus detections can send responders down the wrong path
Explanation
Correct Answer
D:Treating all errors as virus detections can send responders down the wrong path. The planned change can still miss the requirement if this condition is left unresolved. Failed logins are identity events and need separate interpretation from content-inspection threats.
Incorrect Answers
A:Using the prior week's scheduled report may omit the relevant incident. That is a useful action for a different circumstance: during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary. The present case is constrained by a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity; the targeted response is treating all errors as virus detections can send responders down the wrong path.
B:A chart without accessible underlying event details cannot independently explain the suspected incident. 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 support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. The relevant choice is treating all errors as virus detections can send responders down the wrong path.
C:The backup link being alive does not by itself prove the application still works. It could be appropriate when a branch rollout claims reliable failover because the WAN link state changed, but the business owner wants proof that application transactions continued. However, that does not resolve the stated condition: a support analyst sees repeated FortiSASE failed sign-ins from one identity but no corresponding malicious-file activity. A more direct answer is treating all errors as virus detections can send responders down the wrong path.
Question 368
A proposed repair is to apply DNS-filter settings where supported to the relevant FortiSASE policy profile. Why should that repair work in this particular situation? Context: A compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests.
- Security profile groups bundle inspection settings and can be selected per eligible traffic policy
- DNS filtering can enforce policy based on name resolution queries, complementing web URL checks
- Intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation
- Inline application-aware controls can distinguish activity within supported cloud applications rather than only domain access
Explanation
Correct Answer
B:DNS filtering can enforce policy based on name resolution queries, complementing web URL checks. It directly explains the need to apply DNS-filter settings where supported to the relevant FortiSASE policy profile. The narrow validation is: Blocked-domain resolution attempts follow the configured DNS policy and produce expected events.
Incorrect Answers
A:Security profile groups bundle inspection settings and can be selected per eligible traffic policy. That is a useful action for a different circumstance: a remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access. The present case is constrained by a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests; the targeted response is dNS filtering can enforce policy based on name resolution queries, complementing web URL checks.
C:Intrusion prevention inspects matching signatures or behaviors in traffic rather than only destination reputation. It could be appropriate when a security operations team wants to detect exploit-pattern traffic directed at vulnerable services reached through FortiSASE. However, that does not resolve the stated condition: a 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 dNS filtering can enforce policy based on name resolution queries, complementing web URL checks.
D:Inline application-aware controls can distinguish activity within supported cloud applications rather than only domain access. The outcome for that step belongs to a legal department wants to monitor high-risk operations inside a sanctioned SaaS application without blocking the entire service. 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 dNS filtering can enforce policy based on name resolution queries, complementing web URL checks is the better fit.
Question 369
The team plans to enable an appropriate antivirus inspection profile on the traffic's allow security profile group for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category.
- A passing antivirus signal cannot override a separately required management-telemetry check
- Immediate tenant-wide enforcement without testing can interrupt otherwise legitimate access
- Successful SAML authentication alone does not prove acceptable endpoint security posture
- Web categorization alone does not replace malware payload inspection
Explanation
Correct Answer
D:Web categorization alone does not replace malware payload inspection. The planned change can still miss the requirement if this condition is left unresolved. Antivirus scanning targets malicious content, which may reside on otherwise acceptable sites.
Incorrect Answers
A:A passing antivirus signal cannot override a separately required management-telemetry check. That is a useful action for a different circumstance: a managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service. The present case is constrained by a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category; the targeted response is web categorization alone does not replace malware payload inspection.
B:Immediate tenant-wide enforcement without testing can interrupt otherwise legitimate access. It could be appropriate when an organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once. However, that does not resolve the stated condition: a remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category. A more direct answer is web categorization alone does not replace malware payload inspection.
C: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 remote staff cohort downloads infected files from legitimate domains, but the existing policy inspects only destination URL category. The relevant choice is web categorization alone does not replace malware payload inspection.
Question 370
The team plans to check the web-filter security log for the URL category, policy and action for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? Users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event.
- A chart without accessible underlying event details cannot independently explain the suspected incident
- Treating every blocked website as an IPS exploit event misclassifies the cause
- A rule configuration screenshot alone is weaker than observed matched-session behavior
- Reporting only aggregate successful Internet sessions does not answer a group-specific blocking question
Explanation
Correct Answer
B:Treating every blocked website as an IPS exploit event misclassifies the cause. The planned change can still miss the requirement if this condition is left unresolved. Web-filter events concern destination categorization, while IPS events concern detected intrusion patterns.
Incorrect Answers
A:A chart without accessible underlying event details cannot independently explain the suspected incident. It could be appropriate when a quarterly audit asks for a summary of FortiSASE security events and the ability to investigate one anomalous period in detail. However, that does not resolve the stated condition: users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event. A more direct answer is treating every blocked website as an IPS exploit event misclassifies the cause.
C:A rule configuration screenshot alone is weaker than observed matched-session behavior. That is a useful action for a different circumstance: an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. The present case is constrained by users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event; the targeted response is treating every blocked website as an IPS exploit event misclassifies the cause.
D:Reporting only aggregate successful Internet sessions does not answer a group-specific blocking question. The outcome for that step belongs to 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. Here the decisive requirement concerns users are blocked from a suspected phishing site, and an analyst must distinguish web-category enforcement from an IPS signature event, so treating every blocked website as an IPS exploit event misclassifies the cause is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests