Question 130
At a finance team that uses multiple approved SaaS applications, a support engineer needs to verify that ‘Configure application control signatures’ is active for the goal to block a specific risky application without disabling every website in its category. Which observation is decisive?
- DNS query logs show the configured domain-category or threat action.
- The connected SaaS application's API scans produce inventory and findings about stored content.
- Application-control logs identify the named app and enforced action.
- A test destination in the prohibited category is blocked with a web-filter log.
Explanation
Correct Answer
C:This checks ‘Configure application control signatures’ at the correct operational boundary: Application Control identifies application behavior and can apply signature-level allow, monitor, or block actions. It demonstrates the specific capability to block a specific risky application without disabling every website in its category in a finance team that uses multiple approved SaaS applications; deployment should additionally respect the constraint: Port-only access controls are not the same as identifying an application signature.
Incorrect Answers
A:That observation belongs to ‘Use DNS filtering’, not ‘Configure application control signatures’; its purpose is to stop requests to known malicious or restricted domains at the DNS layer, the underlying behavior is that DNS Filter evaluates domain lookup activity before a client establishes a normal destination session. The reviewer is instead verifying ‘Configure application control signatures’ for a finance team that uses multiple approved SaaS applications, not the evidence produced by ‘Use DNS filtering’.
B:That observation belongs to ‘Use cloud API CASB for SaaS data at rest’, not ‘Configure application control signatures’; its purpose is to inspect cloud-service data through supported SaaS APIs rather than only inline user sessions, the underlying behavior is that aPI-connected CASB can examine supported SaaS tenant content and events without requiring every action to cross the inline proxy. The reviewer is instead verifying ‘Configure application control signatures’ for a finance team that uses multiple approved SaaS applications, not the evidence produced by ‘Use cloud API CASB for SaaS data at rest’.
D:That observation belongs to ‘Apply a web-filter category action’, not ‘Configure application control signatures’; its purpose is to block a prohibited web category while allowing legitimate business browsing, the underlying behavior is that web filtering classifies requested sites and applies the configured category or URL action. The reviewer is instead verifying ‘Configure application control signatures’ for a finance team that uses multiple approved SaaS applications, not the evidence produced by ‘Apply a web-filter category action’.
Question 131
During an authorized lab exercise for a branch connected to a SASE point of presence by an encrypted service path, the deployment standard specifies the control ‘Select hub path using SLA health’ to prefer a viable SPA route when one private-access connection becomes degraded. Which functional description matches it?
- An IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay.
- Site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE.
- Health and service-connection priorities can influence which reachable private hub path is preferred.
- Private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers.
Explanation
Correct Answer
C:‘Select hub path using SLA health’ is used to prefer a viable SPA route when one private-access connection becomes degraded in a branch connected to a SASE point of presence by an encrypted service path; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that hub status and SLA data show eligible private service connection preference; the rollout must also respect this constraint: The alternate hub must advertise the needed application prefix to take over.
Incorrect Answers
A:The described behavior is part of ‘Use IPsec transport for the SASE branch connection’, used to carry branch traffic securely across an untrusted ISP toward a SASE service edge instead of the role of ‘Select hub path using SLA health’. In contrast to ‘Use IPsec transport for the SASE branch connection’, ‘Select hub path using SLA health’ follows a different mechanism: health and service-connection priorities can influence which reachable private hub path is preferred. Treating ‘Use IPsec transport for the SASE branch connection’ as equivalent would not address users continue taking a poor-quality service connection while a healthy hub exists in a branch connected to a SASE point of presence by an encrypted service path.
B:The described behavior is part of ‘Verify site-based SASE traffic steering’, used to differentiate local branch DIA from traffic genuinely sent to cloud enforcement instead of the role of ‘Select hub path using SLA health’. In contrast to ‘Verify site-based SASE traffic steering’, ‘Select hub path using SLA health’ follows a different mechanism: health and service-connection priorities can influence which reachable private hub path is preferred. Treating ‘Verify site-based SASE traffic steering’ as equivalent would not address users continue taking a poor-quality service connection while a healthy hub exists in a branch connected to a SASE point of presence by an encrypted service path.
D:The described behavior is part of ‘Configure DNS resolution for private names’, used to let remote users resolve internal application FQDNs to protected addresses instead of the role of ‘Select hub path using SLA health’. In contrast to ‘Configure DNS resolution for private names’, ‘Select hub path using SLA health’ follows a different mechanism: health and service-connection priorities can influence which reachable private hub path is preferred. Treating ‘Configure DNS resolution for private names’ as equivalent would not address users continue taking a poor-quality service connection while a healthy hub exists in a branch connected to a SASE point of presence by an encrypted service path.
Question 132
Within a policy owner protecting HTTPS web sessions without blocking business use, the operator applies the control ‘Enable SSL deep inspection’ as part of an effort to inspect content carried inside HTTPS when allowed by policy and endpoint trust. Which operating behavior should the team expect?
- SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP.
- Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions.
- Inline-CASB application control adds SaaS-aware decisions to recognized HTTP traffic traversing FortiSASE.
- Deep inspection decrypts eligible TLS sessions at the security service for content-aware scanning.
- An enabled antivirus inspection component examines supported file content for malicious signatures or behavior indicators.
Explanation
Correct Answer
D:‘Enable SSL deep inspection’ is used to inspect content carried inside HTTPS when allowed by policy and endpoint trust in a policy owner protecting HTTPS web sessions without blocking business use; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that inspected HTTPS sessions show content controls operating with a trusted inspection CA; the rollout must also respect this constraint: Certificate deployment and inspection exemptions must be handled to avoid breaking legitimate services.
Incorrect Answers
A:The described behavior is part of ‘Distinguish SIA from SSA policy intent’, used to apply general internet threat protection separately from SaaS-specific data and tenant controls instead of the role of ‘Enable SSL deep inspection’. In contrast to ‘Distinguish SIA from SSA policy intent’, ‘Enable SSL deep inspection’ follows a different mechanism: deep inspection decrypts eligible TLS sessions at the security service for content-aware scanning. Treating ‘Distinguish SIA from SSA policy intent’ as equivalent would not address DLP and file inspection are configured but cannot analyze encrypted page bodies in a policy owner protecting HTTPS web sessions without blocking business use.
B:The described behavior is part of ‘Use inline CASB HTTP header restrictions’, used to restrict which SaaS tenant a managed user may access by adjusting inspected web request headers instead of the role of ‘Enable SSL deep inspection’. In contrast to ‘Use inline CASB HTTP header restrictions’, ‘Enable SSL deep inspection’ follows a different mechanism: deep inspection decrypts eligible TLS sessions at the security service for content-aware scanning. Treating ‘Use inline CASB HTTP header restrictions’ as equivalent would not address DLP and file inspection are configured but cannot analyze encrypted page bodies in a policy owner protecting HTTPS web sessions without blocking business use.
C:The described behavior is part of ‘Use inline CASB application controls’, used to apply SaaS-specific application restrictions on inspected cloud traffic instead of the role of ‘Enable SSL deep inspection’. In contrast to ‘Use inline CASB application controls’, ‘Enable SSL deep inspection’ follows a different mechanism: deep inspection decrypts eligible TLS sessions at the security service for content-aware scanning. Treating ‘Use inline CASB application controls’ as equivalent would not address DLP and file inspection are configured but cannot analyze encrypted page bodies in a policy owner protecting HTTPS web sessions without blocking business use.
E:The described behavior is part of ‘Apply an antivirus profile to allowed traffic’, used to detect malware payloads passing through a permitted cloud access policy instead of the role of ‘Enable SSL deep inspection’. In contrast to ‘Apply an antivirus profile to allowed traffic’, ‘Enable SSL deep inspection’ follows a different mechanism: deep inspection decrypts eligible TLS sessions at the security service for content-aware scanning. Treating ‘Apply an antivirus profile to allowed traffic’ as equivalent would not address DLP and file inspection are configured but cannot analyze encrypted page bodies in a policy owner protecting HTTPS web sessions without blocking business use.
Question 133
At an off-site workforce where some endpoints fail compliance verification, a controlled test reveals that a workstation with a critical unremediated issue continues receiving full sensitive-app access. Which setting is the strongest first lead?
- Investigate: Use endpoint-profile assignment for managed groups
- Investigate: Build a security posture tag rule
- Investigate: Check a required running process
- Investigate: Check endpoint vulnerability severity
Explanation
Correct Answer
D:The symptom identifies the missing operational behavior: vulnerability-related posture information can be used to classify a risky endpoint for conditional access. For an off-site workforce where some endpoints fail compliance verification, a direct diagnostic confirmation would be that the device's posture classification reflects the configured vulnerability severity; during repair, posture signals require recent endpoint scanning and successful telemetry exchange.
Incorrect Answers
A:Endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives, which serves the different requirement to apply a stricter posture and connection configuration to a high-risk user population instead of the behavior delivered by ‘Check endpoint vulnerability severity’. If that component were misconfigured, a more characteristic finding would be that contractor devices use the default endpoint configuration rather than the intended restricted policy; the actual report concerns a workstation with a critical unremediated issue continues receiving full sensitive-app access at an off-site workforce where some endpoints fail compliance verification.
B:FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags, which serves the different requirement to label endpoints dynamically when a specified local security condition is met instead of the behavior delivered by ‘Check endpoint vulnerability severity’. If that component were misconfigured, a more characteristic finding would be that the application policy cannot distinguish secure laptops from devices missing a required check; the actual report concerns a workstation with a critical unremediated issue continues receiving full sensitive-app access at an off-site workforce where some endpoints fail compliance verification.
C:Process-presence conditions can contribute to device posture evaluation where supported, which serves the different requirement to permit an internal app only when its approved endpoint security agent is running instead of the behavior delivered by ‘Check endpoint vulnerability severity’. If that component were misconfigured, a more characteristic finding would be that users stop a mandatory protection process yet retain the previous trust classification; the actual report concerns a workstation with a critical unremediated issue continues receiving full sensitive-app access at an off-site workforce where some endpoints fail compliance verification.
Question 134
In a change-control meeting for a dual-ISP FortiGate with BGP-learned routes to private sites, the team is closing the change after testing a design to differentiate a configured route from an actually usable gateway on a WAN link. Which result supports closure?
- The hub's public endpoint resolves through a valid ISP underlay route.
- A route lookup shows the expected egress interface and reachable next hop.
- Route and health-check diagnostics show the failed member and available alternate.
- ARP or neighbor resolution and route lookup identify the reachable gateway.
Explanation
Correct Answer
D:This checks ‘Check the route's next hop reachability’ at the correct operational boundary: forwarding requires that the selected next hop can be resolved and reached via the member. It demonstrates the specific capability to differentiate a configured route from an actually usable gateway on a WAN link in a dual-ISP FortiGate with BGP-learned routes to private sites; deployment should additionally respect the constraint: A route's presence alone does not establish next-hop liveness.
Incorrect Answers
A:That observation belongs to ‘Keep underlay route for tunnel peer’, not ‘Check the route's next hop reachability’; its purpose is to preserve transport reachability to an IPsec hub before private overlay traffic is steered, the underlying behavior is that an overlay tunnel requires the public peer endpoint to remain reachable through an underlay path. The reviewer is instead verifying ‘Check the route's next hop reachability’ for a dual-ISP FortiGate with BGP-learned routes to private sites, not the evidence produced by ‘Keep underlay route for tunnel peer’.
B:That observation belongs to ‘Verify the forwarding information base’, not ‘Check the route's next hop reachability’; its purpose is to confirm the FortiGate has installed a usable next hop for a destination, the underlying behavior is that the FIB holds selected forwarding entries and is essential to actual packet delivery. The reviewer is instead verifying ‘Check the route's next hop reachability’ for a dual-ISP FortiGate with BGP-learned routes to private sites, not the evidence produced by ‘Verify the forwarding information base’.
C:That observation belongs to ‘Inspect route withdrawal after health failure’, not ‘Check the route's next hop reachability’; its purpose is to explain why a failed WAN member stops being considered for new forwarding, the underlying behavior is that SD-WAN health failure can remove a member's route from the link load-balancing candidate set. The reviewer is instead verifying ‘Check the route's next hop reachability’ for a dual-ISP FortiGate with BGP-learned routes to private sites, not the evidence produced by ‘Inspect route withdrawal after health failure’.
Question 135
In a change-control meeting for a help desk investigating a short cloud access degradation, the team is closing the change after testing a design to measure whether a newly deployed protection reduced observed prohibited activity. Which result supports closure?
- Before-and-after summaries show the relevant security category event counts.
- The report associates blocked sessions with the affected destinations and user identities.
- The time-filtered report ranks user or group traffic volume for the affected interval.
- The report breaks down application categories and their traffic share for the period.
Explanation
Correct Answer
A:This checks ‘Trend security events by category’ at the correct operational boundary: security reporting aggregates action and threat categories so changes can be compared across time. It demonstrates the specific capability to measure whether a newly deployed protection reduced observed prohibited activity in a help desk investigating a short cloud access degradation; deployment should additionally respect the constraint: Changes in log policy or user population must be considered before claiming a causal improvement.
Incorrect Answers
B:That observation belongs to ‘Correlate policy action with destination risk’, not ‘Trend security events by category’; its purpose is to identify repeated attempts to reach restricted destinations across remote users, the underlying behavior is that security analytics can group blocked traffic by destination or policy to reveal recurring patterns. The reviewer is instead verifying ‘Trend security events by category’ for a help desk investigating a short cloud access degradation, not the evidence produced by ‘Correlate policy action with destination risk’.
C:That observation belongs to ‘Compare user traffic volume trends’, not ‘Trend security events by category’; its purpose is to find which authenticated population caused a sustained increase in cloud egress, the underlying behavior is that user traffic analytics aggregate bytes and sessions by identity and time for usage investigation. The reviewer is instead verifying ‘Trend security events by category’ for a help desk investigating a short cloud access degradation, not the evidence produced by ‘Compare user traffic volume trends’.
D:That observation belongs to ‘Review application usage reports’, not ‘Trend security events by category’; its purpose is to identify which SaaS or application class dominates inspected remote traffic, the underlying behavior is that application analytics classify observed traffic into recognizable applications for reporting. The reviewer is instead verifying ‘Trend security events by category’ for a help desk investigating a short cloud access degradation, not the evidence produced by ‘Review application usage reports’.
Question 136
At a FortiSASE security investigation following a blocked user action, the change request is to identify blocked malicious name resolution before the browser opens a TCP session. Which configuration is the most direct fit?
- Inspect DLP matches
- Inspect web-filter category logs
- Inspect DNS-filter threat events
- Correlate cloud authentication events
Explanation
Correct Answer
C:DNS security logs record affected domain requests and configured malicious-domain actions; that scope directly serves the goal to identify blocked malicious name resolution before the browser opens a TCP session in a FortiSASE security investigation following a blocked user action. During implementation, DNS filtering operates at name resolution, not by scanning file payloads rather than treating the configuration label as proof of working service.
Incorrect Answers
A:DLP logs record content-rule matches and the action taken for an inspected transfer, a mechanism intended to explain which sensitive-content pattern caused a SaaS upload to be denied rather than the requested ‘Inspect DNS-filter threat events’ control. The stated task instead is to identify blocked malicious name resolution before the browser opens a TCP session, and adjusting ‘Inspect DLP matches’ would not deliver ‘Inspect DNS-filter threat events’. For the ‘Inspect DLP matches’ alternative to ‘Inspect DNS-filter threat events’, saaS allow policy and DLP denial can coexist for the same application.
B:Web-filter logs associate an HTTP or HTTPS destination with category evaluation and action, a mechanism intended to determine whether a website was blocked by category policy rather than by transport failure rather than the requested ‘Inspect DNS-filter threat events’ control. The stated task instead is to identify blocked malicious name resolution before the browser opens a TCP session, and adjusting ‘Inspect web-filter category logs’ would not deliver ‘Inspect DNS-filter threat events’. For the ‘Inspect web-filter category logs’ alternative to ‘Inspect DNS-filter threat events’, category decisions must be distinguished from DNS filter results and generic firewall denies.
D:Authentication events reveal the login or SSO step at which a FortiSASE user failed to establish identity, a mechanism intended to distinguish failed identity sign-in from a denied security profile decision rather than the requested ‘Inspect DNS-filter threat events’ control. The stated task instead is to identify blocked malicious name resolution before the browser opens a TCP session, and adjusting ‘Correlate cloud authentication events’ would not deliver ‘Inspect DNS-filter threat events’. For the ‘Correlate cloud authentication events’ alternative to ‘Inspect DNS-filter threat events’, a successful SAML assertion still does not grant every network destination.
Question 137
Within a policy owner protecting HTTPS web sessions without blocking business use, the operator applies the control ‘Create a security profile group’ as part of an effort to apply a consistent set of inspection components to selected allowed SASE traffic policies. Which operating behavior should the team expect?
- A profile group bundles web, application, SSL, and other security controls for policy attachment.
- Web filtering classifies requested sites and applies the configured category or URL action.
- URL-level exceptions can refine category-based web filtering when an approved exception is required.
- Remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation.
- DNS Filter evaluates domain lookup activity before a client establishes a normal destination session.
Explanation
Correct Answer
A:‘Create a security profile group’ is used to apply a consistent set of inspection components to selected allowed SASE traffic policies in a policy owner protecting HTTPS web sessions without blocking business use; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the access policy references the correct profile group and test detections appear; the rollout must also respect this constraint: The policy action must accept traffic before attached inspection profiles can process it.
Incorrect Answers
B:The described behavior is part of ‘Apply a web-filter category action’, used to block a prohibited web category while allowing legitimate business browsing instead of the role of ‘Create a security profile group’. In contrast to ‘Apply a web-filter category action’, ‘Create a security profile group’ follows a different mechanism: a profile group bundles web, application, SSL, and other security controls for policy attachment. Treating ‘Apply a web-filter category action’ as equivalent would not address individual protections exist but a matched accept policy has no intended profile association in a policy owner protecting HTTPS web sessions without blocking business use.
C:The described behavior is part of ‘Use a specific URL filter exception’, used to allow a justified business website without disabling an entire restrictive category instead of the role of ‘Create a security profile group’. In contrast to ‘Use a specific URL filter exception’, ‘Create a security profile group’ follows a different mechanism: a profile group bundles web, application, SSL, and other security controls for policy attachment. Treating ‘Use a specific URL filter exception’ as equivalent would not address individual protections exist but a matched accept policy has no intended profile association in a policy owner protecting HTTPS web sessions without blocking business use.
D:The described behavior is part of ‘Apply remote browser isolation for risky sites’, used to isolate web rendering from the endpoint when access is required to a questionable website instead of the role of ‘Create a security profile group’. In contrast to ‘Apply remote browser isolation for risky sites’, ‘Create a security profile group’ follows a different mechanism: a profile group bundles web, application, SSL, and other security controls for policy attachment. Treating ‘Apply remote browser isolation for risky sites’ as equivalent would not address individual protections exist but a matched accept policy has no intended profile association in a policy owner protecting HTTPS web sessions without blocking business use.
E:The described behavior is part of ‘Use DNS filtering’, used to stop requests to known malicious or restricted domains at the DNS layer instead of the role of ‘Create a security profile group’. In contrast to ‘Use DNS filtering’, ‘Create a security profile group’ follows a different mechanism: a profile group bundles web, application, SSL, and other security controls for policy attachment. Treating ‘Use DNS filtering’ as equivalent would not address individual protections exist but a matched accept policy has no intended profile association in a policy owner protecting HTTPS web sessions without blocking business use.
Question 138
Within a cloud protection help desk correlating identity and traffic evidence, after the rollout, operators find that a connection is reset during a suspected exploit test but there is no rule-level explanation. Where should they focus troubleshooting?
- Investigate: Inspect DNS-filter threat events
- Investigate: Correlate endpoint posture and access events
- Investigate: Inspect DLP matches
- Investigate: Inspect antivirus detection events
- Investigate: Inspect IPS threat logs
Explanation
Correct Answer
E:The symptom identifies the missing operational behavior: IPS events contain the signature context and configured security response for detected traffic. For a cloud protection help desk correlating identity and traffic evidence, a direct diagnostic confirmation would be that the IPS log records an appropriate attack signature and the related action; during repair, a reset alone is not sufficient evidence to attribute the decision to IPS.
Incorrect Answers
A:DNS security logs record affected domain requests and configured malicious-domain actions, which serves the different requirement to identify blocked malicious name resolution before the browser opens a TCP session instead of the behavior delivered by ‘Inspect IPS threat logs’. If that component were misconfigured, a more characteristic finding would be that clients cannot resolve a dangerous domain while normal internet connectivity still works; the actual report concerns a connection is reset during a suspected exploit test but there is no rule-level explanation at a cloud protection help desk correlating identity and traffic evidence.
B:Endpoint and access records can show that a posture tag triggered a conditional denial, which serves the different requirement to identify an endpoint denied for noncompliance rather than for missing network reachability instead of the behavior delivered by ‘Inspect IPS threat logs’. If that component were misconfigured, a more characteristic finding would be that a valid user is blocked from private access while another managed device succeeds; the actual report concerns a connection is reset during a suspected exploit test but there is no rule-level explanation at a cloud protection help desk correlating identity and traffic evidence.
C:DLP logs record content-rule matches and the action taken for an inspected transfer, which serves the different requirement to explain which sensitive-content pattern caused a SaaS upload to be denied instead of the behavior delivered by ‘Inspect IPS threat logs’. If that component were misconfigured, a more characteristic finding would be that upload traffic is blocked although the SaaS application is otherwise approved; the actual report concerns a connection is reset during a suspected exploit test but there is no rule-level explanation at a cloud protection help desk correlating identity and traffic evidence.
D:AV logs identify signature or file detections and the security action applied to a session, which serves the different requirement to identify which inspected download was blocked for malware and under which policy instead of the behavior delivered by ‘Inspect IPS threat logs’. If that component were misconfigured, a more characteristic finding would be that a user reports a blocked download but only aggregate bandwidth charts were examined; the actual report concerns a connection is reset during a suspected exploit test but there is no rule-level explanation at a cloud protection help desk correlating identity and traffic evidence.
Question 139
For a test lab containing an overlay tunnel and two underlay next hops, a maintenance plan requires the firewall team to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions. Which choice is appropriate?
- Use ECMP-compatible route candidates
- Prefer a more specific prefix
- Install default route through an SD-WAN zone
- Check the route's next hop reachability
Explanation
Correct Answer
A:Equal Cost Multi-Path allows compatible routes to coexist as candidates when distance and priority permit; that scope directly serves the goal to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions in a test lab containing an overlay tunnel and two underlay next hops. During implementation, ECMP eligibility does not itself define an application-aware SD-WAN service strategy rather than treating the configuration label as proof of working service.
Incorrect Answers
B:Longest-prefix match chooses a more specific valid destination route ahead of a broader default, a mechanism intended to send a partner network into a private tunnel even while default internet routing is present rather than the requested ‘Use ECMP-compatible route candidates’ control. The stated task instead is to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions, and adjusting ‘Prefer a more specific prefix’ would not deliver ‘Use ECMP-compatible route candidates’. For the ‘Prefer a more specific prefix’ alternative to ‘Use ECMP-compatible route candidates’, SD-WAN application preference cannot create missing reachability to an internal network.
C:A zone-based default static route gives SD-WAN a routing candidate for nonlocal destinations, a mechanism intended to make general internet destinations reachable without listing every WAN member as a separate policy interface rather than the requested ‘Use ECMP-compatible route candidates’ control. The stated task instead is to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions, and adjusting ‘Install default route through an SD-WAN zone’ would not deliver ‘Use ECMP-compatible route candidates’. For the ‘Install default route through an SD-WAN zone’ alternative to ‘Use ECMP-compatible route candidates’, a route must exist before the steering choice can forward a matching session.
D:Forwarding requires that the selected next hop can be resolved and reached via the member, a mechanism intended to differentiate a configured route from an actually usable gateway on a WAN link rather than the requested ‘Use ECMP-compatible route candidates’ control. The stated task instead is to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions, and adjusting ‘Check the route's next hop reachability’ would not deliver ‘Use ECMP-compatible route candidates’. For the ‘Check the route's next hop reachability’ alternative to ‘Use ECMP-compatible route candidates’, a route's presence alone does not establish next-hop liveness.
Question 140
For a service operator standardizing remote internet protection across sites, a review of the current state finds that routine changes are made using a shared primary login with no individual accountability. Which configuration area most directly addresses this?
- Investigate: Configure a SASE allow policy
- Investigate: Assign FortiSASE administrator access
- Investigate: Choose an appropriate security PoP path
- Investigate: Use geolocation-aware access restrictions
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: distinct authorized administrators enable accountable management while the original account retains ownership. For a service operator standardizing remote internet protection across sites, a direct diagnostic confirmation would be that the intended operator signs in with an authorized administrative identity; during repair, scope and privilege should be limited to the operator's actual duties.
Incorrect Answers
A:FortiSASE traffic policies determine which user or destination flows are accepted or denied and which security-profile groups apply, which serves the different requirement to permit approved user traffic before applying cloud-delivered inspection profiles instead of the behavior delivered by ‘Assign FortiSASE administrator access’. If that component were misconfigured, a more characteristic finding would be that the required application remains blocked even though the desired inspection profiles exist; the actual report concerns routine changes are made using a shared primary login with no individual accountability at a service operator standardizing remote internet protection across sites.
C:FortiSASE steers supported client traffic toward its security points of presence for consistent remote policy enforcement, which serves the different requirement to bring roaming clients to cloud enforcement rather than hairpin every connection through headquarters instead of the behavior delivered by ‘Assign FortiSASE administrator access’. If that component were misconfigured, a more characteristic finding would be that off-site users bypass cloud inspection while on-premises users remain protected; the actual report concerns routine changes are made using a shared primary login with no individual accountability at a service operator standardizing remote internet protection across sites.
D:Geographic policy criteria can help distinguish traffic by geolocation where FortiSASE policy supports that selection, which serves the different requirement to restrict access from locations outside an organization-approved geographic footprint instead of the behavior delivered by ‘Assign FortiSASE administrator access’. If that component were misconfigured, a more characteristic finding would be that remote access occurs from a region that violates the deployment's stated geographic rule; the actual report concerns routine changes are made using a shared primary login with no individual accountability at a service operator standardizing remote internet protection across sites.