Fortinet NSE4_FGT_AD-7.6 Practice Test 36
Question 350
An office switches to a different ISP. The FortiGate WAN interface has the new address but cannot reach its upstream gateway or internet sites. What should be verified?
- Retain the previous ISP default-gateway address but lower the route distance to make it the preferred path.
- Inspect egress firewall policy TCP/443 service matching and change its allowed services to ALL for the new provider path.
- Verify the new WAN mask, provider gateway ARP reachability and installed default route after ISP migration; retest provider return routing to both published services and outbound SNAT pools.
- Review Central SNAT public pools and disable central NAT before testing the new WAN subnet and provider default gateway.
Explanation
Correct Answer
C:A newly assigned WAN IP does not prove the interface can reach the ISP next hop. Compare the interface address and mask to the gateway supplied by the new provider, inspect link/VLAN and ARP, and verify the default route points to an actually reachable next hop. Only after upstream reachability is established should the operator review NAT pool ownership and security policies.
Incorrect Answers
A:The old gateway is not shown reachable on the newly addressed WAN interface. A lower distance can make an unusable next hop more preferred while leaving ARP and connectivity broken. Establish the actual new ISP gateway and mask, then verify the default route and permitted NAT return paths.
B:A restrictive service can prevent some client applications after basic routing works, but the symptom here starts with failure to reach the new WAN gateway. Widening policy services cannot repair an incorrect subnet mask or absent ARP adjacency. Verify on-link ISP gateway and installed default route first.
D:IP-pool translation may need updating during a carrier migration to preserve return routing, but neither removing source NAT nor changing its mode makes an off-link upstream gateway answer ARP. Check the new mask, gateway and physical path first, then reconcile allowed SNAT addresses with ISP routing.
Question 351
A user successfully authenticates to LDAP and appears in FortiGate user monitor, but access to a restricted application is denied. Which layer is next?
- Accept the Finance identity group’s successful LDAP bind as proof that the policy will permit the application even when its source interface or service differs.
- Inspect the LDAP server reachability log and increase its bind timeout for the restricted application while preserving the current Finance policy match.
- Inspect the identity-based rule’s actual matched group, interfaces, addresses, service and schedule after LDAP authentication.
- Disable IPS inspection on the denied application flow while leaving the currently unmatched source-zone and destination conditions in the Finance forwarding rule.
Explanation
Correct Answer
C:A successful LDAP bind and an entry in FortiGate user monitor establish identity but not authorization to every application. Correlate the actual source IP and resolved user group with the rule processing the new connection, then inspect the rule’s interfaces, source/destination objects, ports and schedule. Correct only the failed match; do not relax identity restrictions or disable unrelated security profiles.
Incorrect Answers
A:Authentication establishes an identity mapping, but firewall policy also evaluates addresses, ingress/egress, service and schedule. Check the exact denied session tuple and effective policy.
B:LDAP bind timeouts are relevant when authentication attempts stall or fail to complete. This user already authenticated successfully and appears in FortiGate’s monitor, so repeated longer directory timeouts cannot make a mismatched firewall policy source zone, group, service, destination or schedule valid. Trace the applied rule and authorization selectors on the actual session.
D:An IPS sensor cannot be the first cause when the intended firewall rule never matched. Fix policy selectors or identity scope before considering security-profile enforcement.
Question 352
A team requires interfaces for SD-WAN steering and static routing over IPsec, but the deployed VPN was made in policy-based mode. Which architecture better fits the requirement?
- Use route-based IPsec interfaces for the required static routing and SD-WAN steering, with matching tunnel policies; preserve appropriate local/remote selectors and firewall policy directions after conversion.
- Retain the existing policy-based IPsec object and reference its policy name directly in SD-WAN members, assuming that creates a routable virtual tunnel interface.
- Change the peer's encryption proposal until a policy-based tunnel appears as an SD-WAN member in the GUI.
- Create a source NAT pool for every protected subnet and add that pool as an SD-WAN interface without changing the existing policy-based tunnel.
Explanation
Correct Answer
A:A design that expects normal routing-table selection and tunnel-interface firewall policies should use a route-based IPsec interface. Check the generated VPN type, phase-one and phase-two settings, routes for the remote subnet and bidirectional policies before migration. Preserve peer authentication and allowed selectors when replacing a policy-based design. The tunnel establishing IKE security associations does not prove packets can select a virtual-interface route for the protected destination.
Incorrect Answers
B:Policy-based VPN selection is not automatically an addressable route-based interface for SD-WAN and static routing. The architecture must expose the supported IPsec interface.
C:Crypto algorithms do not create the logical interface required by the routing design. Revisit the VPN type and associated route/policy model before adjusting proposals. Cryptographic negotiation does not determine whether an IPsec tunnel exposes an interface; review its configured tunnel mode.
D:NAT address objects translate traffic but are not virtual tunnel interfaces eligible for static routes or SD-WAN steering. Build route-based IPsec and appropriate policies.
Question 353
A FortiGuard category update changes how a previously allowed site is rated. The owner requests an immediate bypass without testing the new classification. What should happen first?
- Review the current FortiGuard category override list and immediately add an indefinite local Allow rating for the owner’s site.
- Pause scheduled FortiGuard web-rating updates on the affected firewall until the website owner completes a review.
- Confirm the changed FortiGuard category and exact Block event, then request reclassification or a reviewed narrow exception.
- Change the outbound firewall service from HTTPS to ALL while retaining the effective web-filter profile whose newly assigned category now Blocks the site.
Explanation
Correct Answer
C:FortiGuard category ratings can be updated independently of local firewall-policy edits. For an affected URL, record its current rating, the category and action specified by the applied web-filter profile, and any local or FortiGuard override. Compare the observed log with the timing of rating changes. If business use is legitimate, apply a narrow documented exception and monitor it; do not globally disable the filtering category without testing unrelated sites.
Incorrect Answers
A:Local web-rating overrides can handle an approved reclassification error, but making one permanent before verifying the new category and actual Block log defeats the requested review gate. Establish why the site changed, confirm legitimate business need and use a narrowly approved exception with reassessment or submit a FortiGuard reclassification.
B:A global update suspension can affect unrelated site ratings and security intelligence, and it does not prove why this particular hostname was blocked. The right first step is to inspect the effective web-filter category and action, evaluate reclassification, and document any limited business exception.
D:A wider service permit cannot supersede a subsequent web-filter category Block. Review the rating change and approved narrow override instead.
Question 354
FortiGate WAN2 obtains its ISP address and gateway by acting as a DHCP client, but that lease stops renewing after a provider change. Port4 continues serving valid DHCP leases to LAN workstations. Which distinction should the administrator make to diagnose the WAN failure?
- Expand the port4 LAN DHCP server lease range and reset its client lease database.
- Configure WAN2 with the address and gateway from the last known successful ISP DHCP lease.
- Review LAN port4 DHCP server lease timers and extend the workstation renewal interval to match the ISP’s updated address lease duration.
- Troubleshoot WAN2 as a DHCP client: inspect its current lease, renewal packets and learned ISP gateway, without changing the unrelated port4 LAN DHCP server.
Explanation
Correct Answer
D:WAN2 obtains its own address and next hop as a DHCP client from the ISP, while port4 supplies leases as a DHCP server to internal workstations. These are separate FortiGate interface roles. Use interface status and DHCP client packet/lease evidence to diagnose the failed renewal, then validate the new gateway and internet routing. Do not change the functioning port4 DHCP scope.
Incorrect Answers
A:Port4 is demonstrably issuing valid addresses to internal workstations. Changing its server scope does not affect WAN2's separate DHCP client transaction with the ISP or the learned upstream gateway. Troubleshoot renewal packets and lease parameters on the actual failing WAN interface.
B:Temporarily static addressing a DHCP interface can sometimes help isolate a provider issue, but reusing an old lease after a provider migration may conflict with its new allocation and gateway. It does not diagnose why the current DHCP offer or renewal fails. Examine WAN2 client exchange first.
C:LAN DHCP server and WAN DHCP client share protocol vocabulary, but manage opposite roles on different interfaces. Longer leases for workstations on port4 have no effect on wan2 obtaining and renewing the provider-assigned address and learned gateway. Diagnose WAN2 DHCP discover, offer, request, acknowledge, renewal timing and actual next-hop address instead.
Question 355
A new payroll-zone policy was cloned from a guest-zone allow rule. The destination and HTTPS service look right, but payroll packets never hit it. Which attribute requires careful review?
- Reuse the cloned guest-zone source-interface selector and update only the payroll source address object to include the Finance payroll VLAN.
- Compare the cloned firewall rule’s source interface or zone with the payroll VLAN’s actual ingress, and correct that selector while retaining the intended payroll address, HTTPS destination and service constraints.
- Change the cloned policy’s HTTPS service object to ALL while retaining the stale guest-zone ingress interface and leaving the payroll VLAN’s actual source-interface match uncorrected.
- Inspect the cloned payroll HTTPS rule and add a more permissive destination service group while leaving the old guest-zone source interface intact.
Explanation
Correct Answer
B:A copied firewall policy retains more than a name. Compare the clone's incoming and outgoing interfaces, source and destination objects, user conditions, services, schedule, action, NAT and security profiles with the proposed new access path. Verify its order relative to existing rules before enabling. A cloned policy referring to the old source zone can fail to match or accidentally authorize a broader path; changing only the display label is insufficient.
Incorrect Answers
A:An address match cannot compensate for the wrong physical or logical ingress zone. The cloned policy must match actual payroll traffic interfaces and authorized service.
C:Broadening service match cannot make a packet arriving on the payroll-zone interface match a rule still tied to the old guest zone. Compare cloned ingress/egress interface, address, schedule and service against a fresh payroll session, and correct the exact failed condition.
D:Service mismatches can certainly prevent a new flow from matching a firewall rule. Here HTTPS service and destination are already correct, while the rule was cloned from another zone and never receives payroll packets. Broadening permitted services increases exposure without fixing the actual ingress interface or source-zone selector. Correct those copied match conditions and test a fresh payroll client flow.
Question 356
A test browser session was allowed by the firewall rule but then denied. The same policy has both web-filter and application-control profiles. What evidence identifies which engine blocked it?
- Inspect the web-filter event for the browser’s destination and change that website category to Monitor on the matched policy.
- Remove both profiles to see whether access returns, then leave them disabled.
- Review the application-control sensor version and temporarily switch its matching application signature from Block to Monitor.
- Correlate the same session’s web-filter category and app-control signature verdicts to identify the blocking security engine.
Explanation
Correct Answer
D:When web filtering and application control are both attached to a policy, a blocked request needs attribution to the actual profile that enforced it. Correlate the traffic log and policy ID with web-filter category/action events and application signature/action records. Determine whether the failure was a URL classification, app signature or another inspection layer, then change the narrow responsible rule. Disabling both profiles would prevent distinguishing and repairing the actual cause.
Incorrect Answers
A:The firewall has both web-filter and application-control enforcement. A web event may reflect a rating without being the final blocking action; an application signature could independently deny the same session. Correlate action, signature and session identifiers for both engines before modifying one profile.
B:Disabling both simultaneously obscures causality and opens broad risk. Use matching event evidence and controlled profile-specific tests to identify the actual block. Removing both profiles makes the session work but leaves security disabled and does not identify which action caused the deny.
C:A signature action change could restore access when application control caused the denial, but the evidence has not yet identified which of the two attached profiles blocked the browser session. Changing enforcement before matching the exact web-filter and app-control log actions risks allowing a prohibited application.
Question 357
Nightly uploads saturate the low-jitter WAN path reserved for voice calls, while broadband has spare capacity. Which SD-WAN strategy is appropriate?
- Steer scheduled bulk uploads onto the voice-preferred low-jitter member because its delay measurement is currently the best of all SD-WAN paths.
- Review the bulk-upload SD-WAN service’s SLA settings and relax its jitter tolerance until the upload sessions qualify for the low-jitter voice WAN member.
- Steer scheduled uploads over eligible broadband members using a separate SD-WAN rule, reserving low-jitter path for voice; test call quality while the bulk upload rule runs concurrently.
- Remove application matching from the SD-WAN policies and distribute voice and uploads through the same default load-balanced pool based only on member link state.
Explanation
Correct Answer
C:If bulk uploads saturate a low-latency voice link, classify the two workload types using supported SD-WAN service matches and steer uploads to suitable broadband members when those members satisfy the intended SLA. Check route eligibility, member health, and session placement during a realistic simultaneous upload and call. Simply increasing the default bandwidth estimate or disabling voice protection does not ensure appropriate per-application egress or congestion behavior.
Incorrect Answers
A:Voice quality needs isolation from large transfer congestion; choosing the lowest-jitter link for bulk traffic recreates the saturation. Match applications separately and steer uploads to eligible broadband.
B:SLA threshold changes control which members are eligible after an SD-WAN service matches, but making bulk transfers eligible for the voice-preferred path defeats the goal of reserving capacity for calls. The alternative broadband member has spare capacity; use a separate application or schedule-matched service rule to steer bulk uploads there and validate concurrent voice quality.
D:Equal shared selection cannot reserve low-jitter capacity for calls or select high-bandwidth paths for uploads. Use distinct services with measured member criteria.
Question 358
A route-based IPsec tunnel is established but packets toward the protected subnet leave the physical WAN instead of the tunnel interface. Where should diagnosis start?
- Rotate the phase-one IKE PSK even though the child-SA is already established and the protected application packets are routed out the physical WAN.
- Increase the tunnel's phase-two lifetime so its route is chosen even when a more preferred path exists.
- Correct actual protected-prefix forwarding from physical WAN to the intended IPsec interface before changing IKE settings.
- Create a broad physical WAN Accept for the remote protected subnet, leaving its selected egress outside the established IPsec interface.
Explanation
Correct Answer
C:An IPsec interface can show an established tunnel while user packets leave through a different route. For the failing remote subnet, inspect installed static or SD-WAN routes, policy-route matches, the tunnel interface and directional firewall policies. Compare the packet's actual outgoing interface to the intended VPN path, then correct route selection and return reachability. Recreating IKE proposals will not fix a forwarding decision that never chooses the encrypted interface.
Incorrect Answers
A:Credentials do not choose the forwarding interface after establishment. Correct the protected-prefix route or policy/SD-WAN steering to the IPsec tunnel.
B:SA duration is distinct from RIB/FIB selection. The egress mistake must be corrected in routing or steering configuration, not by changing the security-association timer. A longer SA lifetime does not override route preference; use the correct installed destination route to the tunnel.
D:A forwarding permit for the wrong interface is not equivalent to encrypted transport. The route must select the tunnel and match protected selectors and policies.
Question 359
An FGCP subordinate periodically disconnects from the primary during voltage drops and then rejoins, causing fresh primary elections. The heartbeat switch reports interface errors, but an operator proposes enabling override on both peers. What should be diagnosed before changing election preference?
- Enable HA override to make the preferred member win every election while continuing to experience heartbeat resets and voltage-induced physical instability.
- Inspect HA device priority and assign the recovered subordinate maximum preference while retaining its intermittent power and heartbeat errors.
- Inspect subordinate power stability, heartbeat errors and FGCP event history before modifying primary election preference, while preserving monitored-interface protection.
- Review the noisy HA heartbeat switch statistics and extend detection timers while leaving damaged cabling and voltage fluctuations unresolved.
Explanation
Correct Answer
C:A subordinate that repeatedly loses voltage or heartbeat links can leave and rejoin the FGCP cluster, causing elections independent of the configured priority preference. Check logs around power drops and switch error counters, correct the faulty physical path and verify synchronization. Changing override without addressing member health may worsen failover churn and does not repair a failing power supply.
Incorrect Answers
A:HA override influences election preference but cannot restore missed heartbeat packets or prevent power-induced member resets. Changing priority while voltage instability persists masks the fault; inspect PSU events, heartbeat switch-port errors and monitored-interface status before considering an election-policy adjustment.
B:Primary priority influences FGCP election under supported health conditions, but a node with unstable power or heartbeat can repeatedly leave and rejoin. Giving it preference can amplify interruption rather than fix the cause. Diagnose actual supply and interface errors, then validate stable elections before tuning override.
D:A timer adjustment can help narrowly evidenced transient packet loss, but it can also delay detection of a genuinely failed peer and does not correct physical-power instability. Correlate power events, heartbeat CRCs and FGCP transitions and repair the physical source before changing failover sensitivity.
Question 360
The certificate authority used for TLS deep inspection has a private key on the FortiGate. An audit asks how to protect it. Which control is material?
- Distribute the FortiGate SSL-inspection CA certificate and its private signing key together to every managed workstation to avoid future trust prompts.
- Grant all firewall operators unrestricted certificate-export rights to simplify replacement during an outage.
- Protect the SSL-inspection CA private key with least privilege, audited backups and controlled rotation with managed-client trust.
- Set an extremely long inspection CA certificate lifetime and disable signing-key access auditing to reduce the maintenance workload during renewals.
Explanation
Correct Answer
C:A FortiGate SSL inspection CA private key can sign substituted certificates and must not be distributed to clients. Restrict which administrative profiles can manage certificates, protect configuration backups and key material, monitor changes, and document controlled rotation/revocation if the key is compromised. Roll over the trusted public CA through endpoint management and test inspected applications while keeping the signing key protected.
Incorrect Answers
A:Only the public trust certificate should be distributed; the private signing key must remain protected under tightly controlled access and backup policies.
B:Broad access to the inspection signing key increases the risk of impersonation. Restrict administrative roles, enforce secure backups and validate approved key rotation procedures. Unrestricted private-key export rights expand compromise risk; restrict cryptographic key custody and audit access.
D:Long validity and absent auditing increase key-compromise impact without removing safe rotation requirements. Use protected custody, audited access and scheduled replacement.