NSE5_SSE_AD-7.6 Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator Questions and Answers

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

FortiSASE endpoint upgrade rules provide controlled deployment of the latest supported FortiClient version. The FortiSASE study material specifies that administrators can either perform an upgrade immediately or configure a scheduled start time, with the scheduled deployment based on the endpoint ' s local time. It also identifies endpoint groups as the targeting mechanism and explains that automatic reboot behavior is configurable rather than unconditional.

Therefore, A is correct. Fortinet ' s Endpoint Upgrade documentation provides the exact scheduling behavior: when Scheduled (endpoint local time) is configured and the endpoint ' s clock has already passed the selected time, FortiClient installation is deferred until the next day at that selected time.

B is incorrect because upgrade rules cannot be assigned to a user group or user object; they apply to computer/device groups or computer/device objects. C is incorrect because only the Immediate option begins installation immediately; a scheduled deployment follows its configured local schedule. D is incorrect because the automatic reboot setting applies to Windows endpoints. Fortinet specifically states that macOS endpoints do not require a reboot to complete the FortiClient installation.

Study Guide Reference: Endpoint Management > Endpoint Upgrade; FortiSASE Enterprise Administrator Study Guide, Endpoint Management.

===============

According to the FortiSASE 7.6 Architecture Guide and the FCP - FortiSASE 24/25 Administrator study materials, the FortiSASE solution is structured around three primary pillars or " use cases " that address the security requirements of a modern distributed workforce.

Secure Internet Access (SIA) (Option A): This use case focus on protecting remote users as they browse the public internet. It utilizes a full cloud-delivered security stack including Web Filtering, DNS Filtering, Anti-Malware, and Intrusion Prevention (IPS) to ensure that users are protected from web-based threats regardless of their physical location.

Secure SaaS Access (SSA) (Option B): This use case addresses the security of cloud-based applications (like Microsoft 365, Salesforce, and Dropbox). It leverages Inline-CASB (Cloud Access Security Broker) to identify and control " Shadow IT " —unauthorized cloud applications used by employees—and applies Data Loss Prevention (DLP) to prevent sensitive information from being leaked into unsanctioned SaaS platforms.

Secure Private Access (SPA) (Option C): This use case provides secure, granular access to private applications hosted in on-premises data centers or private clouds. It can be achieved through two main methods: ZTNA (Zero Trust Network Access), which provides session-specific access based on identity and device posture, or through SD-WAN integration, where the FortiSASE cloud acts as a spoke connecting to a corporate SD-WAN Hub.

Why other options are incorrect:

Secure VPN Access (SVA) (Option D): While SASE uses VPN technology (SSL or IPsec) as a transport for the Endpoint mode, " SVA " is not a formal curriculum-defined use case. The SASE framework is intended to evolve beyond traditional " Secure VPN Access " into the SIA and SPA models.

Secure Browser Access (SBA) (Option E): Although FortiSASE offers Remote Browser Isolation (RBI), it is considered a feature or a component of the broader Secure Internet Access (SIA) use case rather than a separate, standalone use case in the core administrator curriculum.

According to the FortiSASE 7.6 Feature Administration Guide, steering bypass destinations (also known as split tunneling) allow administrators to optimize bandwidth by redirecting specific trusted traffic away from the SASE tunnel to the endpoint ' s local physical interface.

Destination Types (Option C): When creating a bypass destination, administrators can select from four distinct types: Infrastructure (pre-defined apps like Zoom/O365), FQDN (specific domains), Local Application (identifying processes on the laptop), or Subnet (specific IP ranges).

Apply Condition (Option B): The " Apply " condition is a flexible setting that allows the administrator to choose when the bypass is active. It can be applied to endpoints that are On-net (inside the office), Off-net (remote), or Both. This ensures that if a user is in the office, they don ' t use the SASE tunnel for local resources, but if they are home, they might still bypass high-bandwidth sites like YouTube to preserve tunnel capacity.

Why other options are incorrect:

Option A: Subnet is one of four types and is not the only type supporting these conditions.

Option D: The system explicitly supports " Both " to ensure consistency across network transitions.

The correct answer is B. SSO. The FortiSASE Administrator Study Guide explicitly states that enabling SSO authentication overrides any other previously created authentication methods, including the local user database, LDAP, and RADIUS.

