FCP-FGT-AD domain - 20% of the exam

VPN

VPN is 20% of the FCP-FGT-AD exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

66
Practice questions
2
Objectives
33
Medium
33
Hard

Where people go wrong

  • Giving web mode the powers of tunnel mode

    The wrong answers hand tunnel-mode behaviour to web mode, or the reverse. Web mode is clientless: the FortiGate acts as a reverse proxy and presents bookmarked applications in the browser, and the endpoint never receives a tunnel IP or general network access. Tunnel mode needs FortiClient, builds a virtual adapter with an address from the tunnel pool and carries any IP protocol, including raw UDP and dynamic TCP ports. Bookmarks cannot carry a thick client, and tunnel mode cannot run on a locked-down kiosk.

    See it in a sample question
  • Misreading what a full tunnel does

    The wrong answers describe split tunnelling enabled when the stem says disabled, or blame a full tunnel's side effects on double encryption, per-site renegotiation, DNS, a firewall policy or a disabled adapter. With split tunnelling disabled, a default route over the virtual interface sends all traffic, including internet browsing, to the FortiGate. That one route explains the inspection, the saturated WAN link and the unreachable home printer. With it enabled, only the portal's routing addresses enter the tunnel and the rest leaves by the client's own gateway.

    See it in a sample question
  • Placing a parameter in the wrong IKE phase

    The wrong options move a setting into the other phase. Phase 1 agrees the peer authentication method, the Diffie-Hellman group and the IKE SA lifetime, so a pre-shared key mismatch or non-overlapping groups stop the tunnel before phase 2. Phase 2 agrees the quick-mode selectors and the IPsec SA encryption and lifetime, and Perfect Forward Secrecy is a phase 2 setting that adds a fresh Diffie-Hellman exchange at each rekey.

    See it in a sample question
  • Crediting identity and liveness settings with per-spoke addressing

    Options such as aggressive mode, peer ID matching, dead peer detection and dynamic DNS sound relevant to a dial-up hub, but none of them gives a spoke its own address or interface. IKE mode config makes the hub assign each spoke an overlay address, and net-device makes the hub create a separate virtual tunnel interface per spoke. Those two are what let the hub route to spokes individually and run dynamic routing.

    See it in a sample question
  • Deciding the portal anywhere but the authentication rules

    The wrong answers put the group-to-portal binding in the portal itself, the firewall policy, the LDAP server or FortiClient, or decide it by portal name, realm, IP pool or permissiveness. The binding lives in the SSL VPN settings authentication rules, which pair each user group with a portal. The rules are evaluated top down and the first matching group wins, so a catch-all placed too high takes the user. A user who matches no rule receives the portal named in the default portal setting rather than being refused.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleVPNmedium

A contractor must reach a single internal web application from an unmanaged kiosk where no software can be installed and no administrator rights exist. The administrator wants the FortiGate to broker that one application over HTTPS to the browser. Which SSL VPN mode is fit for this constraint, and why?

  • AWeb mode, because it acts as a reverse proxy that renders bookmarked applications inside the browser with no client software on the endpoint. Correct
  • BTunnel mode, because it is the only mode that can present the internal application without installing FortiClient on the kiosk.
  • CTunnel mode, because the portal can be configured to drop into a browser-only profile that suppresses the FortiClient download requirement.
  • DWeb mode, because it installs a lightweight signed ActiveX agent that gives the kiosk a routed IP for that one application.
Web mode is the clientless, reverse-proxy SSL VPN choice for browser-only access to published applications, with no endpoint software required. Web mode terminates the user session at the FortiGate portal and reverse-proxies each bookmarked resource back to the browser, so no agent or virtual adapter is created on the endpoint. That is what makes it usable on an unmanaged device where nothing can be installed.

Why A is correct: Correct: web mode is clientless, brokering each published resource through the FortiGate as a reverse proxy and presenting it in the browser, which exactly fits an unmanaged kiosk with no install rights.

Why B is wrong: Tempting because tunnel mode is the better-known SSL VPN mode, but it is wrong here: tunnel mode requires the FortiClient agent or the standalone tunnel client and therefore cannot run on a locked-down kiosk.

