NSE7_SSE_AR-26 Fortinet NSE 7 - FortiSASE 26 Architect Questions and Answers

In an SD-WAN rule, you can steer application traffic by using Internet Service Database (ISDB) entries. Facebook and LinkedIn are predefined ISDB objects in FortiGate, so the correct way is to select them in the Internet service field under Destination. This ensures that all traffic to these applications is matched and routed through the chosen (less costly) link. 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.

FortiSASE proxy-based deployment provides cloud-delivered security inspection for browser traffic without requiring the full FortiClient endpoint agent.

Option C is a valid answer because SSL deep inspection allows FortiSASE to decrypt permitted HTTPS traffic and inspect the content for malicious files, suspicious destinations, and other security threats. Without TLS decryption, content-level inspection is limited because much of the application payload remains encrypted.

Option D is also valid because malware inspection and sandboxing capabilities help identify malicious files, including previously unknown threats. Antivirus inspection, cloud reputation analysis, and sandbox analysis contribute to preventing dangerous content from reaching protected endpoints.

Option A is not the intended answer because FortiSASE Secure Web Gateway is not a dedicated web application firewall. WAF primarily protects hosted applications against inbound application-layer attacks.

Option B requires an important qualification: Fortinet ' s official documentation confirms that FortiSASE also supports IPS. IPS is capable of identifying exploit signatures and blocking malicious traffic, including threats carried over web protocols.

Consequently, this question does not provide an entirely exclusive pair of technically valid capabilities. C and D are the intended answer combination, but B is also a genuine FortiSASE security capability. The wording is therefore insufficient to establish a unique pair purely from supported features.

The requirement is to secure internet traffic generated by users behind an existing third-party branch router without necessarily installing FortiClient on individual endpoints.

Option D is correct because the FortiSASE Branch On-ramp subscription enables supported branch IPsec devices to establish encrypted connections to FortiSASE security points of presence.

With Branch On-ramp, the remote router forwards the branch ' s internet-bound traffic through an IPsec tunnel to FortiSASE, where cloud-delivered firewall, web filtering, application control, and other licensed security services can inspect the traffic.

FortiSASE supports the Custom device type for compatible third-party IPsec devices. These deployments use IKEv2 and appropriate tunnel parameters. Static routing is used for third-party branch devices where FortiSASE does not support BGP routing with that device type.

Option A is incorrect because SPA primarily provides access to private applications and corporate resources rather than establishing the required branch internet-security connection.

Option B does not correspond to the specific branch connectivity entitlement.

Option C is incorrect because secure web gateway functionality alone does not provision an IPsec on-ramp for the third-party router.

The applicable Branch On-ramp subscription and compatible FortiSASE base license must both be present. Exact entitlements depend on the FortiSASE release and subscription tier.

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 integrates policy-based traffic steering with the traditional routing subsystem. SD-WAN rules do not automatically override routing-table decisions; they operate within the route-selection framework.

Option A is correct. A member selected by an SD-WAN rule must have a valid route toward the destination. If the selected member cannot reach the destination, FortiGate excludes that member and evaluates another eligible candidate.

Option C is correct. Under default SD-WAN routing behavior, the best route to the destination must point toward an SD-WAN member before SD-WAN service-rule evaluation applies. If the best route points to a non-SD-WAN interface, conventional routing handles the traffic instead.

Option E is correct because a directly connected route can take precedence when it is the best matching route. FortiGate does not unnecessarily divert locally reachable destinations into SD-WAN processing.

Option B is incorrect because the Internet Service Database supplies application and destination classification information; it does not establish a universal routing-precedence rule above SD-WAN.

Option D is incorrect because a static route does not inherently bypass SD-WAN. Static routes commonly provide reachability through SD-WAN member interfaces.

The fundamental principles are route eligibility, valid member reachability, and preservation of conventional routing decisions outside the SD-WAN domain.

The event-log field advpnsc establishes whether the logged VPN tunnel is an ADVPN shortcut. The value advpnsc=1 identifies a shortcut, whereas advpnsc=0 identifies a non-shortcut event. The log for HUB1-VPN1_0 contains advpnsc=1, making the shortcut identification the directly supported conclusion. A different tunnel showing advpnsc=0 does not prove that its master tunnel cannot accept shortcuts. Application steering cannot be inferred from a VPN statistics event without the corresponding SD-WAN rule and session evidence. For ADVPN diagnostics, correlate vpntunnel, tunnelid, advpnsc and status messages. Reference: FortiOS 7.6 — ADVPN Shortcut Paths; Fortinet VPN log-field 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.

