Question 480
During an authorized lab exercise for a company enrolling remote Windows and macOS employees into FortiSASE, the incident notes state that RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server. Which change is most relevant to this symptom?
- Investigate: Distribute a FortiSASE invitation code
- Investigate: Configure RADIUS authentication
- Investigate: Configure SAML single sign-on
- Investigate: Use preconfigured FortiClient installers
- Investigate: Match endpoint profiles to the correct user group
- Investigate: Deploy FortiClient using enterprise management
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: RADIUS integration delegates user authentication to a configured authentication server. For a company enrolling remote Windows and macOS employees into FortiSASE, a direct diagnostic confirmation would be that FortiSASE test authentication obtains a valid response from the designated RADIUS source; during repair, configure the correct shared secret and reachable authentication service endpoints.
Incorrect Answers
A:The Onboard Users workflow provides information that remote users use for FortiSASE client registration, which serves the different requirement to bind an invited remote user's FortiClient enrollment to the correct organization instead of the behavior delivered by ‘Configure RADIUS authentication’. If that component were misconfigured, a more characteristic finding would be that employees have the agent installed but cannot associate it with the enterprise tenant; the actual report concerns RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server at a company enrolling remote Windows and macOS employees into FortiSASE.
C:FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users, which serves the different requirement to let staff authenticate to FortiSASE through the corporate identity provider instead of the behavior delivered by ‘Configure RADIUS authentication’. If that component were misconfigured, a more characteristic finding would be that redirect-based identity login cannot complete because the SP and IdP trust are not aligned; the actual report concerns RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server at a company enrolling remote Windows and macOS employees into FortiSASE.
D:The FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices, which serves the different requirement to enroll a small pilot group with minimal manual agent configuration instead of the behavior delivered by ‘Configure RADIUS authentication’. If that component were misconfigured, a more characteristic finding would be that pilot users install a generic client but lack the intended cloud service configuration; the actual report concerns RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server at a company enrolling remote Windows and macOS employees into FortiSASE.
E: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 ‘Configure RADIUS authentication’. 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 RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server at a company enrolling remote Windows and macOS employees into FortiSASE.
F: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 ‘Configure RADIUS authentication’. 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 RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server at a company enrolling remote Windows and macOS employees into FortiSASE.
Question 481
At a retail campus where underlay and overlay paths require distinct treatment, the rollout includes the control ‘Assign members to the intended zone’ to put two ISP circuits in the internet transport zone rather than the private-overlay group. Which observed mechanism is consistent with this configuration?
- The cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred.
- Physical WAN ports can act as members with their own connectivity, next hops, costs, and measured health.
- A lower member priority value takes precedence when the routing or SD-WAN selection uses priority.
- A zone can contain one member, allowing special security or routing treatment for that interface.
- A member's zone association determines which zone-based routes and policies can use that interface.
- A member health-check source setting controls the source IP used by health probes to a monitored server.
Explanation
Correct Answer
E:‘Assign members to the intended zone’ is used to put two ISP circuits in the internet transport zone rather than the private-overlay group in a retail campus where underlay and overlay paths require distinct treatment; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the member inventory shows wan2 inside the internet transport zone; the rollout must also respect this constraint: Zone placement does not automatically create a firewall rule or a route.
Incorrect Answers
A: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 ‘Assign members to the intended zone’. In contrast to ‘Set member cost’, ‘Assign members to the intended zone’ follows a different mechanism: a member's zone association determines which zone-based routes and policies can use that interface. Treating ‘Set member cost’ as equivalent would not address wan2 is operational but traffic for the transport zone cannot select it in a retail campus where underlay and overlay paths require distinct treatment.
B:The described behavior is part of ‘Use a physical interface as a member’, used to bring a directly connected broadband circuit under SD-WAN decisions instead of the role of ‘Assign members to the intended zone’. In contrast to ‘Use a physical interface as a member’, ‘Assign members to the intended zone’ follows a different mechanism: a member's zone association determines which zone-based routes and policies can use that interface. Treating ‘Use a physical interface as a member’ as equivalent would not address wan2 is operational but traffic for the transport zone cannot select it in a retail campus where underlay and overlay paths require distinct treatment.
C:The described behavior is part of ‘Set member fallback priority’, used to prefer a designated route candidate when priority is the deciding factor instead of the role of ‘Assign members to the intended zone’. In contrast to ‘Set member fallback priority’, ‘Assign members to the intended zone’ follows a different mechanism: a member's zone association determines which zone-based routes and policies can use that interface. Treating ‘Set member fallback priority’ as equivalent would not address wan2 is operational but traffic for the transport zone cannot select it in a retail campus where underlay and overlay paths require distinct treatment.
D:The described behavior is part of ‘Use an isolated single-member zone’, used to apply a dedicated policy to one exceptional transport while keeping other members grouped instead of the role of ‘Assign members to the intended zone’. In contrast to ‘Use an isolated single-member zone’, ‘Assign members to the intended zone’ follows a different mechanism: a member's zone association determines which zone-based routes and policies can use that interface. Treating ‘Use an isolated single-member zone’ as equivalent would not address wan2 is operational but traffic for the transport zone cannot select it in a retail campus where underlay and overlay paths require distinct treatment.
F: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 ‘Assign members to the intended zone’. In contrast to ‘Define the member health-check source’, ‘Assign members to the intended zone’ follows a different mechanism: a member's zone association determines which zone-based routes and policies can use that interface. Treating ‘Define the member health-check source’ as equivalent would not address wan2 is operational but traffic for the transport zone cannot select it in a retail campus where underlay and overlay paths require distinct treatment.
Question 482
During an authorized lab exercise for a private-access application that requires device trust as well as user identity, the deployment standard specifies the control ‘Use a certificate-based posture check’ to identify managed endpoints that carry an enterprise-issued device credential. Which functional description matches it?
- OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds.
- Endpoint tagging can evaluate the presence and properties of a required client certificate.
- A posture rule can evaluate security-product presence or protection state and classify the endpoint.
- Posture-based enforcement depends on updated FortiClient registration and local security-condition evaluation.
Explanation
Correct Answer
B:‘Use a certificate-based posture check’ is used to identify managed endpoints that carry an enterprise-issued device credential in a private-access application that requires device trust as well as user identity; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the endpoint is tagged only after the required trusted certificate is detected; the rollout must also respect this constraint: Certificate lifecycle and private-key protection matter separately from user authentication.
Incorrect Answers
A:The described behavior is part of ‘Use operating-system version posture’, used to restrict access from endpoints that do not meet an approved operating-system baseline instead of the role of ‘Use a certificate-based posture check’. In contrast to ‘Use operating-system version posture’, ‘Use a certificate-based posture check’ follows a different mechanism: endpoint tagging can evaluate the presence and properties of a required client certificate. Treating ‘Use operating-system version posture’ as equivalent would not address personal unmanaged endpoints authenticate with a user password but lack device enrollment evidence in a private-access application that requires device trust as well as user identity.
C:The described behavior is part of ‘Require endpoint antivirus status’, used to treat disabled or missing antimalware protection as a noncompliant device condition instead of the role of ‘Use a certificate-based posture check’. In contrast to ‘Require endpoint antivirus status’, ‘Use a certificate-based posture check’ follows a different mechanism: endpoint tagging can evaluate the presence and properties of a required client certificate. Treating ‘Require endpoint antivirus status’ as equivalent would not address personal unmanaged endpoints authenticate with a user password but lack device enrollment evidence in a private-access application that requires device trust as well as user identity.
D:The described behavior is part of ‘Validate fresh endpoint posture telemetry’, used to avoid relying on stale compliance information after an endpoint stops reporting to management instead of the role of ‘Use a certificate-based posture check’. In contrast to ‘Validate fresh endpoint posture telemetry’, ‘Use a certificate-based posture check’ follows a different mechanism: endpoint tagging can evaluate the presence and properties of a required client certificate. Treating ‘Validate fresh endpoint posture telemetry’ as equivalent would not address personal unmanaged endpoints authenticate with a user password but lack device enrollment evidence in a private-access application that requires device trust as well as user identity.
Question 483
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 ‘Integrate branch SD-WAN with FortiSASE on-ramp’ to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge. Which functional description matches it?
- Health and service-connection priorities can influence which reachable private hub path is preferred.
- Site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE.
- An IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay.
- A supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs.
Explanation
Correct Answer
D:‘Integrate branch SD-WAN with FortiSASE on-ramp’ is used to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge 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 the branch overlay to the service is established and inspected traffic appears in SASE logs; the rollout must also respect this constraint: Branch integration requires transport reachability and matching on-ramp security policy.
Incorrect Answers
A:The described behavior is part of ‘Select hub path using SLA health’, used to prefer a viable SPA route when one private-access connection becomes degraded instead of the role of ‘Integrate branch SD-WAN with FortiSASE on-ramp’. In contrast to ‘Select hub path using SLA health’, ‘Integrate branch SD-WAN with FortiSASE on-ramp’ follows a different mechanism: a supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs. Treating ‘Select hub path using SLA health’ as equivalent would not address the branch's WAN works locally but site users bypass the expected SASE inspection path 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 ‘Integrate branch SD-WAN with FortiSASE on-ramp’. In contrast to ‘Verify site-based SASE traffic steering’, ‘Integrate branch SD-WAN with FortiSASE on-ramp’ follows a different mechanism: a supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs. Treating ‘Verify site-based SASE traffic steering’ as equivalent would not address the branch's WAN works locally but site users bypass the expected SASE inspection path in a branch connected to a SASE point of presence by an encrypted service path.
C: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 ‘Integrate branch SD-WAN with FortiSASE on-ramp’. In contrast to ‘Use IPsec transport for the SASE branch connection’, ‘Integrate branch SD-WAN with FortiSASE on-ramp’ follows a different mechanism: a supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs. Treating ‘Use IPsec transport for the SASE branch connection’ as equivalent would not address the branch's WAN works locally but site users bypass the expected SASE inspection path in a branch connected to a SASE point of presence by an encrypted service path.
Question 484
At an industrial branch sending payroll traffic to a data-center application, a support engineer needs to verify that ‘Use a BGP learned private prefix’ is active for the goal to obtain branch or data-center destinations without maintaining individual manual static routes. Which observation is decisive?
- Policy-route diagnostics and the matched service show the actual selection chain.
- BGP neighbor state and learned route entries show the remote application CIDR.
- A route lookup shows the expected egress interface and reachable next hop.
- The IPsec interface is active and represented in overlay routing and member tables.
Explanation
Correct Answer
B:This checks ‘Use a BGP learned private prefix’ at the correct operational boundary: BGP can advertise and learn remote private networks over supported routed overlays. It demonstrates the specific capability to obtain branch or data-center destinations without maintaining individual manual static routes in an industrial branch sending payroll traffic to a data-center application; deployment should additionally respect the constraint: Routing adjacency and accepted prefix policies must be healthy independently of tunnel state.
Incorrect Answers
A:That observation belongs to ‘Validate policy routing and SD-WAN interaction’, not ‘Use a BGP learned private prefix’; its purpose is to identify why a matching policy-route decision changes normal egress selection, the underlying behavior is that policy route and SD-WAN service rules can influence forwarding decisions beyond basic destination-table lookup. The reviewer is instead verifying ‘Use a BGP learned private prefix’ for an industrial branch sending payroll traffic to a data-center application, not the evidence produced by ‘Validate policy routing and SD-WAN interaction’.
C:That observation belongs to ‘Verify the forwarding information base’, not ‘Use a BGP learned private prefix’; 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 ‘Use a BGP learned private prefix’ for an industrial branch sending payroll traffic to a data-center application, not the evidence produced by ‘Verify the forwarding information base’.
D:That observation belongs to ‘Use a route-based IPsec overlay’, not ‘Use a BGP learned private prefix’; its purpose is to carry private routed traffic as a selectable interface-based tunnel path, the underlying behavior is that route-based IPsec exposes a logical tunnel interface that routing and SD-WAN can reference. The reviewer is instead verifying ‘Use a BGP learned private prefix’ for an industrial branch sending payroll traffic to a data-center application, not the evidence produced by ‘Use a route-based IPsec overlay’.
Question 485
In a change-control meeting for a security operations review of remote-user threat detections, the proposed control is ‘Inspect antivirus detection events’. Which deployment condition is particularly relevant?
- DNS filtering operates at name resolution, not by scanning file payloads.
- A traffic deny log by itself does not establish that antivirus detected malware.
- SaaS allow policy and DLP denial can coexist for the same application.
- A successful SAML assertion still does not grant every network destination.
Explanation
Correct Answer
B:This condition matters for ‘Inspect antivirus detection events’ because aV logs identify signature or file detections and the security action applied to a session. Omitting the relevant safeguard can produce a user reports a blocked download but only aggregate bandwidth charts were examined; a successful test at a security operations review of remote-user threat detections would instead demonstrate that a time-matched AV event shows the detection and enforced action for the download.
Incorrect Answers
A:The condition is associated with ‘Inspect DNS-filter threat events’, a mechanism used to identify blocked malicious name resolution before the browser opens a TCP session instead of ‘Inspect antivirus detection events’, because DNS security logs record affected domain requests and configured malicious-domain actions. For ‘Inspect antivirus detection events’, unlike ‘Inspect DNS-filter threat events’, the characteristic failure would be a user reports a blocked download but only aggregate bandwidth charts were examined, which this alternative prerequisite would not directly address at a security operations review of remote-user threat detections.
C:The condition is associated with ‘Inspect DLP matches’, a mechanism used to explain which sensitive-content pattern caused a SaaS upload to be denied instead of ‘Inspect antivirus detection events’, because DLP logs record content-rule matches and the action taken for an inspected transfer. For ‘Inspect antivirus detection events’, unlike ‘Inspect DLP matches’, the characteristic failure would be a user reports a blocked download but only aggregate bandwidth charts were examined, which this alternative prerequisite would not directly address at a security operations review of remote-user threat detections.
D:The condition is associated with ‘Correlate cloud authentication events’, a mechanism used to distinguish failed identity sign-in from a denied security profile decision instead of ‘Inspect antivirus detection events’, because authentication events reveal the login or SSO step at which a FortiSASE user failed to establish identity. For ‘Inspect antivirus detection events’, unlike ‘Correlate cloud authentication events’, the characteristic failure would be a user reports a blocked download but only aggregate bandwidth charts were examined, which this alternative prerequisite would not directly address at a security operations review of remote-user threat detections.
Question 486
For an administrator analyzing cloud application consumption by user group, a technical review examines the control ‘Correlate policy action with destination risk’ for the objective to identify repeated attempts to reach restricted destinations across remote users. Which statement best describes what it changes?
- Application analytics classify observed traffic into recognizable applications for reporting.
- User traffic analytics aggregate bytes and sessions by identity and time for usage investigation.
- Security analytics can group blocked traffic by destination or policy to reveal recurring patterns.
- Time-bound analytics separate incident-period activity from unrelated historical traffic.
Explanation
Correct Answer
C:‘Correlate policy action with destination risk’ is used to identify repeated attempts to reach restricted destinations across remote users in an administrator analyzing cloud application consumption by user group; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the report associates blocked sessions with the affected destinations and user identities; the rollout must also respect this constraint: An event count requires context to distinguish mistakes from an actual threat campaign.
Incorrect Answers
A:The described behavior is part of ‘Review application usage reports’, used to identify which SaaS or application class dominates inspected remote traffic instead of the role of ‘Correlate policy action with destination risk’. In contrast to ‘Review application usage reports’, ‘Correlate policy action with destination risk’ follows a different mechanism: security analytics can group blocked traffic by destination or policy to reveal recurring patterns. Treating ‘Review application usage reports’ as equivalent would not address a burst of denials is reported without knowing whether one bad domain or many sites were involved in an administrator analyzing cloud application consumption by user group.
B:The described behavior is part of ‘Compare user traffic volume trends’, used to find which authenticated population caused a sustained increase in cloud egress instead of the role of ‘Correlate policy action with destination risk’. In contrast to ‘Compare user traffic volume trends’, ‘Correlate policy action with destination risk’ follows a different mechanism: security analytics can group blocked traffic by destination or policy to reveal recurring patterns. Treating ‘Compare user traffic volume trends’ as equivalent would not address a burst of denials is reported without knowing whether one bad domain or many sites were involved in an administrator analyzing cloud application consumption by user group.
D:The described behavior is part of ‘Use report time filters for incident scoping’, used to limit an investigation to the period in which an employee reported a cloud access failure instead of the role of ‘Correlate policy action with destination risk’. In contrast to ‘Use report time filters for incident scoping’, ‘Correlate policy action with destination risk’ follows a different mechanism: security analytics can group blocked traffic by destination or policy to reveal recurring patterns. Treating ‘Use report time filters for incident scoping’ as equivalent would not address a burst of denials is reported without knowing whether one bad domain or many sites were involved in an administrator analyzing cloud application consumption by user group.
Question 487
For a security analyst reviewing logged blocks and app usage for a site, a maintenance plan requires the firewall team to limit an investigation to the period in which an employee reported a cloud access failure. Which choice is appropriate?
- Use report time filters for incident scoping
- Trend security events by category
- Correlate policy action with destination risk
- Compare user traffic volume trends
Explanation
Correct Answer
A:Time-bound analytics separate incident-period activity from unrelated historical traffic; that scope directly serves the goal to limit an investigation to the period in which an employee reported a cloud access failure in a security analyst reviewing logged blocks and app usage for a site. During implementation, correlate device and timezone timestamps before drawing incident chronology conclusions rather than treating the configuration label as proof of working service.
Incorrect Answers
B:Security reporting aggregates action and threat categories so changes can be compared across time, a mechanism intended to measure whether a newly deployed protection reduced observed prohibited activity rather than the requested ‘Use report time filters for incident scoping’ control. The stated task instead is to limit an investigation to the period in which an employee reported a cloud access failure, and adjusting ‘Trend security events by category’ would not deliver ‘Use report time filters for incident scoping’. For the ‘Trend security events by category’ alternative to ‘Use report time filters for incident scoping’, changes in log policy or user population must be considered before claiming a causal improvement.
C:Security analytics can group blocked traffic by destination or policy to reveal recurring patterns, a mechanism intended to identify repeated attempts to reach restricted destinations across remote users rather than the requested ‘Use report time filters for incident scoping’ control. The stated task instead is to limit an investigation to the period in which an employee reported a cloud access failure, and adjusting ‘Correlate policy action with destination risk’ would not deliver ‘Use report time filters for incident scoping’. For the ‘Correlate policy action with destination risk’ alternative to ‘Use report time filters for incident scoping’, an event count requires context to distinguish mistakes from an actual threat campaign.
D:User traffic analytics aggregate bytes and sessions by identity and time for usage investigation, a mechanism intended to find which authenticated population caused a sustained increase in cloud egress rather than the requested ‘Use report time filters for incident scoping’ control. The stated task instead is to limit an investigation to the period in which an employee reported a cloud access failure, and adjusting ‘Compare user traffic volume trends’ would not deliver ‘Use report time filters for incident scoping’. For the ‘Compare user traffic volume trends’ alternative to ‘Use report time filters for incident scoping’, traffic volume alone is not evidence that a session is malicious.
Question 488
In a change-control meeting for an incident response exercise using allowed test traffic and SASE events, the team is closing the change after testing a design to explain which sensitive-content pattern caused a SaaS upload to be denied. Which result supports closure?
- The DLP event identifies the matching content pattern and policy action.
- A filtered query event shows the domain and DNS-policy enforcement result.
- The authentication event shows IdP or user-session failure independent of traffic-filter logs.
- A time-matched AV event shows the detection and enforced action for the download.
Explanation
Correct Answer
A:This checks ‘Inspect DLP matches’ at the correct operational boundary: DLP logs record content-rule matches and the action taken for an inspected transfer. It demonstrates the specific capability to explain which sensitive-content pattern caused a SaaS upload to be denied in an incident response exercise using allowed test traffic and SASE events; deployment should additionally respect the constraint: SaaS allow policy and DLP denial can coexist for the same application.
Incorrect Answers
B:That observation belongs to ‘Inspect DNS-filter threat events’, not ‘Inspect DLP matches’; its purpose is to identify blocked malicious name resolution before the browser opens a TCP session, the underlying behavior is that DNS security logs record affected domain requests and configured malicious-domain actions. The reviewer is instead verifying ‘Inspect DLP matches’ for an incident response exercise using allowed test traffic and SASE events, not the evidence produced by ‘Inspect DNS-filter threat events’.
C:That observation belongs to ‘Correlate cloud authentication events’, not ‘Inspect DLP matches’; its purpose is to distinguish failed identity sign-in from a denied security profile decision, the underlying behavior is that authentication events reveal the login or SSO step at which a FortiSASE user failed to establish identity. The reviewer is instead verifying ‘Inspect DLP matches’ for an incident response exercise using allowed test traffic and SASE events, not the evidence produced by ‘Correlate cloud authentication events’.
D:That observation belongs to ‘Inspect antivirus detection events’, not ‘Inspect DLP matches’; its purpose is to identify which inspected download was blocked for malware and under which policy, the underlying behavior is that aV logs identify signature or file detections and the security action applied to a session. The reviewer is instead verifying ‘Inspect DLP matches’ for an incident response exercise using allowed test traffic and SASE events, not the evidence produced by ‘Inspect antivirus detection events’.
Question 489
At a FortiSASE deployment that protects a central application behind a FortiGate, the change request is to maintain access to applications when one data-center gateway or tunnel fails. Which configuration is the most direct fit?
- Allow security PoP access to private applications
- Use IPsec transport for the SASE branch connection
- Use ZTNA application proxy for a protected TCP app
- Use a redundant private-access hub
Explanation
Correct Answer
D:Multiple suitably configured SPA hubs can provide a redundant path to private resources; that scope directly serves the goal to maintain access to applications when one data-center gateway or tunnel fails in a FortiSASE deployment that protects a central application behind a FortiGate. During implementation, redundancy depends on both routing and policy consistency across hubs rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers, a mechanism intended to permit cloud-originated SPA traffic through the data-center firewall policy rather than the requested ‘Use a redundant private-access hub’ control. The stated task instead is to maintain access to applications when one data-center gateway or tunnel fails, and adjusting ‘Allow security PoP access to private applications’ would not deliver ‘Use a redundant private-access hub’. For the ‘Allow security PoP access to private applications’ alternative to ‘Use a redundant private-access hub’, routing reachability and firewall permission must both be satisfied.
B:An IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay, a mechanism intended to carry branch traffic securely across an untrusted ISP toward a SASE service edge rather than the requested ‘Use a redundant private-access hub’ control. The stated task instead is to maintain access to applications when one data-center gateway or tunnel fails, and adjusting ‘Use IPsec transport for the SASE branch connection’ would not deliver ‘Use a redundant private-access hub’. For the ‘Use IPsec transport for the SASE branch connection’ alternative to ‘Use a redundant private-access hub’, iKE negotiations and underlay routing must work before traffic steering over the tunnel.
C:ZTNA private access targets authorized TCP applications rather than granting generic network reachability, a mechanism intended to publish a narrowly scoped internal TCP application through a FortiGate ZTNA gateway rather than the requested ‘Use a redundant private-access hub’ control. The stated task instead is to maintain access to applications when one data-center gateway or tunnel fails, and adjusting ‘Use ZTNA application proxy for a protected TCP app’ would not deliver ‘Use a redundant private-access hub’. For the ‘Use ZTNA application proxy for a protected TCP app’ alternative to ‘Use a redundant private-access hub’, the FortiGate ZTNA server, access policy, and required client posture must be configured.
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.