Fortinet NSE4_FGT_AD-7.6 Practice Test 7
Question 60
A FortiGate policy uses web filtering to display a block message for prohibited categories. However, an HTTPS client continues to see the permitted page. Which combination should be verified first?
- Modify the category block-page replacement text without verifying that the correct web-filter profile and action actually matched the HTTPS session.
- Switch the web-filter category action from Block to Monitor in an attempt to force a deny page for the same HTTPS client.
- The effective firewall policy and web-filter action, together with the inspection method needed to evaluate the intended HTTPS URL.
- Enable logging on an unrelated web-filter profile that is not attached to the policy carrying the HTTPS session.
Explanation
Correct Answer
C:Web-filter action applies through a security profile on the firewall policy matching the traffic. Check the actual policy ID, URL or category decision, profile action and whether encrypted inspection reveals enough of the requested site or path. Compare block and permitted test pages, and evaluate supported replacement-message behavior for HTTPS.
Incorrect Answers
A:Replacement-message styling affects the page shown after an eligible security decision, but cannot create a missing deny action. Establish which policy and web profile matched and whether TLS visibility supports the intended category or URL, then inspect replacement behavior.
B:Monitor is intended for observation with permitted traffic, not for enforcing a category block. A browser continuing to load content is consistent with monitor action; inspect the category action, effective policy and applicable HTTPS inspection instead.
D:Changing an unused profile does not affect the current session or generate a block page. Confirm the profile attached to the actually matched firewall rule, its action and supported replacement-message behavior for HTTPS.
Question 61
A finance application must always appear to an outside API as 198.51.100.27, rather than the current WAN interface address. Which source-NAT mechanism should be evaluated?
- Enable outgoing-interface-address NAT on WAN1 while its assigned public IP is different from the required 198.51.100.27.
- Use a suitable public IP pool and the correct policy or central SNAT selection, verifying return routing and public address ownership.
- Create only a destination VIP pointing to the finance PC.
- Change the outbound permit policy’s source-address object to 198.51.100.27.
Explanation
Correct Answer
B:An address pool can provide the approved fixed translated source when matched by an applicable NAT rule. Configure the correct NAT control location for the FortiGate mode, confirm the public IP is routed or owned appropriately, and check outbound sessions and replies. Avoid assuming a pool works without upstream return reachability.
Incorrect Answers
A:Interface-address SNAT uses the selected egress interface address by default. Because that address is not 198.51.100.27, this setting alone cannot guarantee the fixed partner-facing source. Configure a suitable routed public source IP pool in the applicable NAT rule and confirm the translated session.
C:A destination VIP is used primarily to publish internal services to inbound public destinations. It does not automatically select the fixed egress source for all outbound finance API connections. Source and destination translations solve different problems.
D:An address object in the firewall policy describes which original client sources can match the rule; it does not perform address translation. The external API requires the actual post-SNAT source to be 198.51.100.27, selected by an appropriate public IP pool in the effective NAT policy or Central SNAT map.
Question 62
A new web application uses an unusual protocol. Application-control logs classify it as Unknown, while the TCP port alone is permitted. What is the best security inference?
- The application is safe because any unknown signature is equivalent to an approved business application.
- Classify the Unknown protocol as confirmed malware solely from the Unknown application label and block every unclassified client session without investigating visibility or signature coverage.
- Unknown means FortiGate has not positively identified a specific application from the observed session; investigate signatures, visibility and policy handling.
- Increase only the application-control logging level and assume more logs make a previously unknown signature automatically identify the protocol.
Explanation
Correct Answer
C:Application control depends on observed traffic and available signatures. Correlate the session, traffic direction, SSL inspection where applicable, software signature updates and the sensor action. Preserve logs and use controlled tests to decide whether to allow the specific application or restrict unidentified behavior. A safe policy must define how unclassified sessions are treated rather than silently trusting them.
Incorrect Answers
A:Lack of application classification is not a trustworthy allow decision. The flow might be unsupported, encrypted or insufficiently observed. Evaluate the traffic and apply a defined policy for unidentified applications rather than treating unknown as approved.
B:Unknown classification means the observed packets did not match a recognized application signature. It is not independently proof of malware; a legitimate proprietary or encrypted protocol can be unclassified. Investigate signature coverage, inspection and policy before making a proportionate allow or deny decision.
D:Logging provides richer evidence but cannot invent an application signature or decrypt an opaque protocol. Review the FortiGuard signature database, sensor action, traffic visibility and unknown-application policy before trusting or restricting this flow.
Question 63
A two-unit FGCP cluster shows failed heartbeat connectivity between nodes even though their data ports can pass ordinary client traffic. What should the engineer investigate?
- The dedicated heartbeat wiring, HA configuration and monitored member state, recognizing that data forwarding does not prove a healthy cluster control channel.
- Assume successful LAN-to-WAN user packets prove FGCP heartbeat health and skip checking the HA member connection state.
- Enable HA override on both peers to force primary selection.
- Enable session pickup on the current primary and assume state synchronization alone restores heartbeat discovery across a broken cable.
Explanation
Correct Answer
A:HA heartbeat traffic is a control-plane relationship distinct from ordinary firewall forwarding. Inspect heartbeat interfaces, cables or switches, group IDs/passwords, compatibility and HA status. Check for unexpected independent primary roles or split-brain behavior before changes, and restore reliable heartbeat without trusting a data-port ping alone.
Incorrect Answers
B:Normal data-plane traffic can continue independently on a member even when the FGCP control channel is disconnected. It does not prove two cluster units have discovered each other or synchronized config and state; inspect the configured heartbeat interfaces and HA status.
C:HA override influences primary election only among members with a functioning cluster relationship. Enabling it blindly during a broken heartbeat may aggravate unnecessary elections or split-brain concerns. Restore heartbeat connectivity and verify member health before choosing an override policy.
D:Session pickup relies on healthy HA state distribution; it does not substitute for the heartbeat path used to maintain the cluster. Trace heartbeat cabling, switch behavior, peer compatibility and FGCP diagnostics before making service-continuity assumptions.
Question 64
An identity-based firewall policy repeatedly asks an already authenticated browser user to log in during a workday. Which settings and evidence most directly address the problem?
- Turn off every authentication rule so the password prompt disappears globally.
- Increase an administrator GUI idle timeout rather than the end-user firewall authentication session timer associated with the repeated browser challenge.
- Recreate the LDAP server object for every browser challenge.
- Examine the user authentication session, timeout/idle behavior, browser flow and matching identity policy before adjusting scoped authentication settings.
Explanation
Correct Answer
D:Correlate the user identity, policy ID, source IP and authentication logs with session and idle timeouts. Determine whether browser redirects, NAT/IP changes or an overly short auth timer invalidate recognized access. Change only the supported relevant settings, then verify successful authorization and timely expiry.
Incorrect Answers
A:Disabling authentication can stop prompts by allowing unauthorized access, which contradicts a user-restricted policy. Diagnose why the same identity state is not being retained rather than abandon the access requirement.
B:Administrator management-session timeout is distinct from user identity-based firewall authentication. Repeated employee prompts should be correlated with the authenticated user/IP mapping, policy and idle/absolute authentication session timers before any targeted change.
C:The directory might already authenticate successfully while the FortiGate user session expires or remaps when proxy, NAT or browser state changes. Trace the actual auth identity, timeout and policy hit before rebuilding a functioning LDAP integration.
Question 65
An administrator configures a static default route via 192.0.2.1 on wan2, but ARP for that gateway never resolves and traffic cannot exit. What is the first network check?
- Lower the preferred static route administrative distance to prioritize the existing wan2 gateway above backup paths.
- Verify wan2 link state, local subnet membership, L2 adjacency and the actual next-hop address supplied by the ISP.
- Inspect application policy-route selection and explicitly direct the failed client flow to the existing wan2 gateway 192.0.2.1.
- Review stale TCP session entries and clear the affected client flows before reusing the configured wan2 route.
Explanation
Correct Answer
B:A next hop used on an Ethernet segment must be reachable from the relevant interface in the intended topology. Confirm the interface IP/mask, port/VLAN, physical or virtual link and ISP gateway assignment. Use targeted ARP and packet capture to locate failure, then verify the route installation and policy path after fixing adjacency.
Incorrect Answers
A:Route distance determines selection between eligible routes, not layer-two resolution of the selected next hop. The ARP request for 192.0.2.1 is already unanswered, so making the route more preferred leaves the forwarding adjacency missing. Investigate interface addressing, link state and ISP-side gateway presence.
C:A policy route can select a different egress or next hop for a matched flow, but the recorded failure is ARP resolution for that exact wan2 gateway. More steering to an unreachable L2 next hop still blackholes packets. Check subnet mask, link state, VLAN and actual provider gateway first.
D:Resetting sessions may make a new route or policy selection take effect, but a session table entry does not create an ARP reply from the upstream gateway. Before session cleanup, confirm the gateway is on-link and reachable at layer two through the correct WAN interface.
Question 66
Two FortiGate IPsec gateways use IKEv2. One proposes local 10.1.0.0/16 while the partner is configured for only 10.1.12.0/24. Although compatible IKEv2 configurations may negotiate a narrower intersection, the recorded child-SA attempt receives TS_UNACCEPTABLE and no narrowed traffic selector is installed. The intended protected traffic is only 10.1.12.0/24. What should be checked and reconciled?
- Review the established IKEv2 identity and PSK configuration on both sides and renew their authentication secrets before another selector test.
- Propose 0.0.0.0/0 on both peers and let the responder choose the first acceptable child-SA traffic selector.
- Compare the negotiated/rejected IKEv2 local and remote traffic selectors on both peers, use supported selector narrowing where configured, and align each endpoint to the intended protected 10.1.12.0/24 scope.
- Check the phase-two ESP encryption and PFS proposals on each IKEv2 peer, align any differences and repeat the child-SA exchange.
Explanation
Correct Answer
C:IKEv2 supports traffic-selector narrowing in compatible peers; proposing /16 against /24 is not by itself proof every negotiation must fail. Here the observed TS_UNACCEPTABLE and missing child-SA show that no acceptable narrowed selector was negotiated. Compare both endpoints’ local/remote directions and child-SA logs, then align or explicitly permit safe narrowing for the authorized 10.1.12.0/24; verify encrypted traffic and policy afterward.
Incorrect Answers
A:Peer-ID and PSK faults can prevent IKE authentication, but a TS_UNACCEPTABLE child-SA result already demonstrates that the flow reached a traffic-selector decision. Renewing authenticated identities does not reconcile the local and remote /16 versus /24 selector mismatch; use supported narrowing or aligned protected prefixes.
B:Broad traffic selectors can sometimes be narrowed by an IKEv2 peer, but an unrestricted proposal unnecessarily enlarges the authorized scope and is not guaranteed to be accepted by this responder. The required traffic is only 10.1.12.0/24; reconcile direction and the explicitly rejected selectors instead.
D:ESP and PFS agreement is necessary for some child-SA negotiations, so these are credible checks for a generic phase-two failure. The given exchange specifically returns TS_UNACCEPTABLE and never installs the intended narrowed selector. Inspect negotiated local and remote protected prefixes and their peer perspectives first.
Question 67
A FortiGate has a working flow-based antivirus profile and a full SSL inspection profile. HTTP downloads are scanned, but a higher-priority partner-specific outbound policy matches HTTPS downloads with certificate-only SSL inspection. The security team wants HTTPS file scanning for managed endpoints. What is the missing effective-policy dependency?
- Increase the antivirus malware signature threshold on the lower-priority general policy.
- Confirm the actually matched partner policy and apply an authorized full SSL inspection profile with appropriate CA trust and antivirus on that same policy; retest the decrypted HTTPS file.
- Inspect the antivirus profile attached to the original HTTP download policy and increase its scan-size limit for the partner’s large HTTPS files.
- Enable HTTPS session logging on the matching partner rule while keeping certificate-only inspection and assert that the downloaded file is malware scanned.
Explanation
Correct Answer
B:The presence of a full SSL inspection profile elsewhere in configuration is not evidence that this partner session uses it. The higher-priority partner policy performs only certificate inspection, leaving encrypted attachment bytes unavailable to the AV profile. Apply authorized full inspection and suitable antivirus to the effective policy, verify managed endpoint trust, and test actual file events.
Incorrect Answers
A:FortiGate applies security profiles on the policy that actually matches a new session, not on unrelated lower-priority rules. Signature thresholds do not decrypt TLS either. Confirm the HTTPS partner flow policy ID and its SSL/AV attachments before changing any engine sensitivity.
C:File-size thresholds can determine whether a supported scanned transfer exceeds resource limits, so this is a realistic operational check. The named HTTPS sessions instead match a different higher-priority partner policy that uses certificate-only TLS inspection. Enlarging a lower rule’s antivirus threshold cannot decrypt the actual encrypted payload or apply that profile to a policy which never matches.
D:Session logging can show the policy and allowed TCP connection without exposing encrypted file contents to antivirus. The security team needs payload visibility through the effective SSL inspection path and a correctly applied AV profile, not additional log detail alone.
Question 68
A single workstation cannot reach a DMZ server, but others on the same VLAN can. The administrator needs packet-level evidence without capturing the entire network. Which action is appropriate?
- Start an unrestricted debug-flow trace and search the resulting output for the failing workstation address.
- Run a continuous unrestricted capture on every interface for several days.
- Move the workstation's LAN-to-DMZ allow policy above other rules and retry the connection.
- Use a targeted FortiGate packet sniffer or debug-flow filter for the host, server and protocol, and correlate ingress/egress evidence.
Explanation
Correct Answer
D:A FortiGate sniffer filtered to the affected source, destination and protocol can show whether traffic arrives and whether replies return. Pair packet evidence with a flow debug to identify policy selection, route lookup or session disposition. Validate capture vantage points and clear temporary debug settings afterward.
Incorrect Answers
A:Unrestricted flow debugging can produce heavy unrelated output and offers poor specificity for one failing workstation. The question explicitly asks for packet-level evidence without capturing the entire network. Filter the client, destination and protocol, then compare actual ingress and egress packets and policy decisions.
B:Unfiltered captures can consume resources and collect unrelated sensitive traffic. They are also harder to interpret. Use specific host and port filters and bounded capture intervals to locate the failure.
C:Policy order can matter, but the evidence does not show a specific shadowing rule or even prove the client reaches the same ingress as other hosts. Reordering live security policies before a targeted trace may obscure the original cause and affect other users. Collect filtered packet and flow evidence first.
Question 69
An employee changes networks, but FSSO still associates the old IP address with that employee. Another user begins using that address and inherits a group-based policy. What needs investigation?
- Stale FSSO IP-to-user mappings and missing or delayed logoff/update events, followed by correct identity refresh and expiration.
- Increase the FSSO identity-map expiry duration so the old employee remains associated with the shared address even longer.
- Change only the LDAP directory bind password, even though the collector still receives logon events and the stale IP mapping persists.
- Disable FSSO logoff collection because logon-only mappings are more stable when employees roam among networks.
Explanation
Correct Answer
A:FSSO access depends on accurate mapping between user identity, groups and the current source IP. Verify the collector’s logon/logoff inputs, mapping timers and endpoint IP reuse. Expire or correct stale records and confirm that the second user is not authorized as the first. Ensure enforcement remains identity-based rather than a persistent old address guess.
Incorrect Answers
B:Extending expiry can prolong the incorrect user-IP association and grant the second person unintended privileges. Identify which event failed to retire the former user and correct the collector mapping rather than retaining stale state.
C:A wrong LDAP credential can prevent authentication, but the symptom is a current stale passive user-to-address mapping after an IP reassignment. Compare domain logoff events, collector cache and FortiGate connector state before changing a functioning directory bind.
D:Logoff and IP-reassignment signals are important to avoid inherited group permissions on shared or recycled addresses. Suppressing them increases the risk that the next workstation user is assigned a previous identity; instead validate event collection and mapping invalidation.
Question 70
FortiGate IPS logs show repeated exploit signature matches, but the connection remains permitted. What is the most direct configuration check?
- Increase logging detail on the IPS sensor and track new signature events before changing the action assigned to that signature.
- Raise the IPS signature severity filter to Critical while retaining the matching signature’s current Pass action.
- Whether the matching IPS signature action is monitor/pass rather than block, and whether the correct sensor is applied.
- Raise the matching firewall policy priority without changing the effective IPS sensor or its signature action.
Explanation
Correct Answer
C:An IPS signature may be configured to monitor, pass or block depending on profile and override settings. Inspect the actual sensor attached to the traffic policy, signature filter and event action. Test a safe reproduction, then confirm that the expected block occurs without creating false positives for legitimate service.
Incorrect Answers
A:More detailed logs may support investigation, but they do not change a signature configured to Monitor or Pass. The scenario already has matches and permitted sessions; verify the effective sensor and its actual signature enforcement action.
B:Severity filtering selects which IPS signatures are eligible but does not convert an explicitly configured Pass/Monitor action to Block. The observed match must be mapped to its signature action on the actual traffic policy.
D:Policy order determines which firewall policy matches, but the incident already shows an IPS signature match on passing traffic. Moving the rule without correcting the attached sensor action can preserve the same observe-only behavior. Compare sensor override precedence and logs.