The destination matches the corporate SD-WAN service configured in Lowest Cost (SLA) mode. Its diagnostic listing marks six overlay interfaces alive and selected, but shows sla(0x0) and num of pass(0) for all of them. Under the default minimum SLA member behavior, FortiOS may fall back to operational out-of-SLA paths rather than automatically bypassing the service. Thus a blanket conclusion that FortiGate must route only according to the FIB is not supported by this diagnostic alone. All six selected overlays are candidate paths, subject to routing reachability and member-cost rules. Reference: FortiOS 7.6 — Lowest Cost (SLA) 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.

Verification qualification: Six selected out-of-SLA entries do not by themselves prove that every interface will be used for this destination.

The FortiManager SD-WAN overlay system allows only one IPsec template to be assigned to each device per overlay operation. The guide clarifies: " If you attempt to assign more than one IPsec template to a FortiGate device for the same overlay type, FortiManager will display an error, preventing duplicate or conflicting tunnel configurations. This limitation ensures a one-to-one mapping between device and overlay template per operation, maintaining configuration integrity and preventing routing issues. " This prevents complex troubleshooting scenarios and enforces best practices for overlay design. 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.

The rule is in SLA mode with two SLAs. From the status, HUB1-VPN2 and HUB1-VPN3 meet the SLA (sla(0x2) and sla(0x3)), while HUB1-VPN1 does not (sla(0x0)). Among members that meet SLA, FortiGate uses the configured order (priority-members 4 5 6) to pick the first eligible one—HUB1-VPN2—so traffic is routed over HUB1-VPN2. 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.

FortiGate supports Active, Passive, and Prefer Passive performance SLA monitoring modes. Passive monitoring measures actual network traffic rather than generating synthetic probes.

Option B is correct in the conventional preferred-link scenario because passive measurement depends on traffic traversing an SD-WAN member. When traffic is forwarded exclusively through the preferred link, FortiGate cannot measure the performance of unused alternative links. This is a limitation of passive monitoring.

Option D is correct because FortiGate uses TCP session information to measure latency, jitter, and packet loss. Latency measurements are derived from TCP connection behavior, while packet loss and jitter are determined using TCP header information.

Option A is incorrect because passive measurement relies on TCP session characteristics rather than ICMP traffic.

Option C is incorrect because enabling passive WAN health measurement disables automatic ASIC offloading on the affected firewall policies, allowing FortiGate to inspect the required TCP session information.

Option E is incorrect because the three-minute fallback to active probing belongs to Prefer Passive, not Passive mode. In Prefer Passive mode, FortiGate activates probes after three minutes without qualifying TCP traffic.

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.

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.

The screenshot omits the application-destination selector because the corresponding FortiOS GUI feature has not been enabled. Option D is correct: open System > Feature Visibility and enable Application Detection Based SD-WAN. Fortinet documents the equivalent CLI setting as ' config system global ' followed by ' set gui-app-detection-sdwan enable ' . Once visible, individual applications, groups and categories can be selected in SD-WAN rules. This is supported for direct internet access and for standalone FortiGate appliances, so options A and B are wrong. Option C is also wrong because using the CLI is an alternative, not a required prerequisite when the GUI setting is available. Application-aware traffic steering additionally requires an application-control profile on an applicable firewall policy so traffic can be classified. Administrators should distinguish this application-signature selector from the Internet Service Database destination field: ISDB objects are another supported way to define destinations, but ISDB matching is not synonymous with application- control signature recognition. Review the GUI feature flag, firewall policy inspection profile and the matched service rule before evaluating the resulting forwarding member. This behavior is documented specifically in FortiOS 7.6 Application Steering Using SD-WAN Rules.

FortiSASE geofencing provides geographical access control by permitting or denying connections to FortiSASE security points of presence (POPs) according to the originating country or region of the connecting user or edge device.

Option D is correct because FortiSASE identifies the source country using the connection ' s public IP address and evaluates it against configured regional access restrictions.

Administrators configure this functionality under Network > Geofencing > Regional access to FortiSASE.

FortiSASE supports three geographical access modes:

Allow all: Permits connections from all countries and regions. This is the default configuration.

