At a minimum, which two configurations are required to enable captive portal services on FortiAuthenticator? (Choose two.)

To enable captive portal services on FortiAuthenticator, two fundamental components must be configured. First, a portal policy (B) is required. This policy acts as the central logic, linking a source (like a RADIUS client), the user-facing portal page, and the authentication rules. Second, at least one portal page, which provides the login interface for users, must be configured. This is what option (A) refers to, albeit with the potentially ambiguous term "pre-login service." In the context of FortiAuthenticator's configuration, the portal page itself is the primary service presented to the user before they are fully authenticated. Without both the portal page and the policy to govern its use, the captive portal service cannot function.

C. Configuring an external authentication portal: This is an alternative, not a minimum, configuration. FortiAuthenticator hosts the portal by default, and using an external one is not a basic requirement.

D. Configuring a RADIUS client: While a RADIUS client (e.g., a FortiGate) is essential for the entire solution to work, it is configured as a client of the portal service, not as a core component of the service itself. The question focuses on enabling the services on FortiAuthenticator.

1. FortiAuthenticator 6.4.0 Administration Guide

Page 101

Chapter "Portal services". This chapter outlines the components that constitute the portal services. It includes dedicated sections for "Portals" (the user-facing login page

aligning with option A) and "Policies" (option B). This structure separates the core service configuration from client configuration.

2. FortiAuthenticator 6.4.0 Administration Guide

Page 104

"Policies". The documentation for creating a portal policy explicitly states that you must select a "Portal" (the login page) and a "Source" (the RADIUS client). This confirms that both a portal and a policy are mandatory configurations to make the service active. The policy is what "enables" the service by tying the components together.

3. FortiAuthenticator 6.2 Study Guide

Page 167

"Captive Portal". The guide lists the main FortiAuthenticator components for a captive portal solution as: "The RADIUS client"

"The portal itself"

and "The portal policy". The question asks for the two components that enable the service

which are most directly the portal itself (A) and the policy (B).