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

The first server provided to FortiGate when it performed a DNS query looking for a list of rating servers, was 121.111.236.179.

There is a natural correlation between the value in the FortiGuard-requests field and the value in the Weight field.

FortiGate used 64.26.151.37 as the initial server to validate its contract.

Servers with a negative TZ value are less preferred for rating requests.

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.

mschap

pap

mschap2

eap

Set snat-route-change to enable.

Set the priority of the static default route using port2 to 1.

Set preserve-session-route to enable.

Set the priority of the static default route using port1 to 10.

FortiTelemetry and Neighbor Discovery both operate using TCP.

The default port for Neighbor Discovery can be modified.

FortiTelemetry must be manually enabled on the FortiGate interface.

By default, the downstream FortiGate establishes a connection with the upstream FortiGate using TCP port 8013.

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.

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 advertised prefix of 10.20.30.0'24 was configured using the network command.

The first four prefixes are being advertised using a legacy route advertisement.

The advertised prefix of 10.20.30.0'24 is being advertised through the redistribution of another routing protocol.

The output shows all prefixes advertised by all neighbors as well as the local router.

Phase 2 drops but Phase 1 is up.

Dead Peer Detection is not receiving its acknowledge packet.

The tunnel drops during rekey negotiation.

The tunnel drops after the timer expires.

Return traffic to the initiator is sent to 10.1.0.1.

Return traffic to the initiator is sent lo 10.200.1.254.

It is an ICMP session from 10.1.10.10 to 10.200.1.1.

It is an ICMP session from 10.1.10.1 to 10.200.5.1.

The miglogd daemon is running on CPU core ID 0.

The diagnose sys top command has been running for 18 minutes.

The miglogd daemon would be on top of the list, if the administrator pressed m on the keyboard.

The cmdbsvr process is occupying 2.4% of the total user memory space.

If the neweli daemon continues to be in the R state, it will need to be manually restarted.

FortiGate blocks the connection as an invalid URL.

Based on the URL Filter configuration, FortiGate allows the connection.

FortiGate blocks the connection, based on the FortiGuard category-based filter configuration.

Based on the Web Content filter configuration, access to www.dropbox.com would be exempted.

diagnose sniffer packet any 'udp port 500'

diagnose sniffer packet any 'lp proto 50'

diagnose sniffer packet any 'udp port 4500'

diagnose sniffer packet any 'ah'

A batter route to the 8.8.8.8/32 network exists in the routing table.

FGT-B is configured with a prefix list denying the 8.8.8.8/32 network to be injected into the routing table.

The administrator has misconfigured redistribution of routes on FGT-A.

FGT-8 is configured with a distribution list denying the 8.8.8.8/32 network to be injected into the routing table.

Ensure the user logs in using 'John Smith' not 'jsmith'.

Ensure the user is providing the correct user credentials.

Ensure the user is a member of at least one AD group to ensure step 4 of the LDAP authentication process is successful.

Ensure the account is active.

The TCP session has been successfully established.

The session was initiated from an authenticated user.

The session is being inspected using flow inspection.

The session is being offloaded.