Allow specified: Permits connections only from explicitly authorized countries or regions.

Deny specified: Blocks connections originating from selected countries or regions while permitting other locations.

Option A is incorrect because geofencing does not primarily enforce time-based application access restrictions.

Option B is incorrect because content inspection and web filtering are separate security functions.

Option C is incorrect because endpoint data encryption is unrelated to geographical connection restrictions.

Additionally, FortiSASE supports regional compliance rules that prioritize permitted POPs or on-premises gateways for users originating from specified regions. These routing preferences are distinct from geofencing ' s connection admission controls.

Security posture tags are a fundamental component of FortiSASE zero-trust access control. They allow administrators to classify endpoints dynamically according to security conditions and use those classifications in access policies.

Option B is correct because security posture tags can be referenced in policies that permit or deny access to applications and network resources. For example, an organization can allow access to a sensitive application only when an endpoint has an approved antivirus configuration and meets defined compliance requirements.

Option C is correct because posture tagging rules assess endpoint security attributes, including operating system information, installed software, antivirus status, running processes, and vulnerability conditions.

The evaluation process involves FortiSASE distributing tagging rules to FortiClient, FortiClient evaluating those rules locally, and the results being reported to FortiSASE. FortiSASE then dynamically applies the corresponding tags to the endpoint.

Option A is incorrect because posture tags are not primarily designed for continuous CPU, memory, or system resource monitoring.

Option D is incorrect because assigning endpoint profiles to user groups is a separate endpoint-management mechanism. Security posture tags classify device conditions rather than simply representing endpoint profile assignments.

This architecture enables continuous, context-sensitive policy enforcement without requiring administrators to manually update policies whenever an endpoint ' s compliance state changes.

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.

According to the FortiSASE 25 Enterprise Administrator Study Guide, page 25, branch on-ramp deployment enables organizations to secure outbound internet traffic from branch locations by connecting their existing network infrastructure to FortiSASE.

Option A is correct: Branch on-ramp allows remote offices and branch locations to establish secure IPsec VPN tunnels between their FortiGate or supported third-party network devices and FortiSASE points of presence (PoPs). Traffic is forwarded through these tunnels, allowing FortiSASE to deliver cloud-based security inspection and enforcement.

The study guide explains that connected branches can benefit from Secure Internet Access (SIA), Secure SaaS Access (SSA), and Secure Private Access (SPA).

Option B is incorrect: Although branch on-ramp supports secure private application access, providing access through a bookmark portal is not its primary deployment benefit.

Option C is incorrect: Branch on-ramp provides secure network connectivity and traffic inspection. It is not designed primarily for endpoint inventory, administration, or lifecycle management.

Option D is incorrect: The study guide explicitly states that FortiClient installation is not required for branch edge-device deployments and that ZTNA tags are not supported in this configuration.

Therefore, branch on-ramp primarily enables organizations to extend FortiSASE cloud security services to branch offices and secure their internet-bound traffic.

Exact Source References:

FortiSASE 25 Enterprise Administrator Study Guide, page 25 — Thick Edge Use Case, including secure branch outbound traffic and branch on-ramp.

FortiSASE 25 Enterprise Administrator Study Guide, page 26 — FortiSASE Branch On-Ramp Configuration.

FortiSASE 25 Enterprise Administrator Study Guide, page 27 — Edge-Device Policies, explaining the lack of ZTNA tag support.

FortiGate provides three primary SD-WAN health-monitoring modes: Active, Passive, and Prefer Passive. Prefer Passive combines live-session measurements with active probes when sufficient application traffic is unavailable.

Option B is correct because FortiGate measures performance passively when qualifying TCP sessions traverse an SD-WAN member. It derives latency, jitter, and packet-loss measurements from actual TCP session behavior rather than relying exclusively on synthetic probes.

Option E is correct because passive measurements alone cannot reliably determine whether an otherwise idle interface is completely unreachable. In Prefer Passive mode, FortiGate uses active probing when no suitable TCP traffic has been observed for three continuous minutes. Active probes can then identify dead members.

Option A is incorrect because ordinary ICMP traffic does not provide the TCP session information required for this passive measurement mechanism.

Option C reverses the transition logic. The three-minute timer applies to the absence of TCP traffic before switching from passive to active monitoring. FortiGate returns to passive monitoring when eligible TCP traffic becomes available.

