Fortinet NSE4_FGT_AD-7.6 Practice Test 34
Question 330
After a FortiOS upgrade, the policy editor displays fewer visible security profile fields. A tester reports that scanning behavior has changed. Which evidence should establish the active configuration?
- Inspect CLI policy profile bindings and flow/proxy mode, then test actual security events instead of relying on GUI visibility.
- Inspect the previous firmware GUI screenshots and recreate the hidden antivirus and SSL profile fields from memory before checking running CLI bindings.
- Review GUI inspection-mode choices and migrate all firewall policies to proxy mode because their previous security selectors are no longer shown.
- Use a screenshot from the old FortiOS policy editor as the sole source of truth for which security profile actions run after the upgrade.
Explanation
Correct Answer
A:After a firmware change, different policy fields or GUI placement can be a presentation issue rather than a change in enforcement. Compare the effective firewall policy, source and destination match, NAT mode and assigned SSL or security profiles in the running configuration. Test a known session and inspect its actual policy identifier and action. Migrate any deprecated setting using the 7.6 guide rather than assuming an old screenshot depicts the current rule.
Incorrect Answers
B:A GUI field moving after an upgrade does not prove the underlying policy or scanner stopped working. Recreating profiles blindly can change effective enforcement and increase outages. Read the current policy and security-profile configuration in the CLI and observe actual new security events first.
C:Inspection mode controls supported features and performance, but a missing GUI field is not evidence that proxy mode is required or supported by every hardware model. Confirm the effective policy’s actual flow/proxy mode, profile bindings and detection logs before considering any targeted mode change.
D:Historical screenshots can document design but not actual current policy state. Verify the CLI, inspection mode and live test logs.
Question 331
The FortiGate shows application-control signatures older than the expected FortiGuard update, although the policy still uses the same sensor. What should be checked?
- Inspect the assigned application-control sensor for a stale override and rebuild the sensor with the same signature filters.
- Remove the relevant application-control rules and rely on a firewall service permit until signatures appear by themselves.
- Verify current FortiGuard application signature update entitlement, database version and sensor signature matches before policy changes.
- Check the policy’s application-control profile attachment and add an identical copy to the next matching firewall rule.
Explanation
Correct Answer
C:Out-of-date FortiGuard application signatures can leave application control unable to recognize newly revised traffic. Check entitlement, update service reachability, current database version and any update or proxy errors. Confirm the correct application-control sensor is attached to the matching policy and that the target application signature is available. Updating an IPS-only database or opening an unrelated firewall rule does not establish application classification is current.
Incorrect Answers
A:A sensor override can change how an existing signature is enforced, but does not refresh the FortiGuard application-signature database itself. The question says definitions appear older than the expected update. Establish license entitlement, update service reachability, installed database version and signature contents before changing a functioning security rule.
B:This loses the intended app-level enforcement. Retain appropriate protection and diagnose FortiGuard license, DNS, route and update service reachability. A service permit does not substitute for application-signature enforcement; keep the sensor while repairing update delivery.
D:Policy attachment matters for whether signatures inspect traffic, but adding another copy of the same sensor cannot cause FortiGuard to download a newer signature package. Compare the FortiGate’s actual database version and update status first, then test whether the desired signature exists and matches.
Question 332
The cluster shared management IP always connects to the primary, so an administrator configures reserved HA management addresses 10.11.101.101 for the primary and 10.11.101.102 for the secondary. A local management-LAN host can log into the secondary, but a trusted jump host on another subnet cannot. The secondary reserved interface has no HA management gateway while the primary does. Which action provides direct remote access to the intended member?
- Enable unrestricted WAN HTTPS administration on the shared cluster interface, then use the primary’s GUI as the access point to edit secondary-only reserved interface counters.
- Use the secondary member’s reserved management IP and configure its own out-of-band management gateway and return route; verify direct remote access from the trusted jump host.
- Force an HA failover to make the previously subordinate unit primary every time a technician needs to inspect its private reserved management interface.
- Disable HA sync and give the subordinate an independent copied production interface address used by the primary.
Explanation
Correct Answer
B:A cluster-shared management address normally lands on the active primary and does not select the secondary. The reserved.102 interface already works locally, proving its listener and local subnet. Configure the member-specific reserved management gateway/return path on the secondary, verify its interface allowaccess and trusted management sources, and test remote SSH/HTTPS from the approved jump host. Reserved management interface IP and related gateway settings are not automatically synchronized; verify each member independently.
Incorrect Answers
A:A shared cluster IP ordinarily lands on the primary and broad public management is unsafe. Use the secondary’s own reserved management address and local route.
C:Disruptive role changes are unnecessary for dedicated per-member management. Configure and reach the reserved address directly while retaining production cluster operation.
D:An address conflict can disrupt traffic or cluster consistency. Use the supported reserved management interface and nonoverlapping addresses. Copying a production IP between members can create conflicts and does not implement an isolated subordinate management path.
Question 333
The enterprise changes its WAN provider and receives a new public IPv4 block. Several published VIPs and outbound IP pools still reference the old addresses. What should be reconciled?
- Change only the WAN default gateway and leave the published VIP external addresses and Central SNAT source pools pointing at the retired ISP prefix.
- Translate every public service to one shared internal server to reduce the effort of editing several VIP objects.
- Disable Central SNAT globally and activate per-policy NAT on every policy to avoid renumbering the existing public translation pool objects.
- Update the WAN interface address, published VIPs and outbound SNAT pools referencing the old ISP block; test both translated inbound services and outbound flows.
Explanation
Correct Answer
D:After an ISP address change, a VIP or outbound IP pool referencing the old public address can silently break inbound publishing or source NAT. Inventory the actual interface address, mapped service ports, external interface binding and any central SNAT rules. Update only objects tied to the obsolete address, then confirm the inbound policy and return route still match the translated flow. Do not widen the published service simply to restore reachability.
Incorrect Answers
A:Routing to a new provider does not automatically rewrite IP literals in VIP and pool objects. Those service bindings must be inventoried and migrated deliberately.
B:Collapsing mappings can break applications and redirect traffic to the wrong host. Maintain each required service's distinct external address, port and destination mapping. Different published services may map to different servers and ports; preserve each explicit translation while updating external addresses.
C:Changing NAT mode is an unrelated and potentially disruptive redesign. The same public pools and VIP external tuples still require valid new-provider addresses.
Question 334
A QA team must establish that a FortiGate IPS sensor blocks a known test signature for one protected service. Production exploit traffic cannot be generated, and the firewall rule alone reports Accept. What controlled test and event correlation would provide credible IPS enforcement evidence?
- Treat an IPS sensor event with Monitor verdict as conclusive proof the test pattern was blocked despite the forwarding policy remaining ACCEPT.
- Test a real exploit against a production server because only damage proves IPS enforcement.
- Generate a safe isolated IPS test signature and correlate its Block/Reset event with policy and packet capture.
- Place a firewall DENY ALL above the lab server and count a failed connection as evidence the specific IPS signature matched and prevented the test pattern.
Explanation
Correct Answer
C:Proving an IPS block requires more than observing a signature name in the database. Build a controlled benign verification case matching a safe, documented detection pattern and the relevant policy path. Confirm sensor attachment, signature inclusion and action, then correlate a FortiGate IPS event with the expected blocked or monitored outcome. Avoid sending a real exploit against production assets or treating the existence of a log entry as proof every packet was dropped.
Incorrect Answers
A:Monitor explicitly allows logging without prevention in relevant FortiOS controls. A test requires the actual effective Block/Reset action and corresponding packet evidence.
B:A destructive production test is unnecessary and unsafe for evidence collection. Use an authorized harmless simulation or test signature in an isolated lab with reproducible logs.
D:A forwarding deny blocks before IPS inspection and proves nothing about a signature. Keep a scoped authorized lab profile that exercises the IPS detector.
Question 335
The routing table contains a learned default route that appears to conflict with the desired SD-WAN member, and an application follows the wrong path. Which evidence is required?
- Change only SD-WAN health probe targets and infer that the learned/static route preference no longer matters for the actual application session.
- Trace the actual learned/static route, policy route and SD-WAN service that selected the observed next hop.
- Review the learned BGP default distance and increase it to make the static route more preferred without checking active policy-route and SD-WAN service matching.
- Inspect the application Internet-service definition and move its ordinary ACCEPT policy higher, retaining the existing policy routes and learned default.
Explanation
Correct Answer
B:When an upstream route and SD-WAN behavior appear inconsistent, inspect the installed forwarding route and the matched SD-WAN service rule independently. Verify next-hop reachability, interface membership, SLA eligibility and any policy routing that can affect the tested packet. Use the source, destination and service tuple from the actual failed session rather than infer behavior from a static configuration listing alone. The chosen egress must be verified in live diagnostics.
Incorrect Answers
A:Health probes are one input; policy routing, installed route origins and SD-WAN service matches can still select egress. Trace the whole path decision.
C:Increasing route distance may change ordinary best-route selection between eligible defaults, but cannot be assumed to override a matching policy route or SD-WAN steering rule for this flow. Verify which mechanism selected the next hop before changing a learned route that may affect other applications.
D:An Internet-service object and forwarding permit can affect application classification and access, but they do not establish why the chosen next hop differs from the requested SD-WAN member. A policy route or an eligible BGP/static default can still steer sessions. Trace route installation, steering-rule match and actual egress.
Question 336
A site-to-site VPN wizard creates a tunnel that passes a quick ping, but the security requirement limits traffic to two named internal subnets. What should be audited before rollout?
- Keep wizard-created broad local/remote selectors and all-network forwarding policies because one successful ping proves that the tunnel permits only authorized subnets.
- Disable the route-based VPN interface and recreate a policy-based design.
- Use a shared all-networks IPsec permit for every remote branch, controlling access only with the individual spoke’s IKE identity.
- Constrain the wizard-generated IPsec selectors, routes and directional firewall policies to exactly the approved subnet pairs and required services; test prohibited adjacent networks.
Explanation
Correct Answer
D:The IPsec wizard can provide a useful initial tunnel but its generated objects and firewall rules must still match the documented segmentation. Check local and remote protected ranges from both peer perspectives, the installed routes and ingress/egress policies/services, and remove broad matches not needed for the two approved networks. Test authorized traffic and a prohibited adjacent subnet independently before the rollout.
Incorrect Answers
A:Reachability to one host does not establish least privilege for all protected prefixes. Audit selectors, routes and directional policy objects against the two approved pairs.
B:Changing architecture may be unnecessary and can disrupt working traffic. Inspect the delivered tunnel objects and permitted flows before choosing a different model. Tunnel architecture should be driven by route and policy requirements; inspect wizard output before replacing a working supported interface.
C:Peer authentication does not automatically constrain authorized internal network reachability. Narrow selectors and forwarding rules must still restrict each site.
Question 337
A FortiGate debug-flow trace says 'Denied by forward policy check' even though an intended allow rule exists. Which matching evidence should be checked?
- Use scoped debug flow to correlate ingress/egress, translated tuple and actual policy lookup before changing rule order.
- Inspect the intended ACCEPT policy’s numerical position and move it before the existing denies without comparing the observed session ingress, route and destination translation.
- Disable the intrusion-prevention sensor on the intended permit and reproduce the failed flow.
- Enable source NAT on the intended permit to change the client address before the forward-policy match.
Explanation
Correct Answer
A:An explicit accept rule does not guarantee a particular flow will select that rule. Capture the actual incoming interface, source and destination addresses, translated VIP mapping, service and policy order from flow debugging. Identify an earlier matching deny, implicit fallback or different VDOM and adjust the narrow condition responsible. Merely moving an accept rule to the top without examining the session tuple can expand access and conceal the real match problem.
Incorrect Answers
B:An earlier ACCEPT policy can fix a true shadowing error when that same policy otherwise matches the traffic. But an existing allow might have an incorrect source interface, destination after VIP processing, service or schedule, so moving it may not change the actual denied flow. The recorded forward-policy-check result needs a scoped debug-flow policy match and translated tuple comparison before reordering.
C:A forward-policy-check denial occurs at firewall policy matching rather than proving an IPS security-profile verdict. Disabling intrusion prevention may weaken protection without making the nonmatching permit eligible. Use filtered flow data, ingress/egress and original/transformed address conditions to find the actual rule mismatch.
D:Source NAT normally occurs after the packet is matched to the appropriate security policy. Adding a translation to an allow rule that does not match the ingress, destination or service cannot make the rule eligible for the first place. Determine the exact forward-policy lookup failure first.
Question 338
A shared kiosk retains a user-authentication cookie after shift change, and the next person inherits the previous worker's access rights. What should be implemented?
- Extend the kiosk authentication cookie lifetime for all shifts so the first worker’s group identity remains cached and no new login interrupts service.
- Expire the old kiosk authentication cookie and require new-user sign-in before applying the next employee group; after invalidating the prior kiosk session.
- Translate the kiosk's source address to a new public IP.
- Assign both shift workers to one common FSSO authorization group and preserve the old cookie while switching users.
Explanation
Correct Answer
B:A kiosk’s shared IP and browser state can retain a previous user authentication cookie after the person leaves. That session can incorrectly authorize the next worker unless explicit logout/session expiry and new identity validation occur. Inspect FortiGate auth session state and group mapping, enforce bounded timeouts and test two different users through a controlled shift change.
Incorrect Answers
A:Longer cookie lifetime perpetuates inherited entitlements when a different user takes the kiosk. Terminate old authentication state and require the new login.
C:NAT does not prove who is now using the workstation. The authentication association must be refreshed independently of address translation. Address translation changes the packet source but not necessarily the browser cookie or FortiGate session identity mapping.
D:A shared group obscures differences in user privileges and does not correct stale session identity. Reauthentication is required at handover.
Question 339
An enterprise-managed browser trusts the FortiGate inspection CA and successfully completes its HTTPS handshake, but an approved portal starts returning a web-filter Block page immediately after FortiGuard reclassifies its hostname. The matching firewall forwarding policy remains ACCEPT, and there are no TLS certificate errors. What should be investigated before weakening SSL inspection?
- Inspect the managed browser’s trust store and reinstall the company FortiGate signing CA used for the inspected website.
- Review the origin site’s TLS certificate expiry and request a new server certificate from its current public issuer.
- Inspect the current web-filter Block/category event and applied profile; keep the already trusted inspection CA unchanged.
- Move the matched HTTPS Accept policy ahead of other rules while retaining its web-filter profile and newly blocked FortiGuard category.
Explanation
Correct Answer
C:The successful TLS handshake and valid FortiGate inspection CA rule out a client certificate-trust problem. The new denied application outcome follows the changed FortiGuard category in the matched profile. Compare the exact requested hostname, rating, profile action and logged policy, then consider a narrow authorized web-rating override if the portal remains approved.
Incorrect Answers
A:Client trust is relevant to TLS certificate warnings, but this browser completed its handshake successfully and then received a category Block page immediately after a FortiGuard reclassification. Reinstalling an already trusted issuer does not change the web-filter rating or its action. Attribute the category event first.
B:Upstream certificate expiry is a valid independent HTTPS failure cause, but the provided evidence includes a valid completed TLS handshake and a FortiGate web-filter Block verdict. Reissuing the origin certificate will not reverse the newly assigned FortiGuard category. Determine the specific category/profile action before making changes.
D:Forwarding acceptance can be followed by a web-filter Block action. Moving the same matching rule leaves its attached security profile verdict unchanged for the tested connection.
Question 340
An approved HR SaaS page loads, but its embedded login widget comes from a second domain that the web filter blocks. What evidence should guide an exception?
- Set the entire blocked category to Allow for HR employees because the embedded widget belongs to an approved SaaS page.
- Disable deep inspection for all HR staff and assume that removes every secondary-domain web-filter decision.
- Identify the widget’s blocked secondary FQDN in matched web-filter logs and narrowly permit its approved dependency.
- Add another URL Allow for the main HR page but leave the secondary login widget hostname on the matched web-filter Block list.
Explanation
Correct Answer
C:A permitted parent page can load scripts, media and API endpoints hosted on different domains with separate FortiGuard ratings. Inspect the full browser request chain and FortiGate web-filter logs to identify the blocked secondary hostname and its matching profile. Correct a justified category or URL override for that endpoint only, then retest the app. Whitelisting the entire parent category may leave unrelated prohibited sites reachable.
Incorrect Answers
A:Category-wide permission can expose unrelated destinations that were intentionally blocked. Identify the specific secondary login widget FQDN and narrowly authorize only the verified application dependency.
B:Transport inspection and URL filtering are different controls. A blocked embedded hostname may still be rated and denied without decryption; diagnose the exact event before changing TLS policy. Switching off inspection for an entire department may weaken security while the secondary hostname still matches a blocked category.
D:The main page already loads, so another Allow for it cannot resolve a distinct embedded hostname denied by the security profile.