Question 540
At a remote call center measuring two ISP paths to the same application target, the change request is to distinguish basic connectivity from acceptable application performance. Which configuration is the most direct fit?
- Create an active probe health check
- Set packet-loss SLA threshold
- Review SLA historical changes
- Investigate alive versus SLA-qualified state
Explanation
Correct Answer
D:A member may be reachable and report alive while failing a stricter SLA target for performance; that scope directly serves the goal to distinguish basic connectivity from acceptable application performance in a remote call center measuring two ISP paths to the same application target. During implementation, do not equate successful probes with meeting every target threshold rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Active SD-WAN health checks send periodic probes to a designated target over monitored members, a mechanism intended to measure reachability and delay even when no user sessions traverse a circuit rather than the requested ‘Investigate alive versus SLA-qualified state’ control. The stated task instead is to distinguish basic connectivity from acceptable application performance, and adjusting ‘Create an active probe health check’ would not deliver ‘Investigate alive versus SLA-qualified state’. For the ‘Create an active probe health check’ alternative to ‘Investigate alive versus SLA-qualified state’, the target must answer the selected probe method and be reachable from those paths.
B:A loss target evaluates the fraction of missing probes or measured packets before declaring SLA compliance, a mechanism intended to protect application sessions from a link that intermittently drops packets rather than the requested ‘Investigate alive versus SLA-qualified state’ control. The stated task instead is to distinguish basic connectivity from acceptable application performance, and adjusting ‘Set packet-loss SLA threshold’ would not deliver ‘Investigate alive versus SLA-qualified state’. For the ‘Set packet-loss SLA threshold’ alternative to ‘Investigate alive versus SLA-qualified state’, check loss independently of latency and jitter instead of inferring it from link-up state.
C:Historical SLA samples and logs help distinguish transient degradation from a persistent member failure, a mechanism intended to establish whether a brief performance decline coincides with a reported outage rather than the requested ‘Investigate alive versus SLA-qualified state’ control. The stated task instead is to distinguish basic connectivity from acceptable application performance, and adjusting ‘Review SLA historical changes’ would not deliver ‘Investigate alive versus SLA-qualified state’. For the ‘Review SLA historical changes’ alternative to ‘Investigate alive versus SLA-qualified state’, a current snapshot cannot reconstruct past jitter, loss, and threshold violations by itself.
Question 541
Within a branch connected to a SASE point of presence by an encrypted service path, after the rollout, operators find that the branch's WAN works locally but site users bypass the expected SASE inspection path. Where should they focus troubleshooting?
- Investigate: Integrate branch SD-WAN with FortiSASE on-ramp
- Investigate: Use IPsec transport for the SASE branch connection
- Investigate: Use ZTNA application proxy for a protected TCP app
- Investigate: Establish BGP with the SPA hub
- Investigate: Allow security PoP access to private applications
Explanation
Correct Answer
A:The symptom identifies the missing operational behavior: a supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs. For a branch connected to a SASE point of presence by an encrypted service path, a direct diagnostic confirmation would be that the branch overlay to the service is established and inspected traffic appears in SASE logs; during repair, branch integration requires transport reachability and matching on-ramp security policy.
Incorrect Answers
B: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 ‘Integrate branch SD-WAN with FortiSASE on-ramp’. 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 the branch's WAN works locally but site users bypass the expected SASE inspection path at a branch connected to a SASE point of presence by an encrypted service path.
C: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 ‘Integrate branch SD-WAN with FortiSASE on-ramp’. 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 branch's WAN works locally but site users bypass the expected SASE inspection path at a branch connected to a SASE point of presence by an encrypted service path.
D: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 ‘Integrate branch SD-WAN with FortiSASE on-ramp’. 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 branch's WAN works locally but site users bypass the expected SASE inspection path at a branch connected to a SASE point of presence by an encrypted service path.
E:Hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers, which serves the different requirement to permit cloud-originated SPA traffic through the data-center firewall policy instead of the behavior delivered by ‘Integrate branch SD-WAN with FortiSASE on-ramp’. If that component were misconfigured, a more characteristic finding would be that BGP and tunnels are up yet all application SYN packets are denied at the data-center perimeter; the actual report concerns the branch's WAN works locally but site users bypass the expected SASE inspection path at a branch connected to a SASE point of presence by an encrypted service path.
Question 542
Within a logistics site where routing and SD-WAN services have separate responsibilities, the administrator must distribute independent new sessions across eligible members rather than always selecting one without redesigning unrelated services. Which option addresses the goal?
- Enable SD-WAN rule load balancing
- Consider first-flow application recognition
- Use Best Quality with latency
- Test rule matching with service diagnostics
- Match by detected application
Explanation
Correct Answer
A:A load-balancing rule spreads session assignments among candidates by its configured selection behavior; that scope directly serves the goal to distribute independent new sessions across eligible members rather than always selecting one in a logistics site where routing and SD-WAN services have separate responsibilities. During implementation, per-session balancing does not mean one TCP flow is split packet by packet across every link rather than treating the configuration label as proof of working service.
Incorrect Answers
B:FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches, a mechanism intended to explain why the first newly observed app session may not match application-based steering immediately rather than the requested ‘Enable SD-WAN rule load balancing’ control. The stated task instead is to distribute independent new sessions across eligible members rather than always selecting one, and adjusting ‘Consider first-flow application recognition’ would not deliver ‘Enable SD-WAN rule load balancing’. For the ‘Consider first-flow application recognition’ alternative to ‘Enable SD-WAN rule load balancing’, do not assume every first encrypted connection is identified before its initial path is chosen.
C:Best Quality can rank member quality using latency collected by the designated performance health check, a mechanism intended to prefer the lowest-delay usable path for an interactive application rather than the requested ‘Enable SD-WAN rule load balancing’ control. The stated task instead is to distribute independent new sessions across eligible members rather than always selecting one, and adjusting ‘Use Best Quality with latency’ would not deliver ‘Enable SD-WAN rule load balancing’. For the ‘Use Best Quality with latency’ alternative to ‘Enable SD-WAN rule load balancing’, latency-based ranking does not ensure the lowest commercial ISP bill.
D:SD-WAN service diagnostics expose matched rules, interface lists, modes, and selected member status, a mechanism intended to identify which SD-WAN rule and candidate member were chosen for a particular session rather than the requested ‘Enable SD-WAN rule load balancing’ control. The stated task instead is to distribute independent new sessions across eligible members rather than always selecting one, and adjusting ‘Test rule matching with service diagnostics’ would not deliver ‘Enable SD-WAN rule load balancing’. For the ‘Test rule matching with service diagnostics’ alternative to ‘Enable SD-WAN rule load balancing’, inspect rule match and routing context together before changing quality thresholds.
E:Application-based SD-WAN rules use application detection information to identify supported traffic signatures, a mechanism intended to prefer an SD-WAN path based on application identification rather than fixed port alone rather than the requested ‘Enable SD-WAN rule load balancing’ control. The stated task instead is to distribute independent new sessions across eligible members rather than always selecting one, and adjusting ‘Match by detected application’ would not deliver ‘Enable SD-WAN rule load balancing’. For the ‘Match by detected application’ alternative to ‘Enable SD-WAN rule load balancing’, Application Control must be enabled in the matching firewall policy for identification-based steering.
Question 543
Within a cloud security tenant inspecting traffic from managed remote laptops, the team wants to avoid an ineffective configuration of ‘Use cloud API CASB for SaaS data at rest’. Which consideration deserves attention?
- Encrypted payload scanning depends on appropriate TLS inspection and certificate trust.
- API authorization and provider support differ from inline real-time access controls.
- Specific overrides should be tested against recognized application signatures.
- SaaS payload controls normally require SSL deep inspection and compatible traffic protocols.
- IPS coverage depends on the traffic inspection path and enabled profile settings.
Explanation
Correct Answer
B:This condition matters for ‘Use cloud API CASB for SaaS data at rest’ because aPI-connected CASB can examine supported SaaS tenant content and events without requiring every action to cross the inline proxy. Omitting the relevant safeguard can produce a compliance review needs to discover sensitive files already stored in a connected SaaS tenant; a successful test at a cloud security tenant inspecting traffic from managed remote laptops would instead demonstrate that the connected SaaS application's API scans produce inventory and findings about stored content.
Incorrect Answers
A:The condition is associated with ‘Apply an antivirus profile to allowed traffic’, a mechanism used to detect malware payloads passing through a permitted cloud access policy instead of ‘Use cloud API CASB for SaaS data at rest’, because an enabled antivirus inspection component examines supported file content for malicious signatures or behavior indicators. For ‘Use cloud API CASB for SaaS data at rest’, unlike ‘Apply an antivirus profile to allowed traffic’, the characteristic failure would be a compliance review needs to discover sensitive files already stored in a connected SaaS tenant, which this alternative prerequisite would not directly address at a cloud security tenant inspecting traffic from managed remote laptops.
C:The condition is associated with ‘Use application category overrides’, a mechanism used to deny one high-risk application within an otherwise permitted collaboration category instead of ‘Use cloud API CASB for SaaS data at rest’, because Application Control overrides provide a more specific action than a broad application-category setting. For ‘Use cloud API CASB for SaaS data at rest’, unlike ‘Use application category overrides’, the characteristic failure would be a compliance review needs to discover sensitive files already stored in a connected SaaS tenant, which this alternative prerequisite would not directly address at a cloud security tenant inspecting traffic from managed remote laptops.
D:The condition is associated with ‘Use inline CASB application controls’, a mechanism used to apply SaaS-specific application restrictions on inspected cloud traffic instead of ‘Use cloud API CASB for SaaS data at rest’, because inline-CASB application control adds SaaS-aware decisions to recognized HTTP traffic traversing FortiSASE. For ‘Use cloud API CASB for SaaS data at rest’, unlike ‘Use inline CASB application controls’, the characteristic failure would be a compliance review needs to discover sensitive files already stored in a connected SaaS tenant, which this alternative prerequisite would not directly address at a cloud security tenant inspecting traffic from managed remote laptops.
E:The condition is associated with ‘Enable intrusion prevention’, a mechanism used to detect and block network exploits recognized by attack signatures or protocol decoders instead of ‘Use cloud API CASB for SaaS data at rest’, because IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions. For ‘Use cloud API CASB for SaaS data at rest’, unlike ‘Enable intrusion prevention’, the characteristic failure would be a compliance review needs to discover sensitive files already stored in a connected SaaS tenant, which this alternative prerequisite would not directly address at a cloud security tenant inspecting traffic from managed remote laptops.
Question 544
In a change-control meeting for a finance team that uses multiple approved SaaS applications, a design review calls for a way to isolate web rendering from the endpoint when access is required to a questionable website. What should the operator configure?
- Use inline CASB HTTP header restrictions
- Use a specific URL filter exception
- Apply remote browser isolation for risky sites
- Use application category overrides
Explanation
Correct Answer
C:Remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation; that scope directly serves the goal to isolate web rendering from the endpoint when access is required to a questionable website in a finance team that uses multiple approved SaaS applications. During implementation, RBI mitigates browser-execution exposure; it is not a substitute for identity verification rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions, a mechanism intended to restrict which SaaS tenant a managed user may access by adjusting inspected web request headers rather than the requested ‘Apply remote browser isolation for risky sites’ control. The stated task instead is to isolate web rendering from the endpoint when access is required to a questionable website, and adjusting ‘Use inline CASB HTTP header restrictions’ would not deliver ‘Apply remote browser isolation for risky sites’. For the ‘Use inline CASB HTTP header restrictions’ alternative to ‘Apply remote browser isolation for risky sites’, the SaaS provider must support the header convention and the request must be inspectable.
B:URL-level exceptions can refine category-based web filtering when an approved exception is required, a mechanism intended to allow a justified business website without disabling an entire restrictive category rather than the requested ‘Apply remote browser isolation for risky sites’ control. The stated task instead is to isolate web rendering from the endpoint when access is required to a questionable website, and adjusting ‘Use a specific URL filter exception’ would not deliver ‘Apply remote browser isolation for risky sites’. For the ‘Use a specific URL filter exception’ alternative to ‘Apply remote browser isolation for risky sites’, use the narrowest necessary exception to avoid weakening protection broadly.
D:Application Control overrides provide a more specific action than a broad application-category setting, a mechanism intended to deny one high-risk application within an otherwise permitted collaboration category rather than the requested ‘Apply remote browser isolation for risky sites’ control. The stated task instead is to isolate web rendering from the endpoint when access is required to a questionable website, and adjusting ‘Use application category overrides’ would not deliver ‘Apply remote browser isolation for risky sites’. For the ‘Use application category overrides’ alternative to ‘Apply remote browser isolation for risky sites’, specific overrides should be tested against recognized application signatures.
Question 545
During an authorized lab exercise for a dispersed workforce that uses a corporate SAML identity provider, the deployment standard specifies the control ‘Configure SAML single sign-on’ to let staff authenticate to FortiSASE through the corporate identity provider. Which functional description matches it?
- Local user records and groups can be configured for a small controlled FortiSASE rollout.
- The FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices.
- FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users.
- Registered FortiClient maintains connectivity with FortiSASE endpoint management and supplies identity or posture data.
Explanation
Correct Answer
C:‘Configure SAML single sign-on’ is used to let staff authenticate to FortiSASE through the corporate identity provider in a dispersed workforce that uses a corporate SAML identity provider; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that a user authenticates at the IdP and returns with an accepted SAML assertion; the rollout must also respect this constraint: The client browser must reach the IdP and the SP metadata and certificates must agree.
Incorrect Answers
A:The described behavior is part of ‘Create a local FortiSASE test user’, used to authenticate a limited lab user when no central identity source has yet been connected instead of the role of ‘Configure SAML single sign-on’. In contrast to ‘Create a local FortiSASE test user’, ‘Configure SAML single sign-on’ follows a different mechanism: FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users. Treating ‘Create a local FortiSASE test user’ as equivalent would not address redirect-based identity login cannot complete because the SP and IdP trust are not aligned in a dispersed workforce that uses a corporate SAML identity provider.
B:The described behavior is part of ‘Use preconfigured FortiClient installers’, used to enroll a small pilot group with minimal manual agent configuration instead of the role of ‘Configure SAML single sign-on’. In contrast to ‘Use preconfigured FortiClient installers’, ‘Configure SAML single sign-on’ follows a different mechanism: FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users. Treating ‘Use preconfigured FortiClient installers’ as equivalent would not address redirect-based identity login cannot complete because the SP and IdP trust are not aligned in a dispersed workforce that uses a corporate SAML identity provider.
D:The described behavior is part of ‘Maintain FortiClient tenant registration’, used to preserve endpoint identification and posture exchange for protected access instead of the role of ‘Configure SAML single sign-on’. In contrast to ‘Maintain FortiClient tenant registration’, ‘Configure SAML single sign-on’ follows a different mechanism: FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users. Treating ‘Maintain FortiClient tenant registration’ as equivalent would not address redirect-based identity login cannot complete because the SP and IdP trust are not aligned in a dispersed workforce that uses a corporate SAML identity provider.
Question 546
For a logistics site where routing and SD-WAN services have separate responsibilities, a technical review examines the control ‘Use a manual SD-WAN strategy’ for the objective to pin a specific business application to a preferred transport independent of dynamic quality ranking. Which statement best describes what it changes?
- Application-based SD-WAN rules use application detection information to identify supported traffic signatures.
- DSCP match criteria can steer traffic carrying designated IP-header service markings.
- Best Quality supports loss-oriented link comparison using measured health data.
- The Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members.
- FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches.
- Associating a service rule with an SLA target filters or prioritizes measured candidates based on the rule's strategy.
Explanation
Correct Answer
D:‘Use a manual SD-WAN strategy’ is used to pin a specific business application to a preferred transport independent of dynamic quality ranking in a logistics site where routing and SD-WAN services have separate responsibilities; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the matching service displays Manual mode and the chosen ordered member list; the rollout must also respect this constraint: Manual member preference remains subject to route availability and any needed firewall permission.
Incorrect Answers
A:The described behavior is part of ‘Match by detected application’, used to prefer an SD-WAN path based on application identification rather than fixed port alone instead of the role of ‘Use a manual SD-WAN strategy’. In contrast to ‘Match by detected application’, ‘Use a manual SD-WAN strategy’ follows a different mechanism: the Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members. Treating ‘Match by detected application’ as equivalent would not address office backup traffic follows an undesired member despite a fixed circuit preference requirement in a logistics site where routing and SD-WAN services have separate responsibilities.
B:The described behavior is part of ‘Use DSCP-based SD-WAN steering’, used to distinguish preclassified media packets from ordinary web traffic at path-selection time instead of the role of ‘Use a manual SD-WAN strategy’. In contrast to ‘Use DSCP-based SD-WAN steering’, ‘Use a manual SD-WAN strategy’ follows a different mechanism: the Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members. Treating ‘Use DSCP-based SD-WAN steering’ as equivalent would not address office backup traffic follows an undesired member despite a fixed circuit preference requirement in a logistics site where routing and SD-WAN services have separate responsibilities.
C:The described behavior is part of ‘Use Best Quality with packet loss’, used to prefer the circuit losing fewer packets for interactive services instead of the role of ‘Use a manual SD-WAN strategy’. In contrast to ‘Use Best Quality with packet loss’, ‘Use a manual SD-WAN strategy’ follows a different mechanism: the Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members. Treating ‘Use Best Quality with packet loss’ as equivalent would not address office backup traffic follows an undesired member despite a fixed circuit preference requirement in a logistics site where routing and SD-WAN services have separate responsibilities.
E:The described behavior is part of ‘Consider first-flow application recognition’, used to explain why the first newly observed app session may not match application-based steering immediately instead of the role of ‘Use a manual SD-WAN strategy’. In contrast to ‘Consider first-flow application recognition’, ‘Use a manual SD-WAN strategy’ follows a different mechanism: the Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members. Treating ‘Consider first-flow application recognition’ as equivalent would not address office backup traffic follows an undesired member despite a fixed circuit preference requirement in a logistics site where routing and SD-WAN services have separate responsibilities.
F:The described behavior is part of ‘Use an SLA target within an SD-WAN service rule’, used to select a path only after it meets the performance objective for that particular application instead of the role of ‘Use a manual SD-WAN strategy’. In contrast to ‘Use an SLA target within an SD-WAN service rule’, ‘Use a manual SD-WAN strategy’ follows a different mechanism: the Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members. Treating ‘Use an SLA target within an SD-WAN service rule’ as equivalent would not address office backup traffic follows an undesired member despite a fixed circuit preference requirement in a logistics site where routing and SD-WAN services have separate responsibilities.
Question 547
Within an enterprise interconnecting SD-WAN overlays and cloud security edges, the configuration has been applied. Which measurement or record best confirms the goal to exchange private network reachability dynamically between FortiSASE and a FortiGate hub?
- The secure IPsec association is established to the intended cloud edge.
- Hub status and SLA data show eligible private service connection preference.
- The hub connection is healthy and routes exist to the internal application networks.
- The intended private prefix is visible through the correct service connection.
- The BGP neighbor is established and expected private prefixes are accepted.
Explanation
Correct Answer
E:This checks ‘Establish BGP with the SPA hub’ at the correct operational boundary: a supported SPA BGP design learns and advertises routes over the selected overlay connection. It demonstrates the specific capability to exchange private network reachability dynamically between FortiSASE and a FortiGate hub in an enterprise interconnecting SD-WAN overlays and cloud security edges; deployment should additionally respect the constraint: Autonomous system settings and route filters must agree across peers.
Incorrect Answers
A:That observation belongs to ‘Use IPsec transport for the SASE branch connection’, not ‘Establish BGP with the SPA hub’; its purpose is to carry branch traffic securely across an untrusted ISP toward a SASE service edge, the underlying behavior is that an IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay. The reviewer is instead verifying ‘Establish BGP with the SPA hub’ for an enterprise interconnecting SD-WAN overlays and cloud security edges, not the evidence produced by ‘Use IPsec transport for the SASE branch connection’.
B:That observation belongs to ‘Select hub path using SLA health’, not ‘Establish BGP with the SPA hub’; its purpose is to prefer a viable SPA route when one private-access connection becomes degraded, the underlying behavior is that health and service-connection priorities can influence which reachable private hub path is preferred. The reviewer is instead verifying ‘Establish BGP with the SPA hub’ for an enterprise interconnecting SD-WAN overlays and cloud security edges, not the evidence produced by ‘Select hub path using SLA health’.
C:That observation belongs to ‘Use FortiGate as a private-access hub’, not ‘Establish BGP with the SPA hub’; its purpose is to connect remote FortiSASE clients to data-center applications protected behind a FortiGate, the underlying behavior is that FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic. The reviewer is instead verifying ‘Establish BGP with the SPA hub’ for an enterprise interconnecting SD-WAN overlays and cloud security edges, not the evidence produced by ‘Use FortiGate as a private-access hub’.
D:That observation belongs to ‘Advertise internal prefixes to SPA routing’, not ‘Establish BGP with the SPA hub’; its purpose is to make specific private data-center networks reachable from security PoPs, the underlying behavior is that routing advertisement or static private routes informs FortiSASE how to reach protected application subnets. The reviewer is instead verifying ‘Establish BGP with the SPA hub’ for an enterprise interconnecting SD-WAN overlays and cloud security edges, not the evidence produced by ‘Advertise internal prefixes to SPA routing’.
Question 548
At a dispersed workforce that uses a corporate SAML identity provider, a support engineer needs to verify that ‘Distribute a FortiSASE invitation code’ is active for the goal to bind an invited remote user's FortiClient enrollment to the correct organization. Which observation is decisive?
- Browser proxy resolution selects the FortiSASE proxy for the intended URLs.
- The endpoint registers to the intended FortiSASE environment after using the invitation.
- FortiSASE test authentication obtains a valid response from the designated RADIUS source.
- The new local identity appears in the authorized access group and can authenticate.
Explanation
Correct Answer
B:This checks ‘Distribute a FortiSASE invitation code’ at the correct operational boundary: the Onboard Users workflow provides information that remote users use for FortiSASE client registration. It demonstrates the specific capability to bind an invited remote user's FortiClient enrollment to the correct organization in a dispersed workforce that uses a corporate SAML identity provider; deployment should additionally respect the constraint: Onboarding credentials should be shared only with the intended users.
Incorrect Answers
A:That observation belongs to ‘Distribute proxy autoconfiguration settings’, not ‘Distribute a FortiSASE invitation code’; its purpose is to direct selected browser destinations to the FortiSASE secure web gateway, the underlying behavior is that a PAC-based proxy configuration tells supported browsers which web requests should use the cloud proxy. The reviewer is instead verifying ‘Distribute a FortiSASE invitation code’ for a dispersed workforce that uses a corporate SAML identity provider, not the evidence produced by ‘Distribute proxy autoconfiguration settings’.
C:That observation belongs to ‘Configure RADIUS authentication’, not ‘Distribute a FortiSASE invitation code’; 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 ‘Distribute a FortiSASE invitation code’ for a dispersed workforce that uses a corporate SAML identity provider, not the evidence produced by ‘Configure RADIUS authentication’.
D:That observation belongs to ‘Create a local FortiSASE test user’, not ‘Distribute a FortiSASE invitation code’; its purpose is to authenticate a limited lab user when no central identity source has yet been connected, the underlying behavior is that local user records and groups can be configured for a small controlled FortiSASE rollout. The reviewer is instead verifying ‘Distribute a FortiSASE invitation code’ for a dispersed workforce that uses a corporate SAML identity provider, not the evidence produced by ‘Create a local FortiSASE test user’.
Question 549
For a campus running FortiOS 7.6 with application-aware policies, a maintenance plan requires the firewall team to identify cloud-service traffic by maintained service definitions instead of a static destination IP. Which choice is appropriate?
- Use an SLA target within an SD-WAN service rule
- Order specific SD-WAN rules above general matches
- Consider first-flow application recognition
- Match an Internet Service Database destination
Explanation
Correct Answer
D:Internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet; that scope directly serves the goal to identify cloud-service traffic by maintained service definitions instead of a static destination IP in a campus running FortiOS 7.6 with application-aware policies. During implementation, an ISDB object is not the same as a local DNS record or the name of a user group rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Associating a service rule with an SLA target filters or prioritizes measured candidates based on the rule's strategy, a mechanism intended to select a path only after it meets the performance objective for that particular application rather than the requested ‘Match an Internet Service Database destination’ control. The stated task instead is to identify cloud-service traffic by maintained service definitions instead of a static destination IP, and adjusting ‘Use an SLA target within an SD-WAN service rule’ would not deliver ‘Match an Internet Service Database destination’. For the ‘Use an SLA target within an SD-WAN service rule’ alternative to ‘Match an Internet Service Database destination’, a health check without a service rule association may not control this application's steering.
B:SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence, a mechanism intended to ensure a narrow high-priority policy wins instead of a catch-all service rule rather than the requested ‘Match an Internet Service Database destination’ control. The stated task instead is to identify cloud-service traffic by maintained service definitions instead of a static destination IP, and adjusting ‘Order specific SD-WAN rules above general matches’ would not deliver ‘Match an Internet Service Database destination’. For the ‘Order specific SD-WAN rules above general matches’ alternative to ‘Match an Internet Service Database destination’, a highly specific match below a catch-all does not automatically outrank it.
C:FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches, a mechanism intended to explain why the first newly observed app session may not match application-based steering immediately rather than the requested ‘Match an Internet Service Database destination’ control. The stated task instead is to identify cloud-service traffic by maintained service definitions instead of a static destination IP, and adjusting ‘Consider first-flow application recognition’ would not deliver ‘Match an Internet Service Database destination’. For the ‘Consider first-flow application recognition’ alternative to ‘Match an Internet Service Database destination’, do not assume every first encrypted connection is identified before its initial path is chosen.
Question 550
Within a retail hub where two ISP costs differ but application quality still matters, after the rollout, operators find that partner subnet flows accidentally match the generic internet steering policy. Where should they focus troubleshooting?
- Investigate: Use an SLA target within an SD-WAN service rule
- Investigate: Use an implicit SD-WAN rule as fallback
- Investigate: Match an Internet Service Database destination
- Investigate: Match destination address in an SD-WAN rule
- Investigate: Order specific SD-WAN rules above general matches
Explanation
Correct Answer
D:The symptom identifies the missing operational behavior: destination-address matching distinguishes route candidates for a specified network target. For a retail hub where two ISP costs differ but application quality still matters, a direct diagnostic confirmation would be that the relevant service rule includes the exact partner destination address object; during repair, a matching SD-WAN rule still needs a viable route to the partner prefix.
Incorrect Answers
A:Associating a service rule with an SLA target filters or prioritizes measured candidates based on the rule's strategy, which serves the different requirement to select a path only after it meets the performance objective for that particular application instead of the behavior delivered by ‘Match destination address in an SD-WAN rule’. If that component were misconfigured, a more characteristic finding would be that the service chooses a reachable circuit that violates the application delay or loss objective; the actual report concerns partner subnet flows accidentally match the generic internet steering policy at a retail hub where two ISP costs differ but application quality still matters.
B:The implicit SD-WAN rule handles unmatched traffic using available routing and interface-priority logic, which serves the different requirement to provide default path behavior when traffic does not match any explicit steering service instead of the behavior delivered by ‘Match destination address in an SD-WAN rule’. If that component were misconfigured, a more characteristic finding would be that an administrator expects unmatched sessions to be dropped solely because no custom service matched; the actual report concerns partner subnet flows accidentally match the generic internet steering policy at a retail hub where two ISP costs differ but application quality still matters.
C:Internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet, which serves the different requirement to identify cloud-service traffic by maintained service definitions instead of a static destination IP instead of the behavior delivered by ‘Match destination address in an SD-WAN rule’. If that component were misconfigured, a more characteristic finding would be that a SaaS provider changes IP addresses and a hardcoded address-match rule misses new endpoints; the actual report concerns partner subnet flows accidentally match the generic internet steering policy at a retail hub where two ISP costs differ but application quality still matters.
E:SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence, which serves the different requirement to ensure a narrow high-priority policy wins instead of a catch-all service rule instead of the behavior delivered by ‘Match destination address in an SD-WAN rule’. If that component were misconfigured, a more characteristic finding would be that a broad any-destination rule captures sessions meant for the later finance-specific rule; the actual report concerns partner subnet flows accidentally match the generic internet steering policy at a retail hub where two ISP costs differ but application quality still matters.