Fortinet Updated FCSS_LED_AR-7.6 Exam Questions and Answers by yousif

The SSL-VPN configuration hasRequire Client Certificateenabled. When this is enabled, FortiOS performs two checks:

Normal user authentication(username/password or PKI user)

Additional client certificate check– the client certificatemust be signed by a CA that FortiGate trusts

FortiOS documentation for “SSL VPN with certificate authentication” states:

“The client certificate only needs to be signed by a known CA in order to pass authentication.”

“The CA certificate is the certificate that signed both the server certificate and the user certificate… The CA certificate is available to be imported on the FortiGate.”

The debug output shows key lines:

__quick_check_peer-CA does not match.

Issuer of cert depth 0 is not detected in CMDB.

This tells us:

FortiGatedoes see the user’s certificate,

Butcannot find the issuing CAin its local CA certificate store (“CMDB” = configuration database).

This means theCA that signed the user certificate has not been importedinto FortiGate.

Now evaluate the options:

A. Enable Redirect HTTP to SSL-VPN– affects only redirection from HTTP to HTTPS; it has nothing to do with certificate validation.

B. Import the CA that signed the SSL VPN Server Certificate– the server certificate is already working (the portal comes up) and its CA is not what the debug complains about; the error is about thepeer (user) certificate. Often the same CA signs both, but the failing check specifically says the issuer of the client cert is not in CMDB.

C. Set the user certificate as the Server Certificate– incorrect; server and client certificates serve different roles.

D. Import the CA that signed the user certificate to FortiGate– this directly addresses the debug error and aligns with the documented requirement that the CA which issued the user certificate must be known to FortiGate.

WithAD machine authenticationvia FortiAuthenticator:

When a machine successfully authenticates, FortiAuthenticator records:

Machine account / identity

MAC addressof the device

Associated IP and session info

To handle sleep/hibernation:

FortiAuthenticator keeps acache of authenticated MAC addressesfor a configured timeout.

When the device wakes up and sends traffic again, FortiAuthenticator/FSSO can still treat it as authenticated as long as its MAC is in cache, so access is maintained without forcing a full machine re-auth immediately.

This matches optionD.

A(guest VLAN) is not the standard behavior here.

B(WoL) is unrelated.

C(IP-based) would break as IPs can change; MAC-based caching is what’s used.

From the exhibits:

SSID “Guest”

Security mode:Open

Captive Portal: Enabled, portal typeAuthentication → External

External portal URL: https://fac.trainingad.training.lab/guest (FortiAuthenticator)

Exempt destinations/services:FortiAuthenticator and WindowsAD

Firewall policy

From theGuest interface/zonetoport1 (Internet)

Source user group:guest.portal(authenticated users)

The flow for anexternal captive portalis:

Client associates to theopen Guest SSID.

Client makes an HTTP(S) request.

FortiGate intercepts and redirects the client to theexternal portal.

Client must be able toreach FortiAuthenticator’s IP(and AD if the portal needs it)before authentication.

In this setup:

Theexempt destinationsetting tells the captive portal logicnot to require authenticationfor traffic going to FortiAuthenticator and WindowsAD.

However, there still must be a firewall policy that allows traffic from the Guest SSID subnet to those exempt destinations.

The existing firewall policy uses theguest.portal user groupas a source condition, which only matchesaftersuccessful portal authentication. Before login, the client has no user identity, so:

Traffic from the unauthenticated Guest client → FortiAuthenticator isnot matchedby that policy.

It hits theimplicit deny, so the browser never reaches the login page.

To fix this, the administrator must:

Create or modify a firewall policy thatallows traffic from the Guest SSID subnet/interface to FortiAuthenticator and WindowsAD without requiring user authentication.

That is exactly what optionDdescribes.

Why the others are wrong:

A. Change SSID security mode to WPA2-Enterprise– External captive portals are normally used withopenSSIDs; WPA2-Enterprise uses 802.1X, not captive portal.

B. Disable HTTPS redirection– Redirection is required so users are sent to the portal; disabling it doesn’t solve reachability.

C. Exclude FortiAuthenticator and Windows AD from filtering– They’re already listed asexempt destinationsin the SSID configuration; the missing piece is thefirewall policy, not the exemption.

The correct answer is D.

The LAN Edge 7.6 Architect study guide directly explains this exact behavior for SSIDs configured on FortiManager.

The study guide states:

“In central management mode, profiles are created and stored on FortiManager. An AP profile is distributed to a controller when at least one of its supported APs is assigned the profile and the device settings are installed. SSID profiles are delivered only when you select Manual in the SSID field.”

It further says:

“If you create an SSID profile centrally and configure all the AP profiles to be tunnel or bridge, the SSID profile is not delivered to FortiGate. FortiManager does not know which of the SSID profiles to distribute to which FortiGate.”

And the guide gives the exact fix:

“A manual SSID explicitly tells FortiManager which SSID profile to broadcast on the AP and, as a result, the required SSID profile is delivered to the controller.”

Another extract from the same section confirms:

“When you want to broadcast an SSID, you must configure the AP profile that is being used by the APs that are to transmit it... Manual: You can select a mix of SSIDs to broadcast.”

So in this scenario, the AP profile must be changed from Bridge or Tunnel to Manual, and then the required SSIDs must be explicitly selected.

Why the other options are incorrect:

A. Incorrect. The issue is not the AP platform. The study guide identifies the problem as SSID delivery and mapping from FortiManager to FortiGate, not AP hardware support

B. Incorrect. The study guide explicitly says Manual can be used to “select a mix of SSIDs to broadcast,” so a mix is supported when Manual is chosen

C. Incorrect. Transmit Power Mode affects RF behavior, not whether FortiManager delivers SSID profiles to FortiGate. The problem here is SSID assignment and profile distribution, not radio power.

Extra confirmation from FortiGate Cloud administration guidance:

“To configure the SSID that you created select Manual for SSIDs then select the SSID from the dialog.”

Final verified conclusion:

Because the SSIDs were created on FortiManager and are not being broadcast, the AP profile must use Manual in the SSIDs field and the intended SSIDs must be explicitly selected.

So the correct answer is D.