Question 160A branch reports a secure-private-access outage after a routing change and its FortiGate tunnel is up but application packets never reach the server. What is the most appropriate next FortiSASE or SD-WAN engineering action? Validate relevant telemetry capture and safe retention before relying on downstream forensic analysis. Preserve tenant and branch source identifiers in the approved analytics schema and report filters. Inspect the SPA destination route, FortiGate policy and return flow before resetting tunnels. Correlate client diagnostic events with identity and policy results using the same affected session identifiers. ExplanationCorrect Answer C:Inspect the SPA destination route, FortiGate policy and return flow before resetting tunnels. Tunnel establishment is separate from authorized application-layer reachability. A practical way to confirm the repair is: A captured approved application request reaches the server and the response returns over the expected path. Incorrect Answers A:Forensic services cannot reconstruct event details that were never collected or preserved. That is relevant to a different intervention. For the stated situation, the required action is: Inspect the SPA destination route, FortiGate policy and return flow before resetting tunnels. The governing reason is: Tunnel establishment is separate from authorized application-layer reachability. B:Security reports need sufficient source attribution for meaningful operational and contractual conclusions. That is relevant to a different intervention. For the stated situation, the required action is: Inspect the SPA destination route, FortiGate policy and return flow before resetting tunnels. The governing reason is: Tunnel establishment is separate from authorized application-layer reachability. D:Endpoint connection logs and authentication decisions explain different stages of a failed SASE session. That is relevant to a different intervention. For the stated situation, the required action is: Inspect the SPA destination route, FortiGate policy and return flow before resetting tunnels. The governing reason is: Tunnel establishment is separate from authorized application-layer reachability.
Question 161An SD-WAN architect plans to connect FortiSASE and a branch overlay but leaves the service-chain ownership unclear across FortiManager and local devices. Which consequence most directly threatens the environment if this issue is not corrected? Competing configuration authorities can repeatedly overwrite working site settings. Policy overgeneralization can reveal confidential business data through a broad allowed path. An unsuitable entitlement can leave protected traffic outside the planned service. Asymmetric paths can defeat stateful security and cause intermittent transactions. ExplanationCorrect Answer A:Competing configuration authorities can repeatedly overwrite working site settings. The failure can produce this consequence in the affected environment. Multi-platform orchestration requires a clear source of truth for changes and rollback. A repair is: Define the authoritative configuration workflow and installation boundaries for both systems. Incorrect Answers B:Different sensitivity levels should receive different controls even when they traverse the same cloud service. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Competing configuration authorities can repeatedly overwrite working site settings. C:License and access design should follow actual user and traffic requirements rather than a single generic entitlement. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Competing configuration authorities can repeatedly overwrite working site settings. D:Asymmetric paths can defeat stateful security and cause intermittent transactions. The risk follows from the identified transport, identity or policy condition: Competing configuration authorities can repeatedly overwrite working site settings.
Question 162A company adds a new identity provider for administrator SSO but leaves a local privileged account with an unchanged shared password. The team proposes: Enforce the supported SAML administrator sign-on path and govern emergency local access separately. Which technical principle best explains that choice? Endpoint lifecycle operations must balance security fixes with business service continuity. Application reachability and threat inspection are independent security policy conditions. Administrative federation should improve identity accountability without creating an unmanaged bypass. Continuous-access policy must address the lifetime of previously authenticated sessions. ExplanationCorrect Answer C:Administrative federation should improve identity accountability without creating an unmanaged bypass. For these facts, the rule supports: Enforce the supported SAML administrator sign-on path and govern emergency local access separately. Validate by observing: An approved admin logs in through the identity provider and break-glass access is audited and restricted. Incorrect Answers A:Endpoint lifecycle operations must balance security fixes with business service continuity. This does not establish the proposed intervention. The governing principle here is: Administrative federation should improve identity accountability without creating an unmanaged bypass. Apply it by: Enforce the supported SAML administrator sign-on path and govern emergency local access separately. B:Application reachability and threat inspection are independent security policy conditions. This does not establish the proposed intervention. The governing principle here is: Administrative federation should improve identity accountability without creating an unmanaged bypass. Apply it by: Enforce the supported SAML administrator sign-on path and govern emergency local access separately. D:Continuous-access policy must address the lifetime of previously authenticated sessions. It belongs to configure endpoint posture and access control, whereas this action is explained by: Administrative federation should improve identity accountability without creating an unmanaged bypass.
Question 163An MSSP reuses one tenant's overlay addressing template for a second customer, causing overlapping routes. After this change — Separate tenant routing context with an approved VRF-aware overlay design and unique device metadata. — which result would best verify that it worked? A controlled partner prefix cannot reach private employee subnets without an approved route and policy. Web sessions leave through the approved local member and generate the expected security logs. A noisy but tolerable jitter trace no longer triggers repeated unwanted member switches. Overlapping private prefixes from both tenants remain distinct during simultaneous reachability tests. ExplanationCorrect Answer D:Overlapping private prefixes from both tenants remain distinct during simultaneous reachability tests. The observation is discriminating because it follows the stated change. Customer isolation requires independent routing domains when address space is reused across tenants. Otherwise, shared routing tables can send one customer's traffic toward another customer's network. Incorrect Answers A:VRF separation maintains independent forwarding decisions until deliberately permitted interconnects are configured. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Overlapping private prefixes from both tenants remain distinct during simultaneous reachability tests. B:Direct internet access is appropriate when local breakout can enforce required security and routing controls. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Overlapping private prefixes from both tenants remain distinct during simultaneous reachability tests. C:Health-based steering needs hysteresis or stable state decisions to avoid excessive path oscillation. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Overlapping private prefixes from both tenants remain distinct during simultaneous reachability tests.
Question 164A branch uses a FortiGate SPA connector but the target application moves to a new internal subnet. The team proposes: Update only the approved destination objects, routing and application access dependencies. Which technical principle best explains that choice? Published private applications require aligned network reachability and destination-specific policy. Administrative federation should improve identity accountability without creating an unmanaged bypass. A posture tag must reflect current trusted device evidence, not an indefinitely cached result. Private name resolution and traffic paths must remain consistent with the endpoint's network location. ExplanationCorrect Answer A:Published private applications require aligned network reachability and destination-specific policy. The principle motivates the proposed step, not a general configuration change. Update only the approved destination objects, routing and application access dependencies. Confirm: The new server responds through SPA and the retired subnet is no longer exposed. Incorrect Answers B:Administrative federation should improve identity accountability without creating an unmanaged bypass. This does not establish the proposed intervention. The governing principle here is: Published private applications require aligned network reachability and destination-specific policy. Apply it by: Update only the approved destination objects, routing and application access dependencies. C:A posture tag must reflect current trusted device evidence, not an indefinitely cached result. This does not establish the proposed intervention. The governing principle here is: Published private applications require aligned network reachability and destination-specific policy. Apply it by: Update only the approved destination objects, routing and application access dependencies. D:Private name resolution and traffic paths must remain consistent with the endpoint's network location. This does not establish the proposed intervention. The governing principle here is: Published private applications require aligned network reachability and destination-specific policy. Apply it by: Update only the approved destination objects, routing and application access dependencies.
Question 165An administrator enables an allow rule for a cloud-connected application without checking whether web filtering and malware inspection still apply. The team proposes: Attach the intended FortiSASE security profiles and validate both allowed and malicious test traffic. Which technical principle best explains that choice? A provisioned tenant is not proof that user-level enforcement has been connected correctly. A posture tag must reflect current trusted device evidence, not an indefinitely cached result. Application reachability and threat inspection are independent security policy conditions. Posture automation must distinguish transient signal loss from an intentional weakening of security controls. ExplanationCorrect Answer C:Application reachability and threat inspection are independent security policy conditions. Applied to this design, it justifies: Attach the intended FortiSASE security profiles and validate both allowed and malicious test traffic. A successful test shows: Legitimate transactions pass and approved safe test signatures receive the expected blocking verdict. Incorrect Answers A:A provisioned tenant is not proof that user-level enforcement has been connected correctly. It belongs to deploy fortisase access and onboarding, whereas this action is explained by: Application reachability and threat inspection are independent security policy conditions. B:A posture tag must reflect current trusted device evidence, not an indefinitely cached result. This does not establish the proposed intervention. The governing principle here is: Application reachability and threat inspection are independent security policy conditions. Apply it by: Attach the intended FortiSASE security profiles and validate both allowed and malicious test traffic. D:Posture automation must distinguish transient signal loss from an intentional weakening of security controls. This does not establish the proposed intervention. The governing principle here is: Application reachability and threat inspection are independent security policy conditions. Apply it by: Attach the intended FortiSASE security profiles and validate both allowed and malicious test traffic.
Question 166A company publishes a legacy web admin tool through an agentless proxy but gives all remote employees permission by default. What is the most appropriate next FortiSASE or SD-WAN engineering action? Validate supported client connectivity and documented recovery behavior on representative restricted networks. Restrict the application to authorized administrative identities with the required device or certificate controls. Pilot lockdown with approved fail-open or recovery procedures appropriate to the threat model. Choose the supported agentless private-app access method and configure the authorized application proxy. ExplanationCorrect Answer B:Restrict the application to authorized administrative identities with the required device or certificate controls. Sensitive application publishing should enforce purpose-specific least privilege regardless of proxy technology. This is preferable to changing unrelated components; a normal employee fails the access test while an approved administrator passes with the required checks. Incorrect Answers A:Remote access architecture must account for networks outside enterprise control. That is relevant to a different intervention. For the stated situation, the required action is: Restrict the application to authorized administrative identities with the required device or certificate controls. The governing reason is: Sensitive application publishing should enforce purpose-specific least privilege regardless of proxy technology. C:A protective endpoint lock can become an availability risk without controlled recovery procedures. That is relevant to a different intervention. For the stated situation, the required action is: Restrict the application to authorized administrative identities with the required device or certificate controls. The governing reason is: Sensitive application publishing should enforce purpose-specific least privilege regardless of proxy technology. D:Agentless internet access alone does not establish private-app publishing and authentication. That is relevant to a different intervention. For the stated situation, the required action is: Restrict the application to authorized administrative identities with the required device or certificate controls. The governing reason is: Sensitive application publishing should enforce purpose-specific least privilege regardless of proxy technology.
Question 167An SD-WAN administrator chooses passive monitoring for a low-traffic emergency site and expects continuous measurement during idle periods. What is the most appropriate next FortiSASE or SD-WAN engineering action? Plan redundant regional hubs with a documented failure domain and interregion recovery option. Use nonconflicting underlay addressing and explicit tunnel interface references for both overlays. Select an appropriate active or combined monitoring mode for the required idle-time visibility. Align persistent forwarding routes with the authorized SD-WAN zone and inspect policy match order. ExplanationCorrect Answer C:Select an appropriate active or combined monitoring mode for the required idle-time visibility. The controlling distinction is: Pure passive health measurement depends on qualifying production sessions and may lack idle observations. In a representative test, link latency and loss remain visible during a controlled period without user traffic. Incorrect Answers A:Resilient overlay design avoids a global single point of failure for latency-sensitive regional workloads. That is relevant to a different intervention. For the stated situation, the required action is: Select an appropriate active or combined monitoring mode for the required idle-time visibility. The governing reason is: Pure passive health measurement depends on qualifying production sessions and may lack idle observations. B: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: Select an appropriate active or combined monitoring mode for the required idle-time visibility. The governing reason is: Pure passive health measurement depends on qualifying production sessions and may lack idle observations. D:Traffic steering requires a usable routing decision as well as a matching SD-WAN service policy. That is relevant to a different intervention. For the stated situation, the required action is: Select an appropriate active or combined monitoring mode for the required idle-time visibility. The governing reason is: Pure passive health measurement depends on qualifying production sessions and may lack idle observations.
Question 168A remote-access policy treats users on the corporate LAN as off-net and repeatedly sends their internal application traffic through an unnecessary cloud path. What is the most appropriate next FortiSASE or SD-WAN engineering action? Pilot the installer and enrollment sequence across representative devices before phased rollout. Verify event integration, source attribution and the intended downstream security workflow. Correct supported on-net detection and test location-based steering behavior. Restore the approved SPA destination and user restrictions and retain a timed emergency-change record. ExplanationCorrect Answer C:Correct supported on-net detection and test location-based steering behavior. Network location detection affects which policies and traffic paths should be active for an endpoint. A practical way to confirm the repair is: An office laptop follows approved internal routing while an external laptop receives cloud protection. Incorrect Answers A:Endpoint deployment risk is lowered by testing the exact user-facing enrollment flow before mass activation. That is relevant to a different intervention. For the stated situation, the required action is: Correct supported on-net detection and test location-based steering behavior. The governing reason is: Network location detection affects which policies and traffic paths should be active for an endpoint. B:A security integration should preserve enough context to identify where a detected event originated. That is relevant to a different intervention. For the stated situation, the required action is: Correct supported on-net detection and test location-based steering behavior. The governing reason is: Network location detection affects which policies and traffic paths should be active for an endpoint. D:Troubleshooting exceptions need rollback controls because they can outlive the incident. That is relevant to a different intervention. For the stated situation, the required action is: Correct supported on-net detection and test location-based steering behavior. The governing reason is: Network location detection affects which policies and traffic paths should be active for an endpoint.
Question 169A corporate laptop falls out of compliance when its endpoint protection stops, but private application access still succeeds. The team proposes: Use validated security posture tags in the relevant access policy and test noncompliant denial. Which technical principle best explains that choice? Remote access architecture must account for networks outside enterprise control. SaaS security enforcement depends on the actual application and activity classification. Cloud service registration and enterprise identity verification must refer to the same authorized organization. Access decisions should respond to current endpoint security state rather than initial device enrollment alone. ExplanationCorrect Answer D:Access decisions should respond to current endpoint security state rather than initial device enrollment alone. The principle connects the symptom to the engineering choice. Use validated security posture tags in the relevant access policy and test noncompliant denial. Proof is: The same account is denied on the impaired device and allowed on a compliant device. Incorrect Answers A:Remote access architecture must account for networks outside enterprise control. This does not establish the proposed intervention. The governing principle here is: Access decisions should respond to current endpoint security state rather than initial device enrollment alone. Apply it by: Use validated security posture tags in the relevant access policy and test noncompliant denial. B:SaaS security enforcement depends on the actual application and activity classification. This does not establish the proposed intervention. The governing principle here is: Access decisions should respond to current endpoint security state rather than initial device enrollment alone. Apply it by: Use validated security posture tags in the relevant access policy and test noncompliant denial. C:Cloud service registration and enterprise identity verification must refer to the same authorized organization. It belongs to deploy fortisase access and onboarding, whereas this action is explained by: Access decisions should respond to current endpoint security state rather than initial device enrollment alone.
Question 170A field engineer changes the route for one FortiGate's management server and accidentally sends its control traffic through an isolated user overlay. Which consequence most directly threatens the environment if this issue is not corrected? A hidden backup path can delay recovery when the advertised best path fails. Ignoring SLA eligibility can force business traffic onto an unhealthy preferred circuit. Losing management reachability can turn a recoverable WAN incident into an unmanaged outage. Duplicate routing identity can destabilize convergence and obscure route origin. ExplanationCorrect Answer C:Losing management reachability can turn a recoverable WAN incident into an unmanaged outage. This is the exposure to address first. Create an explicit supported management reachability path separate from user application steering. Confirm risk reduction when: Management heartbeat and configuration retrieval continue over the authorized path after user-overlay failover. Incorrect Answers A:Multipath route visibility requires compatible peer configuration and appropriate acceptance policy. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Losing management reachability can turn a recoverable WAN incident into an unmanaged outage. B:A configured priority should not override the service's eligibility rules where SLA compliance is required. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Losing management reachability can turn a recoverable WAN incident into an unmanaged outage. D:Duplicate routing identity can destabilize convergence and obscure route origin. The risk follows from the identified transport, identity or policy condition: Losing management reachability can turn a recoverable WAN incident into an unmanaged outage.