NSE4_FGT-6.2 Exam Dumps - Fortinet NSE 4 - FortiOS 6.2

Configure split tunneling for content inspection.

Configure host restrictions by IP or MAC address.

Configure two-factor authentication using security certificates.

Configure SSL offloading to a content processor (FortiASIC).

Configure a client integrity check (host-check).

The all VDOM is not synchronized between the primary and secondary FortiGate devices.

The root VDOM is not synchronized between the primary and secondary FortiGate devices.

The global configuration is synchronized between the primary and secondary FortiGate devices.

The FortiGate devices have three VDOMs.

When a remote user accesses https://10.200.1.1:443, the FortiGate login page appears.

When a remote user accesses https://10.200.1.1:443, the FortiGate login page appears.

When a remote user accesses http: //10.200.1.1 :443, the FortiGate login page appears.

When a remote user accesses http: /110.200.1.1:443, the SSL VPN login page appears.

The settings are invalid. The administrator settings and the SSL VPN settings cannot use the same port.

Define the phase 1 parameters, without enabling IPsec interface mode

Define the phase 2 parameters.

Set the phase 2 encapsulation method to transport mode

Define at least one firewall policy, with the action set to IPsec.

Define a route to the remote network over the IPsec tunnel.

In aggressive mode, the remote peers are able to provide their peer IDs in the first message.

FortiGate is able to handle NATed connections only in aggressive mode.

FortiClient only supports aggressive mode.

Main mode does not support XAuth for user authentication.

Services defined in the firewall policy.

Incoming and outgoing interfaces

Highest to lowest priority defined in the firewall policy.

Lowest to highest policy ID number.

It limits the scope of application control to the browser-based technology category only.

It limits the scope of application control to scan application traffic based on application category only.

It limits the scope of application control to scan application traffic using parent signatures only

It limits the scope of application control to scan application traffic on DNS protocol only.

IP tool references must be removed from existing firewall policies before enabling central NAT.

Central NAT can be enabled or disabled from the CLI only.

Source NAT, using central NAT, requires at least one central SNAT policy.

Destination NAT, using central NAT, requires a VIP object as the destination address in a firewall.