Pass the Fortinet NSE 7 Network Security Architect NSE7_SSE_AR-26 Questions and answers with CertsForce

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.

When an SD-WAN member is deleted, FortiGate can also remove static routes that were tied to that interface. If those routes are needed for destinations not covered by SD-WAN rules, traffic to those networks becomes unreachable. This explains why flows not matching SD-WAN rules are interrupted after the member was removed. 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.

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.

The policy-route output shows the matching SD-WAN service for destination 10.66.0.0/24 is vwl_service=4 (LAN-to-Corp2) with vwl_mbr_seq=1 2 and paths oif=3(port1) and oif=4(port2). Therefore, traffic from 10.0.1.133 to 10.66.0.125 is steered via SD-WAN member ID 1 or 2. 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 SD-WAN event log shows member 1 transitioning out of SLA. The member diagnostics identify member 1 as port1 and member 2 as port2. The service ' s priority list places port1 before port2, so a properly eligible port2 would be the next forwarding choice when port1 no longer meets the required threshold. This makes option B the intended answer. However, the screenshots do not independently establish port2 ' s current SLA pass state and the complete effective service selection conditions at the instant of the event. A single member ' s out-of-SLA log is insufficient to prove that port2 is healthy, reachable for the destination and selected immediately after the event. Option A is not a universal consequence of one SLA failure; option C incorrectly assumes port1 remains eligible; option D is not proven either because the configuration is not shown to be in a multi-member load-balancing state. To verify B, inspect ' diagnose sys sdwan service4 1 ' and the health-check status after the event, confirming member 2 is selected and destination-route eligible. The item is conditionally supported, not fully established by the current exhibit alone.

Verification qualification: Port2 must be shown operational and in SLA; the exhibit alone does not prove that state.

FortiGate SD-WAN zones are logical containers that group interfaces for traffic steering, route selection, and security-policy enforcement. The exhibit distinguishes zones from their underlying SD-WAN members through a hierarchical display.

Option C is correct. WAN1 is an empty, user-created zone and can be deleted because it has no SD-WAN member associations. The other zones must be evaluated according to their membership and whether they are system-defined.

WAN2 has an expansion indicator, showing that the zone contains member entries even though those entries are currently collapsed. Consequently, option A is incorrect: the absence of visible subordinate interfaces does not prove that a zone has no members.

HUB1 also has an expansion indicator. Its members are hidden by the collapsed view, so option D is incorrect.

The red icon is not a universal deletion indicator. In particular, the built-in virtual-wan-link zone must not be treated as an ordinary removable custom zone. An administrator must distinguish interface or zone operational status from configuration eligibility for deletion.

Before removing a custom zone, its members and any references in firewall policies or SD-WAN rules must be examined.

The zone setting advpn-select enable activates SD-WAN-aware ADVPN shortcut selection. The assigned advpn-health-check provides link metrics for evaluating available shortcut paths. The minimum-sla-meet-members value applies to zone-level SLA-compliant forwarding eligibility; it does not categorically mean shortcut negotiation is prohibited unless two members pass an SLA. Likewise, merely naming a health check does not impose a universal rule that every established shortcut must currently pass that health check. The candidate answer C confuses forwarding eligibility with IPsec ADVPN shortcut establishment. Reference: FortiOS 7.6 — ADVPN 2.0, advpn-select and minimum-sla-meet-members. 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. When troubleshooting, correlate the configured SD-WAN service with diagnose sys sdwan service4, the live session entry and the routing table. An application signature, an IP route and a health-check result describe different decision stages; treating them as interchangeable can produce incorrect conclusions about the egress interface.

FortiManager provisioning templates provide centralized, standardized, and scalable configuration management across FortiGate devices. They are particularly valuable in Secure SD-WAN deployments involving multiple branches, hubs, and overlay networks.

Option C is correct because a provisioning template group can contain both a system template and an SD-WAN template. System templates configure device-level settings, while SD-WAN templates define interfaces, zones, performance SLAs, and traffic-steering rules. FortiManager coordinates their installation according to configuration dependencies.

Option D is correct because CLI template groups support different template types, specifically standard CLI scripts and Jinja scripts. CLI scripts contain FortiOS commands, while Jinja templates support dynamic configuration generation using variables and conditional logic.

Option E is correct because CLI templates within a group are processed sequentially, from top to bottom. Administrators can organize their execution order to ensure prerequisite configurations are established before dependent settings.

Option A is incorrect because current FortiManager releases support CLI and Jinja scripts, not Perl scripts as a provisioning-template type.

Option B is incorrect because a standard template group supports one IPsec tunnel template assignment, not three separate IPsec templates.

The IKE debug shows processing notify type SHORTCUT_QUERY, recv shortcut-query and forward shortcut-query. These commands identify a hub receiving ADVPN shortcut discovery signaling from a spoke and forwarding it toward another spoke. A spoke that merely receives a shortcut query would not be characterized by the explicit forwarding record in the same manner. The output does not establish a two-region topology or a completed direct shortcut. The candidate key identifying a spoke contradicts the forwarded-shortcut-query diagnostic evidence. Reference: FortiOS 7.6 — ADVPN Shortcut Establishment and IKE Debugging. 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.

Before FortiGate can steer traffic according to SD-WAN rules, certain configuration elements must be present. Fortinet SD-WAN design guidance describes the required elements: " SD-WAN is not a standalone feature and interacts with several fundamental FortiGate configurations. Specifically, you must: (1) Define the interfaces (physical, VLAN, or IPsec) that will act as SD-WAN members, (2) Create firewall policies to allow traffic to be steered by SD-WAN, and (3) Set up routing so that traffic has valid routes via SD-WAN members. Without these, SD-WAN rules will not be able to match or steer any traffic. " Security profiles and traffic shaping are not mandatory for basic SD-WAN steering but can be layered on for enhanced security and QoS once foundational elements are present.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.