FortiSASE implements SSO for endpoint users through SAML. In this design, FortiSASE functions as the service provider (SP), while authentication is performed by an external identity provider (IdP), such as Okta, FortiAuthenticator, or another supported IdP. The user database therefore does not need to be hosted directly on FortiSASE. Instead, FortiSASE redirects the user to the IdP and uses the resulting SAML assertion to establish the authenticated SSO session. The study guide confirms that SSO can be configured for both VPN users and Secure Web Gateway (SWG) users.

A. Local and C. RADIUS are authentication sources that SSO supersedes when SSO is enabled. D. MFA is an additional authentication-strength mechanism rather than the FortiSASE authentication mode described as overriding previously configured methods.

Study Guide Reference: User Onboarding and Additional Features > Configuring SSO > VPN User SSO / SWG User SSO, FortiSASE Administrator Study Guide, page 56.

FortiSASE supports SAML, LDAP, and RADIUS as authentication mechanisms applicable to remote-user identity verification. The FortiSASE Administrator Study Guide explicitly identifies its authentication-server configuration objectives as describing remote authentication with LDAP and RADIUS and SAML single sign-on (SSO). It further states that FortiSASE supports authentication through the local database, RADIUS, LDAP, and SAML for SSO.

SAML (A) provides federated SSO by allowing FortiSASE, acting as the service provider, to rely on an external identity provider for user authentication. SAML SSO is specifically supported for FortiSASE SWG and VPN deployments.

LDAP (C) enables integration with directory services such as Microsoft Active Directory. FortiSASE can query directory information and authenticate users against the LDAP infrastructure; LDAPS can be enabled for protected communications. The guide notes an important limitation: LDAP authentication is unavailable for SIA remote users using IPsec VPN, but LDAP remains a supported FortiSASE authentication source.

RADIUS (E) provides centralized remote authentication and supports PAP, CHAP, MS-CHAP, and MS-CHAPv2 authentication methods.

OIDC and TACACS+ are not identified as FortiSASE remote-user authentication sources in this course objective.

The correct answer is A. FortiSASE provides both API-based CASB and inline CASB. Fortinet describes FortiSASE Secure SaaS Access as using a dual-mode CASB architecture that combines inline inspection with out-of-band, API-based inspection. This provides visibility and control over SaaS usage while protecting both data in motion and data at rest.

Inline CASB operates directly in the traffic path between the endpoint and SaaS application. FortiSASE uses capabilities such as application control, web filtering, SSL deep inspection, and DLP to identify applications, enforce SaaS access controls, inspect traffic, and protect data in motion. The study guide specifically describes the inline component as recognizing SaaS application traffic and using protocol decoders and HTTP inspection to enforce controls.

The API-based or out-of-band CASB connects directly to supported cloud applications through APIs. Its principal role is inspecting and assessing data at rest that has already been stored in the SaaS service. The FortiSASE Enterprise material likewise confirms that FortiCASB provides cloud/API-based capabilities while FortiSASE simultaneously provides inline CASB through web filter and application control.

Therefore, B and C incorrectly limit FortiSASE to one CASB mode, while D incorrectly makes Security Fabric integration a prerequisite.

Study Guide Reference: SIA and SSA > Secure SaaS Access > Inline CASB and Out-of-Band CASB, pages 105–108.

The three documented work-from-anywhere challenges are inconsistent security, lack of visibility and control, and performance issues . Fortinet explains that users can receive different levels of protection depending on location and trust context, creating inconsistent security enforcement. The traditional architecture also produces limited visibility into remotely accessed SaaS traffic and corporate data, creating security blind spots. FortiSASE_25_Administrator_Stud… Performance is another challenge because traditional remote-access designs commonly backhaul internet and SaaS traffic through corporate VPN infrastructure, which can introduce latency and degrade the user experience. FortiSASE_25_Administrator_Stud… FortiSASE addresses these problems by delivering consistent cloud-based security inspection, centralized visibility and policy enforcement, and optimized access from distributed locations. Lack of raw bandwidth and remote internet connectivity themselves are not the three architectural challenges identified by the FortiSASE course material.

================

According to the SD-WAN 7.6 Core Administrator study guide and the FortiOS 7.6 Administration Guide, for the FortiGate SD-WAN engine to successfully steer traffic using SD-WAN rules, three fundamental configuration components must be in place. This is because the SD-WAN rule lookup occurs only after certain initial conditions are met in the packet flow:

Interfaces (Option C): You must first define the physical or logical interfaces (such as ISP links, LTE, or VPN tunnels) as SD-WAN members. These members are then typically grouped into SD-WAN Zones. Without designated member interfaces, there is no " pool " of links for the SD-WAN rules to select from.

