FCSS_NST_SE-7.4 FCSS - Network Security 7.4 Support Engineer Questions and Answers

The total slab size of the sctp_session slab is 0 kB and is associated with the user space.

The total slab size of the ip_session slab is 3600 kB and is associated with the user space.

The total slab size of the ip6_session slab is 1300 kB and is associated with the kernel.

The total slab size of the tcp_session slab is 7500 kB and is associated with the kernel.

The local FortiGate has at least one interface that participates in a broadcast network.

The local FortiGate has at least one interface that participates in a point-to-point network.

The local FortiGate is the DR.

Neighbor 0.0.0.18 is the designated router (DR).

The heartbeat messages can be seen using the command diagnose debug authd fsso list.

The heartbeat messages can be seen in the collector agent logs.

The heartbeat messages can be seen on FortiGate using the real-lime FSSO debug.

The heartbeat messages must be manually enabled on FortiGate.

mschap

pap

mschap2

eap

The workstation with IP 10.124.2.90 will be polled frequently using TCP port 445 to see if the user is still logged on.

The logon event can be seen on the collector agent installed on Windows.

FSSO is using DC agent mode to detect logon events.

FSSO is using agentless polling mode to detect logon events.

You can configure automation stitches on any FortiGate device in a Security Fabric environment.

You can configure automation stitches to execute actions sequentially by taking parameters from previous actions as input for the current action.

You can set an automation stitch configured to execute actions in parallel to insert a specific delay between actions.

You can create automation stitches to run diagnostic commands and attach the results to an email message when CPU or memory usage exceeds specified thresholds.

Both IKEv1 and IKEv2 share the feature of asymmetric authentication.

IKEv1 and IKEv2 have enough of the header format in common that both versions can run over the same UDP port.

IKEv1 and IKEv2 use same TCP port but run on different UDP ports.

IKEv1 and IKEv2 share the concept of phase1 and phase2.

The local ForliGate has received one prefix from BGP neighbor 100.64.1.254.

The TCP connection with BGP neighbor 100.64.2.254 was successful.

The local FortiGate has received 18 packets from a BGP neighbor.

The local FortiGate is still calculating the prefixes received from BGP neighbor 100.64.2.264

The egress interface associated with static route 8.8.8.8/32 is administratively up.

The default static route through 10.200.1.254 is not in the forwarding information base.

The default static route through port2 is in the forwarding information base.

The BGP route to 10.0.4.0/24 is not in the forwarding information base.

Remote registry is not running on the workstation.

The user's status shows as "not verified" in the collector agent.

DNS resolution is unable to resolve the workstation name.

The FortiGate firmware version is not compatible with that of the collector agent.

A firewall is blocking traffic to port 139 and 445.

The secondary device has this session synchronized; however, because application control is applied, the session is marked dirty and has to be re-evaluated after failover.

Traffic for this session continues to be permitted on the new primary device after failover, without requiring the client to restart the session with the server.

The session will be removed from the session table of the secondary device because of the presence of allowed error packets, which will force the client to restart the session with the server.

The session state is preserved but the kernel will need to re-evaluate the session because NAT was applied.

IKE_SA_INIT

INFORMATIONAL

CREATE_CHILD_SA

IKE_Auth

FortiGate uses the SNI from the user's web browser.

FortiGate closes the connection because this represents an invalid SSL/TLS configuration.

FortiGate uses the first entry listed in the SAN field in the server certificate.

FortiGate uses theCN information from the Subject field in the server certificate.

Change to aggressive mode on both VPNs.

Enable XAuth on both VPNs.

Use different pre-shared keys on both VPNs.

Set up specific peer IDs on both VPNs.

Change the priority of the port! static route to 11.

Change the priority of the port2 static route to 5.

Configure unset snat-route-change to return it to the default setting.

Configure set snat-route-change enable.

IKE_Req_INIT

Create_CHILD_SA

IKE_Auth

IKE_SA_INIT