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.

The exhibit shows the runtime details of two SD-WAN services (rules): Service(2) Service(3) Traffic from 10.0.1.124 to 10.0.0.254 matches Service(3) because the destination IP 10.0.0.254 falls within the destination range 10.0.0.0– 10.255.255.255. Within Service(3), the member list shows SLA results per interface: This indicates that, for Service(3), only HUB1-VPN2 and HUB2-VPN2 are currently meeting the SLA requirements (passing), and because the rule uses hash-mode=round-robin, FortiGate load-balances sessions across the passing members. Therefore, FortiGate will steer the traffic using HUB1-VPN2 or HUB2-VPN2, which corresponds to Option B. 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.

Verification qualification: SLA eligibility and routing-table reachability need confirmation; the two-member outcome depends on those conditions.

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.

In FortiOS (including FortiOS 7.6), FortiGate follows a strict and well-defined route lookup order when determining how to forward traffic. This order is critical for understanding SD-WAN behavior and is explicitly referenced in the FCSS SD-WAN curriculum. The correct lookup sequence is: Among the options provided, only Option D correctly reflects the beginning of this sequence by placing policy routes first, followed by ISDB routes, then SD-WAN rules, and finally static routes (representing the routing table). Therefore, the correct answer is 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. 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.

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.

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.

When asymmetric routing is observed (such as reply traffic not following the optimal path), the solution is: " The auxiliary-session feature, enabled under config system settings, allows FortiGate to consider multiple egress interfaces for reply traffic, not just the original ingress interface. This is crucial for SD-WAN environments where the best path may differ between forward and return directions, especially when performance or policy rules are dynamically evaluated. " Activating this ensures reply traffic is always sent on the member with the best real-time metrics.References: 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 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.

Comprehensive and Detailed Explanation From Fortinet SD-WAN 7.6 Architect / Course Guide:

FortiManager SD-WAN provisioning templates allow administrators to define installation targets for individual SD-WAN members. This enables a common template to accommodate branch devices with different WAN interfaces or overlay tunnel configurations.

Option B is correct because the diagnostic output corresponds to branch1_fgt, based on the configured installation targets and the absence of SD-WAN member ID 6.

The HUB1 zone configuration shows:

HUB1-VPN1 (ID 4): No installation target restriction; deployed to all assigned devices.

HUB1-VPN2 (ID 5): Assigned to branch1_fgt, branch2_fgt, and branch3_fgt.

HUB1-VPN3 (ID 6): Assigned only to branch2_fgt and branch3_fgt.

The diagnostic output lists members 4, 5, 7, 8, and 9, but member 6 is absent.

This matches branch1_fgt because HUB1-VPN3 is not included in that device ' s installation targets.

Option A is incorrect because branch2_fgt should have member 6 installed.

Option C is incorrect because the absence of a member from the diagnostic output does not establish that it is dead; it may not be configured on that device.

Option D is incorrect because the output is consistent with the template ' s device-specific configuration.

The determining principle is that FortiManager installs SD-WAN members according to their installation targets, and an empty installation target applies the member to all devices assigned to the template.