Why C is wrong: Tempting because portals do have toggles, but there is no portal option that turns tunnel mode into a clientless browser session; tunnel mode always needs the tunnel client to build the virtual adapter.

Why D is wrong: Tempting because older clientless solutions used browser plugins, but FortiOS web mode does not assign a routed IP and does not require an installed agent; it proxies the application without any endpoint software.

Free sampleVPNmedium

A security team must inspect and log every remote worker's internet activity, including general web browsing, while the worker is connected over SSL VPN tunnel mode. Which portal configuration most directly supports this requirement?

  • AEnable split tunnelling and add the public internet ranges as the portal routing addresses so browsing stays local but is still logged.
  • BSwitch the portal to web mode so all browsing is proxied through the FortiGate clientless portal and logged there.
  • CDisable split tunnelling on the portal so the client routes all traffic, including internet-bound traffic, through the FortiGate where firewall policies and security profiles apply. Correct
  • DLeave split tunnelling enabled and rely on FortiClient endpoint logging to capture the internet activity locally on each device.
Disabling split tunnelling routes a remote user's internet traffic through the FortiGate, enabling central inspection and logging at the cost of added link load. Internet traffic can only be inspected and logged by FortiGate security profiles if it actually traverses the FortiGate. A full tunnel (split tunnelling disabled) forces that traffic through the device, which is the security trade-off for the extra bandwidth it consumes.

Why A is wrong: Tempting because adding routing addresses controls what enters the tunnel, but routing internet ranges over a split tunnel is unworkable and split tunnelling sends browsing out the local gateway, bypassing inspection.

Why B is wrong: Tempting because web mode does proxy through the FortiGate, but it only reaches bookmarked internal resources, not the user's general internet browsing.

Why C is correct: Correct: a full tunnel forces internet traffic back through the FortiGate, where outbound policies and UTM profiles can inspect and log it.

Why D is wrong: Tempting because endpoint telemetry exists, but with split tunnelling enabled the internet traffic never reaches the FortiGate, so its policies and security profiles cannot inspect it.

Free sampleVPNhard

An administrator is finalising the IKE phase 2 configuration of a route-based IPsec tunnel between two FortiGates and wants to be sure the quick-mode negotiation will succeed and that the data keys gain forward secrecy. Which statements about phase 2 quick mode and Perfect Forward Secrecy on FortiGate are correct? Select TWO.

  • APhase 2 inherits the phase 1 Diffie-Hellman result automatically, so enabling Perfect Forward Secrecy is unnecessary and has no effect on how the data keys are derived.
  • BThe phase 2 quick-mode selectors, expressed as source and destination proxy IDs, must be compatible on both peers or the IPsec security association will not install even though phase 1 is up. Correct
  • CQuick-mode selectors are negotiated during phase 1 alongside the authentication method, so any selector change must be made on the phase 1 page for it to take effect.
  • DWhen Perfect Forward Secrecy is enabled on phase 2, FortiGate performs a fresh Diffie-Hellman exchange at each IPsec SA rekey so that new session keys are not derived from the phase 1 keying material. Correct
  • EEnabling Perfect Forward Secrecy replaces the need for a phase 2 IPsec SA lifetime, because the fresh Diffie-Hellman exchange keeps the same data keys valid indefinitely.
Phase 2 needs compatible quick-mode selectors to install the IPsec SA, and PFS adds a fresh Diffie-Hellman exchange at each rekey to give the data keys forward secrecy. The IPsec SA is built in quick mode from a matching proxy ID pair, so incompatible selectors block installation even with phase 1 up, and enabling PFS makes FortiGate run a new Diffie-Hellman exchange at every phase 2 rekey so compromise of one key set cannot expose other sessions, while the SA lifetime still drives those rekeys.

Why A is wrong: This is wrong because the point of PFS is to run an additional DH exchange in phase 2; without it the data keys do derive from phase 1 material, which PFS specifically prevents.

Why B is correct: Correct: the proxy ID pair agreed in quick mode must match between peers, otherwise no IPsec SA is created despite a healthy phase 1.

