McAfee Secure

Exam Code: NSE7_SSE_AR-26

Exam Name: Fortinet NSE 7 - FortiSASE 26 Architect

Certification Provider: Fortinet

Fortinet NSE7_SSE_AR-26 Questions & Answers

Study with Up-To-Date REAL Exam Questions and Answers from the ACTUAL Test

50 Questions & Answers with Testing Engine

"Fortinet NSE 7 - FortiSASE 26 Architect Exam", also known as NSE7_SSE_AR-26 exam, is a Fortinet certification exam.

Pass your tests with the always up-to-date NSE7_SSE_AR-26 Exam Engine. Your NSE7_SSE_AR-26 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Fortinet NSE7_SSE_AR-26 Practice Test 13

Question 120

At Evergreen Services, an infrastructure review by the network assurance team is evaluating contractor and staff applications across a regional professional-services firm after an audit of cloud access (FT-E-01-02). The review finds that a branch policy is corrected locally but the next FortiManager install overwrites it from a stale template. Any correction must respect this operating requirement: contractors receive only explicitly authorized private resources. Which result is the strongest evidence that the corrective approach succeeded?

  1. The installed FortiGate configuration retains the approved setting after a second policy push; record the specific tenant and user identities.
  2. The intended tenant appears in the managed inventory and an approved change is reflected accurately; record the specific tenant and user identities.
  3. The unexpected change is linked to a specific install event revision and actor; reproduce it with documented network endpoints.
  4. The trace identifies selected member matched rule and relevant health data at failure time; capture the relevant session and policy trace.

Explanation

Correct Answer

A:

This is the most direct validation of the stated failure: In a controlled a regional professional-services firm acceptance test, The installed FortiGate configuration retains the approved setting after a second policy push; the outcome is recorded under Evergreen Services's rollout (FT-E-01-02). It tests the result of the proposed action, correct the authoritative managed template and install using a reviewed change workflow, rather than a separate feature or an unrelated path metric. The relevant principle is that Central management is authoritative over the managed device configuration.

Incorrect Answers

B:

The source case reports that a branch policy is corrected locally but the next FortiManager install overwrites it from a stale template. The proposed evidence concerns: Visibility and configuration authority depend on establishing the right management relationship. The current question instead requires an outcome tied to: Central management is authoritative over the managed device configuration. The direct observation is “The installed FortiGate configuration retains the approved setting after a second policy push; record the specific tenant and user identities”.

C:

The source case reports that a branch policy is corrected locally but the next FortiManager install overwrites it from a stale template. “The unexpected change is linked to a specific install event revision and actor; reproduce it with documented network endpoints” tests the distinct technical dependency: Versioned central management supplies change lineage beyond the running device state. This test could pass while the stated failure remains. The direct verification here is “The installed FortiGate configuration retains the approved setting after a second policy push; record the specific tenant and user identities” because central management is authoritative over the managed device configuration.

D:

The source case reports that a branch policy is corrected locally but the next FortiManager install overwrites it from a stale template. That observation would support a control associated with: Troubleshooting should correlate flow selection and observed performance rather than guess. It does not prove the specific correction worked. Confirm “The installed FortiGate configuration retains the approved setting after a second policy push; record the specific tenant and user identities” against: Central management is authoritative over the managed device configuration.

Question 121

At Falcon Security MSP, an infrastructure review by the provider services group is evaluating customer tenant connectivity across a managed multitenant edge platform after an audit of cloud access (FT-D-13-01). The review finds that a private web app must be exposed by FortiGate yet users can connect without the intended device and user checks. Any correction must respect this operating requirement: one customer cannot see or change another customer network. Which ongoing control most directly reduces the chance of this issue returning?

  1. Run negative authorization tests whenever application mappings change; include a negative-authorization regression case.
  2. Review permitted application inventory and failed access attempts regularly; retain the evidence under approved change control.
  3. Maintain separate test cases for private TCP and UDP use cases; include explicit primary and alternate path tests.
  4. Review duplicate identities and claim mappings during directory migrations; retain the evidence under approved change control.

