Fortinet NSE4_FGT_AD-7.6 Practice Test 33
Question 320
An external scanner flags a vulnerable application version, but the FortiGate IPS log shows no matched exploit event. Which interpretation is valid?
- Compare the vulnerability advisory with enabled IPS signature coverage, the effective sensor and observed exploit-pattern traffic; a scanner finding alone does not prove exploitation.
- Treat the lack of a FortiGate IPS alert as proof the vulnerable server is patched despite the external scanner identifying an older version.
- Assume the scanner has successfully exploited the server because its version check reported a possible exposure.
- Turn IPS off during a vulnerability scan and interpret any scan result difference as proof of whether the original alert was a true exploit.
Explanation
Correct Answer
A:IPS logging shows matched attack signatures on traversing traffic; it is not an active vulnerability scanner, so an asset can be vulnerable without an observed IPS hit. An IPS sensor observes matching exploit patterns in traversing traffic, whereas a vulnerability scanner can assess installed software without generating a matching attack. Confirm actual sensor coverage, signature availability and monitored path before treating an empty IPS log as a clean bill of health.
Incorrect Answers
B:No IPS alert may reflect no exploit attempt, incomplete sensor placement or missing signature. Compare product version and actual IPS coverage separately.
C:Version-based or authenticated scanning can identify a condition without demonstrating exploitation. Validate the scanner's evidence and the application's patch state separately. A version flag identifies possible exposure but does not prove exploitation; corroborate with service and endpoint evidence.
D:Disabling an inspection control changes the measurement environment and can expose the service without confirming signature or host susceptibility. Use safe test evidence.
Question 321
A FortiGate debug-flow capture for a failing client 10.20.1.25 to server 10.30.1.50:443 is drowned by unrelated traffic, and the operator cannot identify the session policy lookup. Which capture and cleanup sequence should be applied before altering rules?
- Run an unrestricted FortiOS debug-flow trace for all sessions and leave it enabled throughout normal traffic peaks to capture the intermittent failed connection.
- Filter debug flow for 10.20.1.25 to 10.30.1.50 TCP/443 and capture one fresh route/policy decision.
- Clear the entire firewall session table before selecting a source or destination filter.
- Select any debug-flow DENY line involving TCP/443 and treat it as the reported client-server session, without matching the configured IP filters.
Explanation
Correct Answer
B:Apply a bounded FortiOS debug-flow filter for the precise source/destination/protocol, capture one reproducible session and immediately turn debug tracing off. The filtered packet's route and policy decision is more useful than an unbounded stream of unrelated events.
Incorrect Answers
A:Unfiltered debugging can produce noisy, high-cost output and obscure the intended tuple. Apply exact source/destination/protocol filters and limit collection to a fresh test.
C:Disrupting all sessions hides the original failure and impacts unrelated clients. First identify the relevant tuple and use precise debug filters rather than a global reset.
D:The network contains many HTTPS flows; a generic DENY line is not evidence for this client and server. Match the precise tuple and observed policy/route result.
Question 322
A public HTTPS application sits behind an edge firewall and an internal FortiGate. Connections are DNATed at one hop, but the inner firewall policy still expects the original destination address. What should be traced?
- Create the same external public VIP on the inner FortiGate and ignore the edge firewall’s existing destination translation to a private server address.
- Inspect upstream edge DNAT and the private destination tuple entering the inner FortiGate before adjusting its policy.
- Inspect the inner FortiGate source-NAT pool and use a different translated client address so the inner policy sees the expected public destination.
- Review HTTPS timeout settings on both firewalls and increase session idle duration before comparing their pre- and post-DNAT destination addresses.
Explanation
Correct Answer
B:In a two-firewall publication path, DNAT can occur at the outer or inner appliance; trace original destination, VIP match and translated address at each hop. Capture the public destination at the edge and the translated destination arriving at the inner FortiGate. Align the inner policy and routing with the tuple that truly reaches it, and inspect whether a second VIP or SNAT would create an unintended translation.
Incorrect Answers
A:A second unnecessary VIP may cause mismatched destination objects and confusion. Diagnose the post-edge DNAT tuple that the inner FortiGate actually receives.
C:Source NAT affects the source address of a forwarded session; it does not reverse the edge firewall’s destination NAT. The inner appliance receives the private post-DNAT destination and its rule must match that actual tuple. Capture the packet after edge translation before editing source pools.
D:Longer sessions can be appropriate for a legitimately idle application, but cannot make a security rule whose destination object is wrong match the already-translated packet. The incident occurs across two NAT hops; compare the actual destination addresses and inbound policy at each hop first.
Question 323
A deep-inspection rollout makes a midrange FortiGate CPU-bound during peak encrypted downloads. The administrator wants to expand coverage further. Which evidence should govern the decision?
- Increase every policy's simultaneous connection limit before measuring actual SSL decryption throughput and hardware offload.
- Switch all affected policies to proxy mode to resolve deep inspection CPU pressure without comparing model limits, TLS load or supported offload.
- Turn off resource/performance metrics collection while retaining the same deep-inspection rate, then judge success from fewer visible CPU alarms.
- Measure TLS session workload, processor offload, memory and throughput against the FortiGate model’s deep-inspection capacity; under representative peak traffic levels.
Explanation
Correct Answer
D:Deep SSL inspection adds cryptographic and content-analysis work. Measure concurrent TLS handshakes and session rates, per-process CPU, security-processor offload eligibility, available memory, application latency and sustained encrypted-download throughput on the actual FortiGate. Compare the supported SSL/SSH and antivirus profile demands with the model’s published performance and capacity limits, then stage any expansion with measured headroom. Do not assume an untested mode or buffer setting eliminates the measured bottleneck.
Incorrect Answers
A:Connection count is not a substitute for crypto-processing capacity. Profile CPU, memory, enabled ciphers, session offload and traffic mix before expanding a feature that is already resource constrained. Establish actual TLS transactions per second, processor utilization and supported offload before enlarging concurrent session admission.
B:Proxy processing can add buffering and resource demands, so global mode expansion may worsen the bottleneck. Establish actual CPU/crypto workload and capacity.
C:Counter suppression does not improve TLS throughput or memory capacity and removes evidence for tuning. Measure actual process utilization and application latency.
Question 324
The security team wants FortiGate administration available through a separate out-of-band port while production WAN routing changes. What should be designed?
- Bind administrative HTTPS and SSH exclusively to the production WAN and use its existing default route as the out-of-band management recovery path.
- Allow HTTPS administration from any external IP address so an operator can always reconnect during outages.
- Place FortiGate management on its isolated reserved interface with trusted-host controls and independent recovery routing.
- Create a WAN-to-management-address forwarded HTTPS Accept for all source IPs while keeping FortiGate administrative local-in controls unchanged.
Explanation
Correct Answer
C:An out-of-band path should remain usable when transit routes or WAN policies change. Configure the supported FortiGate management interface addressing and secure protocol listeners, separate management routing or VRF if needed, and scoped administrator source restrictions. Verify management from an approved jump host during a simulated production-path outage, while ensuring ordinary user traffic is not forwarded through the management segment.
Incorrect Answers
A:A shared production path can fail during the routing changes in the scenario. The management requirement explicitly needs an isolated reserved interface and independent safe route.
B:Unrestricted external access creates unnecessary exposure and does not guarantee a stable path. Use secured OOB connectivity, MFA and permitted administrator networks. Opening administrative HTTPS to all sources creates a remote attack surface; restrict trusted hosts and secure the management channel.
D:A forwarding firewall rule is not equivalent to the local control-plane listener and would expose a sensitive service. Use the supported dedicated/reserved management interface with trusted sources.
Question 325
A helpdesk technician needs to know which authenticated users FortiGate currently associates with active addresses for identity-based policies. Which evidence is appropriate?
- Use Firewall User Monitor and timestamped FSSO/authentication events to correlate the active source IP, authenticated account and group, accounting for address reassignment.
- Use the FortiGate system administrator login monitor and map the most recent administrator IP to the employee’s identity-based forwarding session.
- Read the FortiGate ARP table and infer that each observed client MAC address implies a particular authenticated directory account and group.
- Trust the last successful RADIUS test message without checking whether the user's current firewall session is established.
Explanation
Correct Answer
A:FortiGate firewall-user monitoring and timestamped FSSO/authentication events identify current users, groups and the IP addresses used for identity-based firewall rules. Correlate the active user entry with the client session and policy ID. A management administrator login, ARP neighbor or successful RADIUS server test does not prove which authenticated end user is associated with an active forwarded session.
Incorrect Answers
B:Administrator control-plane logins are not the same as firewall users authenticated for normal traffic. Firewall User Monitor and FSSO/authentication records show user-to-IP associations.
C:ARP maps IP addresses to link-layer neighbors, not to validated user identities. A shared or reassigned host requires the current user monitor and identity event evidence.
D:A server probe verifies remote authentication reachability, not active user mapping for each client. Inspect the live monitor and timestamped policy evidence. A successful RADIUS server test does not establish the identity currently attached to an individual traffic session; inspect live mapping.
Question 326
Two WANs have valid IP addresses. The backup is carrying new sessions even though the primary carrier is up. What routing checks are needed?
- Inspect only the carrier Up status and static administrative distance of the primary ISP, treating a reachable interface as route eligibility.
- Lower the backup route’s administrative distance to protect ongoing sessions while investigating the primary route failure.
- Increase the primary static route’s numeric priority value so FortiOS ranks the primary above the backup.
- Compare active primary and backup route prefixes, administrative distances, numeric priorities, next-hop/ARP health and any policy-route or SD-WAN match before changing failover preference.
Explanation
Correct Answer
D:A backup route appearing in the forwarding table while the preferred link remains available calls for checking the installed route attributes, not merely changing the firewall permit rule. Compare prefix length, distance, priority, next-hop resolution and interface state for the same destination. Confirm the preferred path is eligible and that an SD-WAN or policy-route decision is not steering the session elsewhere. Change only the route selection property shown to be responsible.
Incorrect Answers
A:Physical carrier and distance are important but do not establish that the active primary route resolves, wins numeric priority or is selected after policy routing/SD-WAN. The backup may be chosen for legitimate route and health reasons.
B:A lower backup distance makes the backup more preferred and therefore deepens the observed unexpected preference. The operator should compare installed prefix, route distance/priority, next hop and SD-WAN steering before changing metrics.
C:For otherwise equivalent FortiOS static routes, a lower numeric priority is preferred. Increasing that number can make the primary even less eligible; verify both entries and policy-routing context before changing it.
Question 327
The enterprise already trusts its approved FortiGate SSL-inspection CA on all managed browsers. After a web-filter rollout, only sessions matching a new high-priority firewall policy display a different, untrusted issuer certificate. The older inspected policy still works. What evidence should be compared before changing any web-category action?
- Review the affected website’s FortiGuard rating and change the blocking web category to Monitor for the new policy.
- Compare the new rule’s SSL inspection profile signing CA against the working, endpoint-trusted CA and correct its selection.
- Inspect the managed endpoint’s enterprise root store and redeploy the approved FortiGate signing CA to all browsers.
- Disable all SSL certificate-chain validation on managed clients because the previous security policy trusted the original inspection issuer.
Explanation
Correct Answer
B:The endpoint trust deployment is known to work for the old matching policy, so repeating a global CA install is not the first fix. Inspect the effective policy IDs and their SSL/SSH inspection profiles, identify the signing CA used for each substituted certificate and compare the client chain validation to the approved enterprise issuer. Correct the wrong CA/profile binding on the new rule, then verify that category decisions and HTTPS payload inspection still work under the intended security policy.
Incorrect Answers
A:A category action can change browsing access but does not determine which signing CA FortiGate presents when deep-inspecting a connection. The browser reports an issuer mismatch limited to sessions using the new higher-priority rule. Compare that rule’s SSL/SSH inspection profile and trusted CA with the working policy.
C:Certificate-store distribution would help if endpoints lacked the approved root. The older policy already succeeds on those same browsers, while the new policy issues a different untrusted substitute certificate. The decisive problem is likely its selected inspection profile or signing CA; redeploying an already trusted certificate does not reconcile a different issuer.
D:Disabling validation hides real impersonation risks and ignores the specific rule-to-rule mismatch. Keep the approved client trust baseline and fix the SSL profile signing identity that the new policy selected.
Question 328
Each branch has primary and standby IPsec tunnels to two headquarters gateways. After failing the primary uplink, one spoke sends traffic on its backup tunnel while return packets still follow the former hub. The design must avoid routing loops and preserve redundancy. What should the architect validate?
- Validate tunnel health and bidirectional primary/backup protected-prefix routes during hub-and-spoke failover.
- Inspect both active IPsec tunnel paths and assign equal static route distance and priority to distribute branch traffic over the redundant gateways.
- Disable one IPsec tunnel permanently so route loops cannot occur, removing redundancy.
- Advertise a default route from the standby headquarters VPN gateway toward all branches and prioritize it after a tunnel failover.
Explanation
Correct Answer
A:With two hub gateways, a branch may use its backup tunnel while headquarters still routes replies toward the former primary hub. Compare the preferred routes and tunnel health on both gateways and each spoke, along with interface and policy matches. Test primary failure, packet symmetry, return NAT if applicable, and loop avoidance before treating redundancy as successful.
Incorrect Answers
B:ECMP can share eligible new sessions, but it does not guarantee stateful return symmetry after a failed hub or preserve established translated session tuples. The case explicitly reports backup branch egress with replies using the former hub. Review bidirectional route health and failover preference at both ends.
C:Eliminating a backup might mask the symptom but abandons the stated resiliency objective. Correct tunnel selection and protected subnet routing while retaining independent paths.
D:A default can provide general connectivity but cannot necessarily override more-specific protected-prefix routes still sending replies toward the failed hub. The topology needs coordinated forward and reverse selections for each branch prefix to avoid loops and blackholes, with tunnel and policy health checked during failover.
Question 329
A SOC analyst searches for a blocked web event and receives no results, even though a local FortiGate log shows the event. What should be verified?
- Search the FortiAnalyzer IPS signature dataset using the same time range as the local blocked-web event.
- Disable the web-filter profile and reproduce the site visit, expecting no log to be easier to locate.
- Search FortiAnalyzer using the known blocked event’s timestamp, device, policy ID and category, then validate delivery; avoid assuming a device registration proves events have survived collector retention and filters.
- Verify the FortiGate is authorized in FortiAnalyzer's device inventory and repeat the web-filter event search.
Explanation
Correct Answer
C:An absent search result is not proof that the firewall generated no record. First reproduce the event with a known timestamp and policy ID, then compare the GUI filter, selected log type and time window with the FortiGate's actual logging action. Check whether the device stored or forwarded the event and whether any collector retained it. Distinguishing a search restriction from missing collection avoids changing otherwise healthy traffic policies.
Incorrect Answers
A:The event described is a FortiGate web-filter category block, not necessarily an IPS attack signature. Searching an unrelated dataset can miss an existing web-filter record. Compare the exact device, timestamp, policy and category in the relevant FortiAnalyzer log type and then validate delivery and retention.
B:Removing the control destroys the event the analyst needs. First check the local event ID, time range, log type and collector search fields. Disabling the filter prevents another meaningful block event and weakens protection; test collector delivery with the existing profile.
D:Device authorization is a prerequisite for collection but does not prove that this historical event was delivered, retained or indexed in the queried dataset. Because the local log already contains it, compare exact identifiers, filtering, transport and retention to establish where the record disappeared.
Question 330
After a FortiOS upgrade, the policy editor displays fewer visible security profile fields. A tester reports that scanning behavior has changed. Which evidence should establish the active configuration?
- Inspect CLI policy profile bindings and flow/proxy mode, then test actual security events instead of relying on GUI visibility.
- Inspect the previous firmware GUI screenshots and recreate the hidden antivirus and SSL profile fields from memory before checking running CLI bindings.
- Review GUI inspection-mode choices and migrate all firewall policies to proxy mode because their previous security selectors are no longer shown.
- Use a screenshot from the old FortiOS policy editor as the sole source of truth for which security profile actions run after the upgrade.
Explanation
Correct Answer
A:After a firmware change, different policy fields or GUI placement can be a presentation issue rather than a change in enforcement. Compare the effective firewall policy, source and destination match, NAT mode and assigned SSL or security profiles in the running configuration. Test a known session and inspect its actual policy identifier and action. Migrate any deprecated setting using the 7.6 guide rather than assuming an old screenshot depicts the current rule.
Incorrect Answers
B:A GUI field moving after an upgrade does not prove the underlying policy or scanner stopped working. Recreating profiles blindly can change effective enforcement and increase outages. Read the current policy and security-profile configuration in the CLI and observe actual new security events first.
C:Inspection mode controls supported features and performance, but a missing GUI field is not evidence that proxy mode is required or supported by every hardware model. Confirm the effective policy’s actual flow/proxy mode, profile bindings and detection logs before considering any targeted mode change.
D:Historical screenshots can document design but not actual current policy state. Verify the CLI, inspection mode and live test logs.