Why C is wrong: Selectors belong to phase 2 quick mode, not phase 1, so this misplaces the setting and the resulting edit would target the wrong configuration.

Why D is correct: Correct: PFS forces a new DH exchange on every phase 2 rekey, decoupling each set of data keys from earlier key material and from the IKE SA secret.

Why E is wrong: PFS does not remove the SA lifetime; the lifetime still triggers rekeys, and PFS only changes how the new keys are derived at each rekey, so the keys are not valid indefinitely.

Free sampleVPNhard

An administrator builds a hub-and-spoke IPsec design where a single dial-up phase 1 on the hub terminates many spokes. Each spoke must be reachable individually so the hub can push spoke-specific routes and run dynamic routing across the overlay. Which phase 1 setting on the hub is essential for the hub to distinguish and address each connected spoke separately?

  • ASet the hub phase 1 type to Dynamic DNS so each spoke registers its public address before the tunnel forms.
  • BEnable IKE mode config or assign per-spoke tunnel addresses so each dial-up child gets its own interface address the hub can route to individually. Correct
  • CEnable Add Route on the hub phase 1 so a static route to each spoke subnet is created automatically when the spoke connects.
  • DSet the hub phase 1 peer ID to accept any peer ID so every spoke shares one common tunnel endpoint on the hub.
Recognise that per-spoke overlay addressing on a dial-up hub phase 1 is what makes each spoke individually addressable for routing. A dial-up phase 1 aggregates many spokes, so without unique overlay addresses the hub cannot tell spokes apart at layer 3. Assigning each spoke its own tunnel address through mode config produces distinct addressable children, enabling spoke-specific static routes and dynamic routing adjacencies over the hub-and-spoke overlay.

Why A is wrong: Dynamic DNS resolves a changing public IP to a name for a static-peer tunnel; it does not let one dial-up phase 1 individualise many concurrent spokes, so it does not meet the requirement.

Why B is correct: Giving each dial-up spoke a unique overlay address, typically through mode config, creates a distinct addressable child the hub can target with spoke-specific routes and form dynamic routing adjacencies over, which is exactly what the design needs.

Why C is wrong: Auto-added routes can populate spoke subnets, but they do not give the hub a per-spoke addressable tunnel interface, and they conflict with running a dynamic routing protocol over the overlay as the scenario requires.

Why D is wrong: Accept-any peer ID lets heterogeneous spokes authenticate against one dial-up phase 1, but sharing one endpoint is the opposite of addressing spokes individually, so it cannot support per-spoke routing.

Free sampleVPNmedium

An SSL VPN tunnel-mode deployment authenticates users against a remote LDAP server. The administrator wants members of the LDAP group Sales to land on a portal with split tunnelling, and members of the group Admins to land on a full-access portal, all from the same SSL VPN configuration. Where is the mapping between an authenticated group and the portal it receives defined?

  • AInside each portal definition, by listing the permitted user groups within the portal object
  • BIn the SSL VPN settings authentication or portal mapping table, which pairs each user group with a portal Correct
  • CIn the firewall policy that allows the ssl.root interface, by selecting the source user group
  • DIn the LDAP server object, by tagging each group with the portal name as an attribute
SSL VPN settings contain an authentication and portal mapping table that pairs each authenticated user group with the portal it should receive. FortiOS evaluates the portal mapping list during login, matches the user's group to its configured portal, and applies that portal's policies such as split tunnelling or full access; portals themselves do not store their member groups.

Why A is wrong: It feels natural that the portal would name its own users, but FortiOS portals do not contain the group list; the binding between group and portal is made elsewhere in the SSL VPN settings.

Why B is correct: Correct. The SSL VPN settings include an authentication and portal mapping list where each authenticated user group is matched to the specific portal it should receive, with a realm or default catch-all entry.

Why C is wrong: The policy does reference user groups for access control, but it grants or denies traffic and does not choose which portal a given group is assigned.

Why D is wrong: This sounds plausible because attributes drive group membership, but FortiOS reads LDAP only for identity and never stores portal assignments on the directory server.

Other domains in this exam

See also the FCP-FGT-AD cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Fortinet. Original, blueprint-aligned practice material only.