Free Fortinet NSE 7 - SASE 26 Architect NSE7_SSE_AR-26 Exam Questions

After using the SD-WAN overlay template, two mandatory post-run tasks remain:'First, administrators must create and assign policy packages to branch devices, as security and access policies are not included in overlay templates. Second, SD-WAN rules must be configured so that traffic can be matched and steered appropriately through the established overlays. Neglecting either task results in ungoverned traffic or inefficient routing, undermining the benefits of SD-WAN.'Templates automate topology, but policy and rule definition are critical for operational effectiveness.Reference: FortiManager templates reduce repetitive work but must resolve to valid, device-specific configurations at installation time. Device assignments, metadata mappings, ADOM scope, policy-package interfaces and provisioning order should be inspected together rather than troubleshooting any one object in isolation. A successful management connection does not guarantee a successful configuration installation. Review the installation preview and task log, then validate the resulting device configuration and operational diagnostics. This separates a deployment-time validation failure from a live tunnel, routing or SLA fault.

FortiOS gathers performance statistics through configured health checks irrespective of whether a particular SD-WAN service rule currently uses the resulting SLA target. That makes option A incorrect. Lowest Cost (SLA) rules use selected SLA targets to determine which members satisfy their latency, jitter or packet-loss requirements; the standard distinction makes B and C the intended correct statements. A service can reference more than one SLA health check using separate entries in its service-level configuration, supporting the intended meaning of E. The CLI uses 'config system sdwan', 'config service', and a nested 'config sla' table, in which each named health-check entry references an SLA ID. Option D suggests multiple target IDs within one entry; that is not what the standard syntax shows. Note that FortiOS versions supporting hybrid quality-and-SLA selection add nuance to the phrase 'only Lowest Cost', so B must be interpreted in the context of the conventional Manual, Best Quality and Lowest Cost strategies addressed by the question. The uploaded FortiSASE guides do not contain the detailed CLI target schema, which is documented in the FortiOS 7.6 SD-WAN command reference.

FortiGate SD-WAN uses traffic-classification criteria to identify application flows and apply appropriate forwarding strategies based on business priorities and link-performance requirements.

Option C is correct because application categories can be used to identify traffic belonging to defined application groups. This capability enables administrators to steer business-critical applications through preferred WAN paths while directing less-sensitive traffic through alternative links.

Application-aware SD-WAN rules can use FortiGuard application identification to make forwarding decisions without relying exclusively on destination IP addresses or transport ports.

Option D is correct because the Internet Service Database provides predefined classifications for cloud services and internet applications. FortiGate can use ISDB objects in SD-WAN service rules to steer traffic toward destinations associated with services such as Microsoft 365 and other cloud applications.

Option A is incorrect because physical interface type is not one of the application or destination matching criteria represented by this question. SD-WAN members identify eligible forwarding interfaces, which is distinct from the traffic-classification criteria.

Option B is incorrect because BGP attributes influence routing decisions and route selection but are not directly equivalent to the application and ISDB matching criteria used by these service rules.

Together, application-category and ISDB matching provide granular, application-aware steering.

Best Quality Custom-profile-1 calculates a composite link-quality value using weighted latency, jitter, packet loss and bandwidth measurements. FortiOS evaluates link-quality index, configured member preference and link-cost-threshold rules when choosing a preferred path. The Custom profile does not simply apply a strict fixed sequence of latency, jitter, packet loss and bandwidth. Nor does it operate like the Lowest Cost (SLA) strategy where explicit SLA eligibility drives traffic distribution. The candidate key identifying SLA member availability is inconsistent with the Best Quality custom-profile design. The option listing quality index, member ordering and link-cost threshold is the closest correct description, though its phrasing overstates these as strictly sequential stages. Reference: FortiOS 7.6 --- Best Quality Strategy; Customized Link-Cost Factors. 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.

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 Reference:

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.