Routing (Option D): For a packet to even be considered by the SD-WAN engine, there must be a matching route in the Forwarding Information Base (FIB). Usually, this is a static route where the destination is the network you want to reach, and the gateway interface is set to the SD-WAN virtual interface (or a specific SD-WAN zone). If there is no route pointing to SD-WAN, the FortiGate will use other routing table entries (like a standard static route) and bypass the SD-WAN rule-based steering logic entirely.

Firewall Policies (Option A): In FortiOS, no traffic is allowed to pass through the device unless a Firewall Policy permits it. To steer traffic, you must have a policy where the Incoming Interface is the internal network and the Outgoing Interface is the SD-WAN zone (or the virtual-wan-link). The SD-WAN rule selection happens during the " Dirty " session state, which requires a policy match to proceed with the session creation.

Why other options are incorrect:

Security Profiles (Option B): While mandatory for Application-level steering (to identify L7 signatures), basic SD-WAN steering based on IP addresses, ports, or ISDB objects does not require security profiles to be active.

Traffic Shaping (Option E): This is an optimization feature used to manage bandwidth once steering is already determined; it is not a prerequisite for the steering engine itself to function.

The selected performance SLA in the exhibit is Corp_HC , and the Latency view shows two configured latency criteria as horizontal threshold lines. Throughout the displayed 60-second interval, the green port1 latency remains below both thresholds, so port1 remains healthy against both Corp_HC latency criteria. Fortinet explains that the FortiGate GUI displays measured member performance and highlights when a member fails a configured SLA target; configured latency values can therefore be compared directly with measured latency. SD-WAN_7.6_Enterprise_Administr… Option A incorrectly associates the graph with HUB1_HC when Corp_HC is selected. Option B cannot be inferred merely because packet loss, latency, and jitter metrics are displayed; those metrics can be measured without all three being configured as SLA targets. Option D confuses the displayed failure/recovery threshold values of 5 with a 5% packet-loss SLA threshold .

================

A and D are correct. Fortinet ' s FortiSASE material identifies two fundamental prerequisites for agentless ZTNA/private application access: an SSO configuration for proxy users and an existing Secure Private Access (SPA) configuration. The Administrator Study Guide states explicitly that agentless support for private applications requires both an SPA configuration and a Secure Web Gateway SSO configuration.

Proxy user SSO (A) provides the identity-verification component. When an agentless user accesses the FortiSASE bookmark portal through a browser, the user must authenticate using SSO. The Enterprise Administrator workflow confirms that authentication occurs through FortiSASE proxy SSO user authentication before authorized application bookmarks are displayed.

SPA (D) provides connectivity from FortiSASE to the protected private applications. After authentication and policy evaluation, the application session is routed through FortiSASE SPA, which functions as the gateway for agentless ZTNA access.

B is incorrect because a FortiGate ZTNA access proxy is not itself a mandatory prerequisite for agentless ZTNA; SPA can be implemented through the supported private-access architecture. C is incorrect by definition: agentless ZTNA is designed for endpoints, including BYOD devices, that do not require FortiClient.

Study Guide Reference: SPA > Agentless ZTNA; Secure Private Access > Private Access for Agentless Users.

According to the FortiSASE 7.6 Administration Guide and the FCP - FortiSASE 24/25 Administrator curriculum, FortiSASE is designed with a hybrid deployment architecture to support various user and device requirements. It primarily operates in two modes:

Endpoint Mode (Agent-based): This mode requires the installation of FortiClient on the user ' s laptop or device. The agent establishes an " always-up " secure VPN tunnel to the nearest FortiSASE Point of Presence (PoP), providing full Secure Internet Access (SIA), Secure Private Access (SPA), and endpoint posture checks (ZTNA).

Secure Web Gateway (SWG) Mode (Agentless): This mode is used for users or devices where installing an agent is not feasible (e.g., unmanaged devices or Chromebooks). It relies on explicit web proxy settings or a PAC (Proxy Auto-Configuration) file to redirect web traffic (HTTP/HTTPS) to the SASE PoP for inspection.

Why other options are incorrect:

Option A: While it supports VPN, " VPN mode " is not the formal name of the deployment type; it is " Endpoint mode " .

Option C: FortiSASE is not limited to SWG; it is a full SSE (Security Service Edge) solution including FWaaS and ZTNA.

Option D: ZTNA is a capability within the platform, not a replacement for the overall endpoint or SWG functions.