Explanation

Correct Answer

A:

This preventive control directly targets recurrence: Run negative authorization tests whenever application mappings change; make it a repeatable part of Falcon Security MSP's change assurance (FT-D-13-01). It sustains the corrective action, configure the approved FortiGate ZTNA access proxy and FortiSASE connection rules with identity checks, and must preserve the requirement that one customer cannot see or change another customer network.

Incorrect Answers

B:

The source case reports that a private web app must be exposed by FortiGate yet users can connect without the intended device and user checks. The alternative is a useful recurring check for: Review permitted application inventory and failed access attempts regularly; retain the evidence under approved change control. The present failure instead depends on: Run negative authorization tests whenever application mappings change; include a negative-authorization regression case. The targeted safeguard is “Run negative authorization tests whenever application mappings change; include a negative-authorization regression case”.

C:

The source case reports that a private web app must be exposed by FortiGate yet users can connect without the intended device and user checks. “Maintain separate test cases for private TCP and UDP use cases; include explicit primary and alternate path tests” maintains another technical control: Maintain separate test cases for private TCP and UDP use cases; include explicit primary and alternate path tests. It does not directly prevent this case’s specific recurrence, for which “Run negative authorization tests whenever application mappings change; include a negative-authorization regression case” addresses: Run negative authorization tests whenever application mappings change; include a negative-authorization regression case.

D:

The source case reports that a private web app must be exposed by FortiGate yet users can connect without the intended device and user checks. That ongoing review concerns: Review duplicate identities and claim mappings during directory migrations; retain the evidence under approved change control. The governing risk here is: Run negative authorization tests whenever application mappings change; include a negative-authorization regression case. Maintain “Run negative authorization tests whenever application mappings change; include a negative-authorization regression case” as the case-specific check.

Question 122

At Silverline Freight, an infrastructure review by the remote site delivery team is evaluating branch and port connectivity across a global transport hub network during a secured remote-work pilot (FT-C-14-02). The review finds that a region depends on one private application hub and a failure isolates all remote FortiSASE users. Any correction must respect this operating requirement: high-value shipment updates remain logged and attributable. Which corrective approach best resolves the observed issue while meeting the operating constraint?

  1. Align FortiSASE SPA connectivity with the hub-side policy and private application mapping; keep the affected tenant scope documented.
  2. Tie intended branch SD-WAN selection to the cloud-security on-ramp and validate policy; limit any exception to authorized flows.
  3. Apply a FortiSASE Secure SaaS Access design with suitable SaaS visibility and policy; test both primary and backup paths.
  4. Design an approved primary and secondary SPA hub path with routing convergence; confirm the dependent routing state.

Explanation

Correct Answer

D:

The observed problem is that a region depends on one private application hub and a failure isolates all remote FortiSASE users. Design an approved primary and secondary SPA hub path with routing convergence as part of Silverline Freight's branch and port connectivity update (FT-C-14-02), while enforcing the constraint that high-value shipment updates remain logged and attributable. A successful implementation must be checked rather than assumed: In a controlled a global transport hub network acceptance test, When the primary hub fails approved users continue reaching intended private services via the secondary; the outcome is recorded under Silverline Freight's rollout (FT-C-14-02). The technical reason is that SPA high availability spans tunnels routes and application firewall permissions.

Incorrect Answers

A:

The source case reports that a region depends on one private application hub and a failure isolates all remote FortiSASE users. “Align FortiSASE SPA connectivity with the hub-side policy and private application mapping; keep the affected tenant scope documented” addresses the technical dependency: Reachable IPsec paths do not grant private application authorization by themselves. The reported problem instead follows: SPA high availability spans tunnels routes and application firewall permissions. The more direct correction is “Design an approved primary and secondary SPA hub path with routing convergence; confirm the dependent routing state”.

B:

