Fortinet Updated NSE7_SSE_AR-26 Exam Questions and Answers by lilly-mae

MSSP-hosted hubs are generally appropriate where remote management and shared infrastructure are primary requirements. A customer-premises hub becomes valuable when corporate data center applications account for most branch traffic or when centralized internet security and egress are required at the customer site. Heavy interbranch traffic alone does not mandate a local hub because ADVPN shortcuts can bypass hubs. VoIP alone is likewise not decisive. Fortinet distinguishes secure internet access (SIA) from remote internet access (RIA); the phrase “SIA with centralized breakout” must be interpreted carefully. Remote breakout through the customer’s site corresponds to an RIA-type design, while SIA is a broader FortiSASE security service. In checking this outcome, an administrator should distinguish what the displayed exhibit proves from configuration prerequisites not visible in the screenshot. Routing eligibility, device role, rule matching, and software-version details should be verified before using the selected answer in a production decision. The referenced Fortinet documentation identifies the underlying feature and its supported configuration context.

Verification qualification: Option A conflates FortiSASE Secure Internet Access (SIA) with SD-WAN remote internet access (RIA).

According to the Fortinet SD-WAN 7.6 Core Administrator Study Guide, Routing and Sessions, page 193, FortiOS supports static routes referencing SD-WAN zones and individual member interfaces. However, duplicate destination routes cannot simultaneously reference a zone and one of its individual member interfaces.

Option A is correct: FortiOS requires the two static routes to have different destination prefixes. When a static route references an SD-WAN zone, FortiGate creates forwarding entries for the members belonging to that zone. Configuring an additional route with the identical destination prefix through an individual member creates a conflicting route definition.

Overlapping destination networks are permitted when their prefixes differ. For example, a zone-based route could reference 10.0.0.0/8, while a member-specific route references 10.2.0.0/16.

Option B is incorrect: Equal administrative distance does not resolve the duplicate-route restriction. ECMP is not a substitute for valid route configuration.

Option C is incorrect: FortiOS supports default static routes (0.0.0.0/0) referencing SD-WAN zones.

Option D is incorrect: SD-WAN members can include physical interfaces, VLAN interfaces, IPsec tunnels, and other supported interface types.

Therefore, the two static routes must have different destination prefixes, although overlapping networks are allowed.

Exact Source References:

Fortinet SD-WAN 7.6 Core Administrator Study Guide, pages 192–193 — Routing and Sessions.

FortiOS 7.6 Administration Guide — Adding a Static Route and SD-WAN Members and Zones.

For SD-WAN deployments that span multiple regions—where most traffic is intra-region and there is no requirement for inter-region ADVPN—the best practice is to use IBGP with BGP on loopback interfaces for routing within each region and EBGP between the regions. This approach ensures robust and scalable routing, isolates regional routing domains, and enables policy control at region boundaries. BGP on loopback is preferred for its reliability and flexibility, as it enables peering that is not tied to specific physical interfaces. EBGP between regions allows each region to maintain independent routing policies and summarization, optimizing performance and manageability. By separating IBGP (intra-region) and EBGP (inter-region), you create a modular architecture that scales easily and simplifies fault isolation and troubleshooting.References: A deployment should preserve the distinction between the physical or logical WAN underlay, the IPsec overlay and the SD-WAN zone that groups forwarding members. These layers can have different routing and security-policy requirements. The configured architecture must also allow the required traffic paths and failover behavior rather than assuming every available interface is interchangeable.

From the exhibit, both branches have an SD-WAN zone named overlay with set advpn-select enable, and each SD-WAN member in that zone is assigned a transport-group value. Branch-A members: Branch-B members: In FCSS SD-WAN 7.6 ADVPN design, transport-group is used to constrain which underlays are allowed to form ADVPN shortcuts with each other. A spoke can establish an ADVPN shortcut only between interfaces that belong to the same transport-group on both sides. This prevents building shortcuts across dissimilar transports. Evaluating the options: Therefore, the valid shortcut pairing listed is between T2 on Branch-A and TA on Branch-B, which corresponds to Option D. An operational review should distinguish the rule that matches the traffic from the interface that is ultimately selected. Valid forwarding also depends on destination route eligibility, current member state and the applicable SLA or quality-selection algorithm. A diagnostic showing configured members alone is not conclusive evidence that all those members will carry a particular flow.