The described design is a multi-region SD-WAN architecture, where: According to Fortinet's SD-WAN Architecture for Enterprise guidance, when deploying multiple ADVPN regions, eBGP is the recommended routing protocol between regions. Each region operates as an independent routing domain (typically iBGP within the region), while eBGP is used to exchange routes between regional hubs. This approach: This is explicitly documented in Fortinet guidance for ''Using eBGP between regions with intra-region ADVPN'', which confirms that the architecture described in the question is valid and recommended when eBGP is used between regions. Why the other options are incorrect: Therefore, the correct and documented conclusion is that the plan is possible and eBGP should be used as the routing protocol between regions, which corresponds to Answer A. 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.

The SD-WAN monitor's table view in FortiManager provides a donut visualization plus a detailed table that shows each SD-WAN member's status and SLA pass/miss, giving the per-member health view you're after. FortiManager templates reduce repetitive work but must resolve to valid, device-specific configurations at installation time. Device assignments, metadata mappings, ADOM scope, policy-package interfaces and provisioning order should be inspected together rather than troubleshooting any one object in isolation. A successful management connection does not guarantee a successful configuration installation. Review the installation preview and task log, then validate the resulting device configuration and operational diagnostics. This separates a deployment-time validation failure from a live tunnel, routing or SLA fault. In the relevant Fortinet FortiManager documentation, the applicable feature should be verified against the deployed software version, the selected configuration mode and the live operational state before the answer is treated as a definitive implementation requirement. The status of individual overlay interfaces can be inspected separately.

FortiSASE Secure Private Access enables remote users and branch networks to connect securely to applications hosted behind on-premises FortiGate devices or within enterprise private networks.

Option D is correct because Fortinet's documented SPA deployment workflow supports configuring up to 12 SPA service connections.

Each service connection represents a configured FortiGate SPA hub that establishes IPsec connectivity with FortiSASE security points of presence. These connections enable the exchange of routing information between FortiSASE and corporate networks through supported BGP routing designs.

The 12-connection limit provides capacity for connecting multiple enterprise locations, including branch networks, private data centers, and hybrid cloud environments.

Option A is incorrect because four connections do not represent the documented maximum. Option B is incorrect because 16 is not the stated limit for SPA service connections in the referenced FortiSASE configuration. Option C similarly understates the supported maximum.

A separate SPA Service Connection subscription is required for each applicable FortiGate hub. Licensing and operational limits should be considered independently: the number of available service connections does not automatically determine aggregate bandwidth, individual hub throughput, or the number of remote users.

The administrator configures these connections through FortiSASE Secure Private Access service-connection management after completing the required SPA network and BGP settings.

When you enable ADVPN (auto-discovery VPN) in the overlay template, FortiManager automatically updates both the IPsec and BGP templates on the hub so that shortcut tunnels can be established dynamically. ADVPN can be activated in the SD-WAN overlay template for any supported topology, including dual-hub primary--primary, not just single hub. 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. Before applying a topology change, review the interface dependencies, static and dynamic routing, security policies and provisioning templates. FortiGate can support multiple transport types, but routing and tunnel compatibility still determine whether the intended member is operationally eligible. In the relevant Fortinet FortiOS documentation, the applicable feature should be verified against the deployed software version, the selected configuration mode and the live operational state before the answer is treated as a definitive implementation requirement.

FortiManager SD-WAN Overlay Orchestration produces the core provisioning artifacts IPsec tunnel templates, BGP templates and CLI templates. IPsec tunnels implement the WAN overlays, BGP exchanges route prefixes and the CLI portion provides other device configuration needed by the topology. The candidate key includes a generic Rules template, but the standard generated template list does not identify such an object. SD-WAN rules are configured using the appropriate SD-WAN provisioning template or follow-up policy tasks, and they are not the same as the three generated template types. Static routing templates are not universally generated as core overlays. Reference: FortiManager 7.6 --- Objects and Templates Created by SD-WAN Overlay Orchestrator. FortiManager templates reduce repetitive work but must resolve to valid, device-specific configurations at installation time. Device assignments, metadata mappings, ADOM scope, policy-package interfaces and provisioning order should be inspected together rather than troubleshooting any one object in isolation. A successful management connection does not guarantee a successful configuration installation. Review the installation preview and task log, then validate the resulting device configuration and operational diagnostics. This separates a deployment-time validation failure from a live tunnel, routing or SLA fault.