The source case reports that a region depends on one private application hub and a failure isolates all remote FortiSASE users. This option would change the control governed by: Path failover should not silently bypass a mandatory inspection service. That does not resolve the present failure, where sPA high availability spans tunnels routes and application firewall permissions. The applicable response is “Design an approved primary and secondary SPA hub path with routing convergence; confirm the dependent routing state”.

C:

The source case reports that a region depends on one private application hub and a failure isolates all remote FortiSASE users. The offered alternative is useful for: SSA focuses on SaaS access controls within the broader SASE offering. In this case the decisive mechanism is: SPA high availability spans tunnels routes and application firewall permissions. The specific action is “Design an approved primary and secondary SPA hub path with routing convergence; confirm the dependent routing state”.

Question 123

At Dovetail Commerce, an infrastructure review by the retail security team is evaluating remote checkout and store systems across a multichannel storefront organization during a regional modernization (FT-C-05-01). The review finds that contractors cannot install FortiClient but still require a narrowly authorized web access solution. Any correction must respect this operating requirement: cardholder systems stay behind effective security policy. Which ongoing control most directly reduces the chance of this issue returning?

  1. Review private application inventory when changing access patterns; include a negative-authorization regression case.
  2. Trend regional PoP reachability and usage before major staffing changes; include explicit primary and alternate path tests.
  3. Document compensating controls for unmanaged contractor endpoints; include a negative-authorization regression case.
  4. Maintain cross-user-type test cases before a shared application launch; retain the evidence under approved change control.

Explanation

Correct Answer

C:

This preventive control directly targets recurrence: Document compensating controls for unmanaged contractor endpoints; make it a repeatable part of Dovetail Commerce's change assurance (FT-C-05-01). It sustains the corrective action, evaluate supported agentless web access rather than assuming a managed endpoint is mandatory, and must preserve the requirement that cardholder systems stay behind effective security policy.

Incorrect Answers

A:

The source case reports that contractors cannot install FortiClient but still require a narrowly authorized web access solution. “Review private application inventory when changing access patterns; include a negative-authorization regression case” maintains another technical control: Review private application inventory when changing access patterns; include a negative-authorization regression case. It does not directly prevent this case’s specific recurrence, for which “Document compensating controls for unmanaged contractor endpoints; include a negative-authorization regression case” addresses: Document compensating controls for unmanaged contractor endpoints; include a negative-authorization regression case.

B:

The source case reports that contractors cannot install FortiClient but still require a narrowly authorized web access solution. That ongoing review concerns: Trend regional PoP reachability and usage before major staffing changes; include explicit primary and alternate path tests. The governing risk here is: Document compensating controls for unmanaged contractor endpoints; include a negative-authorization regression case. Maintain “Document compensating controls for unmanaged contractor endpoints; include a negative-authorization regression case” as the case-specific check.

D:

The source case reports that contractors cannot install FortiClient but still require a narrowly authorized web access solution. “Maintain cross-user-type test cases before a shared application launch; retain the evidence under approved change control” maintains another technical control: Maintain cross-user-type test cases before a shared application launch; retain the evidence under approved change control. It does not directly prevent this case’s specific recurrence, for which “Document compensating controls for unmanaged contractor endpoints; include a negative-authorization regression case” addresses: Document compensating controls for unmanaged contractor endpoints; include a negative-authorization regression case.

Question 124

At Orchard Biotech, an infrastructure review by the laboratory network group is evaluating remote researcher access across a laboratory hybrid network during a scheduled resiliency exercise (FT-C-18-01). The review finds that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. Any correction must respect this operating requirement: sensitive lab assets remain inaccessible to untrusted endpoints. Which architectural or operational principle best explains the appropriate correction?

  1. Business continuity and security policy require an explicit fail-open or fail-closed decision; distinguish desired policy from effective enforcement.
  2. Different onboarding methods can produce different effective access and routing policy; avoid assuming a healthy session proves all services work.
  3. Wireless SASE edge access requires device registration and tenant-scoped policy; verify the dependent conditions independently.
  4. Reachable IPsec paths do not grant private application authorization by themselves; consider the specific security and routing boundary.