Option D is incorrect because enabling passive-wan-health-measurement disables automatic ASIC offloading for the affected firewall policy, allowing the CPU to observe the session characteristics necessary for passive measurement.

The CSV import process for FortiManager model devices requires the fields ' Serial Number ' , ' Device Blueprint ' , and ' Name ' . These are the mandatory identifiers used to create model devices and apply the appropriate initial provisioning configuration. In the exhibit, the missing device-blueprint field and an empty name for one device prevent a complete import. Options A and B are therefore the required corrections. Metadata values for addresses or user-defined variables may be included as additional columns, but they are not universally mandatory to import a model device. Consequently, options C and D impose requirements that depend on a subsequent provisioning template, not the CSV import itself. The selected blueprint must also be compatible with the target hardware platform. When deploying large numbers of devices, administrators should ensure serial numbers are unique, device names are valid and blueprint assignments resolve to templates and packages within the correct ADOM. The definitive FortiManager 7.6 import specification lists precisely those three required CSV columns; it does not impose a blanket requirement for every metadata variable to contain a value at import time.

The IKE debug shows a receiving SHORTCUT_QUERY event and NAT hole punching, without an explicit forward shortcut-query record. This is consistent with a spoke receiving the shortcut-discovery query relayed by its hub over the existing spoke-to-hub tunnel. A hub-forwarder log would ordinarily include forwarding messages; the exhibit does not prove that a final spoke-to-spoke shortcut is already established. NAT hole punching is part of preparing connectivity when at least one endpoint is behind address translation, not proof that two established peers have completed negotiation. Therefore, the supported role is the destination spoke receiving a query via its hub. Reference: FortiOS 7.6 — ADVPN Shortcut Discovery and NAT Traversal. 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.

FortiSASE integrates FortiClient with its Endpoint Management Service (EMS) to provide centralized configuration, security enforcement, and remote-access connectivity. Managed endpoints receive configuration information through the Zero Trust Telemetry communication channel.

Option A is correct. FortiSASE supports automatic installation of its certificate authority certificate on managed FortiClient endpoints when SSL deep inspection is enabled. This allows endpoints to validate certificates issued during TLS inspection without requiring administrators to distribute the CA certificate manually. The important qualification is that automatic certificate deployment is associated with deep inspection; the default inspection mode is certificate inspection.

Option B is correct because FortiSASE centrally manages endpoint connection profiles, including the FortiSASE Cloud Security tunnel. FortiClient obtains the relevant connection parameters from its assigned endpoint profile, providing consistent VPN configuration and reducing administrative overhead.

Option C is incorrect because FortiSandbox integration requires appropriate endpoint-protection settings and licensing. The question does not establish that sandbox configuration is automatically deployed.

Option D is incorrect in the stated default configuration. Security posture tagging rules can be distributed to endpoints, but they must first be defined and enabled; their creation is not an automatic default onboarding action.

This distinguishes the standard connectivity provisioning workflow from optional advanced endpoint security configuration.

The implicit SD-WAN rule serves as the final catch-all. In FortiOS operation: " Sessions matching the implicit SD-WAN rule do not have an SD-WAN service id, as they are not associated with any specific user-defined SD-WAN rule. Additionally, this occurs only when traffic fails to match any entry in the policy route table. This default handling guarantees connectivity while minimizing the risk of blackholed traffic. " Administrators can observe this in diagnostic outputs for troubleshooting. 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.

From the Underlay and network advertisement configuration exhibit for the Secondary HUB: In FortiManager SD-WAN Overlay Orchestrator, underlay interfaces selected for a hub are the transports used to build the overlay IPsec tunnels (one overlay per underlay, per peer as defined by the template). Because both port1 and port2 are configured as underlays, FortiManager will build overlay tunnels over both underlay links. That supports: For the BGP neighbor options: So, the two correct conclusions are B and C. 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.

Fortinet Secure SD-WAN uses underlay and overlay networks to separate transport connectivity from logical routing and secure communication between enterprise locations.

The underlay network provides the underlying IP transport, including broadband internet, MPLS, leased lines, and wireless connectivity such as 4G/5G LTE. The overlay network provides logical connectivity through tunnels established over those transport networks.

Option A is correct because wireless connections can serve as the underlying transport for overlay tunnels. For example, a FortiGate with FortiExtender can establish an IPsec VPN overlay over a 5G cellular WAN connection.

