Fortinet NSE7_SSE_AR-26 Fortinet NSE 7 - FortiSASE 26 Architect Exam Practice Test

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.

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.

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.

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.

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.

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.

FortiGate SD-WAN can distribute traffic over multiple WAN links while applying performance-based eligibility checks. These checks measure network conditions such as latency, jitter, and packet loss against defined service-level agreement thresholds.

Option A is correct because FortiGate can load balance sessions across available SD-WAN members that satisfy the configured SLA target. An interface that fails the required performance criteria is excluded from the eligible load-balancing set under normal SLA-compliant operation.

Option B is correct because current FortiOS versions support load balancing within the Lowest Cost (SLA) strategy. The configuration uses set mode sla together with set load-balance enable under the relevant SD-WAN service rule. Importantly, the load-balancing algorithm does not use interface cost to select individual links once SLA-based load balancing is enabled.

Option C is incorrect because Best Quality is a separate strategy that selects preferred members based on measured link-quality metrics. It is not the supported SLA-based multi-link load-balancing configuration described in the question.

Option D is incorrect because the legacy session, spillover, and volume terminology does not describe supported Best Quality load-balancing algorithms in this context.

FortiOS 7.4.1 and later integrated the former Maximize Bandwidth strategy into the current load-balancing configuration model.

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.

FortiClient integration extends FortiSASE capabilities beyond cloud-based traffic inspection by introducing endpoint-level security assessment, telemetry collection, and vulnerability management.

Option B is correct because FortiClient performs device posture assessments based on security conditions such as operating system information, antivirus status, running processes, and other endpoint attributes. FortiSASE uses this information to generate security posture tags that can be incorporated into zero-trust access policies.

The FortiClient agent evaluates tagging rules locally and reports results to FortiSASE. Administrators can consequently implement context-aware access decisions based on device compliance rather than relying exclusively on user authentication.

Option C is correct because FortiClient supports vulnerability scanning and management. It can identify vulnerable applications and operating system components, helping administrators assess endpoint security exposure and implement appropriate remediation measures.

Option A is incorrect because SSL inspection is a cloud-delivered security capability available through FortiSASE and does not inherently require FortiClient.

Option D is incorrect because inline CASB operates through FortiSASE application control and web security inspection. It is not exclusive to agent-based deployment.

The key architectural distinction is that FortiClient provides endpoint-resident security telemetry and vulnerability assessment capabilities, whereas agentless proxy deployments primarily enforce security through cloud traffic inspection.

When using the diagnose sys session list command, SD-WAN-specific session steering is indicated by the presence of the sdwan_service_id field in the session data. This identifier ties the session directly to a specific SD-WAN rule or service. As noted in the Fortinet documentation: “Sessions that are handled according to SD-WAN rules will include a service ID tag (sdwan_service_id) in their session listing. This allows administrators to correlate live sessions with SD-WAN policy matches for troubleshooting and visibility.” This is a crucial diagnostic tool, as it distinguishes between traffic managed by traditional routing and that explicitly controlled by SD-WAN steering logic, aiding in operational insight and troubleshooting.References: 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 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.

BGP on loopback separates routing adjacency establishment from individual IPsec tunnel interface addresses. Combined with Dynamic BGP, it enables scalable SD-WAN overlays and dynamic spoke-to-spoke routing relationships.

Option A is correct for the intended reference design because enabling net-device on a spoke supports dedicated tunnel-interface handling for IPsec connections and dynamically created ADVPN shortcuts. This configuration appears in Fortinet ' s overlay provisioning examples.

Option C is correct because the spoke ' s localid supplies an identifiable IKE identity that the hub can use when authenticating and matching IPsec peers. It is particularly useful where multiple spokes share a hub ' s dial-up IPsec configuration or the hub requires specific peer identities.

Option B is incorrect because the hub normally acts as the dynamic IPsec dial-up responder, rather than being configured as a static tunnel endpoint for every spoke.

Option D is not a fundamental requirement of BGP-on-loopback routing. IKE mode configuration can distribute tunnel addresses, but loopback-based BGP does not inherently require IP addresses on each IPsec overlay.

An important implementation distinction is that net-device behavior can vary by FortiOS release and reference topology. Therefore, the actual production configuration should follow the selected FortiOS 7.6 deployment template rather than treating this combination as universal.

FortiGate SD-WAN evaluates traffic against configured service rules and uses eligible member interfaces to determine the forwarding path. In this scenario, the destination is an internal corporate server accessible through the SD-WAN overlay.

The exhibit identifies SD-WAN service rule 3, named Corp , with the following configuration:

set load-balance enable

set mode sla

set dst " Corp-net "

set src " LAN-net "

set priority-members 3 4 5

Option D is correct because the rule enables SLA-based load balancing across three overlay members corresponding to HUB1-VPN1, HUB1-VPN2, and HUB1-VPN3.

The route-list output confirms that the corporate service rule has three available paths. Provided the members remain healthy, meet the applicable SLA requirements, and have valid destination reachability, FortiGate can distribute qualifying sessions among these interfaces.