Explanation

Correct Answer

D:

The relevant design principle is: Reachable IPsec paths do not grant private application authorization by themselves. In this remote researcher access decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy; the intended approach is to align FortiSASE SPA connectivity with the hub-side policy and private application mapping. The distinguishing confirmation is that An entitled remote session succeeds while a nonentitled test remains denied.

Incorrect Answers

A:

The source case reports that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. The proposed explanation concerns: Business continuity and security policy require an explicit fail-open or fail-closed decision; distinguish desired policy from effective enforcement. The reported symptom instead follows: Reachable IPsec paths do not grant private application authorization by themselves; consider the specific security and routing boundary.

B:

The source case reports that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. The alternative states a real but different technical principle: Different onboarding methods can produce different effective access and routing policy; avoid assuming a healthy session proves all services work. The facts in this question are explained by: Reachable IPsec paths do not grant private application authorization by themselves; consider the specific security and routing boundary.

C:

The source case reports that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. That principle controls the offered alternative: Wireless SASE edge access requires device registration and tenant-scoped policy; verify the dependent conditions independently. It is not the causal distinction established here: Reachable IPsec paths do not grant private application authorization by themselves; consider the specific security and routing boundary.

Question 125

At Summit Hospitality, an infrastructure review by the guest connectivity group is evaluating hotel staff service applications across a regional resort branch fabric after an audit of cloud access (FT-B-16-03). The review finds that interbranch traffic hairpins through a central hub although approved branch-to-branch direct paths are required. Any correction must respect this operating requirement: guest and staff traffic must use separate security boundaries. Which ongoing control most directly reduces the chance of this issue returning?

  1. Track loopback advertisements and reachability before migrating overlays; confirm this in the next branch rollout checklist.
  2. Monitor asymmetric path changes during failover drills; use a measured acceptance threshold where relevant.
  3. Regression-test route visibility and security segmentation after shortcut changes; schedule a recorded review after topology changes.
  4. Verify overlay prefix advertisements after subnet changes; use a measured acceptance threshold where relevant.

Explanation

Correct Answer

C:

This preventive control directly targets recurrence: Regression-test route visibility and security segmentation after shortcut changes; make it a repeatable part of Summit Hospitality's change assurance (FT-B-16-03). It sustains the corrective action, assess and configure supported ADVPN shortcut conditions without bypassing security or routing policy, and must preserve the requirement that guest and staff traffic must use separate security boundaries.

Incorrect Answers

A:

The source case reports that interbranch traffic hairpins through a central hub although approved branch-to-branch direct paths are required. The alternative is a useful recurring check for: Track loopback advertisements and reachability before migrating overlays; confirm this in the next branch rollout checklist. The present failure instead depends on: Regression-test route visibility and security segmentation after shortcut changes; schedule a recorded review after topology changes. The targeted safeguard is “Regression-test route visibility and security segmentation after shortcut changes; schedule a recorded review after topology changes”.

B:

The source case reports that interbranch traffic hairpins through a central hub although approved branch-to-branch direct paths are required. “Monitor asymmetric path changes during failover drills; use a measured acceptance threshold where relevant” maintains another technical control: Monitor asymmetric path changes during failover drills; use a measured acceptance threshold where relevant. It does not directly prevent this case’s specific recurrence, for which “Regression-test route visibility and security segmentation after shortcut changes; schedule a recorded review after topology changes” addresses: Regression-test route visibility and security segmentation after shortcut changes; schedule a recorded review after topology changes.

D:

The source case reports that interbranch traffic hairpins through a central hub although approved branch-to-branch direct paths are required. The alternative is a useful recurring check for: Verify overlay prefix advertisements after subnet changes; use a measured acceptance threshold where relevant. The present failure instead depends on: Regression-test route visibility and security segmentation after shortcut changes; schedule a recorded review after topology changes. The targeted safeguard is “Regression-test route visibility and security segmentation after shortcut changes; schedule a recorded review after topology changes”.

