Fortinet NSE4_FGT_AD-7.6 Practice Test 14
Question 130
FortiGate uses Central SNAT. A new outbound security policy permits traffic but the public source address is not the requested IP pool. Where should NAT be corrected?
- Enable the NAT checkbox on the outbound security policy while retaining central NAT mode and leaving the matching Central SNAT map unchanged.
- In the Central SNAT map matching the traffic, including rule order and selected IP pool, rather than assuming per-policy NAT governs it.
- Reorder the outbound ACCEPT firewall rule while leaving the matching central-SNAT pool and source/destination/interface selectors unchanged.
- Add a new central-SNAT entry using the desired IP pool BELOW an earlier catch-all central-SNAT rule that still matches every affected outbound session.
Explanation
Correct Answer
B:Central source NAT evaluates its own rule entries to select address translation. Compare original source, destination, egress interface, ordering and pool assignment against the live session translation. Correct the narrow intended rule and verify return connectivity and public address ownership without changing unrelated firewall actions.
Incorrect Answers
A:With Central SNAT enabled, source translation is configured in the separate ordered central SNAT map; the security policy permit does not replace the actual egress NAT rule.
C:Firewall permission order can affect which traffic policy accepts a session, but when central SNAT is enabled, the translated source comes from the matching central-SNAT map. Confirm its criteria and pool, then test a new session rather than assume rule order picks the public IP.
D:A later source-NAT map may never be reached if an earlier broader map matches the traffic. Inspect central-SNAT ordering, source/destination/service selectors and chosen pool, then place an appropriately scoped mapping so the desired public source actually applies.
Question 131
A FortiGate web-filter URL rule blocks https://example.com/confidential/ but must allow https://example.com/public/. The matching policy performs certificate-only TLS inspection; a hostname-level block works, yet requests to the two HTTPS paths have identical visibility in the web-filter log. What change is required to evaluate those two path-specific rules as intended?
- Use a supported full SSL deep-inspection policy on authorized managed clients so web filtering can examine the decrypted HTTP URL path; verify CA trust and test both /confidential/ and /public/ rules.
- Inspect the existing URL-filter regex for /confidential/ and apply a more specific expression to the web profile while keeping certificate-only TLS inspection.
- Keep certificate-only inspection and put an exact Block entry on example.com with a separate Allow entry for example.com/public/.
- Add an additional HTTP URL-filter rule for /confidential/ and redirect affected browsers from HTTPS to HTTP during policy matching.
Explanation
Correct Answer
A:Certificate-only inspection can classify a TLS server hostname without examining encrypted HTTP request paths. Distinguishing two paths on the same HTTPS host requires supported decryption under the effective firewall policy, a correctly ordered static URL rule and client trust of the approved inspection CA. Apply the authorized full-inspection profile and test both a forbidden and a permitted path while documenting certificate-pinned application exceptions.
Incorrect Answers
B:A more precise expression is useful only when the actual HTTP URL path is visible to the selected filter. Certificate-only inspection generally cannot read encrypted HTTPS request paths. The two endpoints share a hostname, so regex and logging refinements cannot separate them while relying only on handshake metadata. Verify supported deep decryption and CA trust for the authorized managed clients.
C:The Block and Allow entries appear targeted, but without decryption the FortiGate sees the same HTTPS hostname for both resources and cannot reliably discriminate the encrypted path. Blocking the entire host would also deny the required public path. Use approved deep inspection with client CA trust and test actual URL matches.
D:A cleartext redirect could make URL paths visible but would weaken transport security and would not correctly apply to existing HTTPS requests without an explicit safe architectural change. The task is to retain HTTPS while enabling path-aware policy. Use supported decryption on managed clients, not protocol downgrade.
Question 132
A newly deployed FortiGate can reach its default gateway by IP but FortiGuard update names fail DNS lookup. What should the administrator distinguish?
- Assume all update services are reachable because the default gateway responds.
- Modify the FortiGuard server reachability test to use IP addresses only.
- Replace the WAN default route despite reliable IP reachability to the assigned gateway.
- DNS resolver configuration and ability to resolve FortiGuard hostnames versus later IP routing and service reachability.
Explanation
Correct Answer
D:Check configured DNS servers, usable source/interface and actual domain resolution results on FortiGate. Once names resolve, test connectivity and authorization to the FortiGuard update endpoints. Keep gateway, DNS and remote-service failure categories separate to avoid unrelated route changes. Record separate DNS lookup and remote HTTPS test results to isolate the true failure layer.
Incorrect Answers
A:A responsive next hop proves local gateway reachability, not that FortiGuard domains can be resolved or remote services contacted. Different failure layers need separate tests. Remote resolution and HTTPS update connectivity are separate from simple LAN-to-gateway reachability.
B:A raw-IP test can isolate transport independently of DNS, but it does not correct the FortiGate inability to resolve update hostnames. Check configured DNS servers, source interface, the resolver request/reply path and the returned address before troubleshooting TLS or FortiGuard licensing.
C:The gateway responds by IP, so the first missing evidence is successful DNS resolution of FortiGuard service names. A new default route could be needed for internet reachability later, but it cannot be justified solely from the stated hostname-resolution failure.
Question 133
A company relies on LDAP for firewall administration, but directory service may be unavailable during an emergency. It needs tightly controlled local recovery access. Which design is appropriate?
- Require the same remote LDAP service for every administrator, including emergency recovery.
- Configure a permanent shared super-admin account with a public-WAN trusted-host range of all addresses for every help-desk operator.
- Maintain an audited, restricted local break-glass administrator with protected credentials and management-source controls.
- Allow unauthenticated console login during directory outages and do not record any emergency configuration actions.
Explanation
Correct Answer
C:Use a narrowly authorized local administrator with a protected secret, trusted management source and a documented procedure for activation and review. Test recovery access before an outage, and examine audit logs after any use. Ordinary administrators should continue to use named enterprise identities. Check that ordinary LDAP users cannot silently escalate to this exceptional local privilege.
Incorrect Answers
A:A directory outage would remove every management authentication path, defeating the stated emergency requirement. Maintain a tightly controlled local recovery identity and audit its use.
B:Shared unrestricted super-admin credentials cannot attribute individual changes and expand the attack surface. A break-glass account should be exceptional, protected, source-restricted and monitored.
D:Console access still requires secure identity and procedural controls; anonymous emergency administration increases misuse risk and undermines accountability. Use documented credential vault/recovery and logging.
Question 134
After a collaboration client update, FortiGate application-control logs begin labeling its sessions differently and blocking required video calls. What should the operator do first?
- Create an application-control override that permits the entire collaboration category for the affected employee group.
- Compare application signatures, client version, matching policy and logged action; then validate a narrowly tailored rule change.
- Change the matching application-control sensor action from Block to Monitor for all signatures on the HTTPS policy.
- Review the collaboration client’s TCP/443 sessions and add an earlier firewall HTTPS permit using the same application sensor but with a broader destination object.
Explanation
Correct Answer
B:Inspect the effective application-control sensor, detected application or category, signature database and the client’s changed protocol behavior. Reproduce a legitimate call and identify why the signature/action changed; adjust an approved exception if necessary while preserving unwanted application blocks. Monitor after the update. Check whether the changed client switched to a new QUIC or encrypted protocol path.
Incorrect Answers
A:A broad category override can quickly restore multiple collaboration features, but it admits unrelated applications and ignores evidence of a particular post-update signature change. Review the logged signature, policy and client version first, then permit only the documented business application behavior.
C:Monitor could restore access and retain event logs, but removing enforcement for the entire sensor is wider than necessary. The symptom begins with a client update and changed application identification; compare the specific signature and permitted functions before testing a narrow exception.
D:An early firewall allow can change which forwarding rule a session selects, which matters in policy lookup disputes. But the application-control event already shows the new client version being classified by the attached sensor as a blocked application. Reusing that sensor and broadening destination scope does not correct the classification or action. Compare signature evidence and change only a justified exception.
Question 135
An SD-WAN zone has a 500 Mbps fiber link and a 50 Mbps DSL link. Both pass basic reachability checks, but equal session splitting saturates DSL. What should be reviewed?
- The chosen load-balancing algorithm and available weight/volume configuration relative to usable member capacity and application requirements.
- Keep an equal 50/50 session-count algorithm and assume that ten times more provisioned fiber bandwidth automatically prevents DSL congestion.
- Switch every application to a strict latency-only SLA strategy.
- Increase the DSL member cost while leaving an explicit equal-weight load-balancing rule unchanged, assuming link cost alone controls all load-balance algorithms.
Explanation
Correct Answer
A:Links with very different capacities should not automatically receive equal offered load. Examine supported SD-WAN balancing methods, member bandwidth/weight settings, measured throughput and application sensitivity. Test traffic distribution under realistic concurrency and retain SLA-based steering for latency-critical services. Measure peak utilization and adjust the configured balancing distribution rather than assume equal capacity.
Incorrect Answers
B:Equal session counts do not imply equal byte volume, and a 50 Mbps DSL link can saturate even while a 500 Mbps fiber link has spare capacity. Review the supported distribution method, weights and actual utilization instead of treating link speed as automatic hashing input.
C:A lowest-latency rule can keep traffic on a path that meets delay targets without allocating enough bandwidth to bulk transfers, and it may unnecessarily steer best-effort sessions. Separate application requirements and choose a balancing strategy grounded in capacity and SLA evidence.
D:In FortiOS SD-WAN, member cost is relevant to strategies that consult it; a configured load-balancing mode may use its own hash/weight method instead. Examine the effective service rule and weight/volume settings when diagnosing this unequal-capacity link pair.
Question 136
A branch has two IPsec connections to headquarters over separate ISPs. The branch wants ISP-A primary and ISP-B failover when the preferred path becomes unusable. Which implementation is most appropriate?
- Assign both protected-prefix static routes equal distance and priority so either tunnel can carry sessions immediately.
- Compare the protected-route static distances and make ISP-A preferable, but keep dead-peer and tunnel-path health detection disabled.
- Inspect the backup phase-two auto-negotiate and treat an established backup child-SA as sufficient to withdraw the failed primary route.
- Configure eligible protected routes/tunnel priorities and reliable health or dead-peer detection, then test controlled failover and return routing.
Explanation
Correct Answer
D:Create the two authenticated tunnel paths with appropriate route preference and supported monitoring. Confirm primary selection, trigger a real path failure and verify that the secondary tunnel passes protected traffic with correct selectors and firewall policies. Test recovery behavior and the HQ return route to avoid asymmetric failover.
Incorrect Answers
A:Equal-cost routing may be useful for load sharing, but the stated design wants ISP-A primary and ISP-B as standby. Making both routes equally eligible can distribute new sessions onto the metered or backup path before a failure. Configure deliberate priority and valid failover health behavior.
B:Different static distances can express an intended primary/backup preference. They cannot reliably withdraw a blackholing primary path when the link remains apparently Up. The implementation must test reachability or peer liveness and confirm branch and headquarters routes select the functioning tunnel after failure.
C:Auto-negotiation can keep the backup security association ready, but an SA being established does not by itself decide forwarding preference or remove a stale primary tunnel route. Confirm protected-prefix route eligibility, reliable failure detection and the return path before declaring the failover ready.
Question 137
A FortiGate forwards logs to FortiAnalyzer, but event timestamps are consistently two hours behind other systems. What should be checked before treating them as separate incidents?
- Apply a two-hour correction offset to the FortiAnalyzer report search and retain the local device clock settings.
- Increase FortiAnalyzer ingestion time tolerance and sort by event arrival timestamp instead of device event time.
- Synchronize appliance time using trusted NTP and verify time-zone display/interpretation across the firewall and analyzer.
- Reconfigure the FortiGate log destination to local disk and compare only local timestamps during the incident.
Explanation
Correct Answer
C:Compare UTC and local display settings, NTP synchronization and clock accuracy on the FortiGate and FortiAnalyzer. Correct drift or interpretation, then generate a known test event and compare timestamps. Document the offset on historical records if they cannot be rewritten safely. Verify a new test event's UTC time at both ends to confirm whether the skew was fixed.
Incorrect Answers
A:A display adjustment can help compare records temporarily, but it does not ensure new logs share a reliable timestamp source. Cross-device investigations need the emitting FortiGate clock and collector display/time-zone interpretation verified so future records align rather than being patched in individual reports.
B:Ingest-time ordering can aid a delayed-log investigation, but the consistent two-hour offset points to source time or timezone representation, not IPS severity or log transport. Validate NTP synchronization and timezone conversion between the FortiGate and analyzer to maintain evidentiary chronology.
D:Local logging can provide a secondary capture if centralized delivery fails, but it does not fix a persistent clock mismatch and sacrifices centralized cross-device correlation. Preserve the FortiAnalyzer feed and verify the appliance time source and how time zones are displayed.
Question 138
An FSSO collector accepts mappings from an untrusted remote segment, and staff report unexpected identity assignments. Which configuration hardening matters most?
- Increase the FSSO mapping idle-time threshold to reduce the frequency of identity reassignments from the remote collector.
- Restrict trusted identity event sources/collectors and validate logon evidence, source-IP ownership and group mapping before granting policy access.
- Inspect the FortiGate remote group filters and restrict each policy to narrower AD groups while continuing to accept identity mappings from the same untrusted collector.
- Review FSSO security event logs and enable high-detail mapping audits while retaining the remote collector’s existing untrusted ingress permissions.
Explanation
Correct Answer
B:FSSO policy grants should rely on authentic domain or collector events, protected connections and accurate identity-to-IP mappings. Restrict event sources and access to the collector, investigate conflicting mappings and verify group membership. Test IP reuse and spoofed/untrusted event paths before restoring trust in the collected records.
Incorrect Answers
A:Longer mapping cache lifetimes can reduce reauthentication but may preserve stale or spoofed user-IP bindings. The problem is that an untrusted segment can supply identity records; caching them longer amplifies the exposure rather than authenticating the source or verifying the user-to-IP link.
C:A precise group policy is important, but an untrusted FSSO event source can still assert false user-to-IP and group assignments within those approved groups. Restrict and authenticate the logon-data source, validate IP ownership and collector evidence, then apply least-privilege identity authorization.
D:Auditing helps reconstruct unexpected assignments, but detection alone does not close the trust boundary. The source can continue inserting incorrect identities and affecting policy matches. Restrict authorized collector or DC agent endpoints, validate credentials and event provenance, and then monitor the accepted mappings.
Question 139
Employees must download legitimate compressed archives but the company also needs to detect malware inside supported archive formats. Which antivirus-policy assessment is appropriate?
- Create a file-filter rule blocking executable content extracted from ZIP archives while continuing to allow all other archive files unscanned.
- Inspect archive recursion counters and raise the antivirus recursion depth to the configured platform maximum before testing approved nested downloads.
- Keep certificate-only SSL inspection for HTTPS archive downloads and raise only the antivirus scan buffer capacity.
- Configure supported archive and protocol scanning limits, consider encrypted archives and confirm the actual AV block behavior on test downloads.
Explanation
Correct Answer
D:Review supported archive scanning settings, limits on size and nesting, encrypted/password-protected archives, and the inspection mode on the effective policy. Test known safe and controlled malicious samples according to lab rules, verify block events, and define escalation for files the appliance cannot inspect completely.
Incorrect Answers
A:A narrow file-type restriction may reduce exposure to known executables, but malware can appear in other files and formats. It does not establish full supported archive scanning for the allowed legitimate downloads. Configure antivirus and appropriate archive recursion, size and encrypted-content handling with observed test behavior.
B:Recursion depth can limit archive inspection and raising it within supported bounds may help certain nested files, making this a relevant near miss. It does not by itself address decompression size, encrypted archives, memory/conserve behavior or the configured disposition of unscannable content. The full security decision needs measured supported limits and a verified block or alternative scan path.
C:Raising scanner capacity cannot expose archive payloads that remain encrypted through a certificate-only HTTPS connection. The policy must supply supported content visibility for the protocol plus archive-scanning and unscannable-file decisions; a buffer change alone does not guarantee examination of the file bytes.
Question 140
An IPS sensor was constructed with a signature filter that includes only low-severity threats. A known critical exploit passes without alert. What should be changed?
- Confirm signature filter severity, relevant protocol and action so high/critical exploits for the protected service are included and blocked appropriately.
- Raise the IPS event logging level to critical and keep the sensor’s low-severity signature filter unchanged.
- Refresh the FortiGuard IPS signature database and retain the existing low-severity-only sensor selection.
- Attach a second copy of the same low-severity IPS sensor to the protected server policy and generate another test session.
Explanation
Correct Answer
A:A sensor filter that excludes critical severities cannot protect against signatures it never selects. Review the intended server exposure and configure suitable severity ranges or signature overrides, with a blocking action for validated threats. Verify the effective policy and IPS database, then perform a safe test to confirm alert and prevention behavior.
Incorrect Answers
B:Logging severity affects how events are displayed or retained, but the sensor still excludes high and critical signatures from inspection. The missing detection is a signature-selection issue, not evidence that a critical match was merely hidden. Update the effective filter and action for the exposed service.
C:A current database is necessary for new exploit signatures, but the configured filter still selects only low-severity entries. Even an up-to-date critical signature would remain outside this sensor’s match set. Include the relevant high/critical threat signatures and validate their policy action.
D:Applying another copy of a sensor with the same filter does not add critical signatures. The existing filter omits the severity that corresponds to the known exploit, so repeated policy attachments cannot make the needed signature active. Adjust selection and enforcement, then test the effective matched policy.