Option B incorrectly assumes that the interface observed in the packet-sniffer output must carry every subsequent session. The displayed ICMP traffic uses HUB1-VPN3, but this observation does not establish exclusive forwarding for HTTP sessions.

Options A and C identify physical WAN interfaces rather than the eligible corporate VPN overlay members.

FortiGate applies the configured load-balancing algorithm when selecting an eligible member for a new session. The original question establishes that all SD-WAN links are stable, supporting the use of the available overlay paths.

The exhibit demonstrates the SD-WAN cascade interface functionality, which propagates a failure detected on monitored WAN links to a designated physical interface.

The configuration includes:

config system sdwan

set fail-detect enable

set fail-alert-interfaces " port5 "

Both configured performance SLAs also enable update-cascade-interface , allowing the SD-WAN health-monitoring subsystem to control the state of the designated alert interface.

Option B is correct because FortiGate restores port5 when at least one monitored SD-WAN member is alive. When all monitored members fail, FortiGate administratively brings port5 down. Once an eligible member recovers, FortiGate brings the interface back up.

This behavior allows downstream network equipment to detect a loss of WAN connectivity even when the local Ethernet link would otherwise remain operational.

Option A is incorrect because the configuration does not specify sending notification messages through port5 whenever an individual member fails.

Option C reverses the expected behavior. Port5 is brought down, not up, when all monitored SD-WAN members fail.

Option D is incorrect because fail-alert-interfaces controls interface state rather than functioning as a dedicated notification transport.

The cascade interface mechanism is particularly useful when an alternative network device must assume traffic forwarding following a complete SD-WAN connectivity failure.

FortiGate SD-WAN traffic steering depends on both service-rule matching and routing-table reachability. A matching SD-WAN rule identifies eligible interfaces, but the selected member must also have a usable route toward the destination.

Option A is correct because service rule 3 matches the specified source and destination address ranges, and the routing table identifies HUB1-VPN3 as the route toward the corporate server subnet.

The source address 10.0.1.0/24 falls within the source range 10.0.0.0/8 , while destination 10.2.5.254 also falls within the configured destination range.

The exhibit identifies service rule 3 as an SLA-based service with multiple available overlay members. However, the route to 10.2.5.0/24 identifies HUB1-VPN3 as the reachable next-hop interface.

Although HUB1-VPN2 appears in the service ' s eligible member list, it does not provide the matching destination route shown in the routing table. Therefore, option B is incorrect.

Options C and D reference service rule 4 and physical WAN interfaces. They do not represent the selected corporate overlay path for the stated source and destination.

This demonstrates a fundamental SD-WAN behavior: matching a service rule does not eliminate the requirement for valid route resolution through its forwarding member.

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.

FortiSASE Secure Private Access can integrate with existing FortiGate SD-WAN infrastructure to provide cloud-delivered security enforcement and connectivity to privately hosted enterprise applications.

Option C is correct because FortiSASE acts as a security enforcement point for traffic entering its cloud infrastructure. Administrators can apply security profiles and traffic policies before permitted sessions are forwarded toward private resources through the established SD-WAN connectivity.

Option D is correct because SD-WAN-integrated SPA provides network-layer connectivity to private applications, supporting both TCP-based and UDP-based protocols. This is valuable for enterprise applications that cannot operate through HTTP-only access proxies.

Option A is incorrect because the SD-WAN integration model does not require FortiClient to establish a direct ZTNA access-proxy tunnel to the on-premises FortiGate. Instead, FortiSASE security points of presence connect to the FortiGate SD-WAN hub through IPsec overlays.

Option B describes an endpoint-posture access-control capability, but posture evaluation is not inherently performed by the SD-WAN hub in this deployment method. FortiSASE and FortiClient can assess endpoint security conditions, while the SD-WAN hub primarily provides network connectivity and local security enforcement.

The principal advantages are protocol-flexible private application connectivity and centralized cloud security inspection, integrated with the existing SD-WAN architecture.

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 FortiManager installation error is associated with the gateway value produced by metadata substitution, not with a general failure of FortiManager-to-FortiGate connectivity. A template uses a variable such as ' $(sdwan_port1_gw) ' to provide the interface gateway at installation time. If the current device has no valid value in its per-device metadata mapping, the generated FortiOS configuration contains an invalid IPv4 gateway and the copy or validation operation fails. Therefore the remediation is to inspect the variable definition and its per-device mapping, which is option C in the normalized question. The administrator can verify the mapping for the affected FortiGate, supply a valid address, regenerate the installation preview and reinstall. It is unnecessary to remove all template installation targets: FortiManager supports them alongside metadata variables. Nor must the members of a zone all use identical gateway configuration methods. This conclusion is specifically tied to the error shown in the original exhibit. The uploaded FortiSASE guides describe centralized management generally, but detailed per-device template substitution belongs to the FortiManager 7.6 Administration Guide.

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.