Question 126

At Silverline Freight, an infrastructure review by the remote site delivery team is evaluating branch and port connectivity across a global transport hub network during a secured remote-work pilot (FT-C-02-01). The review finds that an architect treats access to an internal datacenter application as ordinary internet breakout. Any correction must respect this operating requirement: high-value shipment updates remain logged and attributable. Which architectural or operational principle best explains the appropriate correction?

  1. Agent-based and agentless remote use cases have different deployment requirements; do not infer authorization solely from connectivity.
  2. Cloud security service location can influence compliance and operational design; consider the specific security and routing boundary.
  3. SPA extends governed connectivity to private resources rather than generic web browsing; do not infer authorization solely from connectivity.
  4. Business continuity and security policy require an explicit fail-open or fail-closed decision; distinguish desired policy from effective enforcement.

Explanation

Correct Answer

C:

The relevant design principle is: SPA extends governed connectivity to private resources rather than generic web browsing. In this branch and port connectivity decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that an architect treats access to an internal datacenter application as ordinary internet breakout; the intended approach is to choose a supported Secure Private Access topology for the protected corporate application. The distinguishing confirmation is that A user reaches only the authorized private app without turning it into a public internet service.

Incorrect Answers

A:

The source case reports that an architect treats access to an internal datacenter application as ordinary internet breakout. That principle controls the offered alternative: Agent-based and agentless remote use cases have different deployment requirements; do not infer authorization solely from connectivity. It is not the causal distinction established here: SPA extends governed connectivity to private resources rather than generic web browsing; do not infer authorization solely from connectivity.

B:

The source case reports that an architect treats access to an internal datacenter application as ordinary internet breakout. The proposed explanation concerns: Cloud security service location can influence compliance and operational design; consider the specific security and routing boundary. The reported symptom instead follows: SPA extends governed connectivity to private resources rather than generic web browsing; do not infer authorization solely from connectivity.

D:

The source case reports that an architect treats access to an internal datacenter application as ordinary internet breakout. That principle controls the offered alternative: Business continuity and security policy require an explicit fail-open or fail-closed decision; distinguish desired policy from effective enforcement. It is not the causal distinction established here: SPA extends governed connectivity to private resources rather than generic web browsing; do not infer authorization solely from connectivity.

Question 127

At Juniper Manufacturing, an infrastructure review by the plant network engineers is evaluating plant-to-datacenter traffic across an industrial site WAN after an audit of cloud access (FT-D-04-01). The review finds that an approved user can browse the internet through SIA but cannot reach an internal app because SPA was not enabled. Any correction must respect this operating requirement: operational technology subnets keep their approved segmentation. Which corrective approach best resolves the observed issue while meeting the operating constraint?

  1. Validate version compatibility and effective profile assignment after the upgrade; confirm the dependent routing state.
  2. Configure the required SPA access connection for the approved remote-user group; use a reviewed service change record.
  3. Select an approved FortiSASE agentless internet access deployment with scoped policies; stage the change with an explicit backout plan.
  4. Replace broad bypass entries with the smallest approved destination exceptions; test both primary and backup paths.

Explanation

Correct Answer

B:

The observed problem is that an approved user can browse the internet through SIA but cannot reach an internal app because SPA was not enabled. Configure the required SPA access connection for the approved remote-user group as part of Juniper Manufacturing's plant-to-datacenter traffic update (FT-D-04-01), while enforcing the constraint that operational technology subnets keep their approved segmentation. A successful implementation must be checked rather than assumed: In a controlled an industrial site WAN acceptance test, The user connects to the named internal app and unrelated private networks stay inaccessible; the outcome is recorded under Juniper Manufacturing's rollout (FT-D-04-01). The technical reason is that Cloud internet security and private application access are separate service paths.

Incorrect Answers

A:

