NSE7_SSE_AR-26 Questions and Answers

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.

The exhibit shows the following IPsec phase1-interface configuration applied on spoke tunnels: In the FCSS SD-WAN 7.6 ADVPN architecture, the network-overlay and network-id parameters are used to logically group IPsec tunnels into separate overlays. When network-overlay is enabled, FortiGate treats the tunnel as part of an overlay network rather than a simple transport tunnel. The network-id parameter is critical in multi-overlay ADVPN designs. Fortinet documentation specifies that ADVPN shortcuts are only allowed between tunnels that share the same network-id. This mechanism explicitly prevents cross-overlay shortcuts, ensuring that shortcuts are formed only within the same logical overlay and not across different overlays that may serve different purposes (for example, different hubs, regions, or transport groups). The use of auto-discovery-shortcuts dependent further enforces correct shortcut behavior by ensuring that shortcut tunnels depend on the state of the parent overlay tunnel, but it does not by itself prevent multiple shortcuts or convert ADVPN versions. Why the other options are incorrect: Therefore, the valid objective of these settings is to prevent cross-overlay shortcuts, which corresponds to Option C.

Fortinet Secure SD-WAN supports an integrated networking architecture in which FortiGate appliances provide routing, traffic steering, and security enforcement while extending connectivity through FortiSwitch, FortiAP, and FortiExtender devices.

Option C is correct because a FortiGate configured as an SD-WAN hub can also utilize FortiExtender connectivity. FortiExtender provides cellular WAN transport, including 4G and 5G connectivity, and can be integrated as a logical WAN interface and SD-WAN member.

FortiSwitch provides wired access-layer connectivity through FortiLink, while FortiAP extends wireless LAN access. These components are complementary and do not require separate SD-WAN topologies.

Option A is incorrect because FortiGate devices supporting multiple extension types remain eligible for inclusion in the SD-WAN architecture.

Option B is incorrect because SD-WAN topology design is not restricted to a single extension product category. Multiple Fortinet networking components can be centrally orchestrated within the same deployment.

Option D is incorrect because regional segmentation is determined by network architecture, geographical requirements, routing domains, and operational considerations—not simply the types of extensions attached to each FortiGate.

FortiManager can centrally manage FortiGate devices and associated extensions, applying consistent SD-WAN templates and provisioning policies across enterprise branches and hubs.

The FortiOS 7.6 architecture describes multiple standard SD-WAN deployment designs, each mapped to a specific operational goal or constraint. A cloud on-ramp topology is designed to optimize connectivity to cloud services such as SaaS and IaaS. This design provides the most efficient and reliable path to cloud applications by establishing direct tunnels to cloud gateways or cloud workloads and by avoiding backhauling traffic through a central data center. As a result, its primary indication is improving the performance of cloud applications, which makes option A correct. A remote breakout (centralized breakout) design forwards all internet-bound traffic from branch sites to a central hub for security inspection. This allows security policies, inspection, and logging to be centralized on a high-capacity FortiGate at the hub. Because branch devices do not need advanced local security configurations, this design also limits local management requirements, which makes option C correct. Option B is incorrect because a standalone SD-WAN design is not selected simply because a site has only one WAN link. SD-WAN provides its main benefits when multiple WAN paths exist, and single-link sites do not gain meaningful traffic-steering advantages. Option D is incorrect because a direct internet access (DIA) design performs local internet breakout at the branch and therefore requires strong local security capabilities. DIA does not inherently increase traffic security and is not intended for devices with limited capabilities. Therefore, the two correct associations are A and C.

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.

FortiGate first establishes destination reachability and then evaluates the eligible members of the matching SD-WAN service. The exhibit reports that traffic for the corporate network is reaching HUB1-VPN3 even though HUB1-VPN1 appears earlier in member preference. Option C is supported if HUB1-VPN1 has no valid route for the exact destination prefix. An SD-WAN service cannot force traffic through an overlay member that does not provide reachability. The candidate ' s second answer, D, is less precise: the exhibit presents SD-WAN member preference or priority values, whereas the wording says ' route priority ' . FortiOS distinguishes route priority in the FIB from the preference order defined in an SD-WAN service. A smaller numerical member preference can influence forwarding, but it should not be described as proof of a more-preferred static route. Option A reverses the ranking, and option B invents an overriding conventional policy route not established by the diagnostic output. As presented, C is secure but the complete C,D pair depends on interpreting D as member priority rather than routing-table priority. Validate the actual route entries, their administrative distance and priority, and ' diagnose sys sdwan service4 ' before treating D as conclusive.

