Fortinet NSE4_FGT_AD-7.6 Practice Test 27
Question 260
A security engineer changes an application-control signature from Monitor to Block but an already established session still passes. What should be tested?
- Inspect the updated signature setting in the Application Control GUI and reload the profile on the existing firewall policy.
- Review the FortiGuard application-signature package version and schedule an immediate database update for the same sensor.
- Retest a new session under the updated application-control Block action and compare its verdict with the existing cached session.
- Disable session tracking globally so all active applications are instantly rescanned against the new signature.
Explanation
Correct Answer
C:An existing application session may retain classification or policy state after a sensor edit, so a new connection is needed to evaluate updated enforcement. Confirm the selected application-control sensor, signature ID, old session creation time and new action in the current policy. Establish a fresh test session, compare its actual block/monitor action and logging, and document whether clearing old state is necessary.
Incorrect Answers
A:Confirming the saved profile is useful, but a GUI reload does not establish whether a previously classified session was re-evaluated after the Monitor-to-Block change. Start a fresh matching flow and compare its signature action and logs with the older session state before resetting unrelated active connections.
B:An outdated signature definition can affect recognition, but the observed issue is an administrator changing an already identified signature action. Updating definitions does not by itself guarantee retroactive blocking of an established session. Test a newly created flow against the saved Block action, then decide whether targeted state cleanup is necessary.
D:Removing stateful controls introduces major security and stability risk. Use a controlled session reset if justified, along with a new-session validation test. Establish a fresh test session, compare its actual block/monitor action and logging, and document whether clearing old state is necessary.
Question 261
Several non-domain tablets cannot produce AD logon events, but their employees need controlled access through FortiGate. What should be considered?
- Assign each tablet to a static FSSO identity using its DHCP reservation, keeping AD logon agent collection disabled for those nondomain devices.
- Allow all tablets unconditionally because FSSO is unavailable, treating device presence as authorization to internal applications.
- Configure the DC FSSO agent to associate the tablet’s MAC address with the employee’s AD group even though the tablet never logs into Windows.
- Use supported interactive captive, LDAP or RADIUS firewall authentication for nondomain tablets with real user-group authorization.
Explanation
Correct Answer
D:A non-domain endpoint may not generate an AD logon event FSSO can collect; use a supported captive portal, RADIUS or other authenticated mechanism appropriate to its identity context. For nondomain tablets, use a supported captive portal, RADIUS/LDAP or another approved interactive identity integration rather than synthesizing Windows DC logon events. Confirm each employee's policy identity and device posture independently of an FSSO collector.
Incorrect Answers
A:IP reservations do not prove who is currently operating a tablet or which directory group should authorize a session. Nondomain endpoints need a supported interactive authentication and policy match, not fabricated passive logons.
B:That removes identity-based restrictions. Select an appropriate alternative authentication method and enforce the required user/group access policy. A tablet IP identifies a network attachment, not an authorized employee; apply per-user credentials and the intended group policy.
C:DC-based passive identity requires actual suitable logon events; an observed MAC address cannot substitute for user credentials or group proof. Use a captive portal or supported RADIUS/LDAP firewall authentication.
Question 262
A file-upload application sends documents from a guest subnet into an internal service. Antivirus is present on a different download rule, but upload records show no scanning. What must be reviewed?
- Attach supported antivirus scanning to the actual guest upload policy and protocol, then verify that direction’s verdict log.
- Inspect the upload service’s protocol-options maximum size and raise the accepted file limit on the guest-to-server policy.
- Review the internal upload URL category and apply a static Allow entry for the approved endpoint.
- Disable all guest uploads permanently without first checking whether a narrow AV policy can protect the approved service.
Explanation
Correct Answer
A:FortiGate inspects traffic using the security profiles on the rule matching the actual session. A separate download rule does not automatically protect files uploaded from guests. Trace the source/destination, ingress/egress, protocol and policy ID, select supported upload AV scanning and decryption where needed, and test a harmless detection file without assuming every file type is scannable. Preserve legitimate upload capability and review size/oversize limitations.
Incorrect Answers
B:File-size limits influence scanning only if the upload transport is supported and its effective firewall policy actually applies the antivirus profile. Here AV is attached to a different download rule, so changing the guest upload size limit leaves the missing security-profile coverage unresolved. Test the correct direction.
C:Allowlisting an upload destination can help policy access, but it is not equivalent to antivirus file analysis on the guest-to-server session. An unrelated download rule cannot scan this traffic. Select a supported AV profile and protocol on the actual upload rule and confirm its file verdict.
D:A total block may violate the intended application requirement. Evaluate protocol-specific scanning, file type handling and a controlled fallback for unscannable uploads. The business permits some guest uploads; implement a narrow inspected path with file handling and rejection for malicious payloads.
Question 263
Several administrators edit different policies on the same FortiGate, but change records do not identify owners or previous settings. What governance control should be introduced?
- Use one shared administrator account with an individual change-ticket field on every policy edit, avoiding the need to add FortiGate named accounts.
- Disable configuration change logging to reduce management-plane load while allowing concurrent edits.
- Enable detailed forwarded-traffic session logs for policies being edited and reconstruct administrators from the client source addresses in those events.
- Use named scoped FortiGate administrator accounts with configuration-change auditing and recoverable versioned backups.
Explanation
Correct Answer
D:Give each FortiGate administrator an individually accountable account with an appropriately scoped administrative profile. Enable and retain configuration-change audit records and tested revision backups so concurrent edits can be attributed to the correct operator and restored. Record administrator identity, change time, affected object and pre/post configuration as available through supported logging or revision controls. Reproduce two concurrent edits in a controlled window and verify the audit can distinguish both authors rather than a shared super-admin identity.
Incorrect Answers
A:External tickets can add context but do not reliably attribute system actions when everyone signs in with the same identity. Named restricted accounts and native configuration auditing are required for defensible actor history.
B:Removing audit records makes it harder to attribute conflicting changes. Establish a revision and approval trail, with snapshots or backed-up configurations for rollback. Change logs and revision records are needed when two editors work concurrently, especially to distinguish overwrites from intentional edits.
C:Forwarding session records identify traffic, not necessarily who changed device configuration or prior policy values. Retain admin login/configuration-change events and protected revision backups.
Question 264
A newly added deny rule for a prohibited subnet never gets hits; debug flow shows an earlier broad permit matches those packets. What is the safest policy-order repair?
- Inspect the proposed subnet deny and add a more specific host-deny beneath the existing broad ACCEPT rule.
- Move the confirmed subnet deny above its shadowing broad permit, then test prohibited and unaffected new sessions.
- Disable every existing permit temporarily so the new deny must be the first active rule.
- Review the IPS sensor on the earlier ACCEPT rule and block the prohibited subnet using an application signature exception.
Explanation
Correct Answer
B:An earlier broader ACCEPT policy can shadow a later targeted policy; examine policy lookup and hit counters, then adjust ordering without broadening access. The earlier broad permit shadows the new deny rule for the prohibited subnet. Verify the precise source, service and matched policy ID, then position a narrowly scoped deny ahead of the catch-all and retest legitimate neighboring traffic.
Incorrect Answers
A:The earlier general permit already matches the prohibited source before any lower rule is reached. Additional specificity below that permit does not correct shadowing in ordinary ordered firewall policy lookup. Move the validated subnet deny above the broad rule, then test new permitted and prohibited connections.
C:Blanket shutdown interrupts unrelated legitimate sessions and hides which rule caused shadowing. Use policy lookup and an explicitly scoped ordering change instead of taking down the whole rule base. Disabling every permit introduces a general outage; reorder or narrow the specific catch-all rule and verify the intended deny hit.
D:Application control can restrict classified applications, but the requirement is to deny a source subnet regardless of application. The earlier forwarding permit would still match before the new lower deny, and signature coverage cannot substitute for source-address authorization. Correct the policy ordering and verify the targeted subnet.
Question 265
A business wants traffic from Finance clients to prefer ISP-A while warehouse clients use ISP-B, even when both access the same destination IP. Which routing mechanism should be considered?
- Steer Finance and warehouse by distinct source-subnet SD-WAN rules or supported policy routes to their assigned ISPs.
- Add two equal-destination static default routes with different administrative distances and expect the route table to choose a link based on each packet’s source subnet.
- Change the destination prefix mask for ISP-A so users with a Finance source IP will automatically take the new route.
- Lower the ISP-A SD-WAN member cost globally while retaining only a destination-based catch-all service rule for both departments.
Explanation
Correct Answer
A:Ordinary destination-based routing sees the same target prefix for both groups and cannot select a path solely by the internal source. Create narrowly matched policy-routing or SD-WAN source criteria with the required interface/member and gateway, preserve applicable firewall/NAT policies, then test both source networks to the same destination and verify egress selection.
Incorrect Answers
B:Ordinary destination routing does not make a source-based distinction between Finance and warehouse clients sharing the same destination. Configure supported source policy routing or SD-WAN service selection.
C:Destination masks constrain destination matching, not which internal client initiated traffic. This risks misrouting other users and does not represent the source-aware business rule. Changing a destination mask selects by target prefix, not the Finance client address; match source policy in SD-WAN steering.
D:Global cost can favor one link for all matching traffic, not express different user-group egress choices. Source-subnet match conditions must distinguish Finance from warehouse.
Question 266
Two site-to-site tunnels lead to different peers, but the branch's application subnet is routed through the wrong tunnel after a new default path is installed. Which selection should be reviewed?
- Inspect the static route to the protected application subnet and reduce the numerical priority of the currently selected wrong tunnel.
- Review the two child-SA protected selectors and broaden each tunnel to encompass the full application subnet on both peers.
- Check installed protected-prefix routes and policy/SD-WAN overrides, selecting the correct tunnel for this subnet.
- Delete all explicit remote-prefix tunnel routes and trust the default ISP route to carry traffic securely over whichever IPsec SA is established.
Explanation
Correct Answer
C:Competing routes to a protected peer can select the wrong logical tunnel; inspect installed route distance/priority, SD-WAN eligibility and effective session egress. For the affected application subnet, inspect the longest matching route, distances, policy routes and any SD-WAN tunnel steering that selects the wrong peer. Confirm the intended tunnel's protected prefixes and symmetric return path before changing IKE authentication.
Incorrect Answers
A:A lower priority number can strengthen a route’s preference when competing routes share distance, but this would favor the very tunnel already handling the wrong destination. The correct protected-prefix route must select the intended peer, after considering possible policy-route and SD-WAN overrides.
B:Selectors determine which inner prefixes a child SA can protect, but they do not guarantee the forwarding table chooses the correct tunnel for this destination. Overbroad selectors may also overlap unnecessarily. Resolve the actual installed route and higher-priority steering rule, then ensure selector and firewall-policy coverage for that path.
D:An ordinary internet default does not inherently select a protected route-based tunnel; removing specific routes can send private traffic outside VPN. Preserve a valid prefix route and matching selectors/policies.
Question 267
A critical vulnerability advisory is published for a service exposed through FortiGate. The security team wants to know whether IPS mitigates its exploit. Which check matters?
- Inspect the vulnerable service’s FortiGuard application category and enable a web-filter Block for its software publisher website.
- Map the advisory CVE to an enabled blocking FortiGuard IPS signature on the effective exposed-service policy and test safely.
- Review the IPS sensor’s Critical-severity filter and enable all matching severity signatures on the published server policy.
- Use a firewall ACCEPT log as proof that IPS has mitigated the advisory.
Explanation
Correct Answer
B:A FortiGuard URL category is not an exploit signature; examine relevant IPS coverage, database version and matched sensor for a newly disclosed vulnerability. Map the vulnerability's affected software and exploit behavior to a current FortiGuard IPS signature, sensor assignment and blocking action for the exposed service. A FortiGuard web-category label by itself cannot demonstrate exploit mitigation.
Incorrect Answers
A:A web-filter category acts on browsing destinations and does not demonstrate mitigation of a network exploit targeting the published server service. Map the CVE to an actual enabled IPS signature with the correct block action and policy attachment, then perform authorized non-destructive validation of its applicability.
C:A severity filter can select many exploit signatures, but it does not prove this CVE has a corresponding signature, that its protocol decoder can inspect the traffic, or that the effective action blocks it. Match the actual advisory to a signature ID and service scope with safe tests.
D:A permit record is not an exploit detection or block receipt. Confirm signature ID, profile attachment and post-update behavior on a safe test. A firewall ACCEPT record establishes forwarding permission but not whether a configured IPS signature actually detected or blocked an exploit.
Question 268
Forensics needs visibility at the start of newly accepted sessions, but the FortiGate logs only after a session finishes. Which behavior should be changed?
- Enable log-at-session-start on the accepted policy and verify event timing and remote collector delivery.
- Lower the accepted-session idle timeout so connections close sooner and generate their existing end-of-session event.
- Inspect the existing end-of-session traffic log setting and disable policy traffic logs on the high-volume ACCEPT rule to reduce collector delay.
- Increase FortiAnalyzer ingest capacity so received end-of-session logs appear in search more quickly.
Explanation
Correct Answer
A:A policy that logs only on session completion may not produce evidence until long-lived sessions end. For the forensic requirement, enable the FortiOS start-of-session traffic logging option where supported on the actual matched rule, validate the logging destination and compare start/end entries for one test session. Account for increased log volume and avoid confusing an early Accept record with proof that later application payloads were harmless.
Incorrect Answers
B:Earlier session-end events may shorten a logging delay for idle flows, but do not satisfy the requirement to record when a new connection begins. Enabling and validating the supported start-of-session log behavior on the correct accepted policy is distinct from shortening session lifetime.
C:Reducing log volume can improve throughput under proven collector overload, but disabling the only generated policy events cannot create the requested immediate start-of-session evidence. The FortiGate currently logs at the end. Enable supported start logging on the correct matched rule and verify both generation timestamp and delivery; only then tune throughput and retention if needed.
D:More collector throughput may reduce delivery latency after FortiGate generates an event, but it cannot create a start log that the policy never emitted. Confirm the actual policy's log-at-session-start behavior and then measure forwarding and indexing time at the authorized log destination.
Question 269
A published HTTPS VIP responds to clients in every country, but policy permits should restrict access to a small approved partner network. What is the right separation?
- Remove source restriction from the public VIP mapping and trust the mapped internal address/HTTPS port to reject nonpartner clients before firewall-policy matching.
- Restrict the inbound WAN-to-VIP policy to the approved partner source subnet and HTTPS, preserving DNAT.
- Apply only a web-filter country category to the server response.
- Assign the partner a dedicated outbound source-NAT pool so server replies use that public IP, expecting this to prevent unrelated countries initiating inbound VIP sessions.
Explanation
Correct Answer
B:A public VIP translates inbound destinations but does not restrict who can connect; narrow the associated forwarding policy to the approved geographic or source address scope. A public VIP maps the destination, but the associated WAN-to-DMZ policy must separately restrict the allowed partner source addresses. Validate inbound rule order and translated destination while confirming other internet clients remain denied.
Incorrect Answers
A:A VIP translates destination addressing but does not by itself impose the approved partner-source authorization boundary. Restrict the inbound firewall policy sources while preserving its correct DNAT mapping.
C:Web classification is not a substitute for a source network permit boundary. Enforce the intended source matching in the firewall policy before delivering the server session. An outbound web-category rule does not replace the inbound firewall source-address condition used to authorize partner traffic.
D:Source translation on replies does not replace access controls on incoming client source addresses. The WAN-to-VIP policy must require the approved partner network and service.
Question 270
A partner's HTTPS server presents a self-signed certificate that is not in the trusted issuing-store. The FortiGate inspection path rejects it. How should the exception be evaluated?
- Check the selected SSL inspection profile and permit invalid certificates for the partner’s entire group of HTTPS domains.
- Replace the server's public DNS entry with a private IP.
- Validate the self-signed partner identity and explicitly approve trust for that certificate, or keep the TLS connection denied.
- Import the partner server certificate into the FortiGate trusted certificate store and apply the same trust rule to every HTTPS origin.
Explanation
Correct Answer
C:Self-signed server certificates lack a public CA chain by default; that does not automatically mean a legitimate internal service is unsafe, nor is it sufficient evidence to trust it blindly. Verify the expected hostname and out-of-band certificate fingerprint, apply a supported explicitly trusted CA/certificate only under approved policy, and retest the connection while retaining normal verification for unrelated destinations.
Incorrect Answers
A:Invalid-certificate exceptions can restore connectivity, but this broad domain group extends trust beyond the one specifically self-signed server. The actual identity and certificate ownership need independent approval, or the connection should remain denied. A blanket upstream-validation bypass exposes unrelated sites to substitution.
B:Routing and DNS changes do not validate the certificate's issuer, hostname or expiry. Certificate trust must be addressed independently of the path used to reach the server. A DNS address rewrite does not establish the remote server certificate identity or trusted issuer required by TLS validation.
D:A deliberately pinned and verified self-signed certificate can be trusted for a bounded partner service, but generalizing that trust to all HTTPS destinations is excessive. Validate its subject, SAN, owner and intended endpoint, then scope the exception rather than accepting unrelated certificates.