Fortinet FCSS_LED_AR-7.6 Exam Dumps - Actual Questions Answers

In FortiLink NAC for LAN Edge:

When a device first connects, it is placed into theonboarding VLAN.

NAC policies then classify the device (by MAC, OS, user, EMS tag, etc.).

If a NAC policy matches, the device may be moved to anaccess VLANorquarantine VLAN.

Ifno NAC policy matches, the device simplystays in the onboarding VLAN.

FortiOS / LAN Edge documentation describes the onboarding VLAN as thedefault VLAN for unknown or unclassified devices, until NAC policy evaluation moves them elsewhere.

Goal: enforce captive portal authentication overHTTPSfor guests.

On FortiGate/FortiAuthenticator captive portal setups:

HTTP redirectis used so that when a guest browses to any HTTP site, their request is redirected to theportal URL.

Theportal URLitself must beHTTPSif you want a secure login page.

FortiOS captive portal and firewall authentication guidelines recommend:

EnablingHTTP redirectso unauthenticated HTTP traffic is transparently sent to the portal.

Configuring theportal URL with HTTPS, often referencing a certificate on FortiGate or FortiAuthenticator.

Therefore:

A. Enable HTTP redirect in the user authentication settings.✔This ensures unauthenticated HTTP requests are redirected to the (now HTTPS) portal.

D. Update the captive portal URL to use HTTPS on FortiGate and FortiAuthenticator.✔This makes the login itself secure (TLS-protected).

Incorrect:

B– You don’t need a new SSID; the same SSID can use HTTPS portal.

C– Disabling HTTP admin access on the SSID doesn’t control the captive portal scheme; HTTPS enforcement is done by the portal configuration and redirect, not by admin-access flags.

The LAN Edge 7.6 Architect Study Guide explicitly confirms that during the ZTP process, after FortiGate retrieves the FortiManager address (via DHCP Option 240 for IP address or Option 241 for FQDN), it contacts FortiManager to initiate a secure tunnel on TCP port 541. If that port is unreachable — due to firewall rules, routing issues, or misconfiguration — the tunnel cannot be established, and registration fails.

The guide also confirms in the device registration section: " During device registration, FortiManager and FortiGate create a secure tunnel on TCP port 541. The tunnel is used for checking device status and configuration, as well as configuration installation. "

Why the other options are wrong:

A is incorrect — ZTP is designed specifically to be automated and does not require manual acceptance for the initial tunnel establishment in the standard ZTP flow.

B is incorrect — ZTP operates over the network (LAN/WAN), not via console cable; it is a network-based provisioning process.

C is incorrect — ZTP ' s entire purpose is to allow devices to be deployed without a pre-loaded configuration on-site; the configuration is pushed by FortiManager after registration.