Verification qualification: The choice concerning route priority is imprecisely worded; displayed member priority is not necessarily static-route priority.

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

FortiManager SD-WAN Monitor Template View uses per-branch health indicators and hover details. Orange icons indicate partial degradation or an SLA failure on at least one monitored interface. The branch1 tooltip specifically identifies HUB2-VPN1, HUB2-VPN2 and HUB2-VPN3 as problematic. The map is consistent with other overlays toward the alternate hub, supporting the six-overlay/three-down interpretation, although the full six-interface list is not directly visible in the hover box. Branch3’s exact configured tunnel count cannot be inferred from an orange indicator alone. This is why A and D are stronger than claims about hub counts or branch3’s exact overlay count. Reference: FortiManager 7.6 — SD-WAN Monitor Template View. 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.

Verification qualification: The tooltip alone does not explicitly confirm the inferred total tunnel count.

The session diagnostic displays an original session path and a reflect or auxiliary session for asymmetric forwarding. The reflect session lists dev=7- > 6/6- > 7; interface index 7 corresponds to port3 and index 6 corresponds to port2, establishing a reply direction of port2 to port3. The original session path dev=7- > 5/5- > 7 represents port3 and port1, not port3 and port2. Auxiliary sessions can be hardware-offloaded when the FortiGate network processor supports the relevant configuration and conditions; a single currently observed offload flag does not prove that capability is impossible. Therefore C and D are the correct conclusions. Reference: FortiOS 7.6 — Controlling Return Path with Auxiliary Session. 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.

From the SD-WAN rule configuration (service ID 3, name " Corp " ), the rule is configured as: In the diagnose firewall proute list output for service=3 (Corp), FortiGate shows the actual members considered for this rule and their SLA pass status: Because the rule is SLA-based, FortiGate selects only members that meet the SLA requirements for the rule. The output indicates that HUB1-VPN1 and HUB1-VPN2 pass both SLA checks (num_pass=2), while HUB1-VPN3 passes only one (num_pass=1) and therefore is not selected as an eligible forwarding interface for this rule. Since load-balance is enabled and the rule uses hash-mode source-ip-based, FortiGate will consistently choose an eligible member based on the source IP hash. For traffic sourced from 10.0.1.101, the session can be steered through either HUB1-VPN1 or HUB1-VPN2 (whichever the hash selects), but not HUB1-VPN3. Therefore, the correct answer is 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.

Verification qualification: A specific hash-selected interface cannot be predicted from the supplied configuration without the full evaluation.

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.

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

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.

The line sdwan_mbr_seq=1 sdwan_service_id=4 indicates that this session is part of an SD-WAN rule. sdwan_service_id=4 confirms that the session is being handled by SD-WAN rule ID 4. This directly links the flow to the SD-WAN configuration. The line no_offload_reason: redir-to-ips denied-by-nturbo shows that the session is not offloaded to the NPU (Network Processing Unit) and is being processed by the main CPU. A session that is not offloaded can be re-evaluated. If the outgoing interface (the one currently being used) goes down, the FortiGate will re-evaluate the session against the SD-WAN rules to find a new active member to steer the traffic through. This is a fundamental behavior of SD-WAN, which ensures network 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.

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.

FortiOS supports static routing through both SD-WAN zones and individual SD-WAN member interfaces. However, a specific routing restriction applies when both types of routes are configured.

Option B is correct because FortiOS does not permit duplicate destination prefixes when one static route references an SD-WAN zone and another references an individual interface belonging to that zone.

Although identical destination prefixes are not permitted in this configuration, overlapping subnets with different prefix lengths are supported.

For example:

SD-WAN zone route: 10.0.0.0/8

Individual member route: 10.2.0.0/16