Option E is correct because overlay networks provide routing flexibility independently of the physical transport infrastructure. IPsec VPN and ADVPN overlays enable dynamic route exchange, secure branch connectivity, path selection, and shortcut establishment.

Option B is incorrect because underlay connectivity is not restricted to wired interfaces. Cellular WAN connectivity is fully supported.

Option C is incorrect in the Fortinet SD-WAN terminology used here. A VLAN provides Layer 2 logical segmentation and is not inherently an SD-WAN overlay tunnel.

Option D is incorrect because FortiLink primarily provides management and connectivity between FortiGate and FortiSwitch devices. It is not classified as an SD-WAN transport underlay solely because it is a network interface.

FortiOS ADVPN 2.0 adds SD-WAN-aware shortcut path management over an already established ADVPN infrastructure. The principal spoke-side activation is advpn-select enable in the relevant SD-WAN zone, with advpn-health-check identifying the performance SLA. Transport-group configuration governs compatible underlying networks used to establish direct shortcuts. The FortiGate hubs ordinarily need no wholesale replacement of the existing compatible ADVPN tunnel configuration solely for this upgrade. Removing and recreating every IPsec tunnel is unnecessary and introduces avoidable operational risk. The supplied key selects a hub IPsec change, but the required feature in the question is implemented through the branch SD-WAN configuration. Reference: FortiOS 7.6 — ADVPN 2.0; SD-WAN Zone CLI and Transport Groups. 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.

FortiManager supports advance model-device creation and per-device metadata variable mappings for large-scale onboarding. Model devices can be assigned configuration templates and policy packages before physical installation. When DHCP-based discovery is selected, DHCP options can also be prepared to direct new FortiGates toward FortiManager. Custom metadata values provide branch-specific addresses, site identifiers and gateway settings. The terms “ZTP template” and “policy blueprint” do not accurately identify the documented FortiManager objects in the candidate answers: device blueprints and policy packages are distinct components. Consequently, options A, B and D are valid under a DHCP-based ZTP design. This choice is dependent on the selected bootstrap method. Reference: FortiManager 7.6 — Model Devices, Metadata Variables, Zero-Touch Provisioning and Device Blueprints. 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.

Verification qualification: The DHCP-server step depends on the zero-touch-provisioning method; it is not universally mandatory.

The command shown in the exhibit is: diagnose sys sdwan service 4 3 This command displays the runtime state of SD-WAN rule ID 3 on the device. The output explicitly shows: The listed members include multiple IPsec tunnel interfaces such as HUB1-VPN1, HUB1-VPN2, HUB1-VPN3, HUB2-VPN1, HUB2-VPN2, and HUB2-VPN3, which is characteristic of a spoke device connecting to multiple hubs in a hub-and-spoke ADVPN topology, as defined in the FCSS SD-WAN 7.6 architecture. Option B is incorrect because, although members are listed under different interfaces, the output does not indicate SD-WAN zones. Zones are shown only in configuration output, not in this diagnostic command. Option C is incorrect because this is not a hub device. The presence of multiple hub tunnels as SD-WAN members indicates a spoke role. Additionally, the output does not confirm the number of established ADVPN shortcuts. Option D is incorrect because the output clearly references SD-WAN rule 3, not rule 4, and it does not state that exactly three shortcut tunnels are allowed. Therefore, the correct conclusion is that this is a spoke device and SD-WAN rule 3 is configured with nine members, which matches option A.

The SD-WAN overlay template defines a zone for each underlay interface and moves the interfaces into those zones. This statement perfectly describes the likely sequence of events. The template, when applied, re-organizes the interfaces and zones, causing the existing firewall policy that relies on the old zone configuration to fail. This is the most plausible root cause. 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 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.

The phase 1 interface explicitly configures IKEv2, so a compatible peer must support that IKE version. With mode-cfg disabled, the overlay interface is not automatically assigned an address using IKE mode configuration, and the required interface addressing must be configured. The exchange-interface-ip capability exchanges configured FortiGate IPsec interface addresses, enabling user-defined overlay addressing. It is a Fortinet-specific integration and should not be assumed to interoperate with any third-party IPsec peer. The source candidate key incorrectly includes general third-party compatibility as if every configured Fortinet-specific mechanism were interoperable. Reference: FortiOS 7.6 CLI Reference — vpn ipsec phase1-interface, ike-version, mode-cfg, exchange-interface-ip. 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.

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.