When referencing a zone in a static route, FortiGate’s behavior is described as: " Referencing a zone in a static route causes FortiGate to install a static route for each member interface of the zone. This enables ECMP (Equal-Cost Multi-Path) and load balancing where supported and ensures that traffic can be steered over any valid zone member according to SD-WAN rules or standard routing. " This mechanism is fundamental to Fortinet’s implementation of SD-WAN and simplifies large, multi-interface deployments.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. 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.

Application-based SD-WAN rules enable intelligent traffic steering. The FortiOS behavior is: " If a flow is identified as belonging to a defined application category (such as social media), FortiGate will match it to the corresponding service rule (rule 2) and route it through the specified interface, such as port2. However, if the application is not recognized during the session setup, the system defaults to load balancing the traffic using the available tunnels according to the policy for unclassified traffic, ensuring continuous connectivity while waiting for application classification. " This guarantees both performance and resilience. 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.

For FortiGate to steer traffic using SD-WAN rules, two foundational elements must be in place: available WAN paths (underlay links) and firewall policies that allow traffic to reach the SD-WAN interface. Underlay links (Option B) are mandatory because SD-WAN operates by selecting among multiple WAN transports (for example, broadband, MPLS, LTE, or IPsec tunnels). These links are configured as SD-WAN members and form the physical or logical paths over which traffic can be steered. Without underlay links, SD-WAN has no paths to evaluate or select. Firewall policies (Option E) are also mandatory because FortiGate only processes and forwards traffic that is explicitly permitted by a firewall policy. When SD-WAN is enabled, firewall policies must reference the SD-WAN interface or SD-WAN zone as the outgoing interface. If no such policy exists, traffic will not be forwarded and SD-WAN rules will never be evaluated. Why the other options are incorrect: Therefore, the two required features that must be configured before FortiGate can steer traffic according to SD-WAN rules are underlay links and firewall policies, which correspond to B and E.

FortiManager enforces a strict distinction: " Firewall policies must reference SD-WAN zones, not individual SD-WAN members, when used in conjunction with SD-WAN templates. Attempting to install a policy that references a specific member (interface) will result in a deployment error, as member-level targeting is not supported in SD-WAN policy abstraction. This enforces centralized policy consistency and proper SD-WAN operation. " Ensuring policies target zones allows FortiGate to dynamically select the optimal member. 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 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.

FortiSASE Branch On-ramp provides a cloud-integrated connectivity method for branch networks that require centralized security enforcement without building a traditional enterprise WAN infrastructure at every location.

Option B is correct because Branch On-ramp enables supported branch routers and FortiGate devices to establish secure IPsec tunnels to FortiSASE security points of presence.

After establishing the connection, branch traffic can be inspected using cloud-delivered firewall and security services. The architecture reduces the need to deploy and maintain a complete set of security inspection capabilities at each remote site.

Branch endpoints generally forward traffic through their local IPsec device, which serves as the default gateway. FortiClient installation is not required solely for branch on-ramp connectivity.

Option A is incorrect because the primary architecture forwards selected branch traffic toward FortiSASE rather than limiting connectivity to direct local internet breakout.

Option C is incorrect because Branch On-ramp does not universally replace endpoint protection software. Endpoint security remains an independent requirement.

Option D is incorrect because application performance optimization is associated primarily with SD-WAN path selection and digital experience monitoring rather than the principal Branch On-ramp function.

The architectural objective is to simplify branch deployment while maintaining consistent security inspection and access policies across geographically distributed sites.

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.

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 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.

For a large-scale SD-WAN deployment (such as 1000 spokes) where ADVPN shortcut routing is required and some remote sites connect via FortiSASE, the recommended overlay routing configuration is BGP running on loopback interfaces, combined with dynamic BGP for ADVPN shortcut routing. This design leverages the scalability and resilience of BGP, allowing dynamic discovery and route exchange necessary for shortcut tunnels between spokes in ADVPN environments. Using loopback interfaces for BGP peering is considered best practice because it decouples routing protocol stability from physical link status, ensuring that if a physical underlay interface fails, the BGP session remains up as long as there’s an alternate path. With dynamic BGP, each spoke can efficiently learn the routes to other spokes and dynamically establish shortcuts, which is critical at this scale. This method also integrates smoothly with FortiSASE for remote connectivity to the SD-WAN hub, providing flexibility and centralized management.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.

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.

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 diagnose sys sdwan advpn-session output shows remote health check info(3) and a selected local path such as HUB1-VPN1. It describes health-check information received by the local spoke from another spoke as part of ADVPN 2.0 edge discovery. The remote records can include bandwidth, latency, jitter, packet loss, transport group and SLA state. This information enables the local spoke to evaluate candidate direct shortcuts using both endpoints’ path conditions. The output does not show a hub providing embedded measurements to a spoke and does not by itself indicate ongoing ICMP-based embedded SLA redistribution. The candidate key incorrectly describes the local spoke as the transmitter of the shown measurements. Reference: FortiOS 7.6 — ADVPN 2.0 Edge Discovery and Path Management. 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.

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.