Both routes can coexist because their destination prefixes are different, despite overlapping address ranges. FortiGate applies longest-prefix matching when determining the most specific destination route.

Option A is incorrect because FortiOS explicitly supports SD-WAN zones as static-route interfaces.

Option C is incorrect because static routes can reference individual SD-WAN members, providing more granular routing control.

Option D is incorrect because overlapping destinations are permitted but not mandatory. The essential requirement is that the zone route and individual member route must not use identical destination prefixes.

When a static route references an SD-WAN zone, FortiOS installs corresponding routes for the eligible zone members. These routes can participate in equal-cost multipath routing.

The application-aware SD-WAN rule can initially route a connection through the implicit SD-WAN rule if its three-tuple (destination IP, port, protocol) has not yet been learned in the application cache. Once the application-control engine identifies GoToMeeting as a Collaboration application, session reevaluation can allow matching of the intended application rule. Depending on state, NAT and route changes, an existing session might not migrate successfully. This mechanism is not universally dependent on deep SSL inspection, and the configured Collaboration category is a legitimate match for GoToMeeting. The first cause is established; the second is a plausible interpretation not proven by the visible log alone. Reference: FortiOS 7.6 — Application Detection Steering; Fortinet Technical Tip — Application Learning Phases. 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: The exhibit establishes initial application classification behavior, but not that session route refresh definitely failed.

One SD-WAN rule is defined with application categories as the destination → The diagnose output shows application control matches such as Microsoft.Portal, Operational.Technology, and Social.Media, confirming that SD-WAN rules are using application categories as destinations. UDP traffic destined to the subnet 10.22.0.0/24 matches a policy route → The first entry (id=1) shows protocol=17 (UDP) with destination 10.22.0.0/24, confirming this traffic is handled by a policy route instead of an SD-WAN rule. 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.

FortiSASE supports federated identity authentication through Security Assertion Markup Language (SAML), enabling enterprises to integrate their existing identity providers into centralized secure access workflows.

Option C is correct because FortiSASE can function as a SAML service provider while delegating user authentication to an external identity provider such as Microsoft Entra ID, formerly Azure AD, Okta, or FortiAuthenticator.

During authentication, FortiSASE redirects or delegates the authentication exchange to the configured identity provider. After successful authentication, the identity provider issues a signed SAML assertion containing the identity information required by the service provider. FortiSASE validates the assertion and applies the appropriate access-control policies.

Option A is incorrect because SSO reduces repetitive authentication across supported services rather than requiring independent authentication for every security function.

Option B is incorrect because SSO does not eliminate identity verification. Authentication remains mandatory according to configured access requirements, and zero-trust policies may additionally assess endpoint posture and contextual conditions.

Option D is incorrect because the principal purpose of federated authentication is to leverage an established identity system rather than duplicate enterprise passwords within FortiSASE.

SSO simplifies administration while maintaining centralized identity governance, supporting secure internet and private application access.

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.

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 proxy-based secure internet access allows managed and unmanaged endpoints to use cloud-delivered security controls without requiring the FortiClient endpoint agent.

Option A is correct because a proxy auto-configuration file can define how browsers and operating systems redirect eligible HTTP and HTTPS requests to the FortiSASE secure web gateway.

A PAC file allows automatic proxy selection based on destination URLs, hostnames, and other conditions. FortiSASE supports hosted and downloadable PAC file configurations, simplifying deployment across large endpoint populations.

Option B is correct because endpoints should install and trust the FortiSASE certificate authority certificate when SSL deep inspection is required. During TLS inspection, FortiSASE decrypts permitted traffic for security analysis and presents certificates that must be trusted by the endpoint.

Without the appropriate certificate, browsers and applications may reject inspected HTTPS connections because the signing authority is untrusted.

Option C is incorrect because FortiClient is associated with agent-based endpoint connectivity. Proxy-based deployment can operate without installing FortiClient.

Option D is incorrect because a tunnel policy applies to tunnel-based traffic handling rather than constituting an endpoint onboarding component for explicit proxy access.

PAC configuration provides traffic steering, while CA certificate installation establishes the certificate trust needed for SSL inspection.

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.

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

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.