Question 210A new branch-edge enrollment reports connected yet the corporate service test reveals its traffic is still using raw local internet. What is the most appropriate next FortiSASE or SD-WAN engineering action? Investigate telemetry stability and apply supported posture transition handling without relaxing the actual compliance requirement. Configure the supported agentless ZTNA authentication and certificate checks for that application. Confirm edge-to-SASE steering, intended policy association and end-to-end security enforcement after onboarding. Enable supported digital experience monitoring and correlate client-path measurements with the affected app. ExplanationCorrect Answer C:Confirm edge-to-SASE steering, intended policy association and end-to-end security enforcement after onboarding. A registration success message does not demonstrate inspected data-plane forwarding. A tagged test flow is visible at FortiSASE and receives the expected cloud security result. This avoids the exposure that an edge can appear onboarded while its user traffic bypasses cloud protection. Incorrect Answers A:Posture automation must distinguish transient signal loss from an intentional weakening of security controls. That is relevant to a different intervention. For the stated situation, the required action is: Confirm edge-to-SASE steering, intended policy association and end-to-end security enforcement after onboarding. The governing reason is: A registration success message does not demonstrate inspected data-plane forwarding. B:Browser-based private access still requires a trusted user or device identity and application policy. That is relevant to a different intervention. For the stated situation, the required action is: Confirm edge-to-SASE steering, intended policy association and end-to-end security enforcement after onboarding. The governing reason is: A registration success message does not demonstrate inspected data-plane forwarding. D:Application experience depends on endpoint, local network, path and service conditions together. That is relevant to a different intervention. For the stated situation, the required action is: Confirm edge-to-SASE steering, intended policy association and end-to-end security enforcement after onboarding. The governing reason is: A registration success message does not demonstrate inspected data-plane forwarding.
Question 211A small factory's FortiBranch device sends all backup traffic through cloud inspection even though the architecture requires local backup breakout. What is the most appropriate next FortiSASE or SD-WAN engineering action? Document alternative POP behavior and test supported service availability and regional fallback. Limit route advertisements to approved application networks and test access at the FortiGate policy boundary. Reconcile user, edge and service consumption requirements against the active FortiSASE offer and FortiFlex terms. Classify and steer backup destinations separately from protected web traffic at the supported edge. ExplanationCorrect Answer D:Classify and steer backup destinations separately from protected web traffic at the supported edge. The recommendation addresses the failure at its actual dependency. Traffic classification should distinguish protected internet paths from locally retained bulk services. Verify: The backup transfer uses its approved local route while browser tests use SASE processing. Incorrect Answers A:Cloud-access resilience requires validating dependency on distributed entry points. That is relevant to a different intervention. For the stated situation, the required action is: Classify and steer backup destinations separately from protected web traffic at the supported edge. The governing reason is: Traffic classification should distinguish protected internet paths from locally retained bulk services. B:Route availability is not a grant of authorization for all internal resources. That is relevant to a different intervention. For the stated situation, the required action is: Classify and steer backup destinations separately from protected web traffic at the supported edge. The governing reason is: Traffic classification should distinguish protected internet paths from locally retained bulk services. C:Capacity and feature licensing is an architectural input, not a postdeployment accounting detail. That is relevant to a different intervention. For the stated situation, the required action is: Classify and steer backup destinations separately from protected web traffic at the supported edge. The governing reason is: Traffic classification should distinguish protected internet paths from locally retained bulk services.
Question 212A hub serves hundreds of remote spokes but IKE negotiation spikes repeatedly during scheduled branch reboot windows. The team proposes: Stage reconnection load and validate hub capacity and keepalive timing against supported design guidance. Which technical principle best explains that choice? Administrative member priority and measured quality are distinct selection inputs. Control-plane scalability is a separate requirement from aggregate data throughput. Loopback-based control-plane peering depends on stable underlay and overlay reachability to the peer address. A configured priority should not override the service's eligibility rules where SLA compliance is required. ExplanationCorrect Answer B:Control-plane scalability is a separate requirement from aggregate data throughput. The principle motivates the proposed step, not a general configuration change. Stage reconnection load and validate hub capacity and keepalive timing against supported design guidance. Confirm: A staged restart test keeps tunnel setup success within the planned recovery threshold. Incorrect Answers A:Administrative member priority and measured quality are distinct selection inputs. This does not establish the proposed intervention. The governing principle here is: Control-plane scalability is a separate requirement from aggregate data throughput. Apply it by: Stage reconnection load and validate hub capacity and keepalive timing against supported design guidance. C:Loopback-based control-plane peering depends on stable underlay and overlay reachability to the peer address. This does not establish the proposed intervention. The governing principle here is: Control-plane scalability is a separate requirement from aggregate data throughput. Apply it by: Stage reconnection load and validate hub capacity and keepalive timing against supported design guidance. D:A configured priority should not override the service's eligibility rules where SLA compliance is required. This does not establish the proposed intervention. The governing principle here is: Control-plane scalability is a separate requirement from aggregate data throughput. Apply it by: Stage reconnection load and validate hub capacity and keepalive timing against supported design guidance.
Question 213An enterprise service rule routes payroll traffic over a low-cost broadband link even when the app needs low jitter. What is the most appropriate next FortiSASE or SD-WAN engineering action? Create an explicit supported management reachability path separate from user application steering. Build tenant-specific overlay and routing separation before exposing the managed hub service. Put the verified payroll match above more general rules and apply the required SLA-based strategy. Disambiguate the intended peer identity and verify phase-one and phase-two settings for each overlay. ExplanationCorrect Answer C:Put the verified payroll match above more general rules and apply the required SLA-based strategy. Changing this setting targets the described failure rather than a nearby symptom. SD-WAN service-policy order and match criteria determine which traffic receives specialized steering. Evidence: A traced payroll session matches the specialized rule and selects a member meeting its jitter target. Incorrect Answers A:Operational control-plane access must remain reachable independent of user-flow route experiments. That is relevant to a different intervention. For the stated situation, the required action is: Put the verified payroll match above more general rules and apply the required SLA-based strategy. The governing reason is: SD-WAN service-policy order and match criteria determine which traffic receives specialized steering. B:Multi-tenant overlay-as-a-service requires separate logical forwarding and policy namespaces. That is relevant to a different intervention. For the stated situation, the required action is: Put the verified payroll match above more general rules and apply the required SLA-based strategy. The governing reason is: SD-WAN service-policy order and match criteria determine which traffic receives specialized steering. D:Separate tunnel identities are necessary for deterministic establishment and route association. That is relevant to a different intervention. For the stated situation, the required action is: Put the verified payroll match above more general rules and apply the required SLA-based strategy. The governing reason is: SD-WAN service-policy order and match criteria determine which traffic receives specialized steering.
Question 214A traffic policy favors the highest-priority member even after its measured quality fails the application's target. What is the most appropriate next FortiSASE or SD-WAN engineering action? Create an explicit supported management reachability path separate from user application steering. Reconcile shortcut route advertisements and allowed return-path policy on both spokes. Require valid SLA membership and inspect how priority is considered among surviving candidates. Harmonize approved cryptographic proposals for all intended primary and backup overlays. ExplanationCorrect Answer C:Require valid SLA membership and inspect how priority is considered among surviving candidates. A configured priority should not override the service's eligibility rules where SLA compliance is required. This is preferable to changing unrelated components; the impaired high-priority link is excluded from the application service until it recovers. Incorrect Answers A:Operational control-plane access must remain reachable independent of user-flow route experiments. That is relevant to a different intervention. For the stated situation, the required action is: Require valid SLA membership and inspect how priority is considered among surviving candidates. The governing reason is: A configured priority should not override the service's eligibility rules where SLA compliance is required. B:Spoke-to-spoke optimization requires compatible forwarding and policy state in both directions. That is relevant to a different intervention. For the stated situation, the required action is: Require valid SLA membership and inspect how priority is considered among surviving candidates. The governing reason is: A configured priority should not override the service's eligibility rules where SLA compliance is required. D:Harmonize approved cryptographic proposals for all intended primary and backup overlays. This action is not specific enough to the observed failure. A configured priority should not override the service's eligibility rules where SLA compliance is required. Corrective step: Require valid SLA membership and inspect how priority is considered among surviving candidates.
Question 215An employee uses a client bypass destination list copied from another region and accidentally excludes a sensitive SaaS service from inspection. The team proposes: Review and narrow approved steering bypasses to explicit business and regional exceptions. Which technical principle best explains that choice? A registration success message does not demonstrate inspected data-plane forwarding. SaaS security enforcement depends on the actual application and activity classification. Secure access onboarding depends on agent compatibility and the correct tenant association. Bypass lists can remove traffic from security controls and require the same scrutiny as allow policies. ExplanationCorrect Answer D:Bypass lists can remove traffic from security controls and require the same scrutiny as allow policies. The concept matches the specific dependency described. Review and narrow approved steering bypasses to explicit business and regional exceptions. Observable outcome: The sensitive SaaS flow is inspected while a documented exempt destination remains reachable. Incorrect Answers A:A registration success message does not demonstrate inspected data-plane forwarding. This does not establish the proposed intervention. The governing principle here is: Bypass lists can remove traffic from security controls and require the same scrutiny as allow policies. Apply it by: Review and narrow approved steering bypasses to explicit business and regional exceptions. B:SaaS security enforcement depends on the actual application and activity classification. This does not establish the proposed intervention. The governing principle here is: Bypass lists can remove traffic from security controls and require the same scrutiny as allow policies. Apply it by: Review and narrow approved steering bypasses to explicit business and regional exceptions. C:Secure access onboarding depends on agent compatibility and the correct tenant association. This does not establish the proposed intervention. The governing principle here is: Bypass lists can remove traffic from security controls and require the same scrutiny as allow policies. Apply it by: Review and narrow approved steering bypasses to explicit business and regional exceptions.
Question 216An MSSP reuses one tenant's overlay addressing template for a second customer, causing overlapping routes. What is the most appropriate next FortiSASE or SD-WAN engineering action? Use nonconflicting underlay addressing and explicit tunnel interface references for both overlays. Create a service-representative health check with the appropriate path, protocol and SLA thresholds. Correlate historical SD-WAN health events with FortiAnalyzer traffic and event records. Separate tenant routing context with an approved VRF-aware overlay design and unique device metadata. ExplanationCorrect Answer D:Separate tenant routing context with an approved VRF-aware overlay design and unique device metadata. Customer isolation requires independent routing domains when address space is reused across tenants. A practical way to confirm the repair is: Overlapping private prefixes from both tenants remain distinct during simultaneous reachability tests. Incorrect Answers A:Underlay reachability must be unambiguous before overlay control traffic can remain stable. That is relevant to a different intervention. For the stated situation, the required action is: Separate tenant routing context with an approved VRF-aware overlay design and unique device metadata. The governing reason is: Customer isolation requires independent routing domains when address space is reused across tenants. B:A health measurement is meaningful only when its destination and transport resemble the protected application. That is relevant to a different intervention. For the stated situation, the required action is: Separate tenant routing context with an approved VRF-aware overlay design and unique device metadata. The governing reason is: Customer isolation requires independent routing domains when address space is reused across tenants. C:Current link status is not a substitute for time-aligned historical performance evidence. That is relevant to a different intervention. For the stated situation, the required action is: Separate tenant routing context with an approved VRF-aware overlay design and unique device metadata. The governing reason is: Customer isolation requires independent routing domains when address space is reused across tenants.
Question 217A hub-based SD-WAN service provider needs to isolate customer overlays despite reused branch private addressing. Which consequence most directly threatens the environment if this issue is not corrected? Static assumptions about the peer endpoint can strand remote sites after provider changes. Unsegmented managed overlays can mix traffic belonging to unrelated organizations. Unplanned learning-state behavior can route startup traffic through the wrong security path. Assuming instant rebalance can leave critical flows on the impaired path. ExplanationCorrect Answer B:Unsegmented managed overlays can mix traffic belonging to unrelated organizations. The failure can produce this consequence in the affected environment. Multi-tenant overlay-as-a-service requires separate logical forwarding and policy namespaces. A repair is: Build tenant-specific overlay and routing separation before exposing the managed hub service. Incorrect Answers A:Dynamic underlay addressing requires tunnel establishment to follow current peer reachability. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unsegmented managed overlays can mix traffic belonging to unrelated organizations. C:Application-specific routing may not be fully informed until the service is classified from observed sessions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unsegmented managed overlays can mix traffic belonging to unrelated organizations. D:Session affinity can preserve earlier forwarding decisions until the supported state transition occurs. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unsegmented managed overlays can mix traffic belonging to unrelated organizations.
Question 218An administrator configures HTTPS application proxy access but does not install the trusted certificate path required for client validation. Which consequence most directly threatens the environment if this issue is not corrected? Long-lived sessions can retain more privilege than the endpoint's current state warrants. Untrusted certificates can produce failed connections or encourage unsafe trust exceptions. Broad guest profile assignment can expose private organization resources. Coarse availability checks can conceal significant customer-impacting service failures. ExplanationCorrect Answer B:Untrusted certificates can produce failed connections or encourage unsafe trust exceptions. This is the exposure to address first. Deploy the supported proxy certificate configuration and validate trust on representative clients. Confirm risk reduction when: The approved client establishes the application session without bypassing certificate verification. Incorrect Answers A:Long-lived sessions can retain more privilege than the endpoint's current state warrants. The risk follows from the identified transport, identity or policy condition: Untrusted certificates can produce failed connections or encourage unsafe trust exceptions. C:Broad guest profile assignment can expose private organization resources. The option is related to deploy fortisase access and onboarding rather than the described control gap. The actual risk is: Untrusted certificates can produce failed connections or encourage unsafe trust exceptions. D:A reachable control portal does not prove that every inspection and private-access function is healthy. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Untrusted certificates can produce failed connections or encourage unsafe trust exceptions.
Question 219An SD-WAN design includes two internet circuits but they were assigned to different zones from the required shared service rule. After this change — Reconcile the rule's intended zone and member associations before enabling traffic distribution. — which result would best verify that it worked? Each tunnel resolves its own expected next hop and remains established during concurrent load tests. Synthetic European branch traffic follows the approved regional path and stays within the required boundary. Test traffic is classified into the selected zone and can use both eligible uplinks. The monitored member state changes when impairment is introduced on the conference-service path. ExplanationCorrect Answer C:Test traffic is classified into the selected zone and can use both eligible uplinks. The observation is discriminating because it follows the stated change. A steering policy applies to the SD-WAN members visible through its configured zone context. Otherwise, an incorrect zone membership can silently exclude the backup path. Incorrect Answers A:Underlay reachability must be unambiguous before overlay control traffic can remain stable. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Test traffic is classified into the selected zone and can use both eligible uplinks. B:Geographic topology must reflect routing, latency and data-handling constraints, not only the shortest configuration. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Test traffic is classified into the selected zone and can use both eligible uplinks. D:A health measurement is meaningful only when its destination and transport resemble the protected application. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Test traffic is classified into the selected zone and can use both eligible uplinks.
Question 220A health provider chooses a single global SD-WAN hub even though clinics need local clinical-app access during an intercontinental outage. What is the most appropriate next FortiSASE or SD-WAN engineering action? Configure the documented dual-hub fallback and perform an isolated primary-hub outage test. Select an appropriate active or combined monitoring mode for the required idle-time visibility. Plan redundant regional hubs with a documented failure domain and interregion recovery option. Reconcile the rule's intended zone and member associations before enabling traffic distribution. ExplanationCorrect Answer C:Plan redundant regional hubs with a documented failure domain and interregion recovery option. Resilient overlay design avoids a global single point of failure for latency-sensitive regional workloads. The next useful check is concrete: Disconnecting the primary regional hub leaves each pilot clinic connected through its authorized alternate. Incorrect Answers A:Dual-hub resilience depends on valid alternate control-plane and tunnel paths, not two configured names. That is relevant to a different intervention. For the stated situation, the required action is: Plan redundant regional hubs with a documented failure domain and interregion recovery option. The governing reason is: Resilient overlay design avoids a global single point of failure for latency-sensitive regional workloads. B:Pure passive health measurement depends on qualifying production sessions and may lack idle observations. That is relevant to a different intervention. For the stated situation, the required action is: Plan redundant regional hubs with a documented failure domain and interregion recovery option. The governing reason is: Resilient overlay design avoids a global single point of failure for latency-sensitive regional workloads. D:A steering policy applies to the SD-WAN members visible through its configured zone context. That is relevant to a different intervention. For the stated situation, the required action is: Plan redundant regional hubs with a documented failure domain and interregion recovery option. The governing reason is: Resilient overlay design avoids a global single point of failure for latency-sensitive regional workloads.