Fortinet NSE4_FGT_AD-7.6 Practice Test 15
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.
Question 141
After rebooting two matching FGCP members, the unit with the higher configured priority is not consistently primary. Both units are healthy but the log shows different uptime values; the cluster may have override disabled. Which settings and election evidence should the administrator evaluate before forcing a preferred member?
- Inspect the configured device-priority values on both members and select the higher one as primary after the next reboot.
- Inspect each member’s monitored-port health, uptime, override setting and priority against the FGCP primary-election criteria before deliberately enabling a preferred-primary override.
- Enable override on both units to elevate configured priority above HA operating age, then recheck the elected primary.
- Enable session pickup and validate synchronized session counts as the deciding evidence for the preferred primary.
Explanation
Correct Answer
B:FGCP does not choose the higher numeric priority unconditionally. With override disabled, member uptime and other criteria may affect election; with override enabled, a healthy preferred member can regain primary status subject to the documented order. Compare the cluster primary-selection reason, monitored-interface health and override configuration before making a controlled change and validating failover behavior.
Incorrect Answers
A:Priority is a legitimate FGCP election factor, but it is not the first decisive factor in every override/uptime state. This proposed review does not inspect monitored interface health, HA age, or whether override is configured; the case cannot be resolved from priority alone.
C:Override changes the weight of priority relative to uptime and can be appropriate for an intentionally preferred unit. However, changing the election policy before diagnosing a monitored-link failure and failover logs may mask an impaired member and does not establish why the current election varied.
D:Session pickup supports continuity of eligible sessions during HA failover but is not a primary-election criterion. The operator still needs monitored-port health, override, age, priority and selection-history evidence to explain which unit won the election.
Question 142
Finance VLAN 30 was moved from port3 to a tagged trunk on port5. A policy that permitted its HTTPS sessions now has no hits. Which change should the administrator investigate first?
- Retain the port3 zone on the policy and update only its source address object to the Finance VLAN 30 subnet.
- Match the Finance VLAN 30 subinterface on port5 in the effective policy ingress zone, verifying tag and egress route.
- Insert a higher-precedence policy for Finance traffic that still names port3 as ingress but uses the updated VLAN subnet and HTTPS service.
- Create a temporary policy accepting HTTPS from all VLAN zones to the Finance destination while retaining policy 30 for later review.
Explanation
Correct Answer
B:Moving a tagged VLAN from port3 to a trunk on port5 changes the logical ingress interface that the FortiGate uses for firewall-policy matching. Confirm the new VLAN ID and subinterface, its zone membership, route lookup and existing Finance rule interfaces; then test a fresh HTTPS session and record its policy ID rather than blindly broadening addresses.
Incorrect Answers
A:Address membership alone cannot change the ingress interface on which a policy matches. After moving the Finance clients to a tagged subinterface on port5, their new sessions arrive through that logical interface or zone; a port3-only rule remains inapplicable even with the correct subnet.
C:First-match order matters only among eligible policies. A high-position rule with the old ingress port will not match packets entering on the new tagged VLAN subinterface. Validate the VLAN tag, actual ingress interface or zone and route before selecting the matching permit.
D:A broad interzone permit might restore service but would avoid identifying the changed interface match and expand access well beyond the Finance VLAN. The correct repair maps the actual VLAN interface or zone to the intended existing policy and service restrictions.
Question 143
Headquarters has two route-based IPsec tunnel interfaces to one branch. After the primary tunnel fails, the backup phase-two SA to 10.44.12.0/24 is established, but HQ still has a more-preferred static route for that subnet pointing to the old down primary tunnel. The branch return route and the backup security policies are valid. What should HQ correct?
- Check the backup IPsec SA’s auto-negotiate flag and force a new backup child-SA even though the existing standby association is already established.
- Lower the route distance on the failed primary tunnel's static route to preserve its preferred state during failover.
- Move the headquarters 10.44.12.0/24 route to the healthy backup IPsec interface after primary failure and test forwarding.
- Inspect the backup tunnel’s installed default route and add a higher-preference 0.0.0.0/0 over backup while retaining the failed primary 10.44.12.0/24 entry.
Explanation
Correct Answer
C:The active branch prefix must select the backup tunnel rather than a stale more-preferred route through the down primary. Correct route distance/priority or approved health-based withdrawal so the usable backup path wins. Verify HQ route lookup, IPsec counters, allowed inner traffic and restoration when the preferred tunnel returns.
Incorrect Answers
A:Reestablishing an unavailable child SA may be valid during an actual tunnel negotiation failure. The provided backup association is already up, while the headquarters FIB still favors the failed primary interface. Changing SA initiation cannot repair a route lookup that never selects the healthy backup.
B:The current problem is excessive preference for the dead primary path, not a lack of priority. Lowering its distance would reinforce that erroneous selection and continue blackholing private traffic even though a good backup SA exists. Direct the branch /24 over the healthy interface.
D:A default route can carry otherwise unmatched destinations, but the specific 10.44.12.0/24 still matches first even when its next hop is the down tunnel. Fix that specific protected-prefix route or withdraw it in favor of the healthy backup path; default-route preference cannot override longest-prefix selection.
Question 144
Three branches exchange traffic: A and B need a direct path, but C communicates only with headquarters. The architect proposes full mesh for all peers. Which topology requirement should drive the decision?
- Keep only hub-and-spoke tunnels and tune the headquarters relay path to meet the A-to-B application latency budget.
- Use partial mesh: an authenticated A–B tunnel plus C-to-headquarters hub-and-spoke paths, so the latency-sensitive A–B flow avoids headquarters relay.
- Deploy a full mesh of authenticated IPsec tunnels so A, B, C and headquarters can all communicate directly.
- Use separate hub-and-spoke tunnels plus static routes over headquarters for A-to-B and C-to-HQ traffic, with no branch-to-branch SA.
Explanation
Correct Answer
B:A full mesh would provision unnecessary direct tunnels for branch C even though its requirements are only toward headquarters. The specified A–B direct traffic justifies one additional branch-to-branch link on top of the required hub paths. Validate phase-two protected networks, routing convergence, tunnel credentials and directional policies for both direct and hub flows.
Incorrect Answers
A:Hub-and-spoke minimizes direct tunnels but still hairpins the explicitly latency-sensitive A-to-B flow through headquarters. Without a proved relay path meeting the strict application requirement, this option does not provide the requested direct branch-to-branch path.
C:A full mesh can provide A-to-B connectivity, but it unnecessarily creates direct links to C even though the stated design explicitly needs C only through HQ. Partial mesh meets the specified direct relationship with fewer peer associations and maintenance obligations.
D:Static routing through HQ can reach A and B, but it still lacks the required direct authenticated A-to-B tunnel. The topology requirement is a direct path for that pair, not just eventual reachability through the hub.
Question 145
During a controlled FortiGate deep-inspection CA rollover, managed Windows endpoints have already received and trust the approved NEW inspection CA. However, the common SSL/SSH inspection profile unexpectedly continues signing substitute certificates with the RETIRED CA, which managed clients no longer trust. HTTPS warnings affect all policies using that common profile. What configuration repair is needed?
- Deploy the newly approved enterprise root CA to endpoints again while leaving the FortiGate signing-certificate selection unchanged.
- Switch upstream-certificate validation to an allow-invalid setting while retaining the old FortiGate inspection signing CA.
- Change affected clients to certificate-only inspection and retain the existing antivirus profile for encrypted payload scanning.
- Replace the retired inspection signing CA selected on the FortiGate profile with the newly approved, client-trusted CA.
Explanation
Correct Answer
D:The endpoint trust rollout has already completed; the defect is that the common FortiGate SSL/SSH profile still signs with the retired CA. Select the approved replacement CA on that effective profile, keep its signing private key protected, and verify the managed browsers trust the newly generated substitute certificates. This differs from diagnosing a single high-priority policy using an unintended alternate profile.
Incorrect Answers
A:Endpoint trust-store distribution is important, but the scenario says that installation already succeeded. If FortiGate continues signing substituted server certificates with the retired CA, repeating client deployment will not correct the mismatch; inspect the selected signing CA on the actual inspection profile.
B:Upstream server certificate validation is distinct from the trust of FortiGate-generated certificates on managed clients. Permitting invalid upstream chains reduces security and does not align the FortiGate signing CA with the already trusted new issuer.
C:Certificate-only inspection may avoid substitution certificate warnings, but it cannot give antivirus visibility into encrypted file contents. This violates the requirement to retain payload scanning and does not complete the approved deep-inspection signing CA transition.
Question 146
A tagged guest VLAN works on one switch but fails when traversing the trunk connected to the FortiGate. The firewall rule is unchanged. Which layer should be investigated?
- Check whether the firewall permits the guest VLAN to reach its destination, then expand the firewall policy to accept guest traffic across the trunk.
- Install a more specific guest subnet route with a lower administrative distance toward the WAN gateway.
- Compare the switch-trunk allowed VLAN tags with the guest FortiGate VLAN subinterface, its parent and physical link state.
- Adjust the firewall policy source zone from physical port5 to the intended guest zone without checking trunk-tag consistency.
Explanation
Correct Answer
C:A guest VLAN that works locally but fails at a new trunk may be blocked by switch VLAN membership, tag mismatch or a FortiGate VLAN subinterface bound to the wrong physical parent. Inspect trunk allowed VLANs, PVID/native tagging where relevant, switch MAC learning and subinterface packet counters before changing firewall-policy access. Validate both ingress frames and reply path.
Incorrect Answers
A:Policy selection matters only after tagged frames reach the FortiGate. If the guest VLAN is absent from the trunk or attached to the wrong parent/tag, broadening a security policy cannot restore the missing Ethernet VLAN delivery.
B:The failure occurs on the trunk carrying the tagged guest VLAN before a valid guest packet reaches the FortiGate routing decision. Changing WAN routes cannot repair an omitted 802.1Q allowed tag or mismatched FortiGate VLAN subinterface parent.
D:A zone correction can be necessary after moving VLAN interfaces, but the stated symptom points to the trunk crossing. It cannot substitute for confirming that the switch forwards the guest tag and the FortiGate subinterface is bound to that tagged parent.
Question 147
Central NAT is enabled. A technician ticks NAT on an IPv4 firewall-policy form and expects a new outgoing pool, but traffic still uses the old translation. Why?
- Prioritize the outbound accept policy and select an IP pool using the policy-level NAT option.
- Create a VIP mapping to the proposed public egress address and reference it in the outbound security policy.
- Create a new IP pool and bind it to a second outbound accept rule while leaving the existing Central SNAT table unchanged.
- Edit the matching Central SNAT rule and pool, not policy NAT, after confirming central NAT mode and translation precedence.
Explanation
Correct Answer
D:When FortiOS central NAT is enabled, source NAT is handled by central SNAT mapping rather than an ordinary per-policy NAT checkbox. Review the real matched security policy and the central SNAT rule criteria for both interfaces, source/destination objects and pool selection. Test a new flow and verify its translated source; do not assume toggling an unused per-policy setting changes it.
Incorrect Answers
A:Policy ordering governs forwarding permission, but in central NAT mode source translation is selected through Central SNAT maps rather than the regular per-policy NAT controls. The right egress and source match must be adjusted in that table.
B:A destination VIP implements DNAT for an incoming destination, not the source translation needed for outbound clients. It cannot replace the Central SNAT map that matches the original source, destination, interfaces and appropriate public IP pool.
C:An IP pool alone does not alter an existing Central SNAT rule hit. With central NAT enabled, map ordering and source/egress selectors still determine the translated source. The new pool must be referenced by an actually matching Central SNAT entry.
Question 148
A web-filter profile was added to policy 30, but sessions to a blocked category are recorded under policy 8 and continue. What should the administrator verify?
- Raise the blocked FortiGuard category action to Block in the web-filter profile attached to policy 30.
- Identify the actual matching firewall policy and attach the intended web-filter profile there, correcting selectors or policy order.
- Add a static URL rule for the destination to the web-filter profile on policy 30, then retest new sessions.
- Change policy 8 to a broader destination and service match while leaving its current web-filter profile unset.
Explanation
Correct Answer
B:Security profiles act only when the firewall policy containing them handles the session. Logs identify policy 8 as the actual match, so the web-filter profile attached to policy 30 is not being evaluated. Compare sources, destinations, services, interfaces and order; then make a narrowly scoped correction and confirm blocked-category events under the intended policy.
Incorrect Answers
A:Changing the category in a profile that does not inspect the sessions cannot affect their outcome. The observed traffic matches policy 8, so confirm the rule and its applied security profiles before editing a different policy.
C:A static URL entry would be useful only on the effective policy/profile. The logs identify policy 8 as the matching rule, so the rule bound to policy 30 remains outside the traffic path regardless of the URL pattern.
D:Broadening the rule that already matches sessions can further bypass the intended category controls. Correct the effective policy profile or reorder/narrow the selectors so the intended rule applies, rather than weakening policy 8.
Question 149
A voice SD-WAN rule requires latency below 70 ms and loss below 1%. WAN1 shows 0% packet loss but 110 ms latency; WAN2 shows 45 ms and 0.2% loss. Both interfaces have carrier. What must the administrator consider when determining which link is eligible?
- Select WAN2: its 45 ms latency and 0.2% loss pass the voice SLA; WAN1 exceeds the 70 ms limit.
- Choose WAN1 using the loss metric of 0%, and retain it as the preferred voice member because the physical link is stable.
- Reconfigure the voice health check latency ceiling to 120 ms so WAN1 now passes both measured SLA metrics.
- Use a manual SD-WAN preference rule selecting WAN1 when its interface status is Up, rather than the measured performance-SLA outcome.
Explanation
Correct Answer
A:A performance SLA combines the configured metrics rather than checking packet loss alone. WAN1 has no loss but fails the stated latency requirement; WAN2 meets latency and loss, assuming its measured jitter and reachability are also acceptable. Verify the health-check targets, selected member and actual voice-session egress under the rule’s configured fallback behavior.
Incorrect Answers
B:Zero loss satisfies only one of the explicitly required measurements. WAN1 latency is 110 ms and exceeds the stated 70-ms limit; FortiOS SLA membership must meet the rule’s configured thresholds, not just line state or a single favorable metric.
C:Raising the specified latency objective solely to make an unsuitable path pass changes the voice service requirement. WAN1 remains over the authorized 70-ms target; WAN2 is already within both loss and delay bounds and is the eligible choice.
D:Link-up status cannot establish voice service quality. The case explicitly requires latency under 70 ms and loss below 1%; a manual preference that favors the high-latency member defeats those criteria even though the member is physically operational.
Question 150
A FortiGate-VM autoscale group adds instances, but new nodes do not inherit policy configuration and some report license errors. What should the launch process provide?
- Use a common gold VM image for each replacement instance and rely on launch-time image content alone for active policy and license state.
- Assign the same cloud security group to all newly launched instances and enforce FortiGate policies once the bootstrap has been manually completed.
- Let the autoscale platform join new instances first and complete policy, routing and licensing by post-deployment operator checks.
- Repair autoscale bootstrap so each FortiGate-VM receives its valid license and synchronized security configuration, before each replacement begins accepting production sessions.
Explanation
Correct Answer
D:Auto Scaling starts new VMs but does not ensure they automatically inherit a registered FortiOS license and every intended security-policy object. Review the deployment template, bootstrap script or FortiManager process, FortiGuard license state, configuration version and route insertion for newly added nodes. Test a new instance from launch through traffic inspection and confirm it has identical required controls.
Incorrect Answers
A:A common image can seed a baseline, but dynamic configuration, instance licensing/registration and rule updates require verified bootstrap and synchronization. A static image alone does not establish that newly launched FortiGate-VMs have current configuration and entitlement.
B:Cloud security groups complement FortiGate policy, but they do not distribute FortiOS policy databases or activate licenses. The case needs reliable launch-time policy/configuration and entitlement on every new instance before production traffic is steered through it.
C:Post-launch operational review is useful but does not guarantee newly created nodes are ready before traffic reaches them. The documented failure is inconsistent bootstrap and registration, so automated provisioning and verified readiness are essential.