The source case reports that an approved user can browse the internet through SIA but cannot reach an internal app because SPA was not enabled. The offered alternative is useful for: Endpoint software version and assigned security policy together determine effective enforcement. In this case the decisive mechanism is: Cloud internet security and private application access are separate service paths. The specific action is “Configure the required SPA access connection for the approved remote-user group; use a reviewed service change record”.

C:

The source case reports that an approved user can browse the internet through SIA but cannot reach an internal app because SPA was not enabled. This option would change the control governed by: Select an approved FortiSASE agentless internet access deployment with scoped policies as part of Willow Mobility's parts and diagnostics services update (FT-D-05-01), while enforcing the constraint that vehicle telemetry is available only to approved maintenance roles. That does not resolve the present failure, where cloud internet security and private application access are separate service paths. The applicable response is “Configure the required SPA access connection for the approved remote-user group; use a reviewed service change record”.

D:

The source case reports that an approved user can browse the internet through SIA but cannot reach an internal app because SPA was not enabled. The offered alternative is useful for: Steering exceptions should be narrow because they can bypass inspection. In this case the decisive mechanism is: Cloud internet security and private application access are separate service paths. The specific action is “Configure the required SPA access connection for the approved remote-user group; use a reviewed service change record”.

Question 128

At Willow Mobility, an infrastructure review by the fleet security engineers is evaluating parts and diagnostics services across a vehicle service branch platform following a complex hub migration (FT-C-15-03). The review finds that two private organizations expose the same internal subnet to a shared SASE tenant without isolation. Any correction must respect this operating requirement: vehicle telemetry is available only to approved maintenance roles. Which architectural or operational principle best explains the appropriate correction?

  1. Different onboarding methods can produce different effective access and routing policy; avoid assuming a healthy session proves all services work.
  2. Path failover should not silently bypass a mandatory inspection service; distinguish desired policy from effective enforcement.
  3. Agent-based and agentless remote use cases have different deployment requirements; do not infer authorization solely from connectivity.
  4. Private access address overlap must be resolved through explicit routing and identity segmentation; verify the dependent conditions independently.

Explanation

Correct Answer

D:

The relevant design principle is: Private access address overlap must be resolved through explicit routing and identity segmentation. In this parts and diagnostics services decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that two private organizations expose the same internal subnet to a shared SASE tenant without isolation; the intended approach is to use supported tenant or routing segmentation and restrict access to the correct private prefix. The distinguishing confirmation is that A user belonging to tenant A cannot reach tenant B's overlapping resource.

Incorrect Answers

A:

The source case reports that two private organizations expose the same internal subnet to a shared SASE tenant without isolation. The alternative states a real but different technical principle: Different onboarding methods can produce different effective access and routing policy; avoid assuming a healthy session proves all services work. The facts in this question are explained by: Private access address overlap must be resolved through explicit routing and identity segmentation; verify the dependent conditions independently.

B:

The source case reports that two private organizations expose the same internal subnet to a shared SASE tenant without isolation. That principle controls the offered alternative: Path failover should not silently bypass a mandatory inspection service; distinguish desired policy from effective enforcement. It is not the causal distinction established here: Private access address overlap must be resolved through explicit routing and identity segmentation; verify the dependent conditions independently.

C:

The source case reports that two private organizations expose the same internal subnet to a shared SASE tenant without isolation. The proposed explanation concerns: Agent-based and agentless remote use cases have different deployment requirements; do not infer authorization solely from connectivity. The reported symptom instead follows: Private access address overlap must be resolved through explicit routing and identity segmentation; verify the dependent conditions independently.

Question 129

At Aster Media, an infrastructure review by the cross-region WAN engineers is evaluating content workflow access across a global publishing enterprise following an underlay circuit upgrade (FT-E-02-02). The review finds that a regional operator can assign new branch identities and silently push organization-wide access policy changes. Any correction must respect this operating requirement: licensed content remains limited to authorized business units. Which architectural or operational principle best explains the appropriate correction?

  1. Visibility and configuration authority depend on establishing the right management relationship; avoid assuming a healthy session proves all services work.
  2. Template consistency supports scale when local differences are deliberate and reviewable; separate observed path selection from configuration intent.
  3. Endpoint evidence helps isolate device-specific failures from cloud or hub outages; distinguish desired policy from effective enforcement.
  4. Administrative separation of duties reduces accidental high-impact configuration changes; consider the specific security and routing boundary.

