Question 1
For an insurance branch with a real-time application and a bulk-backup workload, an audit asks for evidence that the team can ensure a narrow high-priority policy wins instead of a catch-all service rule. Which finding would answer that question?
- The service's candidate list contains only the authorized WAN paths.
- The service's quality factor is latency and the member ordering reflects measured delay.
- Separate old and new session entries reveal their actual selected interfaces.
- The narrow rule appears ahead of the broad rule and receives matching hits.
Explanation
Correct Answer
D:This checks ‘Order specific SD-WAN rules above general matches’ at the correct operational boundary: SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence. It demonstrates the specific capability to ensure a narrow high-priority policy wins instead of a catch-all service rule in an insurance branch with a real-time application and a bulk-backup workload; deployment should additionally respect the constraint: A highly specific match below a catch-all does not automatically outrank it.
Incorrect Answers
A:That observation belongs to ‘Restrict the candidate member preference list’, not ‘Order specific SD-WAN rules above general matches’; its purpose is to prevent a sensitive service from using an otherwise healthy but unapproved ISP, the underlying behavior is that an explicit member or zone preference limits which eligible paths a matching service may choose. The reviewer is instead verifying ‘Order specific SD-WAN rules above general matches’ for an insurance branch with a real-time application and a bulk-backup workload, not the evidence produced by ‘Restrict the candidate member preference list’.
B:That observation belongs to ‘Use Best Quality with latency’, not ‘Order specific SD-WAN rules above general matches’; its purpose is to prefer the lowest-delay usable path for an interactive application, the underlying behavior is that Best Quality can rank member quality using latency collected by the designated performance health check. The reviewer is instead verifying ‘Order specific SD-WAN rules above general matches’ for an insurance branch with a real-time application and a bulk-backup workload, not the evidence produced by ‘Use Best Quality with latency’.
C:That observation belongs to ‘Treat existing sessions differently from new flows’, not ‘Order specific SD-WAN rules above general matches’; its purpose is to troubleshoot a session that remains associated with an earlier selection after an SD-WAN change, the underlying behavior is that session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering. The reviewer is instead verifying ‘Order specific SD-WAN rules above general matches’ for an insurance branch with a real-time application and a bulk-backup workload, not the evidence produced by ‘Treat existing sessions differently from new flows’.
Question 2
At a monitoring dashboard where health status disagrees with user experience, the rollout includes the control ‘Inspect SD-WAN rule hit counters’ to determine whether sessions are matching the intended service rule before editing path priorities. Which observed mechanism is consistent with this configuration?
- Service rule counters and diagnostics help confirm which policy actually handles observed traffic.
- The service4 diagnostic command exposes IPv4 rule modes, matched criteria, and selected candidates.
- SD-WAN service diagnostics show selected members, eligibility, and rule selection behavior.
- Health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification.
Explanation
Correct Answer
A:‘Inspect SD-WAN rule hit counters’ is used to determine whether sessions are matching the intended service rule before editing path priorities in a monitoring dashboard where health status disagrees with user experience; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that rule hit evidence increments for a controlled session that meets the match criteria; the rollout must also respect this constraint: No rule hits often indicates an earlier match or unmatched traffic rather than faulty member quality.
Incorrect Answers
B:The described behavior is part of ‘Use SD-WAN service4 diagnostics’, used to examine IPv4 SD-WAN rule selection rather than a generic interface status page instead of the role of ‘Inspect SD-WAN rule hit counters’. In contrast to ‘Use SD-WAN service4 diagnostics’, ‘Inspect SD-WAN rule hit counters’ follows a different mechanism: service rule counters and diagnostics help confirm which policy actually handles observed traffic. Treating ‘Use SD-WAN service4 diagnostics’ as equivalent would not address a priority member is blamed though the expected service rule never matches any sessions in a monitoring dashboard where health status disagrees with user experience.
C:The described behavior is part of ‘Inspect selected member in service diagnostics’, used to establish which egress candidate an SD-WAN service is actively using instead of the role of ‘Inspect SD-WAN rule hit counters’. In contrast to ‘Inspect selected member in service diagnostics’, ‘Inspect SD-WAN rule hit counters’ follows a different mechanism: service rule counters and diagnostics help confirm which policy actually handles observed traffic. Treating ‘Inspect selected member in service diagnostics’ as equivalent would not address a priority member is blamed though the expected service rule never matches any sessions in a monitoring dashboard where health status disagrees with user experience.
D:The described behavior is part of ‘Inspect member health-check output’, used to explain why a link was removed from service despite remaining physically up instead of the role of ‘Inspect SD-WAN rule hit counters’. In contrast to ‘Inspect member health-check output’, ‘Inspect SD-WAN rule hit counters’ follows a different mechanism: service rule counters and diagnostics help confirm which policy actually handles observed traffic. Treating ‘Inspect member health-check output’ as equivalent would not address a priority member is blamed though the expected service rule never matches any sessions in a monitoring dashboard where health status disagrees with user experience.
Question 3
In a change-control meeting for an enterprise interconnecting SD-WAN overlays and cloud security edges, acceptance testing shows that branch internet sessions show a public ISP path and lack expected cloud security logs. Which control should be investigated first?
- Investigate: Establish BGP with the SPA hub
- Investigate: Use a redundant private-access hub
- Investigate: Verify site-based SASE traffic steering
- Investigate: Use IPsec transport for the SASE branch connection
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE. For an enterprise interconnecting SD-WAN overlays and cloud security edges, a direct diagnostic confirmation would be that matching site flows are observed through the branch on-ramp and SASE enforcement logs; during repair, make the observed steering decision consistent with routing, policy, and tunnel state.
Incorrect Answers
A:A supported SPA BGP design learns and advertises routes over the selected overlay connection, which serves the different requirement to exchange private network reachability dynamically between FortiSASE and a FortiGate hub instead of the behavior delivered by ‘Verify site-based SASE traffic steering’. If that component were misconfigured, a more characteristic finding would be that the hub responds on its tunnel addresses but remote application routes never appear; the actual report concerns branch internet sessions show a public ISP path and lack expected cloud security logs at an enterprise interconnecting SD-WAN overlays and cloud security edges.
B:Multiple suitably configured SPA hubs can provide a redundant path to private resources, which serves the different requirement to maintain access to applications when one data-center gateway or tunnel fails instead of the behavior delivered by ‘Verify site-based SASE traffic steering’. If that component were misconfigured, a more characteristic finding would be that one hub outage removes private access despite a second deployment being available; the actual report concerns branch internet sessions show a public ISP path and lack expected cloud security logs at an enterprise interconnecting SD-WAN overlays and cloud security edges.
D:An IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay, which serves the different requirement to carry branch traffic securely across an untrusted ISP toward a SASE service edge instead of the behavior delivered by ‘Verify site-based SASE traffic steering’. If that component were misconfigured, a more characteristic finding would be that branch packets are routed directly to internet without the configured secure service tunnel; the actual report concerns branch internet sessions show a public ISP path and lack expected cloud security logs at an enterprise interconnecting SD-WAN overlays and cloud security edges.
Question 4
Within a campus running FortiOS 7.6 with application-aware policies, the configuration has been applied. Which measurement or record best confirms the goal to explain why the first newly observed app session may not match application-based steering immediately?
- The selected member passes SLA and has the lowest cost among qualified paths.
- The application-control internet-service list contains the learned application destination tuple.
- The SD-WAN rule matches the designated Internet Service Database object.
- The diagnostic output identifies the matching service and its selected eligible member.
- The service's quality factor is latency and the member ordering reflects measured delay.
Explanation
Correct Answer
B:This checks ‘Consider first-flow application recognition’ at the correct operational boundary: FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches. It demonstrates the specific capability to explain why the first newly observed app session may not match application-based steering immediately in a campus running FortiOS 7.6 with application-aware policies; deployment should additionally respect the constraint: Do not assume every first encrypted connection is identified before its initial path is chosen.
Incorrect Answers
A:That observation belongs to ‘Use Lowest Cost with an SLA target’, not ‘Consider first-flow application recognition’; its purpose is to send a service on the cheapest circuit that still meets quality objectives, the underlying behavior is that Lowest Cost chooses the smallest configured member cost among those that satisfy the selected SLA. The reviewer is instead verifying ‘Consider first-flow application recognition’ for a campus running FortiOS 7.6 with application-aware policies, not the evidence produced by ‘Use Lowest Cost with an SLA target’.
C:That observation belongs to ‘Match an Internet Service Database destination’, not ‘Consider first-flow application recognition’; its purpose is to identify cloud-service traffic by maintained service definitions instead of a static destination IP, the underlying behavior is that internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet. The reviewer is instead verifying ‘Consider first-flow application recognition’ for a campus running FortiOS 7.6 with application-aware policies, not the evidence produced by ‘Match an Internet Service Database destination’.
D:That observation belongs to ‘Test rule matching with service diagnostics’, not ‘Consider first-flow application recognition’; its purpose is to identify which SD-WAN rule and candidate member were chosen for a particular session, the underlying behavior is that SD-WAN service diagnostics expose matched rules, interface lists, modes, and selected member status. The reviewer is instead verifying ‘Consider first-flow application recognition’ for a campus running FortiOS 7.6 with application-aware policies, not the evidence produced by ‘Test rule matching with service diagnostics’.
E:That observation belongs to ‘Use Best Quality with latency’, not ‘Consider first-flow application recognition’; its purpose is to prefer the lowest-delay usable path for an interactive application, the underlying behavior is that Best Quality can rank member quality using latency collected by the designated performance health check. The reviewer is instead verifying ‘Consider first-flow application recognition’ for a campus running FortiOS 7.6 with application-aware policies, not the evidence produced by ‘Use Best Quality with latency’.
Question 5
In a change-control meeting for a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, the team is closing the change after testing a design to exclude a WAN circuit from SD-WAN decisions during scheduled carrier work. Which result supports closure?
- Member status shows the maintenance circuit disabled and other members eligible.
- The member now appears in the target zone and corresponding policies use it.
- The LAG interface, not its individual component ports, is the member.
- The physical WAN device is an enabled member with a valid gateway.
Explanation
Correct Answer
A:This checks ‘Disable a maintenance member’ at the correct operational boundary: disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration. It demonstrates the specific capability to exclude a WAN circuit from SD-WAN decisions during scheduled carrier work in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs; deployment should additionally respect the constraint: Ensure remaining members provide viable routes and sufficient capacity.
Incorrect Answers
B:That observation belongs to ‘Move a member between zones’, not ‘Disable a maintenance member’; 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 ‘Disable a maintenance member’ for a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, not the evidence produced by ‘Move a member between zones’.
C:That observation belongs to ‘Use an aggregate interface as a member’, not ‘Disable a maintenance member’; its purpose is to treat an LAG upstream handoff as a selectable SD-WAN transport, the underlying behavior is that a link aggregation interface can be an SD-WAN member while LAG distributes frames across its constituent ports. The reviewer is instead verifying ‘Disable a maintenance member’ for a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, not the evidence produced by ‘Use an aggregate interface as a member’.
D:That observation belongs to ‘Use a physical interface as a member’, not ‘Disable a maintenance member’; its purpose is to bring a directly connected broadband circuit under SD-WAN decisions, the underlying behavior is that physical WAN ports can act as members with their own connectivity, next hops, costs, and measured health. The reviewer is instead verifying ‘Disable a maintenance member’ for a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, not the evidence produced by ‘Use a physical interface as a member’.
Question 6
Within a hub-and-spoke network with internet breakout and private IPsec overlays, the team wants to avoid an ineffective configuration of ‘Validate policy routing and SD-WAN interaction’. Which consideration deserves attention?
- The SD-WAN rule must be reconciled with actual route installation.
- Review configured policy-routing precedence before rewriting otherwise correct static routes.
- Routing adjacency and accepted prefix policies must be healthy independently of tunnel state.
- Firewall policies must authorize both traffic classes with suitable inspection.
- A failed SLA state can change route eligibility without a physical link-down event.
Explanation
Correct Answer
B:This condition matters for ‘Validate policy routing and SD-WAN interaction’ because policy route and SD-WAN service rules can influence forwarding decisions beyond basic destination-table lookup. Omitting the relevant safeguard can produce a destination has a correct static route but a separate steering or policy route sends it elsewhere; a successful test at a hub-and-spoke network with internet breakout and private IPsec overlays would instead demonstrate that policy-route diagnostics and the matched service show the actual selection chain.
Incorrect Answers
A:The condition is associated with ‘Verify the forwarding information base’, a mechanism used to confirm the FortiGate has installed a usable next hop for a destination instead of ‘Validate policy routing and SD-WAN interaction’, because the FIB holds selected forwarding entries and is essential to actual packet delivery. For ‘Validate policy routing and SD-WAN interaction’, unlike ‘Verify the forwarding information base’, the characteristic failure would be a destination has a correct static route but a separate steering or policy route sends it elsewhere, which this alternative prerequisite would not directly address at a hub-and-spoke network with internet breakout and private IPsec overlays.
C:The condition is associated with ‘Use a BGP learned private prefix’, a mechanism used to obtain branch or data-center destinations without maintaining individual manual static routes instead of ‘Validate policy routing and SD-WAN interaction’, because BGP can advertise and learn remote private networks over supported routed overlays. For ‘Validate policy routing and SD-WAN interaction’, unlike ‘Use a BGP learned private prefix’, the characteristic failure would be a destination has a correct static route but a separate steering or policy route sends it elsewhere, which this alternative prerequisite would not directly address at a hub-and-spoke network with internet breakout and private IPsec overlays.
D:The condition is associated with ‘Use split routing for private and internet destinations’, a mechanism used to send corporate destinations over overlay but ordinary internet traffic via local DIA instead of ‘Validate policy routing and SD-WAN interaction’, because destination-specific private routes and a general internet default route allow distinct traffic paths. For ‘Validate policy routing and SD-WAN interaction’, unlike ‘Use split routing for private and internet destinations’, the characteristic failure would be a destination has a correct static route but a separate steering or policy route sends it elsewhere, which this alternative prerequisite would not directly address at a hub-and-spoke network with internet breakout and private IPsec overlays.
E:The condition is associated with ‘Inspect route withdrawal after health failure’, a mechanism used to explain why a failed WAN member stops being considered for new forwarding instead of ‘Validate policy routing and SD-WAN interaction’, because SD-WAN health failure can remove a member's route from the link load-balancing candidate set. For ‘Validate policy routing and SD-WAN interaction’, unlike ‘Inspect route withdrawal after health failure’, the characteristic failure would be a destination has a correct static route but a separate steering or policy route sends it elsewhere, which this alternative prerequisite would not directly address at a hub-and-spoke network with internet breakout and private IPsec overlays.
Question 7
At a test lab containing an overlay tunnel and two underlay next hops, an engineer is preparing ‘Inspect route withdrawal after health failure’ to explain why a failed WAN member stops being considered for new forwarding. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- SD-WAN application preference cannot create missing reachability to an internal network.
- A failed SLA state can change route eligibility without a physical link-down event.
- Firewall policies must authorize both traffic classes with suitable inspection.
- A route lookup shows the expected egress interface and reachable next hop.
- Route and health-check diagnostics show the failed member and available alternate.
Explanation
Correct Answers
B:This safeguard applies to ‘Inspect route withdrawal after health failure’, which works because SD-WAN health failure can remove a member's route from the link load-balancing candidate set. Without the correct deployment condition, operators may see that a path disappears from installed eligible routes when probes fail though interface carrier remains up in a test lab containing an overlay tunnel and two underlay next hops.
E:The observation follows from the operation of ‘Inspect route withdrawal after health failure’: SD-WAN health failure can remove a member's route from the link load-balancing candidate set. It directly tests the requested ability to explain why a failed WAN member stops being considered for new forwarding in a test lab containing an overlay tunnel and two underlay next hops, rather than another policy or network layer.
Incorrect Answers
A:The planning point is associated with ‘Prefer a more specific prefix’, not ‘Inspect route withdrawal after health failure’; its real role is to send a partner network into a private tunnel even while default internet routing is present. The required deployment instead centers on ‘Inspect route withdrawal after health failure’, rather than ‘Prefer a more specific prefix’; the distinct symptom to guard against is that a path disappears from installed eligible routes when probes fail though interface carrier remains up.
C:The planning point is associated with ‘Use split routing for private and internet destinations’, not ‘Inspect route withdrawal after health failure’; its real role is to send corporate destinations over overlay but ordinary internet traffic via local DIA. The required deployment instead centers on ‘Inspect route withdrawal after health failure’, rather than ‘Use split routing for private and internet destinations’; the distinct symptom to guard against is that a path disappears from installed eligible routes when probes fail though interface carrier remains up.
D:This result would validate ‘Verify the forwarding information base’, not ‘Inspect route withdrawal after health failure’, because the FIB holds selected forwarding entries and is essential to actual packet delivery. That separate implementation serves confirm the FortiGate has installed a usable next hop for a destination, whereas the audit needs evidence specifically of ‘Inspect route withdrawal after health failure’ at a test lab containing an overlay tunnel and two underlay next hops.
Question 8
For a data analytics site comparing primary and backup overlay health, a technical review examines the control ‘Compare health across multiple SLAs’ for the objective to measure distinct service destinations separately rather than treating the internet as one uniform path. Which statement best describes what it changes?
- An SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface.
- Active SD-WAN health checks send periodic probes to a designated target over monitored members.
- Separate health checks can reveal that a circuit reaches one remote service well but another poorly.
- A latency target makes a member fail that SLA when measured delay exceeds the configured limit.
Explanation
Correct Answer
C:‘Compare health across multiple SLAs’ is used to measure distinct service destinations separately rather than treating the internet as one uniform path in a data analytics site comparing primary and backup overlay health; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that each relevant service target has its own member quality observations; the rollout must also respect this constraint: A single probe destination cannot establish health to every application region.
Incorrect Answers
A:The described behavior is part of ‘Assign the relevant member set to a health check’, used to compare only the transport members serving a given application class instead of the role of ‘Compare health across multiple SLAs’. In contrast to ‘Assign the relevant member set to a health check’, ‘Compare health across multiple SLAs’ follows a different mechanism: separate health checks can reveal that a circuit reaches one remote service well but another poorly. Treating ‘Assign the relevant member set to a health check’ as equivalent would not address the administrator assumes one successful probe proves all SaaS destinations are reachable in a data analytics site comparing primary and backup overlay health.
B:The described behavior is part of ‘Create an active probe health check’, used to measure reachability and delay even when no user sessions traverse a circuit instead of the role of ‘Compare health across multiple SLAs’. In contrast to ‘Create an active probe health check’, ‘Compare health across multiple SLAs’ follows a different mechanism: separate health checks can reveal that a circuit reaches one remote service well but another poorly. Treating ‘Create an active probe health check’ as equivalent would not address the administrator assumes one successful probe proves all SaaS destinations are reachable in a data analytics site comparing primary and backup overlay health.
D:The described behavior is part of ‘Set latency SLA threshold’, used to exclude paths whose round-trip delay exceeds a real-time application's bound instead of the role of ‘Compare health across multiple SLAs’. In contrast to ‘Set latency SLA threshold’, ‘Compare health across multiple SLAs’ follows a different mechanism: separate health checks can reveal that a circuit reaches one remote service well but another poorly. Treating ‘Set latency SLA threshold’ as equivalent would not address the administrator assumes one successful probe proves all SaaS destinations are reachable in a data analytics site comparing primary and backup overlay health.
Question 9
In a change-control meeting for a managed laptop fleet governed by FortiClient endpoint profiles, a colleague challenges the proposed control ‘Configure pre-connection posture enforcement’ for the requirement to block an untrusted FortiClient endpoint before it establishes its protected cloud tunnel. Which explanation accurately describes its behavior?
- Endpoint tagging can evaluate the presence and properties of a required client certificate.
- An allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity.
- Private access policies can use security posture tags as dynamic matching criteria.
- A configured pre-connection check can allow or deny a tunnel attempt based on an assigned posture tag.
Explanation
Correct Answer
D:‘Configure pre-connection posture enforcement’ is used to block an untrusted FortiClient endpoint before it establishes its protected cloud tunnel in a managed laptop fleet governed by FortiClient endpoint profiles; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that FortiClient rejects the tunnel according to the configured posture-tag action; the rollout must also respect this constraint: This workflow depends on appropriate IPsec remote-agent support and endpoint profile setup.
Incorrect Answers
A:The described behavior is part of ‘Use a certificate-based posture check’, used to identify managed endpoints that carry an enterprise-issued device credential instead of the role of ‘Configure pre-connection posture enforcement’. In contrast to ‘Use a certificate-based posture check’, ‘Configure pre-connection posture enforcement’ follows a different mechanism: a configured pre-connection check can allow or deny a tunnel attempt based on an assigned posture tag. Treating ‘Use a certificate-based posture check’ as equivalent would not address a failed device is permitted to connect and only rejected later at application policy in a managed laptop fleet governed by FortiClient endpoint profiles.
B:The described behavior is part of ‘Review the posture tag's allow or deny direction’, used to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint instead of the role of ‘Configure pre-connection posture enforcement’. In contrast to ‘Review the posture tag's allow or deny direction’, ‘Configure pre-connection posture enforcement’ follows a different mechanism: a configured pre-connection check can allow or deny a tunnel attempt based on an assigned posture tag. Treating ‘Review the posture tag's allow or deny direction’ as equivalent would not address a failed device is permitted to connect and only rejected later at application policy in a managed laptop fleet governed by FortiClient endpoint profiles.
C:The described behavior is part of ‘Assign compliant endpoint tags to private policies’, used to grant sensitive private access only to managed devices meeting specified security conditions instead of the role of ‘Configure pre-connection posture enforcement’. In contrast to ‘Assign compliant endpoint tags to private policies’, ‘Configure pre-connection posture enforcement’ follows a different mechanism: a configured pre-connection check can allow or deny a tunnel attempt based on an assigned posture tag. Treating ‘Assign compliant endpoint tags to private policies’ as equivalent would not address a failed device is permitted to connect and only rejected later at application policy in a managed laptop fleet governed by FortiClient endpoint profiles.
Question 10
In a change-control meeting for an onboarding pilot with a small set of managed test laptops, the team is closing the change after testing a design to roll out FortiClient at scale without requiring hundreds of manual installer sessions. Which result supports closure?
- A user authenticates at the IdP and returns with an accepted SAML assertion.
- Managed devices receive the intended FortiClient package through centralized deployment.
- New login attempts follow the configured IdP authentication flow.
- FortiSASE test authentication obtains a valid response from the designated RADIUS source.
Explanation
Correct Answer
B:This checks ‘Deploy FortiClient using enterprise management’ at the correct operational boundary: group policy or mobile device management can deploy prepared FortiClient packages to managed endpoints. It demonstrates the specific capability to roll out FortiClient at scale without requiring hundreds of manual installer sessions in an onboarding pilot with a small set of managed test laptops; deployment should additionally respect the constraint: The enterprise deployment tool must match endpoint operating systems and device ownership.
Incorrect Answers
A:That observation belongs to ‘Configure SAML single sign-on’, not ‘Deploy FortiClient using enterprise management’; its purpose is to let staff authenticate to FortiSASE through the corporate identity provider, the underlying behavior is that FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users. The reviewer is instead verifying ‘Deploy FortiClient using enterprise management’ for an onboarding pilot with a small set of managed test laptops, not the evidence produced by ‘Configure SAML single sign-on’.
C:That observation belongs to ‘Account for SSO precedence over other methods’, not ‘Deploy FortiClient using enterprise management’; its purpose is to avoid expecting local or RADIUS credentials to work after enabling SAML SSO, the underlying behavior is that enabling FortiSASE SSO takes precedence over previously configured user authentication methods. The reviewer is instead verifying ‘Deploy FortiClient using enterprise management’ for an onboarding pilot with a small set of managed test laptops, not the evidence produced by ‘Account for SSO precedence over other methods’.
D:That observation belongs to ‘Configure RADIUS authentication’, not ‘Deploy FortiClient using enterprise management’; its purpose is to authenticate managed remote agents against a reachable RADIUS infrastructure, the underlying behavior is that RADIUS integration delegates user authentication to a configured authentication server. The reviewer is instead verifying ‘Deploy FortiClient using enterprise management’ for an onboarding pilot with a small set of managed test laptops, not the evidence produced by ‘Configure RADIUS authentication’.