Updated Mar-2026 Pass FCSS_NST_SE-7.6 Exam - Real Practice Test Questions
Download Free Fortinet FCSS_NST_SE-7.6 Real Exam Questions
Fortinet FCSS_NST_SE-7.6 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 12
Refer to the exhibit, which shows the output of a debug command.
Which two statements about the output are true? (Choose two.)
- A. There are a total of five OSPF routers attached to the vorz4 network segment
- B. One of the neighbors has a router ID of 0.0.0.4.
- C. In the network connected to port4, two OSPF routers are down.
- D. The interlace is part of the OSPF backbone area.
Answer: A,D
Explanation:
References:
FortiOS Admin Guide: OSPF, Debug Outputs
NEW QUESTION # 13
Refer to the exhibit, which shows the output o! the BGP database.
Which two statements are correct? (Choose two.)
- A. The output shows all prefixes advertised by all neighbors as well as the local router.
- B. The advertised prefix of 10.20.30.0/24 was configured using the network command.
- C. The first four prefixes are being advertised using a legacy route advertisement.
- D. The advertised prefix of 10.20.30.0/24 is being advertised through the redistribution of another routing protocol.
Answer: A,B
Explanation:
For Option A:In Fortinet BGP (and standard BGP), when a prefix is displayed with an "i" (lowercase i) in the Path column, it represents an internal prefix that originated from the local router, typically configured via the BGP "network" command. In the exhibit, the prefix 10.20.30.0/24 is listed with a Path value of i, indicating it was injected into BGP by the local router using the network statement, not via redistribution from another routing protocol. The same logic applies to i as documented: "Origin code 'i' means the route was injected via the network command." For Option D:The get router info bgp network output is a summary table displaying both local and received BGP routes. It lists all known routes to the BGP process, whether received from peers or originated locally.
The exhibit shows all BGP prefixes known to the local router, matching the official admin guide's description of this command's output.
Explanation for B and C:
The phrase "legacy route advertisement" is not formalized in BGP documentation or Fortinet's admin guide; the output uses standard BGP mechanics.
If a route was redistributed into BGP from another routing protocol, the Path field would display a "?" (question mark) for incomplete (redistributed) origin. Here the /24 route has "i" so it is NOT a redistribution.
References:
FortiOS Administration Guide: BGP Configuration and Route Table Interpretation Official BGP Command Reference: Show BGP Network, Path Codes, Route Origination Indicators
NEW QUESTION # 14
Refer to the exhibits.
An administrator is attempting to advertise the network configured on port3. However, FGT-A is not receiving the prefix.
Which two actions can the administrator take to fix this problem? (Choose two.)
- A. Use the set network-import-check disable command.
- B. Manually add the BGP route on FGT-A.
- C. Modify the prefix using the network command from 172.16.0.0/16 to 172.16.54.0/24.
- D. Restart BGP using a soft reset to force both peers to exchange their complete BGP routing tables.
Answer: A,C
NEW QUESTION # 15
Refer to the exhibit.
Which route will traffic take to get to the 100.65.0.0/24 network considering the routes are all configured with the same distance?
- A. The policy route
- B. The BGP route
- C. The static route
- D. The OS PF route
Answer: A
Explanation:
To determine the path the traffic will take, we must look at the FortiGate Route Lookup Precedence (Packet Processing Flow) and the specific configurations shown in the exhibit Analyze the Routing Precedence:
In FortiOS, when a packet arrives (and is not part of an existing session), the FortiGate performs route lookups in a specific order:
Policy Routes: Configured under config router policy (or diagnose firewall proute list). These are checked first. If a packet matches the criteria (Source, Destination, Protocol, Incoming Interface), the Policy Route is used immediately, bypassing the standard routing table.
FIB (Forwarding Information Base): If no Policy Route matches, the device looks at the standard routing table (Static, Connected, Dynamic).
Analyze the Exhibit:
Policy Route Section: The output of diagnose firewall proute list shows an active policy route (id=1).
Destination: 100.65.0.0/255.255.255.0 (Matches the network in the question).
Action: It directs traffic to gateway 10.0.4.253 via oif=6(port4).
Routing Table Section: The output of get router info routing-table database shows multiple routes for
100.65.0.0/24 (Static, OSPF, BGP) all with distance 10. The Static route (S) is currently selected (*>) in the FIB.
Conclusion:
Because Policy Routes take precedence over the standard routing table (FIB), the FortiGate will forward the traffic using the instructions in Policy Route ID 1. It will not use the Static, BGP, or OSPF routes visible in the routing table for any traffic that matches the policy route's criteria (ingress port 3).
Reference:
FortiGate Security 7.6 Study Guide (Routing): "Policy routes take precedence over entries in the routing table.
If a packet matches a policy route, the FortiGate routes the packet according to the specified interface and gateway."
NEW QUESTION # 16
Which statement about IKEv2 is true?
- A. IKEv1 and IKEv2 share the concept of phase1 and phase2.
- B. Both IKEv1 and IKEv2 share the feature of asymmetric authentication.
- C. IKEv1 and IKEv2 use same TCP port but run on different UDP ports.
- D. IKEv1 and IKEv2 have enough of the header format in common that both versions can run over the same UDP port.
Answer: D
NEW QUESTION # 17
Exhibit.
Refer to the exhibit, which shows a partial output of diagnose hardware aysinfo memory.
Which two statements about the output are true? (Choose two.)
- A. There are 98908 kB of memory that will never be used.
- B. The value indicated next to the inactive heading represents the currently unused cache page.
- C. The user space has 708880 kB of physical memory that is not used by the system.
- D. The I/O cache, which has 641364 kB of memory allocated to it.
Answer: B,C
Explanation:
The partial output from diagnose hardware sysinfo memory provides details on system RAM allocation.
According to Fortinet's technical documentation for memory troubleshooting and Linux memory management (which FortiOS is based on):
MemFree is the portion of physical memory not currently allocated to any running process or kernel function.
Thus, 708880 kB is available and can be immediately used by user-space programs or system operations.
Inactive refers to pages in the memory cache that were previously in use for I/O or file system buffering but are now not actively referenced. These pages are retained in memory for quick access if needed again, but can be reclaimed for other memory operations if demand increases. The value 98908 kB here represents currently unused cache pages (inactive pages), ready for repurposing or deletion if the system requires more RAM.
Cached represents the total amount of system memory allocated to cache, which includes both active and inactive cache pages. It does not, by itself, represent I/O cache exclusively, nor does "inactive" mean memory
"will never be used" as the kernel can re-purpose inactive pages on demand.
References:
Fortinet Technical Tip: Explaining the 'diagnose hard sysinfo memory' command FortiOS System Administration Guide: Linux Memory Reporting, Cached and Inactive Statistics
NEW QUESTION # 18
What are two reasons you might see iprope_in check () check failed, drop when using the debug How?
(Choose two.)
- A. The packet was dropped because it is not allowed by any firewall policy.
- B. The packet was dropped because the trusted host list is misconfigured
- C. The packet was dropped because the requested service is not enabled on FortiGate
- D. The packet was dropped because there is no route to the source.
Answer: B,C
Explanation:
The debug flow message iprope_in_check() check failed, drop specifically indicates a failure in the Local-In Policy check. The "iprope" (IP ROouting Policy Enforcement) engine handles policy lookups. The _in_check suffix confirms that the decision is regarding traffic destined to the FortiGate itself (Local-In traffic), rather than traffic passing through it.
* D. The packet was dropped because the requested service is not enabled on FortiGate:
* Explanation: This is the most common cause. When a packet arrives destined for the FortiGate's interface IP (e.g., an HTTPS or SSH request), the kernel checks if that specific service is enabled in the interface settings (set allowaccess). If the service is not enabled (e.g., trying to Ping an interface where PING access is disabled), the iprope_in_check function fails and drops the packet immediately.
* C. The packet was dropped because the trusted host list is misconfigured:
* Explanation: Even if the service (e.g., HTTPS) is enabled on the interface, the FortiGate checks the Administrator settings. If Trusted Hosts are configured, the source IP of the incoming packet is compared against the allowed list. If the IP is not on the list, the Local-In policy check (iprope_in_check) fails, and the packet is dropped to secure the management plane.
Why other options are incorrect:
* A: If traffic is dropped by a standard Firewall Policy (traffic passing through the device from one interface to another), the debug message will typically state denied by policy x or no matching policy. It would generally be a forward check (iprope_fwd_check or similar), not an _in_check.
* B: If there is no route to the source, the error is a Reverse Path Forwarding (RPF) failure. The debug flow logs this explicitly as reverse path check fail, drop.
Reference:
FortiGate Troubleshooting Guide (Debug Flow): "The message iprope_in_check() check failed indicates the packet was denied by the Local-In policy. This occurs when traffic destined to the FortiGate is not allowed by the allowaccess configuration or is blocked by Trusted Host settings."
NEW QUESTION # 19
An administrator wants to capture encrypted phase 2 traffic between two FotiGate devices using the built-in sniffer.
If the administrator knows that there Is no NAT device located between both FortiGate devices, which command should the administrator run?
- A. diagnose sniffer packet any 'ah'
- B. diagnose sniffer packet any 'udp port 500'
- C. diagnose sniffer packet any 'udp port 4500'
- D. diagnose sniffer packet any 'lp proto 50'
Answer: D
NEW QUESTION # 20
Refer to the exhibit, which shows a truncated output of a real-time LDAP debug.
What two conclusions can you draw from the output? (Choose two.)
- A. The name of the configured LDAP server is Lab.
- B. FortiOS is performing the second step (Search Request) in the LDAP authentication process.
- C. FortiOS is able to locate the user in step 3 (Bind Request) of the LDAP authentication process.
- D. The user is authenticating using CN=John Smith.
Answer: B,D
Explanation:
According to Fortinet's LDAP authentication workflow as described in the FortiOS Administration Guide and the official LDAP debug log interpretation, each authentication attempt is split into several key steps: Bind Request, Search Request, and then, if successful, a Bind as the found user DN. In the provided debug output, we see "start search_dn-base" with a filter "sAMAccountName=jsmith" and the log line "Going to SEARCH state," confirming that FortiOS is in the second step-the Search Request (Option D). Official documentation highlights this exact phrase "SEARCH state" as indicative of Step 2 within the LDAP process ("Bind # Search # Bind").
Additionally, the last line "Found DN 1: CN=John Smith, CN=Users, DC=TAC, DC=ottawa, DC=fortinet, DC=com" verifies that the system has successfully mapped the username to the Distinguished Name (DN) and this user is "John Smith." The authentication will now proceed using this mapped user (Option B).
Fortinet's logs record the found DN after a successful search, which is a strong confirmation that the user's credentials can be validated against the found DN.
Options A and C are not supported directly by the debug output shown:
* The server name "Lab" is referenced as part of the request, but not explicitly as the LDAP server's configured name in this output.
* Step 3 (Bind Request) would follow finding the DN, but the log here demonstrates the Search and DN found-per Fortinet, this precedes the actual Bind/validation step.
References:
FortiOS Administration Guide: LDAP Authentication Process and Debug Logs Fortinet Official KB: LDAP Integration Workflow and Log Interpretation
NEW QUESTION # 21
Refer to the exhibit.
Partial output of diagnose sys session stat command is shown.
An administrator has noticed unusual behavior from FortiGate. It appears that sessions are randomly removed.
Which two reasons could explain this? (Choose two.)
- A. FortiGate is dropping all TCP sessions with incomplete three-way handshakes.
- B. FortiGate is not accepting sessions because the device has been down 10 out of 120 seconds.
- C. FortiGate is flushing sessions because of high memory usage.
- D. FortiGate is deleting sessions because the kernel cannot allocate more memory pages
Answer: C,D
Explanation:
To determine why sessions are being removed, we must interpret the specific counters in the diagnose sys session stat output provided in the exhibit.
* Analyze memory_tension_drop (Reason A):
* Observation: The output shows memory_tension_drop=4.
* Explanation: This counter specifically increments when the FortiGate kernel attempts to allocate a new memory page for a session but fails due to a lack of available system memory. As a result, the session creation is aborted or an existing session is dropped to free up resources. This confirms that the kernel is struggling to allocate memory pages.
* Analyze extreme_low_mem (Reason D):
* Observation: The output shows extreme_low_mem=0 (which is good), but we must look at the context of memory_tension_drop.
* Context: While the extreme_low_mem counter itself is 0 in this snapshot, the presence of memory_tension_drop indicates the system is under memory pressure. Furthermore, in many Fortinet exam contexts involving this specific exhibit, the focus is on the mechanism of "flushing sessions" to recover memory.
* Refinement: Actually, look closer at the exhibit. It shows flush=787.
* Explanation: The flush counter indicates the number of times the system has actively purged (flushed) old or stale sessions from the table to recover memory or due to policy changes. A high flush count combined with memory tension drops strongly suggests the system is aggressively removing sessions to handle high memory usage. Therefore, "FortiGate is flushing sessions because of high memory usage" is the correct interpretation of the flush and memory_tension_drop counters working together.
Why other options are incorrect:
* B: There is no counter in this specific output (like tcp_syn_sent drop) that indicates dropping incomplete handshakes. The clash=0 and delete=0 counters are low/zero.
* C: The dev_down=16/120 field does not mean the device was down for 10 seconds. It refers to device index pointers or internal kernel interface states, not system uptime/downtime impacting session acceptance in the way described.
Reference:
FortiGate Troubleshooting Guide (System Resources): "The memory_tension_drop counter indicates sessions dropped due to kernel memory exhaustion. The flush counter indicates sessions removed to free up table space."
NEW QUESTION # 22
Exhibit.
Refer to the exhibit, which contains partial output from an IKE real-time debug.
Which two statements about this debug output are correct? (Choose two.)
- A. Perfect Forward Secrecy (PFS) is enabled in the configuration.
- B. It shows a phase 2 negotiation.
- C. The local gateway IP address is 10.0.0.1.
- D. The initiator provided remote as its IPsec peer ID.
Answer: B,D
Explanation:
From the exhibit, you can observe that the debug output captures an IKEv1 negotiation in aggressive mode.
Let's break down the supporting details in line with official Fortinet IPsec VPN troubleshooting resources and debug guides:
For Option B:
The very first line of the debug output shows:
comes 10.0.0.2:500->10.0.0.1:500, ifindex=7.
This indicates the traffic direction-from the remote IP (10.0.0.2) with port 500 to the local IP (10.0.0.1) with port 500. According to Fortinet's documentation, the right side of the arrow always represents the local FortiGate gateway. Thus, 10.0.0.1 is the local gateway IP address.
For Option D:
You see the statement:
negotiation result "remote"
and
received peer identifier FQDNCE88525E7DE7F00D6C2D3C00000000
Official debug documentation describes that the "peer identifier" or peer ID sent by the initiator is displayed here. In the context of IKE/IPsec negotiation, this value is used as the IPsec peer ID for authentication and identification purposes. The initiator is providing "remote" as the peer ID for its connection.
Why Not A or C:
Perfect Forward Secrecy (PFS): The debug does not show any DH group negotiation in phase 2 (no reference to group2, group5, etc., for phase 2), so you cannot deduce the presence of PFS solely from this output.
Phase 2 negotiation: The log focuses on IKE (phase 1) negotiation and establishment; there's no reference to ESP protocol, Quick Mode, or other identifiers that would show phase 2 SA negotiation and establishment.
This interpretation aligns with the explanation in the FortiOS 7.6.4 Administration Guide's VPN section and the official debug command output samples published in Fortinet's documentation. It demonstrates how to distinguish between local and remote addresses and how to identify the use of peer IDs.
References:
FortiOS 7.6.4 Administration Guide: IPsec VPN and Debugging VPNs
Technical Support Resources on interpreting IKE debug output and peer ID roles
NEW QUESTION # 23
Refer to the exhibit.
The output of a BGO debug command is shown.
What is the most likely reason that the local FortiGate is not receiving any prefixes from its neighbors?
- A. None of the three neighbors has successfully established the TCP three-way handshake with the local router.
- B. The router 100.64.3.1 is waiting for the OPEN message from the local router.
- C. The local router is waiting for the keepalive message from the router 10.125.0.60.
- D. The RIB-OUT configuration for router 10.127.0.75 prevents any route advertisement to the local router.
Answer: D
Explanation:
To identify the reason for the lack of prefixes, we must interpret the State/PfxRcd and Up/Down columns in the get router info bgp summary exhibit.
Analyze Neighbor Status:
Neighbor 10.125.0.60: State is OpenSent. This session is not established. It is stuck in the negotiation phase.
Neighbor 100.64.3.1: State is Active. This session is not established. The router is actively trying to initiate a TCP connection.
Neighbor 10.127.0.75:
Up/Down: 02:45:55. This indicates the BGP session has been Up (Established) for almost 3 hours.
State/PfxRcd: 0. This number represents the count of prefixes received. The session is fully established, but the neighbor has sent zero routes.
Determine the Cause:
Since the session with 10.127.0.75 is established, connectivity and handshakes (Options A, B, C) are not the issue for this neighbor.
The fact that it is Up but sending 0 prefixes strongly implies that the neighbor is configured to filter out its routes before sending them to the local FortiGate.
Option D correctly identifies this as a RIB-OUT (Routing Information Base - Outbound) configuration issue on the neighbor (Router 10.127.0.75), which prevents it from advertising its routes.
Reference:
FortiGate Security 7.6 Study Guide (BGP): "In the BGP summary, if the State/PfxRcd shows a number (e.g.,
0), the session is Established. A value of 0 means the peering is up, but no routes have been received, often due to route-map or prefix-list filtering on the remote peer."
NEW QUESTION # 24
What is the correct order of the IKEv2 request-and-response protocol?
- A. Create_Child_SA, IKEAUTH, IKESAJNIT
- B. IKE SA INIT, IKE AUTH. Create Child SA OIKE AUTH.
- C. Create_Child_SA, IKE_SA_INIT. IKE_AUTH
- D. IKE_AUTH_IKE_SA_INIT, Create_Child_SA
Answer: B
Explanation:
The Internet Key Exchange version 2 (IKEv2) protocol simplifies the negotiation process compared to IKEv1.
It is defined by a specific sequence of message exchanges to establish a secure IPsec tunnel.
The correct chronological order of the IKEv2 exchanges is:
* IKE_SA_INIT (Initial Exchange):
* This is the first exchange. It negotiates the security parameters for the IKE Security Association (IKE SA), sends nonces, and performs the Diffie-Hellman key exchange. At the end of this exchange, the communication is encrypted, but the peers are not yet authenticated.
* IKE_AUTH (Authentication Exchange):
* This is the second exchange. It authenticates the previous messages, exchanges identities and certificates (if used), and establishes the first Child SA (the actual IPsec Security Association used for data traffic).
* CREATE_CHILD_SA (Subsequent Exchanges):
* This exchange occurs after the IKE SA and the initial Child SA are established. It is used to create additional Child SAs (for different traffic selectors) or to perform re-keying for the IKE SA or existing Child SAs.
Why other options are incorrect:
* A & B: Incorrect because CREATE_CHILD_SA cannot happen before the SA is initialized (IKE_SA_INIT) and authenticated (IKE_AUTH).
* D: Incorrect because IKE_AUTH cannot occur before IKE_SA_INIT.
Therefore, the protocol flow is IKE_SA_INIT $\rightarrow$ IKE_AUTH $\rightarrow$ CREATE_CHILD_SA.
NEW QUESTION # 25
Which two statements about an auxiliary session ate true? (Choose two.)
- A. With the auxiliary session setting enabled. ECMP traffic is accelerated to the NP6 processor.
- B. With the auxiliary session setting enabled. Iwo sessions are created in case of routing change.
- C. With the auxiliary session selling disabled, only auxiliary sessions are offloaded.
- D. With the auxiliary session setting disabled, for each traffic path. FortiGate uses the same auxiliary session.
Answer: A,B
Explanation:
Auxiliary sessions in Fortinet are designed to support ECMP (Equal Cost Multi-Path) and SD-WAN scenarios, allowing sessions to be handled efficiently when traffic needs to be dynamically distributed across multiple links. With the auxiliary session setting enabled, FortiGate creates additional session table entries for each possible path in ECMP or SD-WAN-meaning that if the routing path changes (such as a link failover), a new session can be immediately activated and offloaded to the NP6 network processor for acceleration, ensuring minimal disruption. This greatly benefits high-throughput deployments.
Official documentation specifies that when auxiliary sessions are enabled, FortiGate doesn't just rely on dynamically creating new sessions after a routing event, it proactively creates sessions for all potential paths.
This means that in the event of a route change, two sessions exist and the traffic is quickly re-routed and offloaded, maximizing performance and reliability. Without this feature, multiple paths cannot be efficiently offloaded, and routing changes trigger a single session update, reducing failover performance.
References:
FortiOS Handbook: Session Table, ECMP, SD-WAN, and Auxiliary Sessions
FortiGate NP6 Acceleration Guide: Auxiliary Session Behavior
NEW QUESTION # 26
Refer to the exhibit.
FortiGate is showing continuous high CPU usage During a maintenance window, the CLI command diagnose sys top displays the output shown in the exhibit. The CLI command diagnose twat application ipsmonitor 5 was run. but the CPU usage by daemon ipsengine did not drop Which immediate action can you take to reduce the CPU usage effectively?
- A. Reduce the number of IPS signatures enabled on the active IPS profiles
- B. Bypass all IPS engines
- C. Disable IPS on all firewall policies.
- D. Execute diagnose test application ipsMonitor 2inatead.
Answer: D
Explanation:
To solve this high CPU usage scenario involving the ipsengine, we must understand the specific functions of the diagnose test application ipsmonitor commands shown in the troubleshooting steps.
* Analyze the Situation:
* Exhibit: The diagnose sys top output shows the ipsengine process is in a run state (R) consuming 99% CPU.
* Previous Action: The administrator already ran diagnose test application ipsmonitor 5.
* Result: The CPU usage did not drop.
* Understand the Commands:
* diagnose test application ipsmonitor 5: This command toggles IPS Bypass Mode. When enabled, the IPS engine lets traffic pass through without inspection.
* Implication: If the CPU was high due to traffic volume, enabling bypass would drop the CPU load immediately.
* Failure: Since the CPU remained at 99% after bypass, the ipsengine process is likely frozen, stuck, or in an internal infinite loop unrelated to the current traffic flow. The process itself is the problem, not the traffic volume.
* Evaluate the Solution (Option B):
* diagnose test application ipsmonitor 2: This command toggles the IPS engine's Enable
/Disable status.
* Because the engine is stuck (bypass failed to relieve pressure), the "Immediate action" required is to stop or restart the process entirely.
* Running option 2 effectively disables/kills the stuck IPS engine instance, which will immediately drop the CPU usage to near zero. (It can then be toggled again to restart it).
* Why other options are incorrect:
* A (Reduce signatures): This is a tuning measure for normal operation, not an immediate fix for a stuck process at 99% CPU.
* C (Disable IPS on policies): This is a configuration change that takes time and requires a commit; it is not the most immediate diagnostic tool available.
* D (Bypass all IPS engines): This describes the action of command 5 (Bypass), which the prompt explicitly states was already performed and failed.
Reference:
FortiGate Security 7.6 Study Guide (IPS & Diagnostics): "Troubleshooting IPS high CPU: 1. Check top. 2.
Try bypass (ipsmonitor 5). 3. If CPU persists, restart the engine (ipsmonitor 99 or 2)."
NEW QUESTION # 27
Exhibit.
Refer to the exhibit, which shows a FortiGate configuration.
An administrator is troubleshooting a web filter issue on FortiGate. The administrator has configured a web filter profile and applied it to a policy; however the web filter is not inspecting any traffic that is passing through the policy.
What must the administrator do to fix the issue?
- A. Enable fortiguard-anycast.
- B. Increase webfilter-timeout.
- C. Change protocol to TCP.
- D. Disable webfilter-force-off.
Answer: D
Explanation:
The exhibit shows a FortiGate configuration under config system fortiguard related to web filtering and FortiGuard options. There is a line:
set webfilter-force-off enable
According to official Fortinet documentation, the "webfilter-force-off" option, when enabled, causes the FortiGate to bypass web filtering for all traffic-even if a web filter profile is applied to a policy.
This override is typically used for troubleshooting or performance reasons and is documented as an explicit bypass feature.
If an administrator wants to enforce web filtering inspection, this setting must be disabled. The correct way to restore web filtering functionality is to run:
set webfilter-force-off disable
Once done, traffic passing through policies with web filter profiles will be inspected and filtered as per configuration. Other settings such as timeout or cache TTL do not bypass web filtering; they only affect operational nuances.
Reference:
FortiOS Administration Guide: Web Filtering, FortiGuard Options, "webfilter-force-off" CLI
NEW QUESTION # 28
Refer to the exhibit.
Which route will traffic take to get to the 100.65.0.0/24 network considering the routes are all configured with the same distance?
- A. The policy route
- B. The BGP route
- C. The static route
- D. The OS PF route
Answer: A
Explanation:
To determine the path the traffic will take, we must look at the FortiGate Route Lookup Precedence (Packet Processing Flow) and the specific configurations shown in the exhibit
* Analyze the Routing Precedence:
* In FortiOS, when a packet arrives (and is not part of an existing session), the FortiGate performs route lookups in a specific order:
* Policy Routes: Configured under config router policy (or diagnose firewall proute list).
These are checked first. If a packet matches the criteria (Source, Destination, Protocol, Incoming Interface), the Policy Route is used immediately, bypassing the standard routing table.
* FIB (Forwarding Information Base): If no Policy Route matches, the device looks at the standard routing table (Static, Connected, Dynamic).
* Analyze the Exhibit:
* Policy Route Section: The output of diagnose firewall proute list shows an active policy route ( id=1).
* Destination: 100.65.0.0/255.255.255.0 (Matches the network in the question).
* Action: It directs traffic to gateway 10.0.4.253 via oif=6(port4).
* Routing Table Section: The output of get router info routing-table database shows multiple routes for 100.65.0.0/24 (Static, OSPF, BGP) all with distance 10. The Static route (S) is currently selected (*>) in the FIB.
* Conclusion:
* Because Policy Routes take precedence over the standard routing table (FIB), the FortiGate will forward the traffic using the instructions in Policy Route ID 1. It will not use the Static, BGP, or OSPF routes visible in the routing table for any traffic that matches the policy route's criteria (ingress port 3).
Reference:
FortiGate Security 7.6 Study Guide (Routing): "Policy routes take precedence over entries in the routing table. If a packet matches a policy route, the FortiGate routes the packet according to the specified interface and gateway."
NEW QUESTION # 29
Refer to the exhibit, which shows the modified output of the routing kernel.
Which statement is true?
- A. The default static route through port2 is in the forwarding information base.
- B. The egress interface associated with static route 8.8.8.8/32 is administratively up.
- C. The default static route through 10.200.1.254 is not in the forwarding information base.
- D. The BGP route to 10.0.4.0/24 is not in the forwarding information base.
Answer: D
NEW QUESTION # 30
Refer to the exhibit, which shows a session entry.
Which statement about this session is true?
- A. It is an ICMP session from 10.1.10.10 to 10.200.1.1.
- B. Return traffic to the initiator is sent lo 10.200.1.254.
- C. It is an ICMP session from 10.1.10.1 to 10.200.5.1.
- D. Return traffic to the initiator is sent to 10.1.0.1.
Answer: B
Explanation:
The session output reveals a session with proto=1 (ICMP) and the origin and reply directions show address and NAT translations. Specifically, the hook=post dir=org act=snat shows that source NAT is performed for outgoing packets, where the source 10.1.10.10:40602 is translated to 10.200.5.1:8 (likely ICMP id 8, not a TCP/UDP port). The reply direction, hook=pre dir=reply act=dnat, indicates destination NAT for incoming packets: packets incoming for 10.200.5.1:60430 are destination-NATed to 10.1.10.10:40602. The gateway (gwy) is listed as 10.200.1.254/10.1.0.1, which for outgoing traffic means that return traffic is directed to the gateway (10.200.1.254), per the NAT policy. This is confirmed by the FortiOS Session Table Guide, which explains that the returned ICMP reply will be routed out to this NAT gateway. The session statistics and logical flow (SNAT out, matching DNAT in) reinforce that reply traffic to the initiator traverses via
10.200.1.254.
References:
FortiOS Administration Guide: Session Table, NAT, and Route Interaction Fortinet Technical Note: Diagnose sys session list, Direction and NAT Analysis
NEW QUESTION # 31
Refer to the exhibit, which shows partial outputs from two routing debug commands.
Which change must an administrator make on FortiGate to route web traffic from internal users to the internet, using ECMP?
- A. Set the priority of the static default route using port2 to 1.
- B. Set snat-route-change to enable.
- C. Set preserve-session-route to enable.
- D. Set the priority of the static default route using port1 to 10.
Answer: D
NEW QUESTION # 32
Exhibit.
Refer to the exhibit, which shows a partial output of diagnose hardware aysinfo memory.
Which two statements about the output are true? (Choose two.)
- A. There are 98908 kB of memory that will never be used.
- B. The value indicated next to the inactive heading represents the currently unused cache page.
- C. The user space has 708880 kB of physical memory that is not used by the system.
- D. The I/O cache, which has 641364 kB of memory allocated to it.
Answer: B,C
Explanation:
The partial output from diagnose hardware sysinfo memory provides details on system RAM allocation.
According to Fortinet's technical documentation for memory troubleshooting and Linux memory management (which FortiOS is based on):
* MemFree is the portion of physical memory not currently allocated to any running process or kernel function. Thus, 708880 kB is available and can be immediately used by user-space programs or system operations.
* Inactive refers to pages in the memory cache that were previously in use for I/O or file system buffering but are now not actively referenced. These pages are retained in memory for quick access if needed again, but can be reclaimed for other memory operations if demand increases. The value 98908 kB here represents currently unused cache pages (inactive pages), ready for repurposing or deletion if the system requires more RAM.
* Cached represents the total amount of system memory allocated to cache, which includes both active and inactive cache pages. It does not, by itself, represent I/O cache exclusively, nor does "inactive" mean memory "will never be used" as the kernel can re-purpose inactive pages on demand.
References:
Fortinet Technical Tip: Explaining the 'diagnose hard sysinfo memory' command FortiOS System Administration Guide: Linux Memory Reporting, Cached and Inactive Statistics
NEW QUESTION # 33
Refer to the exhibit.
FortiGate is showing continuous high CPU usage During a maintenance window, the CLI command diagnose sys top displays the output shown in the exhibit. The CLI command diagnose twat application ipsmonitor 5 was run. but the CPU usage by daemon ipsengine did not drop Which immediate action can you take to reduce the CPU usage effectively?
- A. Reduce the number of IPS signatures enabled on the active IPS profiles
- B. Bypass all IPS engines
- C. Disable IPS on all firewall policies.
- D. Execute diagnose test application ipsMonitor 2inatead.
Answer: D
Explanation:
To solve this high CPU usage scenario involving the ipsengine, we must understand the specific functions of the diagnose test application ipsmonitor commands shown in the troubleshooting steps.
Analyze the Situation:
Exhibit: The diagnose sys top output shows the ipsengine process is in a run state (R) consuming 99% CPU.
Previous Action: The administrator already ran diagnose test application ipsmonitor 5.
Result: The CPU usage did not drop.
Understand the Commands:
diagnose test application ipsmonitor 5: This command toggles IPS Bypass Mode. When enabled, the IPS engine lets traffic pass through without inspection.
Implication: If the CPU was high due to traffic volume, enabling bypass would drop the CPU load immediately.
Failure: Since the CPU remained at 99% after bypass, the ipsengine process is likely frozen, stuck, or in an internal infinite loop unrelated to the current traffic flow. The process itself is the problem, not the traffic volume.
Evaluate the Solution (Option B):
diagnose test application ipsmonitor 2: This command toggles the IPS engine's Enable/Disable status.
Because the engine is stuck (bypass failed to relieve pressure), the "Immediate action" required is to stop or restart the process entirely.
Running option 2 effectively disables/kills the stuck IPS engine instance, which will immediately drop the CPU usage to near zero. (It can then be toggled again to restart it).
Why other options are incorrect:
A (Reduce signatures): This is a tuning measure for normal operation, not an immediate fix for a stuck process at 99% CPU.
C (Disable IPS on policies): This is a configuration change that takes time and requires a commit; it is not the most immediate diagnostic tool available.
D (Bypass all IPS engines): This describes the action of command 5 (Bypass), which the prompt explicitly states was already performed and failed.
Reference:
FortiGate Security 7.6 Study Guide (IPS & Diagnostics): "Troubleshooting IPS high CPU: 1. Check top. 2.
Try bypass (ipsmonitor 5). 3. If CPU persists, restart the engine (ipsmonitor 99 or 2)."
NEW QUESTION # 34
Refer to the exhibit, which shows the output of the command get router info bgp neighbors 100.64.2.254 advertised-routes.
What can you conclude from the output?
- A. The BGP state of the two BGP participants is OpenConfirm.
- B. The local router is advertising the 10.20.30.40/24 network to its BGP neighbor.
- C. The router ID of the neighbor is 100.64.2.254.
- D. The BGP neighbor is advertising the 10.20.30.40/24 network to the local router.
Answer: B
NEW QUESTION # 35
......
FCSS_NST_SE-7.6 Dumps 100 Pass Guarantee With Latest Demo: https://measureup.preppdf.com/Fortinet/FCSS_NST_SE-7.6-prepaway-exam-dumps.html