Explanation

Correct Answer

D:

The relevant design principle is: Administrative separation of duties reduces accidental high-impact configuration changes. In this content workflow access decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that a regional operator can assign new branch identities and silently push organization-wide access policy changes; the intended approach is to create distinct FortiManager administrative roles and approval scopes for provisioning and policy installation. The distinguishing confirmation is that A provisioning-only test operator cannot approve or install a global security change.

Incorrect Answers

A:

The source case reports that a regional operator can assign new branch identities and silently push organization-wide access policy changes. That principle controls the offered alternative: Visibility and configuration authority depend on establishing the right management relationship; avoid assuming a healthy session proves all services work. It is not the causal distinction established here: Administrative separation of duties reduces accidental high-impact configuration changes; consider the specific security and routing boundary.

B:

The source case reports that a regional operator can assign new branch identities and silently push organization-wide access policy changes. The proposed explanation concerns: Template consistency supports scale when local differences are deliberate and reviewable; separate observed path selection from configuration intent. The reported symptom instead follows: Administrative separation of duties reduces accidental high-impact configuration changes; consider the specific security and routing boundary.

C:

The source case reports that a regional operator can assign new branch identities and silently push organization-wide access policy changes. The alternative states a real but different technical principle: Endpoint evidence helps isolate device-specific failures from cloud or hub outages; distinguish desired policy from effective enforcement. The facts in this question are explained by: Administrative separation of duties reduces accidental high-impact configuration changes; consider the specific security and routing boundary.

Question 130

At Bayline Logistics, an infrastructure review by the branch operations engineers is evaluating warehouse application transport across a multiwarehouse distribution fabric while testing an alternate WAN provider (FT-B-18-02). The review finds that one hub outage leaves remaining tunnels established but branch prefixes unreachable. Any correction must respect this operating requirement: warehouse scanning must remain available during carrier loss. Which ongoing control most directly reduces the chance of this issue returning?

  1. Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant.
  2. Monitor asymmetric path changes during failover drills; use a measured acceptance threshold where relevant.
  3. Track loopback advertisements and reachability before migrating overlays; confirm this in the next branch rollout checklist.
  4. Check rule hits and shadowing in each SD-WAN policy review; include a negative-authorization regression case.

Explanation

Correct Answer

A:

This preventive control directly targets recurrence: Include hub-loss cases in scheduled private access exercises; make it a repeatable part of Bayline Logistics's change assurance (FT-B-18-02). It sustains the corrective action, verify alternate hub IPsec and BGP adjacency plus route convergence behavior, and must preserve the requirement that warehouse scanning must remain available during carrier loss.

Incorrect Answers

B:

The source case reports that one hub outage leaves remaining tunnels established but branch prefixes unreachable. The alternative is a useful recurring check for: Monitor asymmetric path changes during failover drills; use a measured acceptance threshold where relevant. The present failure instead depends on: Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant. The targeted safeguard is “Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant”.

C:

The source case reports that one hub outage leaves remaining tunnels established but branch prefixes unreachable. “Track loopback advertisements and reachability before migrating overlays; confirm this in the next branch rollout checklist” maintains another technical control: Track loopback advertisements and reachability before migrating overlays; confirm this in the next branch rollout checklist. It does not directly prevent this case’s specific recurrence, for which “Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant” addresses: Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant.

D:

The source case reports that one hub outage leaves remaining tunnels established but branch prefixes unreachable. That ongoing review concerns: Check rule hits and shadowing in each SD-WAN policy review; include a negative-authorization regression case. The governing risk here is: Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant. Maintain “Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant” as the case-specific check.

Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests