Question 380An analyst observes that ADVPN spoke shortcuts form but keep directing return traffic through the hub due to asymmetric route policies. What is the most appropriate next FortiSASE or SD-WAN engineering action? Explain the session-based selection limit and use appropriate multi-session workload distribution if applicable. Review the supported session reevaluation and NAT handling during route changes for the traffic class. Reconcile shortcut route advertisements and allowed return-path policy on both spokes. Repair loopback reachability across eligible overlay transports before enabling failover. ExplanationCorrect Answer C:Reconcile shortcut route advertisements and allowed return-path policy on both spokes. Spoke-to-spoke optimization requires compatible forwarding and policy state in both directions. The next useful check is concrete: Bidirectional test traffic traverses the authorized shortcut after it is established. Incorrect Answers A:Per-session steering does not automatically stripe a single connection over multiple WAN members. That is relevant to a different intervention. For the stated situation, the required action is: Reconcile shortcut route advertisements and allowed return-path policy on both spokes. The governing reason is: Spoke-to-spoke optimization requires compatible forwarding and policy state in both directions. B:Existing stateful sessions and source translations can constrain how route updates affect live flows. That is relevant to a different intervention. For the stated situation, the required action is: Reconcile shortcut route advertisements and allowed return-path policy on both spokes. The governing reason is: Spoke-to-spoke optimization requires compatible forwarding and policy state in both directions. D:Loopback-based control-plane peering depends on stable underlay and overlay reachability to the peer address. That is relevant to a different intervention. For the stated situation, the required action is: Reconcile shortcut route advertisements and allowed return-path policy on both spokes. The governing reason is: Spoke-to-spoke optimization requires compatible forwarding and policy state in both directions.
Question 381A private-app support engineer sees that requests leave the cloud gateway but replies disappear on a local FortiGate with an unexpected source translation. After this change — Inspect the return path, NAT policy and session state for the affected SPA connection. — which result would best verify that it worked? A test trace identifies the particular blocked or misrouted SaaS flow while other apps remain healthy. A controlled test alert reaches the correct owner and produces a time-stamped escalation acknowledgment. The same test flow shows valid translated addresses and completed response packets on both ends. A failing test login identifies the precise rejection stage without exposing its secret values. ExplanationCorrect Answer C:The same test flow shows valid translated addresses and completed response packets on both ends. The test addresses the root condition instead of an unrelated service. Inspect the return path, NAT policy and session state for the affected SPA connection. That guards against: Asymmetric translation can break sessions while all link-health dashboards remain green. Incorrect Answers A:An application-specific failure should be localized before applying an estate-wide endpoint change. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The same test flow shows valid translated addresses and completed response packets on both ends. B:Outsourced monitoring does not remove the customer's need for explicit response accountability. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The same test flow shows valid translated addresses and completed response packets on both ends. D:Endpoint connection logs and authentication decisions explain different stages of a failed SASE session. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The same test flow shows valid translated addresses and completed response packets on both ends.
Question 382An administrator configures HTTPS application proxy access but does not install the trusted certificate path required for client validation. The team proposes: Deploy the supported proxy certificate configuration and validate trust on representative clients. Which technical principle best explains that choice? TLS proxy access must establish authenticated server identity in addition to user permission. A registration success message does not demonstrate inspected data-plane forwarding. Troubleshooting exceptions need rollback controls because they can outlive the incident. A security integration should preserve enough context to identify where a detected event originated. ExplanationCorrect Answer A:TLS proxy access must establish authenticated server identity in addition to user permission. The failure depends on this mechanism; the sensible response is: Deploy the supported proxy certificate configuration and validate trust on representative clients. Test: The approved client establishes the application session without bypassing certificate verification. Incorrect Answers B:A registration success message does not demonstrate inspected data-plane forwarding. This does not establish the proposed intervention. The governing principle here is: TLS proxy access must establish authenticated server identity in addition to user permission. Apply it by: Deploy the supported proxy certificate configuration and validate trust on representative clients. C:Troubleshooting exceptions need rollback controls because they can outlive the incident. This does not establish the proposed intervention. The governing principle here is: TLS proxy access must establish authenticated server identity in addition to user permission. Apply it by: Deploy the supported proxy certificate configuration and validate trust on representative clients. D:A security integration should preserve enough context to identify where a detected event originated. This does not establish the proposed intervention. The governing principle here is: TLS proxy access must establish authenticated server identity in addition to user permission. Apply it by: Deploy the supported proxy certificate configuration and validate trust on representative clients.
Question 383An analyst uses an internet-service destination object for a SaaS application but the observed connections use addresses outside the expected match. Which consequence most directly threatens the environment if this issue is not corrected? Outdated or incorrect service matches can cause SaaS traffic to bypass the required SLA. Unused service rules can conceal unintended fallback behavior. Stale or inaccessible BGP next hops can blackhole critical applications. Loopback blackholes can disrupt the control plane despite redundant tunnels. ExplanationCorrect Answer A:Outdated or incorrect service matches can cause SaaS traffic to bypass the required SLA. The uncorrected condition exposes the organization to this outcome. Dynamic service identification depends on the current service database and the actual destination tuple. Correct it by: Verify the active internet-service definition and compare it with real destination classifications. Incorrect Answers B:Unused service rules can conceal unintended fallback behavior. An alternate issue might create that effect, but the stated failure threatens: Outdated or incorrect service matches can cause SaaS traffic to bypass the required SLA. C:Control-plane route advertisements and data-plane reachability must agree during hub failure. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Outdated or incorrect service matches can cause SaaS traffic to bypass the required SLA. D:Loopback peering separates logical route sessions from physical tunnel endpoints only when reachability is engineered. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Outdated or incorrect service matches can cause SaaS traffic to bypass the required SLA.
Question 384A FortiGate keeps sending traffic to a degraded carrier because an old session table entry remains bound to that interface. Which consequence most directly threatens the environment if this issue is not corrected? Assuming instant rebalance can leave critical flows on the impaired path. Stale or inaccessible BGP next hops can blackhole critical applications. Misunderstood granularity can yield unrealistic throughput and availability expectations. Incomplete selectors can cause selective application failure even though the VPN is established. ExplanationCorrect Answer A:Assuming instant rebalance can leave critical flows on the impaired path. This follows directly from the described weakness. Mitigation: Inspect documented session state and reevaluation triggers instead of assuming every rule edit updates existing flows. The test to perform is: Old and new sessions follow expected member selection after the controlled change. Incorrect Answers B:Control-plane route advertisements and data-plane reachability must agree during hub failure. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Assuming instant rebalance can leave critical flows on the impaired path. C:Misunderstood granularity can yield unrealistic throughput and availability expectations. The risk follows from the identified transport, identity or policy condition: Assuming instant rebalance can leave critical flows on the impaired path. D:Incomplete selectors can cause selective application failure even though the VPN is established. The connection to the stated facts is weaker. The specific preventable harm is: Assuming instant rebalance can leave critical flows on the impaired path.
Question 385A headquarters FortiGate permits private-app access from FortiSASE but the policy accepts every cloud-originating source rather than the intended users. Which consequence most directly threatens the environment if this issue is not corrected? Competing configuration authorities can repeatedly overwrite working site settings. A single untested cloud entry point can create a company-wide remote-work outage. Asymmetric paths can defeat stateful security and cause intermittent transactions. An overly broad cloud-to-site rule can expand the attack surface of private systems. ExplanationCorrect Answer D:An overly broad cloud-to-site rule can expand the attack surface of private systems. The failure can produce this consequence in the affected environment. SPA integration should not equate cloud connectivity with unlimited internal network authorization. A repair is: Narrow the FortiGate SPA policy to verified service identities, destination objects and authorized applications. Incorrect Answers A:Competing configuration authorities can repeatedly overwrite working site settings. The option is related to integrate sd-wan and fortisase workflows rather than the described control gap. The actual risk is: An overly broad cloud-to-site rule can expand the attack surface of private systems. B:Cloud-access resilience requires validating dependency on distributed entry points. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An overly broad cloud-to-site rule can expand the attack surface of private systems. C:Asymmetric paths can defeat stateful security and cause intermittent transactions. An alternate issue might create that effect, but the stated failure threatens: An overly broad cloud-to-site rule can expand the attack surface of private systems.
Question 386A FortiClient profile forces full tunnel for an internal DNS suffix that is resolved only by a local on-site server. The team proposes: Add an authorized location-aware DNS and steering exception after validating the required split behavior. Which technical principle best explains that choice? Secure access onboarding depends on agent compatibility and the correct tenant association. Distributed service entry points should provide equivalent required access protections. Secure private access does not justify unrestricted reachability into the internal network. Private name resolution and traffic paths must remain consistent with the endpoint's network location. ExplanationCorrect Answer D:Private name resolution and traffic paths must remain consistent with the endpoint's network location. For these facts, the rule supports: Add an authorized location-aware DNS and steering exception after validating the required split behavior. Validate by observing: The internal name resolves and routes correctly on-site without exposing unapproved public traffic. Incorrect Answers A:Secure access onboarding depends on agent compatibility and the correct tenant association. This does not establish the proposed intervention. The governing principle here is: Private name resolution and traffic paths must remain consistent with the endpoint's network location. Apply it by: Add an authorized location-aware DNS and steering exception after validating the required split behavior. B:Distributed service entry points should provide equivalent required access protections. This does not establish the proposed intervention. The governing principle here is: Private name resolution and traffic paths must remain consistent with the endpoint's network location. Apply it by: Add an authorized location-aware DNS and steering exception after validating the required split behavior. C:Secure private access does not justify unrestricted reachability into the internal network. This does not establish the proposed intervention. The governing principle here is: Private name resolution and traffic paths must remain consistent with the endpoint's network location. Apply it by: Add an authorized location-aware DNS and steering exception after validating the required split behavior.
Question 387A field sales team receives FortiClient installers for an unsupported device platform and cannot enroll in FortiSASE. Which consequence most directly threatens the environment if this issue is not corrected? Assuming all agentless services are identical can leave business access unavailable. Misrouted DNS can make local applications appear unavailable after SASE deployment. Unsupported installer distribution can delay protection for mobile staff. Broad SPA access can turn one published service into a lateral movement pathway. ExplanationCorrect Answer C:Unsupported installer distribution can delay protection for mobile staff. The scenario leaves this precise control gap. Secure access onboarding depends on agent compatibility and the correct tenant association. To address it, assign installers and supported enrollment instructions appropriate to the tested endpoint operating systems. Incorrect Answers A:Assuming all agentless services are identical can leave business access unavailable. The connection to the stated facts is weaker. The specific preventable harm is: Unsupported installer distribution can delay protection for mobile staff. B:Misrouted DNS can make local applications appear unavailable after SASE deployment. The option is related to configure endpoint posture and access control rather than the described control gap. The actual risk is: Unsupported installer distribution can delay protection for mobile staff. D:Broad SPA access can turn one published service into a lateral movement pathway. An alternate issue might create that effect, but the stated failure threatens: Unsupported installer distribution can delay protection for mobile staff.
Question 388A FortiGate keeps sending traffic to a degraded carrier because an old session table entry remains bound to that interface. The team proposes: Inspect documented session state and reevaluation triggers instead of assuming every rule edit updates existing flows. Which technical principle best explains that choice? Conflicting ordered service rules require an explicit precedence decision. Control-plane scalability is a separate requirement from aggregate data throughput. Session affinity can preserve earlier forwarding decisions until the supported state transition occurs. Redundant encrypted paths must meet the same organizational security baseline. ExplanationCorrect Answer C:Session affinity can preserve earlier forwarding decisions until the supported state transition occurs. The principle motivates the proposed step, not a general configuration change. Inspect documented session state and reevaluation triggers instead of assuming every rule edit updates existing flows. Confirm: Old and new sessions follow expected member selection after the controlled change. Incorrect Answers A:Conflicting ordered service rules require an explicit precedence decision. This does not establish the proposed intervention. The governing principle here is: Session affinity can preserve earlier forwarding decisions until the supported state transition occurs. Apply it by: Inspect documented session state and reevaluation triggers instead of assuming every rule edit updates existing flows. B:Control-plane scalability is a separate requirement from aggregate data throughput. This does not establish the proposed intervention. The governing principle here is: Session affinity can preserve earlier forwarding decisions until the supported state transition occurs. Apply it by: Inspect documented session state and reevaluation triggers instead of assuming every rule edit updates existing flows. D:Redundant encrypted paths must meet the same organizational security baseline. This does not establish the proposed intervention. The governing principle here is: Session affinity can preserve earlier forwarding decisions until the supported state transition occurs. Apply it by: Inspect documented session state and reevaluation triggers instead of assuming every rule edit updates existing flows.
Question 389A global enterprise deploys identical overlay templates across regions with unequal link bandwidths and ignores sizing differences. After this change — Segment branch blueprints into capacity-appropriate profiles while preserving a common policy foundation. — which result would best verify that it worked? Two test branches enroll with the intended unique site values and the same validated baseline. Test traffic is classified into the selected zone and can use both eligible uplinks. Pilot branches select the intended capacity profile and sustain their design traffic within the monitored thresholds. The monitored member state changes when impairment is introduced on the conference-service path. ExplanationCorrect Answer C:Pilot branches select the intended capacity profile and sustain their design traffic within the monitored thresholds. The test addresses the root condition instead of an unrelated service. Segment branch blueprints into capacity-appropriate profiles while preserving a common policy foundation. That guards against: An undersized regional template can overload tunnels despite successful enrollment. Incorrect Answers A:Repeatable provisioning reduces configuration drift while keeping site identity and uplink parameters explicit. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Pilot branches select the intended capacity profile and sustain their design traffic within the monitored thresholds. B:Test traffic is classified into the selected zone and can use both eligible uplinks. It is consistent with an unrelated working feature, but the direct evidence is: Pilot branches select the intended capacity profile and sustain their design traffic within the monitored thresholds. D:The monitored member state changes when impairment is introduced on the conference-service path. This test might pass while the original defect remains. The relevant confirmation is: Pilot branches select the intended capacity profile and sustain their design traffic within the monitored thresholds.
Question 390A SOC provider wants FortiSASE event visibility in FortiAnalyzer, but the security team has configured only dashboard monitoring without log transport. After this change — Enable a supported FortiAnalyzer logging integration with an authorized secure path and retention policy. — which result would best verify that it worked? The next managed installation preserves the reviewed correction without unrelated drift. Correlated records identify whether the denial occurred in policy or after a tunnel failure. A clean test endpoint opens the authorized app with valid certificate verification. A distinct test policy event appears in FortiAnalyzer with source, timestamp and decision fields. ExplanationCorrect Answer D:A distinct test policy event appears in FortiAnalyzer with source, timestamp and decision fields. This confirms the new state under representative conditions. Operational analytics depend on delivered event records rather than merely viewing local status summaries. The failure otherwise risks: Unavailable centralized events can delay incident detection and historical investigation. Incorrect Answers A:Central configuration and device-local state must converge under an explicit change ownership model. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A distinct test policy event appears in FortiAnalyzer with source, timestamp and decision fields. B:End-to-end diagnosis needs events from the cloud service and the branch transport plane. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A distinct test policy event appears in FortiAnalyzer with source, timestamp and decision fields. C:Secure HTTPS private access depends on end-to-end certificate trust, not simply a connected agent status. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A distinct test policy event appears in FortiAnalyzer with source, timestamp and decision fields.