Fortinet NSE4_FGT_AD-7.6 Practice Test 30
Question 290
Two nearly identical user sessions are logged with different policy IDs although source IP and destination hostname appear the same. What should be compared?
- Match source and destination IP addresses only and declare two sessions equivalent even if their user identity, destination port and interface path differ.
- Force all traffic through one broad allow rule to make logged policy IDs uniform.
- Compare each flow’s complete tuple, ingress, identity, schedule and policy order to explain the different matched IDs.
- Compare policy ID numbers and choose the lower one as the first-match rule without reading the current policy order or session selectors.
Explanation
Correct Answer
C:Two sessions with the same displayed source and hostname may resolve to different destination IPs, ports or application paths, or have different authenticated user/group, VDOM, zone and schedule context. Compare the actual five-tuples, NAT translations and policy logs on fresh flows, then inspect rule order and match criteria. Do not assume two log entries are equivalent because a GUI summary hides fields.
Incorrect Answers
A:FortiOS policy matching considers service, direction, schedule and identity in addition to addresses. The full session and timing context is required before comparing different policy IDs.
B:Uniform logging through an unrestricted rule can conceal distinct security requirements. Find the actual fields that selected each original policy first. A catch-all permit hides meaningful separation and can grant more access than either original rule intended.
D:Policy ID is an identifier, not a reliable global sort order across changed rules. Use the actual policy list and each session’s full selectors for diagnosis.
Question 291
A RADIUS server authenticates a remote user but returns a vendor/group attribute different from the FortiGate remote-group condition. The user is denied by group policy. What should be compared?
- Increase the RADIUS shared-secret length and retry count without examining the Access-Accept group attribute or FortiGate remote user-group mapping.
- Match the RADIUS Access-Accept group attribute to the FortiGate remote-group mapping without broadening the security policy.
- Increase the RADIUS timeout so a mismatched group string becomes accepted once the server response is slower.
- Create a catch-all RADIUS group match allowing all authenticated remote users to bypass the intended departmental policy until the attribute format is standardized.
Explanation
Correct Answer
B:RADIUS authentication can return vendor-specific or group attributes; verify the exact accepted response and FortiGate local group mapping required by firewall policies. Compare the RADIUS group or vendor-specific attribute actually returned in Access-Accept with the FortiGate remote-group matching configuration. Authentication success does not guarantee the asserted group maps to the policy's permitted identity.
Incorrect Answers
A:An Access-Accept establishes successful credential exchange, but group authorization can still fail when the expected attribute value differs. Transport tuning does not correct the mapping.
C:Timeouts govern missing or delayed replies, not the content of a successful response. Correct attribute values or FortiGate matching rules. An explicit IPv6 policy needs suitable IPv6 addresses, interface bindings and routes; changing web filtering does not provide them.
D:Broad acceptance would defeat the required department-specific group-based boundary and permit employees who are not authorized. Correct the expected remote group/vendor attribute and retest included and excluded users before deployment.
Question 292
A vendor support portal was mistakenly blocked by the FortiGuard web category used in a staff firewall policy. The owner approves access for one named support group for 48 hours only, while other denied destinations must remain blocked. Which controlled FortiOS 7.6.0 exception best meets the limited duration and user scope?
- Create a site-specific FortiGuard web-rating override mapping the portal to a permitted local category, and record a change-ticket reminder to reverse it after 48 hours.
- Configure an approved alternate web-filter profile that permits only the required portal, assign a user/group-scoped web-profile override with a 48-hour switch duration, and test expiration plus unrelated blocks.
- Add a portal-specific static URL Allow rule to the existing shared staff web-filter profile, with a calendar reminder to remove the entry two days later.
- Change the existing shared web-filter profile from Block to Monitor for the entire affected category during the two-day support period.
Explanation
Correct Answer
B:FortiOS 7.6.0 documents web-profile overrides that switch specified users, groups or IP addresses to another web-filter profile for a predetermined number of days, hours and minutes. Configure a narrowly scoped alternate profile that permits the verified vendor portal while keeping other protected categories blocked, restrict the override to the approved support group, and verify access plus expiry after 48 hours.
Incorrect Answers
A:A site-specific rating override is a credible way to reclassify a false-positive portal but it changes the destination rating wherever that rating applies, not only for the approved support group. A change-ticket reminder is not a FortiOS-controlled 48-hour user-profile switch. Use the authorized group-scoped alternate web-profile override with a specified duration.
C:An exact static URL rule can allow a verified portal in the relevant profile, but the original shared staff profile is used beyond the approved support group, and a calendar reminder is not an enforced expiry. Static URL Allow also may not override an independent security-profile action. Apply the same narrow URL decision through a group-scoped alternate profile with a fixed FortiOS switch duration.
D:Switching an entire blocked category to Monitor can permit unrelated destinations for every user of that profile. It also lacks the approved group scope and predictable, automatic 48-hour profile duration. Retain the main policy and use only a verified limited alternate profile for authorized identities.
Question 293
An active-passive FGCP cluster protects a critical application through port4. A port4 link failure leaves the unit reachable on its heartbeat interface but production traffic unavailable, and no primary change occurs. Which HA health setting should be reviewed to trigger the intended failover?
- Monitor port4 on both FGCP members and test a controlled link failure with heartbeat and election checks.
- Review standby device priority and increase it so the cluster prefers that node without adding the failed port4 to HA interface monitoring.
- Inspect the FGCP session-pickup counters and enable additional session synchronization while port4 remains outside monitored-interface health.
- Enable additional heartbeat interfaces while keeping port4 excluded from the HA monitored-interface list.
Explanation
Correct Answer
A:Port4's loss did not trigger HA election because its monitoring or interface-health condition was not configured as expected. Review `config system ha` monitored-interface selection on both units, then safely test a port4 failure without breaking heartbeat redundancy.
Incorrect Answers
B:Changing priority may influence an election but cannot detect an unmonitored production link outage. The case says heartbeat connectivity survives, so a healthy control-plane link masks the lost application path. Set monitored port4 and verify the election under a controlled failure.
C:Session pickup helps preserve eligible existing sessions after a primary changes. It is not the signal that port4 failed. With the production port excluded from monitoring, no link-failure election is required; add and test the correct monitored-interface setting before tuning state synchronization.
D:Heartbeat redundancy helps cluster-member awareness, but this incident has not lost heartbeat connectivity. The failure is a customer-facing link left outside the primary-selection health criteria. Add the correct production interface to monitoring and test that the cluster protects this service.
Question 294
The FSSO monitor still shows users on an old workstation subnet after DHCP migration. Current AD events reference new addresses. What should be reconciled?
- Reconcile current DHCP leases and DC logon records against cached FSSO mappings; expire old-subnet entries.
- Increase FSSO user cache timeout to preserve pre-migration workstation mappings until all users naturally reauthenticate from their new DHCP subnet.
- Create broad firewall permits for both old and new subnets to keep access until the monitor eventually refreshes.
- Create an FSSO allow group for every source address in both old and new subnets while retaining all existing cached associations.
Explanation
Correct Answer
A:Outdated FSSO mappings after an address change can authorize the wrong person; compare DC/collector logon events, group records and mapping age for the current IP. Compare DHCP old/new address leases against FSSO collector user/IP timestamps, aging and current DC events. Clear only stale mappings and confirm a new workstation logon reassigns the correct group before granting a subnet-based rule.
Incorrect Answers
B:Longer cache lifetime increases the chance of stale identity grants on recycled addresses. Reconcile DHCP and logon events, then expire obsolete entries.
C:This could grant former users' entitlements to new devices. Restore accurate IP-to-user mapping and narrow authorized policies. Reconcile DHCP lease changes with FSSO workstation mappings and expiration; broad subnet permits could reauthorize an unrelated new device.
D:Broad source-based access sidesteps current employee identity and leaves stale mappings in place. The correct fix restores trustworthy IP-to-user association.
Question 295
A broad application-control sensor checks detailed signatures on all traffic, and the FortiGate becomes CPU-bound. Which tuning approach is least disruptive?
- Disable all application-control signatures on the high-traffic user policy permanently and treat CPU relief as proof the existing security requirement is unnecessary.
- Increase SSL decryption exceptions for all HTTPS sessions to reduce application-control work without documenting lost visibility or testing impacted signatures.
- Use process and signature workload measurements to narrow costly application-control inspection without discarding needed detection.
- Enable application-control logging for every signature in the already overloaded sensor, with no measurement of the signatures and decoders consuming CPU.
Explanation
Correct Answer
C:Application-control sensors impose processing overhead, particularly when broad rule sets inspect many sessions or encrypted protocols. Review resource diagnostics, policy hit counts and signature-classification logs to locate the expensive workload. Apply a scoped profile or signature tuning adjustment, then compare CPU, latency and blocked-app detection against baseline. Do not disable all application control or infer causes from a single bandwidth counter.
Incorrect Answers
A:This can reduce load but removes required application control without measuring which signature or traffic causes cost. Narrow supported inspection with evidence and detection validation.
B:Broad TLS bypass can reduce inspection but also prevent supported signature detection. Identify bottlenecks and apply a defensible targeted change.
D:Adding detailed logging to every application signature can increase processor and collection overhead without identifying the expensive inspection path. Correlate actual sensor/signature workload with the affected policies before scoped tuning.
Question 296
Two routes to 0.0.0.0/0 exist: one learned dynamically and one static. The admin deletes a learned neighbor but traffic still uses a default. What must be inspected?
- Assume deleting one dynamic neighbor withdraws every usable default route, even when a static default remains installed and eligible.
- Inspect the active RIB/FIB after neighbor deletion and identify the actual remaining default route for a new session.
- Review firewall policy ordering for the affected source and move its ACCEPT policy above other rules to select the remaining gateway.
- Inspect the configured static default route and raise its distance to influence traffic after the deleted dynamic neighbor disappears.
Explanation
Correct Answer
B:Deleting one learned default route does not change the active FIB if a static entry is still selected; inspect all candidate route sources and administrative distances. Deleting a dynamic routing neighbor does not remove a separate static default route. Inspect both installed RIB entries, administrative distances, next-hop reachability and actual forwarding source to identify the default that remains active.
Incorrect Answers
A:Routing decisions use the active RIB/FIB after the change. A surviving static or SD-WAN route can continue forwarding; inspect actual installation.
C:Security-policy ordering controls whether a flow is allowed and which profiles apply; it does not establish the installed route after deletion of a dynamic-routing neighbor. Determine the exact remaining default in the routing table and any higher-priority policy or SD-WAN selection first.
D:Distance determines preference between eligible candidates, but the request asks which route is actually installed after a dynamic neighbor was removed. Changing a static distance first can make forwarding less reliable and still does not establish whether another learned default exists. Read the current RIB and FIB for the new session.
Question 297
One IPsec peer reports increasing replay-window drops during bursty traffic, but authentication and tunnel establishment remain successful. Which evidence should guide tuning?
- Review replay-error counters and disable ESP anti-replay as a first response while preserving existing packet forwarding and application traffic.
- Correlate ESP anti-replay drops with sequence reordering and the supported replay window before making transport changes.
- Change user LDAP group membership because successful VPN authentication implies replay errors are user-policy failures.
- Inspect phase-one IKE lifetime and increase it so IPsec rekeys occur less frequently during bursts with ESP replay drops.
Explanation
Correct Answer
B:IPsec replay-window errors can be caused by excessive packet reordering or duplicates; capture sequence/SA behavior and avoid disabling integrity or anti-replay controls blindly. Check anti-replay counters, reordering, duplicate packets and the negotiated SA replay window against burst timing before modifying a security setting. Disabling replay protection risks admitting captured packets and would not explain asymmetric upstream sequencing.
Incorrect Answers
A:Disabling integrity-related replay protection can mask counter growth without diagnosing duplicate, reordered or old packets. It removes a meaningful security control and is unjustified by successful IKE alone. Capture ESP sequence behavior and determine whether the supported window or path reordering is the real issue.
C:Replay-window counters describe how encrypted packets arrive and are validated, not directory group entitlement. Inspect packet sequence and tunnel paths rather than altering unrelated identity permissions. LDAP membership is irrelevant to ESP sequence validation once the authenticated tunnel is carrying packets.
D:IKE SA lifetime can affect control-plane rekey frequency, but anti-replay checks use ESP sequence numbers and the negotiated child-SA replay window. The question reports successful authentication and increasing replay-window drops under burst traffic. Correlate packet ordering, sequence gaps and supported replay-window behavior instead.
Question 298
A scheduled content-scan job causes recurring CPU spikes. The team must tell normal expected inspection load from a runaway process. What should be compared?
- Raise the overall FortiGate CPU alarm threshold during scheduled scanning and treat reduced alert frequency as proof processing is healthy.
- Disable IPS for the scheduled job on every security policy because antivirus scanning is present during the same time period.
- Inspect WAN traffic shaper counters and reduce the scheduled scan job’s interface bandwidth allocation to keep aggregate CPU usage below its alarm threshold.
- Compare scan-job timestamps with process CPU, throughput, and matched security-profile workload to identify abnormal growth.
Explanation
Correct Answer
D:A scan job can raise CPU normally during bounded high-throughput inspection. Use FortiOS process and resource diagnostics with session counts and applied security profiles to compare peak and idle periods, identifying whether one engine stays elevated after the scheduled job. Record before/after CPU and latency and apply only evidence-backed profile or capacity changes; do not restart daemons or disable protection based on one spike.
Incorrect Answers
A:Threshold changes alter monitoring, not the workload or resource bottleneck. Correlate the known scan interval with processes and capacity to distinguish normal load from pathology.
B:AV and IPS protect different threats, and a global IPS bypass is not justified by correlated CPU spikes. Use per-process metrics and profile scope.
C:Traffic shaping can reduce a network-driven inspection workload when packet rate is demonstrably tied to resource saturation, so the change is technically plausible. But the distinction needed here is whether one process grows abnormally relative to its scheduled tasks, while ordinary profile work returns to baseline. Collect time-aligned process CPU, session volume and inspection counters before changing WAN capacity.
Question 299
An internal user can browse the internet, but customers cannot reach a public IP mapped to an internal web server. The outbound HTTPS rule shows successful hits. What should be diagnosed?
- Add a second outbound LAN-to-WAN HTTPS Accept and point its source address at the public web-server VIP used by customers.
- Inspect the successful outbound LAN-to-WAN HTTPS rule and add the server public VIP to its destination object before retesting an external client.
- Trace public inbound traffic through WAN VIP/DNAT and the matching WAN-to-DMZ HTTPS policy, not outbound user rules.
- Review server reply source NAT and choose a new public IP pool while the incoming VIP and WAN-to-DMZ policy remain unverified.
Explanation
Correct Answer
C:Outbound HTTPS authorization differs from an inbound published server session; inbound VIP DNAT and external-to-internal policy must match the public service tuple. Outbound browsing uses a LAN-to-WAN policy and is unrelated to clients initiating connections toward a VIP. Trace an external connection's ingress interface, VIP/DNAT object, WAN-to-DMZ permit, server listener and return route.
Incorrect Answers
A:Outbound user traffic policy does not authorize external inbound connections or implement destination NAT. Check WAN ingress, public VIP mapping and inbound server rule.
B:A LAN-originated browsing policy cannot authorize a new inbound public-to-DMZ connection. The two flows have different ingress interfaces, translated destination tuples and policy direction. Inspect WAN VIP/DNAT and its matching inbound security rule, plus the server return path.
D:Reply SNAT may be relevant to asymmetric server return routing after an inbound session is established, but cannot create a missing inbound DNAT or security policy. The external connection first needs to arrive at the correct VIP and match a restricted WAN-to-DMZ permit before return translation is tuned.
Question 300
During a burst of archived downloads, FortiGate enters conserve mode and AV workers consume unusually high memory. The operator proposes disabling all malware scanning. What should be examined?
- Correlate AV worker memory and archive limits with conserve thresholds, then apply a narrowly tested inspection or capacity adjustment.
- Check current proxy antivirus archive recursion depth and raise the decompression limit to the model’s supported maximum.
- Raise the proxy antivirus archive-scanning size and buffer limits during the memory-conserve incident.
- Inspect the FortiGate conserve-mode alarm threshold and increase its notification severity during large archived downloads.
Explanation
Correct Answer
A:Large archive inspection can increase proxy buffering and antivirus process memory, potentially entering FortiOS conserve mode. Before disabling security, inspect process and memory diagnostics, active AV profiles, protocol oversize handling and download size patterns. Test a safely constrained size/capacity adjustment or appropriate policy scope, confirm memory returns below conserve thresholds and preserve detection on unrelated traffic.
Incorrect Answers
B:Archive-depth configuration can affect inspection completeness, but raising it under measured AV worker memory pressure can increase buffering and worsen conserve mode. Compare actual worker and session memory, supported limits and oversize dispositions before choosing narrowly bounded tuning or extra capacity; retain essential malware detection.
C:Larger buffering or scanning limits can increase memory demand during large or nested archive inspection. Before raising them, profile actual AV worker consumption and conserve thresholds, assess oversize/decompression actions and test a scoped change that preserves malware controls while remaining within model capacity.
D:Alarm severity influences notification, not process allocation or the memory thresholds that protect packet processing. The incident already shows unusually high AV worker memory under archive load. Correlate the worker, file handling limits and conserve state, then select a tested workload or profile correction without suppressing visibility.