Question 490
During an authorized lab exercise for a managed laptop fleet governed by FortiClient endpoint profiles, the incident notes state that unpatched legacy operating systems gain the same access as approved updated workstations. Which change is most relevant to this symptom?
- Investigate: Configure pre-connection posture enforcement
- Investigate: Assign compliant endpoint tags to private policies
- Investigate: Use operating-system version posture
- Investigate: Review the posture tag's allow or deny direction
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds. For a managed laptop fleet governed by FortiClient endpoint profiles, a direct diagnostic confirmation would be that the endpoint tag reflects the configured OS-version acceptance criterion; during repair, version policy should account for supported platforms and enterprise patch baselines.
Incorrect Answers
A:A configured pre-connection check can allow or deny a tunnel attempt based on an assigned posture tag, which serves the different requirement to block an untrusted FortiClient endpoint before it establishes its protected cloud tunnel instead of the behavior delivered by ‘Use operating-system version posture’. If that component were misconfigured, a more characteristic finding would be that a failed device is permitted to connect and only rejected later at application policy; the actual report concerns unpatched legacy operating systems gain the same access as approved updated workstations at a managed laptop fleet governed by FortiClient endpoint profiles.
B:Private access policies can use security posture tags as dynamic matching criteria, which serves the different requirement to grant sensitive private access only to managed devices meeting specified security conditions instead of the behavior delivered by ‘Use operating-system version posture’. If that component were misconfigured, a more characteristic finding would be that a valid user's unmanaged laptop reaches a restricted private service despite failing device requirements; the actual report concerns unpatched legacy operating systems gain the same access as approved updated workstations at a managed laptop fleet governed by FortiClient endpoint profiles.
D:An allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity, which serves the different requirement to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint instead of the behavior delivered by ‘Use operating-system version posture’. If that component were misconfigured, a more characteristic finding would be that devices labeled as risky are inadvertently allowed by an inverted preconnection action; the actual report concerns unpatched legacy operating systems gain the same access as approved updated workstations at a managed laptop fleet governed by FortiClient endpoint profiles.
Question 491
In a change-control meeting for a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, a colleague challenges the proposed control ‘Create a dedicated overlay zone’ for the requirement to group IPsec tunnel interfaces separately from physical WAN underlays. Which explanation accurately describes its behavior?
- Overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks.
- A member health-check source setting controls the source IP used by health probes to a monitored server.
- The cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred.
- Reassigning the member to a different zone changes its logical policy and rule membership.
Explanation
Correct Answer
A:‘Create a dedicated overlay zone’ is used to group IPsec tunnel interfaces separately from physical WAN underlays in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that both IPsec tunnel members appear in the overlay zone and match the private route; the rollout must also respect this constraint: The tunnel interfaces must first be configured and eligible to join SD-WAN.
Incorrect Answers
B:The described behavior is part of ‘Define the member health-check source’, used to send probes using the correct reachable source address on a multiaddress uplink instead of the role of ‘Create a dedicated overlay zone’. In contrast to ‘Define the member health-check source’, ‘Create a dedicated overlay zone’ follows a different mechanism: overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks. Treating ‘Define the member health-check source’ as equivalent would not address private application traffic follows an internet egress policy instead of an overlay policy in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.
C:The described behavior is part of ‘Set member cost’, used to favor a lower-priced uplink only when eligible under lowest-cost SLA rules instead of the role of ‘Create a dedicated overlay zone’. In contrast to ‘Set member cost’, ‘Create a dedicated overlay zone’ follows a different mechanism: overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks. Treating ‘Set member cost’ as equivalent would not address private application traffic follows an internet egress policy instead of an overlay policy in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.
D:The described behavior is part of ‘Move a member between zones’, used to change how one interface is referenced by routes and policies without rebuilding the WAN port instead of the role of ‘Create a dedicated overlay zone’. In contrast to ‘Move a member between zones’, ‘Create a dedicated overlay zone’ follows a different mechanism: overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks. Treating ‘Move a member between zones’ as equivalent would not address private application traffic follows an internet egress policy instead of an overlay policy in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.
Question 492
For an enterprise interconnecting SD-WAN overlays and cloud security edges, a maintenance plan requires the firewall team to differentiate local branch DIA from traffic genuinely sent to cloud enforcement. Which choice is appropriate?
- Establish BGP with the SPA hub
- Verify site-based SASE traffic steering
- Use FortiGate as a private-access hub
- Use a redundant private-access hub
Explanation
Correct Answer
B:Site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE; that scope directly serves the goal to differentiate local branch DIA from traffic genuinely sent to cloud enforcement in an enterprise interconnecting SD-WAN overlays and cloud security edges. During implementation, make the observed steering decision consistent with routing, policy, and tunnel state rather than treating the configuration label as proof of working service.
Incorrect Answers
A:A supported SPA BGP design learns and advertises routes over the selected overlay connection, a mechanism intended to exchange private network reachability dynamically between FortiSASE and a FortiGate hub rather than the requested ‘Verify site-based SASE traffic steering’ control. The stated task instead is to differentiate local branch DIA from traffic genuinely sent to cloud enforcement, and adjusting ‘Establish BGP with the SPA hub’ would not deliver ‘Verify site-based SASE traffic steering’. For the ‘Establish BGP with the SPA hub’ alternative to ‘Verify site-based SASE traffic steering’, autonomous system settings and route filters must agree across peers.
C:FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic, a mechanism intended to connect remote FortiSASE clients to data-center applications protected behind a FortiGate rather than the requested ‘Verify site-based SASE traffic steering’ control. The stated task instead is to differentiate local branch DIA from traffic genuinely sent to cloud enforcement, and adjusting ‘Use FortiGate as a private-access hub’ would not deliver ‘Verify site-based SASE traffic steering’. For the ‘Use FortiGate as a private-access hub’ alternative to ‘Verify site-based SASE traffic steering’, the protected data-center prefixes need return routes toward FortiSASE clients.
D:Multiple suitably configured SPA hubs can provide a redundant path to private resources, a mechanism intended to maintain access to applications when one data-center gateway or tunnel fails rather than the requested ‘Verify site-based SASE traffic steering’ control. The stated task instead is to differentiate local branch DIA from traffic genuinely sent to cloud enforcement, and adjusting ‘Use a redundant private-access hub’ would not deliver ‘Verify site-based SASE traffic steering’. For the ‘Use a redundant private-access hub’ alternative to ‘Verify site-based SASE traffic steering’, redundancy depends on both routing and policy consistency across hubs.
Question 493
For a logistics site where routing and SD-WAN services have separate responsibilities, a technical review examines the control ‘Treat existing sessions differently from new flows’ for the objective to troubleshoot a session that remains associated with an earlier selection after an SD-WAN change. Which statement best describes what it changes?
- DSCP match criteria can steer traffic carrying designated IP-header service markings.
- The Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members.
- Source-address criteria restrict SD-WAN rule matching to sessions from specified client address ranges.
- Session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering.
Explanation
Correct Answer
D:‘Treat existing sessions differently from new flows’ is used to troubleshoot a session that remains associated with an earlier selection after an SD-WAN change in a logistics site where routing and SD-WAN services have separate responsibilities; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that separate old and new session entries reveal their actual selected interfaces; the rollout must also respect this constraint: Do not assume a rule edit retroactively redistributes every already established flow.
Incorrect Answers
A:The described behavior is part of ‘Use DSCP-based SD-WAN steering’, used to distinguish preclassified media packets from ordinary web traffic at path-selection time instead of the role of ‘Treat existing sessions differently from new flows’. In contrast to ‘Use DSCP-based SD-WAN steering’, ‘Treat existing sessions differently from new flows’ follows a different mechanism: session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering. Treating ‘Use DSCP-based SD-WAN steering’ as equivalent would not address fresh sessions choose the new preferred WAN while established sessions appear on the old member in a logistics site where routing and SD-WAN services have separate responsibilities.
B:The described behavior is part of ‘Use a manual SD-WAN strategy’, used to pin a specific business application to a preferred transport independent of dynamic quality ranking instead of the role of ‘Treat existing sessions differently from new flows’. In contrast to ‘Use a manual SD-WAN strategy’, ‘Treat existing sessions differently from new flows’ follows a different mechanism: session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering. Treating ‘Use a manual SD-WAN strategy’ as equivalent would not address fresh sessions choose the new preferred WAN while established sessions appear on the old member in a logistics site where routing and SD-WAN services have separate responsibilities.
C:The described behavior is part of ‘Match a source subnet in an SD-WAN rule’, used to apply a special path selection only to traffic originating in one department network instead of the role of ‘Treat existing sessions differently from new flows’. In contrast to ‘Match a source subnet in an SD-WAN rule’, ‘Treat existing sessions differently from new flows’ follows a different mechanism: session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering. Treating ‘Match a source subnet in an SD-WAN rule’ as equivalent would not address fresh sessions choose the new preferred WAN while established sessions appear on the old member in a logistics site where routing and SD-WAN services have separate responsibilities.
Question 494
At a remote-user design needing both public SaaS and internal subnet access, a controlled test reveals that internet access works for remote agents but data-center CIDRs remain unreachable. Which setting is the strongest first lead?
- Investigate: Select hub path using SLA health
- Investigate: Use FortiGate as a private-access hub
- Investigate: Allow security PoP access to private applications
- Investigate: Use SD-WAN private access for TCP and UDP
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic. For a remote-user design needing both public SaaS and internal subnet access, a direct diagnostic confirmation would be that the hub connection is healthy and routes exist to the internal application networks; during repair, the protected data-center prefixes need return routes toward FortiSASE clients.
Incorrect Answers
A:Health and service-connection priorities can influence which reachable private hub path is preferred, which serves the different requirement to prefer a viable SPA route when one private-access connection becomes degraded instead of the behavior delivered by ‘Use FortiGate as a private-access hub’. If that component were misconfigured, a more characteristic finding would be that users continue taking a poor-quality service connection while a healthy hub exists; the actual report concerns internet access works for remote agents but data-center CIDRs remain unreachable at a remote-user design needing both public SaaS and internal subnet access.
C:Hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers, which serves the different requirement to permit cloud-originated SPA traffic through the data-center firewall policy instead of the behavior delivered by ‘Use FortiGate as a private-access hub’. If that component were misconfigured, a more characteristic finding would be that BGP and tunnels are up yet all application SYN packets are denied at the data-center perimeter; the actual report concerns internet access works for remote agents but data-center CIDRs remain unreachable at a remote-user design needing both public SaaS and internal subnet access.
D:An SD-WAN-based SPA design can provide routed access to private TCP and UDP applications, which serves the different requirement to extend private resource connectivity beyond the TCP-focused ZTNA access proxy model instead of the behavior delivered by ‘Use FortiGate as a private-access hub’. If that component were misconfigured, a more characteristic finding would be that the organization requires an internal UDP service that a TCP-only application proxy cannot carry; the actual report concerns internet access works for remote agents but data-center CIDRs remain unreachable at a remote-user design needing both public SaaS and internal subnet access.
Question 495
In a change-control meeting for a security team classifying devices by their current local protection state, the team is closing the change after testing a design to apply a stricter posture and connection configuration to a high-risk user population. Which result supports closure?
- Registration health and a recent tag update corroborate the current device state.
- The group receives the profile containing the designated posture and connection controls.
- The configured action denies devices carrying the noncompliant tag.
- The posture telemetry classifies the device according to antivirus status.
Explanation
Correct Answer
B:This checks ‘Use endpoint-profile assignment for managed groups’ at the correct operational boundary: endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives. It demonstrates the specific capability to apply a stricter posture and connection configuration to a high-risk user population in a security team classifying devices by their current local protection state; deployment should additionally respect the constraint: A cloud traffic policy alone does not deploy settings to FortiClient endpoints.
Incorrect Answers
A:That observation belongs to ‘Validate fresh endpoint posture telemetry’, not ‘Use endpoint-profile assignment for managed groups’; its purpose is to avoid relying on stale compliance information after an endpoint stops reporting to management, the underlying behavior is that posture-based enforcement depends on updated FortiClient registration and local security-condition evaluation. The reviewer is instead verifying ‘Use endpoint-profile assignment for managed groups’ for a security team classifying devices by their current local protection state, not the evidence produced by ‘Validate fresh endpoint posture telemetry’.
C:That observation belongs to ‘Review the posture tag's allow or deny direction’, not ‘Use endpoint-profile assignment for managed groups’; its purpose is to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint, the underlying behavior is that an allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity. The reviewer is instead verifying ‘Use endpoint-profile assignment for managed groups’ for a security team classifying devices by their current local protection state, not the evidence produced by ‘Review the posture tag's allow or deny direction’.
D:That observation belongs to ‘Require endpoint antivirus status’, not ‘Use endpoint-profile assignment for managed groups’; its purpose is to treat disabled or missing antimalware protection as a noncompliant device condition, the underlying behavior is that a posture rule can evaluate security-product presence or protection state and classify the endpoint. The reviewer is instead verifying ‘Use endpoint-profile assignment for managed groups’ for a security team classifying devices by their current local protection state, not the evidence produced by ‘Require endpoint antivirus status’.
Question 496
For a regional hub where live transport measurements do not agree with the user complaint, a maintenance plan requires the firewall team to turn observed quality metrics into a pass-or-fail objective for rule selection. Which choice is appropriate?
- Configure an SLA target for a health check
- Use SLA measurements for best-quality steering
- Set latency SLA threshold
- Set jitter SLA threshold
- Use probe loss to trigger failover
- Use passive WAN health measurement
Explanation
Correct Answer
A:The SLA target defines tolerated delay, loss, or jitter against measured health-check values; that scope directly serves the goal to turn observed quality metrics into a pass-or-fail objective for rule selection in a regional hub where live transport measurements do not agree with the user complaint. During implementation, measurement alone and selecting a traffic-steering target are different steps rather than treating the configuration label as proof of working service.
Incorrect Answers
B:Best Quality uses configured quality criteria derived from a health check to prioritize the most suitable available member, a mechanism intended to feed measured latency, jitter, or loss into a dynamic path-selection rule rather than the requested ‘Configure an SLA target for a health check’ control. The stated task instead is to turn observed quality metrics into a pass-or-fail objective for rule selection, and adjusting ‘Use SLA measurements for best-quality steering’ would not deliver ‘Configure an SLA target for a health check’. For the ‘Use SLA measurements for best-quality steering’ alternative to ‘Configure an SLA target for a health check’, choosing best quality differs from deciding which member has the smallest monetary cost.
C:A latency target makes a member fail that SLA when measured delay exceeds the configured limit, a mechanism intended to exclude paths whose round-trip delay exceeds a real-time application's bound rather than the requested ‘Configure an SLA target for a health check’ control. The stated task instead is to turn observed quality metrics into a pass-or-fail objective for rule selection, and adjusting ‘Set latency SLA threshold’ would not deliver ‘Configure an SLA target for a health check’. For the ‘Set latency SLA threshold’ alternative to ‘Configure an SLA target for a health check’, thresholds must be realistic for the probe destination and business application.
D:A jitter target compares delay variation with an allowed maximum to qualify or reject a member, a mechanism intended to avoid a circuit whose packet-delay variation damages live audio rather than the requested ‘Configure an SLA target for a health check’ control. The stated task instead is to turn observed quality metrics into a pass-or-fail objective for rule selection, and adjusting ‘Set jitter SLA threshold’ would not deliver ‘Configure an SLA target for a health check’. For the ‘Set jitter SLA threshold’ alternative to ‘Configure an SLA target for a health check’, low average latency alone does not demonstrate satisfactory jitter.
E:Failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group, a mechanism intended to remove a genuinely unreachable transport from eligible load-balancing routes rather than the requested ‘Configure an SLA target for a health check’ control. The stated task instead is to turn observed quality metrics into a pass-or-fail objective for rule selection, and adjusting ‘Use probe loss to trigger failover’ would not deliver ‘Configure an SLA target for a health check’. For the ‘Use probe loss to trigger failover’ alternative to ‘Configure an SLA target for a health check’, healthy alternate routing must exist for traffic to continue.
F:Passive measurements can obtain link metrics from observed traffic instead of relying solely on synthetic monitoring packets, a mechanism intended to derive quality observations from actual matched user sessions rather than dedicated probes rather than the requested ‘Configure an SLA target for a health check’ control. The stated task instead is to turn observed quality metrics into a pass-or-fail objective for rule selection, and adjusting ‘Use passive WAN health measurement’ would not deliver ‘Configure an SLA target for a health check’. For the ‘Use passive WAN health measurement’ alternative to ‘Configure an SLA target for a health check’, traffic and policy instrumentation must support the passive measurement mechanism.
Question 497
At a FortiSASE security investigation following a blocked user action, an engineer is preparing ‘Inspect DNS-filter threat events’ to identify blocked malicious name resolution before the browser opens a TCP session. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- A filtered query event shows the domain and DNS-policy enforcement result.
- DNS filtering operates at name resolution, not by scanning file payloads.
- Category decisions must be distinguished from DNS filter results and generic firewall denies.
- The IPS log records an appropriate attack signature and the related action.
- SaaS allow policy and DLP denial can coexist for the same application.
Explanation
Correct Answers
A:The observation follows from the operation of ‘Inspect DNS-filter threat events’: DNS security logs record affected domain requests and configured malicious-domain actions. It directly tests the requested ability to identify blocked malicious name resolution before the browser opens a TCP session in a FortiSASE security investigation following a blocked user action, rather than another policy or network layer.
B:This safeguard applies to ‘Inspect DNS-filter threat events’, which works because DNS security logs record affected domain requests and configured malicious-domain actions. Without the correct deployment condition, operators may see that clients cannot resolve a dangerous domain while normal internet connectivity still works in a FortiSASE security investigation following a blocked user action.
Incorrect Answers
C:The planning point is associated with ‘Inspect web-filter category logs’, not ‘Inspect DNS-filter threat events’; its real role is to determine whether a website was blocked by category policy rather than by transport failure. The required deployment instead centers on ‘Inspect DNS-filter threat events’, rather than ‘Inspect web-filter category logs’; the distinct symptom to guard against is that clients cannot resolve a dangerous domain while normal internet connectivity still works.
D:This result would validate ‘Inspect IPS threat logs’, not ‘Inspect DNS-filter threat events’, because IPS events contain the signature context and configured security response for detected traffic. That separate implementation serves verify whether an exploit signature triggered inspection rather than a generic connectivity failure, whereas the audit needs evidence specifically of ‘Inspect DNS-filter threat events’ at a FortiSASE security investigation following a blocked user action.
E:The planning point is associated with ‘Inspect DLP matches’, not ‘Inspect DNS-filter threat events’; its real role is to explain which sensitive-content pattern caused a SaaS upload to be denied. The required deployment instead centers on ‘Inspect DNS-filter threat events’, rather than ‘Inspect DLP matches’; the distinct symptom to guard against is that clients cannot resolve a dangerous domain while normal internet connectivity still works.
Question 498
For a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, an audit asks for evidence that the team can group IPsec tunnel interfaces separately from physical WAN underlays. Which finding would answer that question?
- The member now appears in the target zone and corresponding policies use it.
- Both IPsec tunnel members appear in the overlay zone and match the private route.
- The member status shows the intended lower numerical priority on the preferred circuit.
- Health-check packets use the specified reachable source on the chosen member.
Explanation
Correct Answer
B:This checks ‘Create a dedicated overlay zone’ at the correct operational boundary: overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks. It demonstrates the specific capability to group IPsec tunnel interfaces separately from physical WAN underlays in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels; deployment should additionally respect the constraint: The tunnel interfaces must first be configured and eligible to join SD-WAN.
Incorrect Answers
A:That observation belongs to ‘Move a member between zones’, not ‘Create a dedicated overlay zone’; its purpose is to change how one interface is referenced by routes and policies without rebuilding the WAN port, the underlying behavior is that reassigning the member to a different zone changes its logical policy and rule membership. The reviewer is instead verifying ‘Create a dedicated overlay zone’ for a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, not the evidence produced by ‘Move a member between zones’.
C:That observation belongs to ‘Set member fallback priority’, not ‘Create a dedicated overlay zone’; its purpose is to prefer a designated route candidate when priority is the deciding factor, the underlying behavior is that a lower member priority value takes precedence when the routing or SD-WAN selection uses priority. The reviewer is instead verifying ‘Create a dedicated overlay zone’ for a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, not the evidence produced by ‘Set member fallback priority’.
D:That observation belongs to ‘Define the member health-check source’, not ‘Create a dedicated overlay zone’; its purpose is to send probes using the correct reachable source address on a multiaddress uplink, the underlying behavior is that a member health-check source setting controls the source IP used by health probes to a monitored server. The reviewer is instead verifying ‘Create a dedicated overlay zone’ for a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, not the evidence produced by ‘Define the member health-check source’.
Question 499
At an industrial branch sending payroll traffic to a data-center application, an engineer is preparing ‘Keep underlay route for tunnel peer’ to preserve transport reachability to an IPsec hub before private overlay traffic is steered. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- Tunnel security negotiation and return routing still need separate validation.
- The hub's public endpoint resolves through a valid ISP underlay route.
- The expected route has the winning administrative distance for its destination.
- Priority has meaning within the relevant route-selection context, not across unrelated prefixes.
- Protect tunnel-control reachability from routing recursion into the same tunnel.
Explanation
Correct Answers
B:The observation follows from the operation of ‘Keep underlay route for tunnel peer’: an overlay tunnel requires the public peer endpoint to remain reachable through an underlay path. It directly tests the requested ability to preserve transport reachability to an IPsec hub before private overlay traffic is steered in an industrial branch sending payroll traffic to a data-center application, rather than another policy or network layer.
E:This safeguard applies to ‘Keep underlay route for tunnel peer’, which works because an overlay tunnel requires the public peer endpoint to remain reachable through an underlay path. Without the correct deployment condition, operators may see that the VPN repeatedly drops when the route to its public peer recursively follows the overlay itself in an industrial branch sending payroll traffic to a data-center application.
Incorrect Answers
A:The planning point is associated with ‘Use a route-based IPsec overlay’, not ‘Keep underlay route for tunnel peer’; its real role is to carry private routed traffic as a selectable interface-based tunnel path. The required deployment instead centers on ‘Keep underlay route for tunnel peer’, rather than ‘Use a route-based IPsec overlay’; the distinct symptom to guard against is that the VPN repeatedly drops when the route to its public peer recursively follows the overlay itself.
C:This result would validate ‘Review administrative distance’, not ‘Keep underlay route for tunnel peer’, because administrative distance influences which equal-prefix route source is preferred for installation. That separate implementation serves choose between competing routes learned from different sources for the same prefix, whereas the audit needs evidence specifically of ‘Keep underlay route for tunnel peer’ at an industrial branch sending payroll traffic to a data-center application.
D:The planning point is associated with ‘Review route priority’, not ‘Keep underlay route for tunnel peer’; its real role is to resolve preference among otherwise comparable FortiGate route candidates. The required deployment instead centers on ‘Keep underlay route for tunnel peer’, rather than ‘Review route priority’; the distinct symptom to guard against is that the VPN repeatedly drops when the route to its public peer recursively follows the overlay itself.
Question 500
In a change-control meeting for a global remote-user rollout with separate employee and contractor policies, acceptance testing shows that directory staff are not visible to SASE policy although the directory contains them. Which control should be investigated first?
- Investigate: Import users through LDAP
- Investigate: Deploy FortiClient using enterprise management
- Investigate: Match endpoint profiles to the correct user group
- Investigate: Configure agentless proxy SSO
Explanation
Correct Answer
A:The symptom identifies the missing operational behavior: LDAP integration allows FortiSASE to reference directory accounts and user groups. For a global remote-user rollout with separate employee and contractor policies, a direct diagnostic confirmation would be that the configured LDAP source resolves expected groups and authenticated users; during repair, FortiSASE must reach the directory service through its permitted network path.
Incorrect Answers
B:Group policy or mobile device management can deploy prepared FortiClient packages to managed endpoints, which serves the different requirement to roll out FortiClient at scale without requiring hundreds of manual installer sessions instead of the behavior delivered by ‘Import users through LDAP’. If that component were misconfigured, a more characteristic finding would be that a mass enrollment depends on each employee manually finding and configuring a local installer; the actual report concerns directory staff are not visible to SASE policy although the directory contains them at a global remote-user rollout with separate employee and contractor policies.
C:Endpoint profiles can be assigned according to relevant groups or administrative selection, which serves the different requirement to deliver one set of endpoint controls to contractors and a stricter set to employees instead of the behavior delivered by ‘Import users through LDAP’. If that component were misconfigured, a more characteristic finding would be that a contractor device receives the general employee tunnel settings instead of its restricted profile; the actual report concerns directory staff are not visible to SASE policy although the directory contains them at a global remote-user rollout with separate employee and contractor policies.
D:SWG SSO authenticates a web proxy session using the configured identity provider, which serves the different requirement to associate proxied browser traffic with enterprise user identity during secure web gateway inspection instead of the behavior delivered by ‘Import users through LDAP’. If that component were misconfigured, a more characteristic finding would be that proxy requests arrive but user-based policies cannot associate them with an authenticated identity; the actual report concerns directory staff are not visible to SASE policy although the directory contains them at a global remote-user rollout with separate employee and contractor policies.