Fortinet NSE4_FGT_AD-7.6 Practice Test 32
Question 310
After an HA failover, FortiAnalyzer has no event for a known connection, but the former primary displays an older local log. Where should retention be checked?
- Review the new primary’s on-box historical log buffer and rely on FGCP session synchronization to recover the former primary’s missing records.
- Inspect time synchronization between FGCP members and FortiAnalyzer, then reset both appliance clocks before tracing event forwarding.
- Determine the logging HA member and validate FortiAnalyzer ingestion, device registration and time filters after failover.
- Delete both FortiAnalyzer device records and register the HA cluster again before checking local event timestamps and collector forwarding on the former primary.
Explanation
Correct Answer
C:HA failover can move session and log forwarding between physical members; inspect current and former member event stores, timestamps and FortiAnalyzer device identity. Find the current HA member that produced the test event, its timestamp and FortiAnalyzer device identity; check forwarding after failover and local log buffers on both members. A log remaining on the old primary does not prove the central collector received it.
Incorrect Answers
A:FGCP can synchronize configuration and eligible session state, not necessarily every stored historical log entry between members. The known event exists on the former primary; trace its original timestamp and forwarding target, then check FortiAnalyzer ingestion and selected device/time filters rather than assuming replicated local history.
B:Time skew can make a real event appear outside a query window, so comparing timestamps is useful. Blindly resetting clocks, however, is disruptive and does not prove that the new active member sent the event to FortiAnalyzer. Verify logging registration, destination and actual delivery after failover.
D:Premature re-registration can destroy context and does not prove whether the missing log was generated, transported or indexed. Preserve local and central evidence first.
Question 311
An auditor needs to prove which employee accessed a protected share at 10:03. FortiGate traffic logs contain source IP and policy ID, and FSSO has time-varying mappings. Which evidence is necessary?
- Use today’s Firewall User Monitor identity for the source IP as definitive attribution for a connection logged yesterday at 10:03.
- Correlate the traffic session tuple logged at 10:03 with contemporaneous FSSO identity and DHCP lease/reassignment records, rather than today’s user-to-IP mapping.
- Inspect the endpoint MAC address recorded on the switch at 10:03 and use its vendor and OUI as the employee attribution for the share access.
- Use the employee’s current AD group membership and the protected share’s allow rule as proof that this employee actually accessed it at 10:03.
Explanation
Correct Answer
B:Attributing traffic to a person requires contemporaneous FSSO user/IP mapping, firewall policy log tuple and synchronized time; stale mappings alone are inadequate audit evidence. Reconstruct the source IP to employee mapping as of 10:03 using timestamped FSSO events, DHCP/IP assignment where appropriate and the exact traffic-policy tuple. The current user display may have changed since the event, so a present-day mapping alone is insufficient attribution.
Incorrect Answers
A:IP leases and user mappings can change between the incident and review. Attribution needs the historical FSSO logon mapping synchronized to the traffic timestamp, not just current ownership.
C:A contemporaneous MAC-to-port record can help identify which device was connected, but it cannot establish which human user signed in or which identity was mapped by FSSO at the event time. A reused workstation or changing DHCP lease can make current addresses misleading. Correlate the traffic tuple with historical FSSO logon and DHCP assignment evidence for the exact timestamp.
D:Group eligibility is not event evidence. Correlate the specific traffic session with time-aligned user/IP and DHCP records before claiming a historical user action.
Question 312
SLA probes reach both WAN gateways with zero loss, but voice latency rises dramatically on one circuit. An engineer proposes a simple reachability-only route failover. What distinction matters?
- Steer voice using measured SD-WAN latency/jitter/loss SLA rather than a gateway ping or static-route distance.
- Use successful low-loss ICMP pings to each WAN gateway as the sole voice link-quality evidence and keep the current cheapest-link steering.
- Set a lower administrative distance on the provider whose gateway responds fastest, without inspecting measured voice jitter or the existing SD-WAN service rule.
- Disable every probe because test packets can occasionally add latency to a congested circuit.
Explanation
Correct Answer
A:A successful gateway probe with zero loss can coexist with unacceptable end-to-end delay or jitter. Static route preference and interface-up monitoring do not necessarily enforce voice-quality thresholds. Configure suitable FortiOS SD-WAN health targets and SLA limits for voice, associate the matching service rule and verify chosen member during measured degradation; leave ordinary static route failover for reachability goals.
Incorrect Answers
B:Gateway reachability is not end-to-end application latency or jitter. The case says voice suffers despite successful probes; use an application-representative SLA to select the actual service path.
C:Distance influences route preference but cannot substitute for service-specific quality thresholds and congestion. Investigate actual member SLA before reassigning voice.
D:Removing health evidence prevents informed steering and may keep degraded links in service. Use suitable targets and measured thresholds, not unobserved routing choices. Suppressing probes removes performance evidence; choose appropriate targets and intervals rather than guessing link quality.
Question 313
Two sites are connected by route-based IPsec, but both currently use 10.10.0.0/24 behind their respective FortiGates. Hosts at each site must reach specific remote resources, and a plain route for 10.10.0.0/24 resolves locally. Which address-design decision prevents ambiguous protected traffic?
- Use identical 10.10.0.0/24 phase-two protected selectors at both sites and rely on IPsec encryption to distinguish their equal internal prefixes.
- Add wider firewall permit rules while keeping the overlapping route prefixes unchanged.
- Create additional IPsec tunnel interfaces between the overlapping sites while retaining the same protected /24, routes and host addresses on both sides.
- Use approved, documented address translation or renumbering so each site has a distinct reachable prefix; update the IPsec protected selectors, routes and firewall policies consistently.
Explanation
Correct Answer
D:Both sites advertise the same 10.10.0.0/24, so an ordinary route lookup cannot distinguish remote from local hosts using those addresses. Implement a documented nonoverlapping translated subnet or renumber one side, then configure appropriate VPN protected selectors, NAT and route entries on both FortiGates. Test both directions and preserve source identity where required.
Incorrect Answers
A:Encrypted encapsulation does not resolve overlapping inner destination addresses in route-based forwarding. Approved NAT or renumbering is needed for deterministic addresses and selectors.
B:An ACCEPT rule cannot resolve two networks claiming the same destination address space. The routing and protected-subnet design must differentiate sites before policy can select safe access.
C:Extra tunnel count does not make identical local and remote prefixes distinguishable in routing. Translation or addressing changes and coherent policies are required.
Question 314
A FortiGuard application signature misidentifies an approved SaaS client as a prohibited remote-control tool. The event includes the signature ID. How should the exception be assessed?
- Set the entire Remote Access and Control app category to Allow to recover the one approved SaaS process after a false-positive signature update.
- Disable deep inspection for all users and assume the signature will classify more accurately when it sees less traffic.
- Change the SaaS client’s source-NAT public pool and treat the new egress IP as proof its previously blocked application-control signature has been corrected.
- Identify the misclassified SaaS signature and apply a narrow approved override that leaves actual remote-control signatures blocked.
Explanation
Correct Answer
D:A false SaaS application signature classification can be resolved through event/packet evidence and a narrow approved override, preserving protections for unrelated traffic. Use the exact application signature ID and false-positive event to create a narrow authorized override while preserving blocking for genuinely prohibited remote-control tools. Compare new sample sessions against the approved SaaS app and unrelated category traffic.
Incorrect Answers
A:Category-wide Allow would reauthorize genuine remote-control tools forbidden by policy. Confirm the precise signature and use a narrow verified override with new-session tests.
B:Reducing application visibility is not a diagnosis and can weaken control coverage. Validate the observed payload/protocol and signature metadata before changing inspection. Disabling inspection can reduce classification evidence and broader security; inspect the signature and supported exclusions.
C:SNAT changes identity/route context but does not inherently change payload signature classification. The sensor’s matched application ID and Block action must be reviewed.
Question 315
An HA pair has synchronized firewall policies, but the secondary unit reports different FortiGuard entitlement details tied to its serial number. What is the correct interpretation?
- Inspect the primary member’s FortiGuard contract and assign its same serial-specific entitlement to the secondary because firewall policies are synchronized.
- Disable FGCP security-policy synchronization to make license-status screens independent and assume differing service entitlement proves the cluster configuration diverged.
- Review HA heartbeat group and source addresses, then change heartbeat identity to match the primary’s support-contract identifier.
- Check each HA member’s separate FortiGuard entitlement and device serial despite synchronized FGCP security configuration; validate the individual secondary serial number’s subscription and update-server status.
Explanation
Correct Answer
D:Some FortiGate licensing and HA identifiers are device-specific and do not synchronize; verify the standby member's own entitlement and serial association independently. FGCP copies most policy settings, but FortiGuard entitlement and certain per-device HA properties remain associated with the member's own serial/license state. Verify the secondary's registration and feature status rather than treating all license differences as cluster-sync corruption.
Incorrect Answers
A:FGCP synchronizes many security configurations, but Fortinet documents that most subscriptions and licenses are individual to each cluster member. A functioning primary does not automatically license the secondary serial. Check that unit’s registered contract and ability to reach the update service independently.
B:Device-specific FortiGuard registration can differ even when synchronized security policies are consistent. Disabling synchronization undermines policy availability without fixing service entitlement.
C:Heartbeat configuration governs cluster membership and synchronization, not the FortiGuard entitlement associated with a device serial. Modifying it risks availability without fixing the secondary’s expired or different contract. Verify registration and license status for each member separately.
Question 316
A policy permits Finance users to reach a cloud service, yet traffic from an unauthenticated machine in the same subnet is denied. An operator proposes removing the user condition. What should be checked first?
- Replace the Finance identity condition with the full workstation subnet because the target host and service are otherwise correct.
- Change the Finance firewall policy source address from the workstation subnet to its SNAT pool, treating translation as proof of a Finance user-group login.
- Verify whether this workstation has a current authenticated Finance identity/group mapping on FortiGate and satisfies the effective user-scoped policy selectors before changing the authorization rule.
- Inspect the Finance rule order and move it above broader generic rules without confirming the unauthenticated workstation’s Finance identity mapping.
Explanation
Correct Answer
C:Source identity selectors require a current authenticated user/group mapping in addition to source address; a subnet match cannot alone satisfy a user-specific policy. The unauthenticated machine shares the subnet but not the identity required by the Finance policy. Inspect current FSSO/LDAP group mapping and the matched user rule; removing the user selector would grant unintended access beyond authorized staff.
Incorrect Answers
A:Source subnet membership is not proof of an authenticated Finance user and would permit unauthorized clients. Restore proper FSSO/explicit authentication mapping instead.
B:Source NAT changes egress packet identity and cannot authenticate a workstation or establish Finance directory membership. Check a current FSSO or explicit authentication mapping for this host and its effective identity-based firewall policy before widening access.
D:Firewall ordering matters when a more general policy shadows a permitted Finance rule, so checking priority is valid. The denied host is explicitly unauthenticated, however, and changing rule order cannot make it satisfy an identity-group condition. Prove its live FSSO, LDAP or captive-authentication mapping and only then troubleshoot other policy selectors, retaining the Finance restriction.
Question 317
A tester needs repeatable evidence that FortiGate antivirus blocks known test malware without introducing real malicious files. Which test is appropriate?
- Download a random executable from a live malware-distribution site to see whether a security alert appears.
- Use nonmalicious EICAR via the matching AV policy and required SSL inspection, correlating the resulting Block event.
- Use the antivirus profile’s enabled checkbox and a test traffic ACCEPT log as evidence that malware was blocked without generating a safe test detection.
- Visit a known FortiGuard web-filter Block category and count its browser denial page as proof that antivirus blocked a malicious file.
Explanation
Correct Answer
B:Fortinet documents testing an antivirus profile with the EICAR safe sample through a configured FortiGate firewall policy and appropriate SSL inspection. Use a controlled permitted endpoint, record the test timestamp, policy and antivirus profile, confirm the expected block/replacement action, and compare relevant antivirus logs and counters. Avoid obtaining real malware to demonstrate routine enforcement.
Incorrect Answers
A:Introducing active malware is unnecessary and unsafe for a routine controls test. Use an approved harmless standard test artifact and validate the effective policy and AV action. Use recognized harmless test objects such as EICAR under controlled rules rather than downloading unknown live malware.
C:Configuration presence and forwarding permission are not observed antivirus enforcement. Use the approved harmless EICAR sample and correlate the actual AV Block event.
D:Web-filter destination classification differs from AV file scanning and can block without ever scanning a file. The proof must be an AV detection for the safe test sample.
Question 318
The Finance group must send all approved ERP transactions over a dedicated low-latency ISP, while ordinary branch browsing can load-share across other WAN members. The existing catch-all SD-WAN rule selects broadband first. Which identity/application matching and rule-order design should be implemented?
- Place a dedicated Finance ERP SD-WAN rule above catch-all browsing, steering eligible transactions to the low-latency ISP; keep general user web traffic on the separate lower-cost catch-all strategy.
- Set the dedicated ERP ISP as the global default route for all branch users, leaving the lower-cost bulk/browsing WAN strategy unconfigured.
- Match the dedicated WAN rule only by TCP/443, assuming that port distinguishes Finance ERP traffic from every other HTTPS video, browsing and collaboration session in the branch.
- Relax the dedicated ISP SLA thresholds until the member is always eligible for Finance ERP, even during unacceptable application latency.
Explanation
Correct Answer
A:SD-WAN service rules are evaluated in order and can match approved application, destination, source and identity criteria when supported. The Finance ERP rule must sit above the general broadband rule and list the dedicated eligible WAN member; other web traffic should continue to match a separate load-balancing rule. Validate classification and SLA eligibility with new sessions and record the selected member.
Incorrect Answers
B:A global default cannot confine premium egress to Finance ERP; it would steer unrelated traffic too. Use a narrow high-priority SD-WAN rule.
C:The same HTTPS service port is used by many departments and applications. A TCP/443-only match can steer unrelated sessions onto the expensive dedicated provider and does not establish Finance identity or ERP application selection. Use the approved source group and supported application or destination selectors in a higher-priority SD-WAN rule.
D:Artificially lenient SLA masks service degradation and does not guarantee low-latency application experience. Maintain the required threshold and eligible alternate design.
Question 319
A remote peer sits behind two routers and an upstream NAT device. IKE packets intermittently fail to reach it even though local tunnel configuration appears correct. What should be tested?
- Inspect the FortiGate branch-to-headquarters forwarding permit and add an explicit allow for the private tunnel subnet.
- Trace UDP/500 and UDP/4500 through both routers and the NAT mapping to correct the first missing IKE path.
- Review the child-SA selectors and include all private branch subnets in the phase-two protected address ranges.
- Enable UDP/4500 NAT-T on the final FortiGate peer but leave upstream router translations and UDP/500 forwarding unverified across the two intervening hops.
Explanation
Correct Answer
B:Two routers and an upstream NAT appliance may each have different forwarding and state constraints. Capture IKE UDP/500, then UDP/4500 when NAT traversal is negotiated, on both sides of the intermediary path. Verify that external-to-private peer translation, source/return route and security rules consistently reach the intended FortiGate, then test a new IKE attempt. Unlike a cryptographic child-SA mismatch, packets lost before the peer cannot be repaired by changing Phase 2 proposals.
Incorrect Answers
A:An inner firewall policy is important after IKE transport reaches both peers and a tunnel negotiates, but the given failure occurs before intermittent UDP/500 or UDP/4500 packets traverse two routers and upstream NAT. Trace the encapsulated exchange and NAT port mappings instead of changing downstream private-user authorization.
C:Selectors govern encrypted inner traffic only after IKE negotiation and authentication. The present symptom is intermittent reachability of the external peer over UDP through intervening NAT and routers. Broadening phase-two traffic ranges cannot correct missing IKE packets along that transport path.
D:NAT traversal cannot reach a remote IKE gateway through an upstream device that drops the first IKE UDP/500 exchange or lacks required return mappings. Trace both UDP/500 and UDP/4500 through each router and NAT mapping to the intended peer before changing child-SA configuration.
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.