Question 770
During an authorized lab exercise for a hub-and-spoke network with internet breakout and private IPsec overlays, the incident notes state that the overlay tunnels are healthy but the remote private prefix lacks a usable route. Which change is most relevant to this symptom?
- Investigate: Use a BGP learned private prefix
- Investigate: Compare routing table and SD-WAN rule decision
- Investigate: Configure a static partner route through overlay zone
- Investigate: Keep underlay route for tunnel peer
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: a destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection. For a hub-and-spoke network with internet breakout and private IPsec overlays, a direct diagnostic confirmation would be that the target private CIDR resolves through the overlay SD-WAN zone; during repair, the remote peer must also know a return path to the local subnet.
Incorrect Answers
A:BGP can advertise and learn remote private networks over supported routed overlays, which serves the different requirement to obtain branch or data-center destinations without maintaining individual manual static routes instead of the behavior delivered by ‘Configure a static partner route through overlay zone’. If that component were misconfigured, a more characteristic finding would be that the tunnel stays up but dynamically announced private subnets never enter the routing table; the actual report concerns the overlay tunnels are healthy but the remote private prefix lacks a usable route at a hub-and-spoke network with internet breakout and private IPsec overlays.
B:SD-WAN candidate preference works only after routing makes a compatible egress path available, which serves the different requirement to find which stage prevents a preferred member from being used instead of the behavior delivered by ‘Configure a static partner route through overlay zone’. If that component were misconfigured, a more characteristic finding would be that an SD-WAN service names wan2 first but forwarding still excludes wan2; the actual report concerns the overlay tunnels are healthy but the remote private prefix lacks a usable route at a hub-and-spoke network with internet breakout and private IPsec overlays.
D:An overlay tunnel requires the public peer endpoint to remain reachable through an underlay path, which serves the different requirement to preserve transport reachability to an IPsec hub before private overlay traffic is steered instead of the behavior delivered by ‘Configure a static partner route through overlay zone’. If that component were misconfigured, a more characteristic finding would be that the VPN repeatedly drops when the route to its public peer recursively follows the overlay itself; the actual report concerns the overlay tunnels are healthy but the remote private prefix lacks a usable route at a hub-and-spoke network with internet breakout and private IPsec overlays.
Question 771
At a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, the change request is to favor a lower-priced uplink only when eligible under lowest-cost SLA rules. Which configuration is the most direct fit?
- Use an aggregate interface as a member
- Move a member between zones
- Set member cost
- Assign members to the intended zone
Explanation
Correct Answer
C:The cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred; that scope directly serves the goal to favor a lower-priced uplink only when eligible under lowest-cost SLA rules in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels. During implementation, cost does not replace health measurements or firewall policy matching rather than treating the configuration label as proof of working service.
Incorrect Answers
A:A link aggregation interface can be an SD-WAN member while LAG distributes frames across its constituent ports, a mechanism intended to treat an LAG upstream handoff as a selectable SD-WAN transport rather than the requested ‘Set member cost’ control. The stated task instead is to favor a lower-priced uplink only when eligible under lowest-cost SLA rules, and adjusting ‘Use an aggregate interface as a member’ would not deliver ‘Set member cost’. For the ‘Use an aggregate interface as a member’ alternative to ‘Set member cost’, LAG redundancy and SD-WAN multi-carrier path selection solve different failure domains.
B:Reassigning the member to a different zone changes its logical policy and rule membership, a mechanism intended to change how one interface is referenced by routes and policies without rebuilding the WAN port rather than the requested ‘Set member cost’ control. The stated task instead is to favor a lower-priced uplink only when eligible under lowest-cost SLA rules, and adjusting ‘Move a member between zones’ would not deliver ‘Set member cost’. For the ‘Move a member between zones’ alternative to ‘Set member cost’, review policies and static routes referencing the source zone before moving the member.
D:A member's zone association determines which zone-based routes and policies can use that interface, a mechanism intended to put two ISP circuits in the internet transport zone rather than the private-overlay group rather than the requested ‘Set member cost’ control. The stated task instead is to favor a lower-priced uplink only when eligible under lowest-cost SLA rules, and adjusting ‘Assign members to the intended zone’ would not deliver ‘Set member cost’. For the ‘Assign members to the intended zone’ alternative to ‘Set member cost’, zone placement does not automatically create a firewall rule or a route.
Question 772
During an authorized lab exercise for an enterprise interconnecting SD-WAN overlays and cloud security edges, a pilot is about to enable ‘Establish BGP with the SPA hub’. Which precaution is most closely tied to this choice?
- Branch integration requires transport reachability and matching on-ramp security policy.
- Name resolution must be reachable over the chosen private access topology.
- Redundancy depends on both routing and policy consistency across hubs.
- Autonomous system settings and route filters must agree across peers.
Explanation
Correct Answer
D:This condition matters for ‘Establish BGP with the SPA hub’ because a supported SPA BGP design learns and advertises routes over the selected overlay connection. Omitting the relevant safeguard can produce the hub responds on its tunnel addresses but remote application routes never appear; a successful test at an enterprise interconnecting SD-WAN overlays and cloud security edges would instead demonstrate that the BGP neighbor is established and expected private prefixes are accepted.
Incorrect Answers
A:The condition is associated with ‘Integrate branch SD-WAN with FortiSASE on-ramp’, a mechanism used to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge instead of ‘Establish BGP with the SPA hub’, because a supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs. For ‘Establish BGP with the SPA hub’, unlike ‘Integrate branch SD-WAN with FortiSASE on-ramp’, the characteristic failure would be the hub responds on its tunnel addresses but remote application routes never appear, which this alternative prerequisite would not directly address at an enterprise interconnecting SD-WAN overlays and cloud security edges.
B:The condition is associated with ‘Configure DNS resolution for private names’, a mechanism used to let remote users resolve internal application FQDNs to protected addresses instead of ‘Establish BGP with the SPA hub’, because private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers. For ‘Establish BGP with the SPA hub’, unlike ‘Configure DNS resolution for private names’, the characteristic failure would be the hub responds on its tunnel addresses but remote application routes never appear, which this alternative prerequisite would not directly address at an enterprise interconnecting SD-WAN overlays and cloud security edges.
C:The condition is associated with ‘Use a redundant private-access hub’, a mechanism used to maintain access to applications when one data-center gateway or tunnel fails instead of ‘Establish BGP with the SPA hub’, because multiple suitably configured SPA hubs can provide a redundant path to private resources. For ‘Establish BGP with the SPA hub’, unlike ‘Use a redundant private-access hub’, the characteristic failure would be the hub responds on its tunnel addresses but remote application routes never appear, which this alternative prerequisite would not directly address at an enterprise interconnecting SD-WAN overlays and cloud security edges.
Question 773
Within a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, the operator applies the control ‘Use an IPsec interface as a member’ as part of an effort to apply SD-WAN selection to redundant encrypted site-to-site paths. Which operating behavior should the team expect?
- A zone can contain one member, allowing special security or routing treatment for that interface.
- Physical WAN ports can act as members with their own connectivity, next hops, costs, and measured health.
- The cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred.
- Route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing.
- Disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration.
Explanation
Correct Answer
D:‘Use an IPsec interface as a member’ is used to apply SD-WAN selection to redundant encrypted site-to-site paths in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the tunnel interface is listed as an SD-WAN overlay member; the rollout must also respect this constraint: Bring up the route-based tunnel and verify selectors and reachability independently.
Incorrect Answers
A: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 ‘Use an IPsec interface as a member’. In contrast to ‘Use an isolated single-member zone’, ‘Use an IPsec interface as a member’ follows a different mechanism: route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing. Treating ‘Use an isolated single-member zone’ as equivalent would not address the VPN tunnel passes traffic manually but is absent from overlay service member lists in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
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 ‘Use an IPsec interface as a member’. In contrast to ‘Use a physical interface as a member’, ‘Use an IPsec interface as a member’ follows a different mechanism: route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing. Treating ‘Use a physical interface as a member’ as equivalent would not address the VPN tunnel passes traffic manually but is absent from overlay service member lists in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
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 ‘Use an IPsec interface as a member’. In contrast to ‘Set member cost’, ‘Use an IPsec interface as a member’ follows a different mechanism: route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing. Treating ‘Set member cost’ as equivalent would not address the VPN tunnel passes traffic manually but is absent from overlay service member lists in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
E:The described behavior is part of ‘Disable a maintenance member’, used to exclude a WAN circuit from SD-WAN decisions during scheduled carrier work instead of the role of ‘Use an IPsec interface as a member’. In contrast to ‘Disable a maintenance member’, ‘Use an IPsec interface as a member’ follows a different mechanism: route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing. Treating ‘Disable a maintenance member’ as equivalent would not address the VPN tunnel passes traffic manually but is absent from overlay service member lists in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
Question 774
In a change-control meeting for a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall, a design review calls for a way to use a common logical outgoing interface for two alternate WAN circuits. What should the operator configure?
- Use DHCP-provided WAN gateway
- Configure an SD-WAN zone
- Enable SD-WAN traffic logging on the egress policy
- Enable interface-based source NAT
Explanation
Correct Answer
B:A zone groups SD-WAN members for firewall policies, static routes, and service rules without merging the physical circuits; that scope directly serves the goal to use a common logical outgoing interface for two alternate WAN circuits in a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall. During implementation, use the zone as the policy interface instead of individual member ports rather than treating the configuration label as proof of working service.
Incorrect Answers
A:An SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface, a mechanism intended to keep a dynamically assigned ISP next hop aligned with lease changes rather than the requested ‘Configure an SD-WAN zone’ control. The stated task instead is to use a common logical outgoing interface for two alternate WAN circuits, and adjusting ‘Use DHCP-provided WAN gateway’ would not deliver ‘Configure an SD-WAN zone’. For the ‘Use DHCP-provided WAN gateway’ alternative to ‘Configure an SD-WAN zone’, a DHCP-derived gateway should not be confused with the SD-WAN zone route itself.
C:Logging allowed traffic records matched firewall-policy activity and supports investigation of chosen egress paths, a mechanism intended to retain session evidence when validating a new dual-WAN deployment rather than the requested ‘Configure an SD-WAN zone’ control. The stated task instead is to use a common logical outgoing interface for two alternate WAN circuits, and adjusting ‘Enable SD-WAN traffic logging on the egress policy’ would not deliver ‘Configure an SD-WAN zone’. For the ‘Enable SD-WAN traffic logging on the egress policy’ alternative to ‘Configure an SD-WAN zone’, logging visibility should be configured on the matched firewall policy, not assumed from SD-WAN alone.
D:Source NAT using the outgoing interface address permits private LAN hosts to communicate through each public ISP path, a mechanism intended to translate RFC1918 office source addresses for public internet egress rather than the requested ‘Configure an SD-WAN zone’ control. The stated task instead is to use a common logical outgoing interface for two alternate WAN circuits, and adjusting ‘Enable interface-based source NAT’ would not deliver ‘Configure an SD-WAN zone’. For the ‘Enable interface-based source NAT’ alternative to ‘Configure an SD-WAN zone’, the NAT decision belongs in the applicable firewall policy and must match the routing design.
Question 775
At a remote-user design needing both public SaaS and internal subnet access, a controlled test reveals that the SPA connection is up but the private /24 is absent from SASE routing information. Which setting is the strongest first lead?
- Investigate: Use SD-WAN private access for TCP and UDP
- Investigate: Use ZTNA application proxy for a protected TCP app
- Investigate: Establish BGP with the SPA hub
- Investigate: Advertise internal prefixes to SPA routing
Explanation
Correct Answer
D:The symptom identifies the missing operational behavior: routing advertisement or static private routes informs FortiSASE how to reach protected application subnets. For a remote-user design needing both public SaaS and internal subnet access, a direct diagnostic confirmation would be that the intended private prefix is visible through the correct service connection; during repair, a working tunnel does not automatically advertise every internal route.
Incorrect Answers
A: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 ‘Advertise internal prefixes to SPA routing’. 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 the SPA connection is up but the private /24 is absent from SASE routing information at a remote-user design needing both public SaaS and internal subnet access.
B:ZTNA private access targets authorized TCP applications rather than granting generic network reachability, which serves the different requirement to publish a narrowly scoped internal TCP application through a FortiGate ZTNA gateway instead of the behavior delivered by ‘Advertise internal prefixes to SPA routing’. If that component were misconfigured, a more characteristic finding would be that an administrator offers broad subnet access when only one protected TCP service is approved; the actual report concerns the SPA connection is up but the private /24 is absent from SASE routing information at a remote-user design needing both public SaaS and internal subnet access.
C: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 ‘Advertise internal prefixes to SPA routing’. 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 the SPA connection is up but the private /24 is absent from SASE routing information at a remote-user design needing both public SaaS and internal subnet access.
Question 776
Within an administrator analyzing cloud application consumption by user group, the administrator must identify repeated attempts to reach restricted destinations across remote users without redesigning unrelated services. Which option addresses the goal?
- Trend security events by category
- Use report time filters for incident scoping
- Correlate policy action with destination risk
- Compare user traffic volume trends
- Review application usage reports
Explanation
Correct Answer
C:Security analytics can group blocked traffic by destination or policy to reveal recurring patterns; that scope directly serves the goal to identify repeated attempts to reach restricted destinations across remote users in an administrator analyzing cloud application consumption by user group. During implementation, an event count requires context to distinguish mistakes from an actual threat campaign rather than treating the configuration label as proof of working service.
Incorrect Answers
A: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 ‘Correlate policy action with destination risk’ control. The stated task instead is to identify repeated attempts to reach restricted destinations across remote users, and adjusting ‘Trend security events by category’ would not deliver ‘Correlate policy action with destination risk’. For the ‘Trend security events by category’ alternative to ‘Correlate policy action with destination risk’, changes in log policy or user population must be considered before claiming a causal improvement.
B:Time-bound analytics separate incident-period activity from unrelated historical traffic, a mechanism intended to limit an investigation to the period in which an employee reported a cloud access failure rather than the requested ‘Correlate policy action with destination risk’ control. The stated task instead is to identify repeated attempts to reach restricted destinations across remote users, and adjusting ‘Use report time filters for incident scoping’ would not deliver ‘Correlate policy action with destination risk’. For the ‘Use report time filters for incident scoping’ alternative to ‘Correlate policy action with destination risk’, correlate device and timezone timestamps before drawing incident chronology conclusions.
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 ‘Correlate policy action with destination risk’ control. The stated task instead is to identify repeated attempts to reach restricted destinations across remote users, and adjusting ‘Compare user traffic volume trends’ would not deliver ‘Correlate policy action with destination risk’. For the ‘Compare user traffic volume trends’ alternative to ‘Correlate policy action with destination risk’, traffic volume alone is not evidence that a session is malicious.
E:Application analytics classify observed traffic into recognizable applications for reporting, a mechanism intended to identify which SaaS or application class dominates inspected remote traffic rather than the requested ‘Correlate policy action with destination risk’ control. The stated task instead is to identify repeated attempts to reach restricted destinations across remote users, and adjusting ‘Review application usage reports’ would not deliver ‘Correlate policy action with destination risk’. For the ‘Review application usage reports’ alternative to ‘Correlate policy action with destination risk’, app recognition depends on available inspection and classification signals.
Question 777
For a global remote-user rollout with separate employee and contractor policies, a maintenance plan requires the firewall team to direct selected browser destinations to the FortiSASE secure web gateway. Which choice is appropriate?
- Enroll an agentless web user
- Distribute a FortiSASE invitation code
- Configure SAML single sign-on
- Distribute proxy autoconfiguration settings
Explanation
Correct Answer
D:A PAC-based proxy configuration tells supported browsers which web requests should use the cloud proxy; that scope directly serves the goal to direct selected browser destinations to the FortiSASE secure web gateway in a global remote-user rollout with separate employee and contractor policies. During implementation, PAC logic and browser support should be tested for exceptions and split behavior rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Agentless secure web gateway access uses explicit proxy steering rather than a full-device agent tunnel, a mechanism intended to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient rather than the requested ‘Distribute proxy autoconfiguration settings’ control. The stated task instead is to direct selected browser destinations to the FortiSASE secure web gateway, and adjusting ‘Enroll an agentless web user’ would not deliver ‘Distribute proxy autoconfiguration settings’. For the ‘Enroll an agentless web user’ alternative to ‘Distribute proxy autoconfiguration settings’, agentless proxy steering does not automatically tunnel all nonweb IP traffic.
B:The Onboard Users workflow provides information that remote users use for FortiSASE client registration, a mechanism intended to bind an invited remote user's FortiClient enrollment to the correct organization rather than the requested ‘Distribute proxy autoconfiguration settings’ control. The stated task instead is to direct selected browser destinations to the FortiSASE secure web gateway, and adjusting ‘Distribute a FortiSASE invitation code’ would not deliver ‘Distribute proxy autoconfiguration settings’. For the ‘Distribute a FortiSASE invitation code’ alternative to ‘Distribute proxy autoconfiguration settings’, onboarding credentials should be shared only with the intended users.
C:FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users, a mechanism intended to let staff authenticate to FortiSASE through the corporate identity provider rather than the requested ‘Distribute proxy autoconfiguration settings’ control. The stated task instead is to direct selected browser destinations to the FortiSASE secure web gateway, and adjusting ‘Configure SAML single sign-on’ would not deliver ‘Distribute proxy autoconfiguration settings’. For the ‘Configure SAML single sign-on’ alternative to ‘Distribute proxy autoconfiguration settings’, the client browser must reach the IdP and the SP metadata and certificates must agree.
Question 778
In a change-control meeting for a small campus moving from single-WAN routing to resilient FortiGate SD-WAN, the team is closing the change after testing a design to keep ISP transports and IPsec private overlays independently selectable in policy. Which result supports closure?
- The member gateway matches the adjacent router on that circuit.
- A matching accepted session shows the LAN ingress and SD-WAN zone egress.
- Both carrier-facing ports appear as enabled SD-WAN members.
- Firewall and service policies distinguish transport and private-overlay zones.
Explanation
Correct Answer
D:This checks ‘Separate underlay and overlay SD-WAN zones’ at the correct operational boundary: distinct SD-WAN zones make underlay internet circuits and overlay tunnels separate logical choices. It demonstrates the specific capability to keep ISP transports and IPsec private overlays independently selectable in policy in a small campus moving from single-WAN routing to resilient FortiGate SD-WAN; deployment should additionally respect the constraint: Create the correct member-to-zone mapping before using zones in rules.
Incorrect Answers
A:That observation belongs to ‘Set a static WAN member gateway’, not ‘Separate underlay and overlay SD-WAN zones’; its purpose is to reach an ISP next hop on a manually numbered uplink, the underlying behavior is that a statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding. The reviewer is instead verifying ‘Separate underlay and overlay SD-WAN zones’ for a small campus moving from single-WAN routing to resilient FortiGate SD-WAN, not the evidence produced by ‘Set a static WAN member gateway’.
B:That observation belongs to ‘Allow LAN-to-SD-WAN firewall policy’, not ‘Separate underlay and overlay SD-WAN zones’; its purpose is to authorize office clients to reach external destinations over eligible SD-WAN members, the underlying behavior is that the stateful firewall policy permits internal-to-zone sessions and can apply source NAT and inspection as required. The reviewer is instead verifying ‘Separate underlay and overlay SD-WAN zones’ for a small campus moving from single-WAN routing to resilient FortiGate SD-WAN, not the evidence produced by ‘Allow LAN-to-SD-WAN firewall policy’.
C:That observation belongs to ‘Enable SD-WAN member selection’, not ‘Separate underlay and overlay SD-WAN zones’; its purpose is to place two independently addressed internet interfaces under centralized path selection, the underlying behavior is that SD-WAN creates selectable member objects while retaining each interface's underlying addressing and link state. The reviewer is instead verifying ‘Separate underlay and overlay SD-WAN zones’ for a small campus moving from single-WAN routing to resilient FortiGate SD-WAN, not the evidence produced by ‘Enable SD-WAN member selection’.
Question 779
At a company enrolling remote Windows and macOS employees into FortiSASE, an engineer is preparing ‘Configure RADIUS authentication’ to authenticate managed remote agents against a reachable RADIUS infrastructure. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- Proxy SSO often depends on compatible deep inspection and IdP reachability.
- Local credentials are less desirable than an enterprise identity source at scale.
- The endpoint registers to the intended FortiSASE environment after using the invitation.
- Configure the correct shared secret and reachable authentication service endpoints.
- FortiSASE test authentication obtains a valid response from the designated RADIUS source.
Explanation
Correct Answers
D:This safeguard applies to ‘Configure RADIUS authentication’, which works because RADIUS integration delegates user authentication to a configured authentication server. Without the correct deployment condition, operators may see that RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server in a company enrolling remote Windows and macOS employees into FortiSASE.
E:The observation follows from the operation of ‘Configure RADIUS authentication’: RADIUS integration delegates user authentication to a configured authentication server. It directly tests the requested ability to authenticate managed remote agents against a reachable RADIUS infrastructure in a company enrolling remote Windows and macOS employees into FortiSASE, rather than another policy or network layer.
Incorrect Answers
A:The planning point is associated with ‘Configure agentless proxy SSO’, not ‘Configure RADIUS authentication’; its real role is to associate proxied browser traffic with enterprise user identity during secure web gateway inspection. The required deployment instead centers on ‘Configure RADIUS authentication’, rather than ‘Configure agentless proxy SSO’; the distinct symptom to guard against is that RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server.
B:The planning point is associated with ‘Create a local FortiSASE test user’, not ‘Configure RADIUS authentication’; its real role is to authenticate a limited lab user when no central identity source has yet been connected. The required deployment instead centers on ‘Configure RADIUS authentication’, rather than ‘Create a local FortiSASE test user’; the distinct symptom to guard against is that RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server.
C:This result would validate ‘Distribute a FortiSASE invitation code’, not ‘Configure RADIUS authentication’, because the Onboard Users workflow provides information that remote users use for FortiSASE client registration. That separate implementation serves bind an invited remote user's FortiClient enrollment to the correct organization, whereas the audit needs evidence specifically of ‘Configure RADIUS authentication’ at a company enrolling remote Windows and macOS employees into FortiSASE.
Question 780
Within an industrial branch sending payroll traffic to a data-center application, after the rollout, operators find that a backup static route remains installed ahead of an intended learned route due to distance. Where should they focus troubleshooting?
- Investigate: Confirm return route for remote private access
- Investigate: Review administrative distance
- Investigate: Prefer a more specific prefix
- Investigate: Configure a static partner route through overlay zone
- Investigate: Use routing diagnostics before changing SD-WAN cost
- Investigate: Verify the forwarding information base
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: administrative distance influences which equal-prefix route source is preferred for installation. For an industrial branch sending payroll traffic to a data-center application, a direct diagnostic confirmation would be that the expected route has the winning administrative distance for its destination; during repair, specificity is considered before comparing administrative distance on different prefix lengths.
Incorrect Answers
A:Bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix, which serves the different requirement to repair one-way traffic where forward packets reach the data center but replies do not instead of the behavior delivered by ‘Review administrative distance’. If that component were misconfigured, a more characteristic finding would be that SYN packets arrive at the protected application but no responses reach the branch client; the actual report concerns a backup static route remains installed ahead of an intended learned route due to distance at an industrial branch sending payroll traffic to a data-center application.
C:Longest-prefix match chooses a more specific valid destination route ahead of a broader default, which serves the different requirement to send a partner network into a private tunnel even while default internet routing is present instead of the behavior delivered by ‘Review administrative distance’. If that component were misconfigured, a more characteristic finding would be that partner traffic exits public internet despite a required private-subnet route being missing; the actual report concerns a backup static route remains installed ahead of an intended learned route due to distance at an industrial branch sending payroll traffic to a data-center application.
D:A destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection, which serves the different requirement to reach an on-premises network across an IPsec overlay SD-WAN group instead of the behavior delivered by ‘Review administrative distance’. If that component were misconfigured, a more characteristic finding would be that the overlay tunnels are healthy but the remote private prefix lacks a usable route; the actual report concerns a backup static route remains installed ahead of an intended learned route due to distance at an industrial branch sending payroll traffic to a data-center application.
E:Route inspection distinguishes absent routes from member cost or performance rankings, which serves the different requirement to avoid misdiagnosing unreachable prefixes as an economic-selection problem instead of the behavior delivered by ‘Review administrative distance’. If that component were misconfigured, a more characteristic finding would be that the application is unreachable although administrators keep reducing the WAN member cost; the actual report concerns a backup static route remains installed ahead of an intended learned route due to distance at an industrial branch sending payroll traffic to a data-center application.
F:The FIB holds selected forwarding entries and is essential to actual packet delivery, which serves the different requirement to confirm the FortiGate has installed a usable next hop for a destination instead of the behavior delivered by ‘Review administrative distance’. If that component were misconfigured, a more characteristic finding would be that the service-rule configuration looks valid while the forwarding result points elsewhere; the actual report concerns a backup static route remains installed ahead of an intended learned route due to distance at an industrial branch sending payroll traffic to a data-center application.