Fortinet NSE4_FGT_AD-7.6 Practice Test 10
Question 90
An FGCP active-passive pair is scheduled for a controlled failover. Administrators want existing supported sessions to continue as smoothly as possible. What configuration and test are needed?
- Enable session pickup on two FortiGates running incompatible firmware that are not members of the same synchronized FGCP cluster.
- Disable heartbeat connectivity just before failover, assuming any manually promoted device can reconstruct established session state without synchronization.
- Confirm supported session-pickup/session synchronization settings and verify session continuity under a controlled failover.
- Enable HA override and increase priority on the secondary, but do not enable supported session synchronization or test the application sessions.
Explanation
Correct Answer
C:Configure session pickup where supported for the application and cluster design, verify HA state/configuration synchronization and monitor protected interfaces. Use a controlled failover test with representative TCP sessions and application checks; some protocols and sessions may still reconnect, so document observed limits rather than promise universal zero-loss.
Incorrect Answers
A:Session pickup requires a supported synchronized cluster. Incompatible versions or nonmembers cannot be assumed to share coherent session state merely because the setting is selected. Verify FGCP health and supported model/firmware first.
B:Heartbeat and synchronization maintain cluster awareness and state exchange. Severing the heartbeat can create dual-primary risks, and a new primary cannot infer all established session details without a valid pickup mechanism.
D:Override and priority influence primary-member election, not necessarily established TCP state continuity. Confirm compatible session-pickup settings and synchronization, then perform a controlled failover with real applications and measured interruption.
Question 91
A firewall rule intended for a small application group unexpectedly permits a new guest subnet. Investigation shows the source address group includes nested objects. What should be done?
- Inspect and correct the nested group membership so only intended CIDR objects are included, then verify actual policy lookup.
- Inspect the contractor-specific deny policy position and place the application permit beneath it while preserving its current nested source group.
- Review the application service object and restrict the existing permit to TCP/443 without changing nested source memberships.
- Change the rule's source NAT mode to use a dedicated public IP pool for the application group.
Explanation
Correct Answer
A:Nested address groups expand the actual set of sources eligible to match the policy. Review inherited members, exact subnet masks and change history, remove only the unintended guest object, then test both authorized and guest sessions. Confirm the policy ID to ensure no other broader rule remains.
Incorrect Answers
B:Rule ordering can stop traffic covered by a prior deny, but the named contractor restriction does not necessarily cover the newly inherited guest subnet. The source group still contains the unintended guest CIDR. Remove that nested membership and verify policy matches from both approved and guest networks.
C:Service restriction is sound least-privilege work when broad ports are the defect. It does not prevent a guest host from using the intended HTTPS application while that subnet remains in the allowed source group. Correct the nested address object, then verify host and service matching separately.
D:Source NAT changes how matching packets appear upstream, not which internal subnet qualifies as an authorized policy source. The guest subnet remains inside the nested address group and can match the accept policy. Correct the actual group membership and confirm policy hits from both networks.
Question 92
A legacy vendor payment client uses a proprietary TLS handshake extension that the vendor documents as unsupported by intermediate decryption proxies. A FortiGate full SSL inspection policy logs a handshake/protocol compatibility failure for only that client, while a controlled certificate-only test succeeds. The business must keep full inspection for other HTTPS applications. What is the defensible response?
- Set the SSL/SSH inspection profile to permit invalid upstream server certificates for the vendor destination.
- Deploy the FortiGate inspection signing CA to the payment-client trust store and retry full inspection.
- Review the payment client’s offered TLS versions and move the inspection profile minimum to TLS 1.3 before retrying the same vendor transaction.
- Verify the unsupported handshake in FortiOS SSL negotiation logs and vendor support guidance, then create an approved destination/application-scoped inspection exemption with compensating controls.
Explanation
Correct Answer
D:Correlate the FortiGate SSL handshake/negotiation error with the vendor-supported protocol and reproduce the failure using a narrowly scoped test. If deep inspection remains incompatible, exempt only the documented application or destination from decryption, preserve other filtering controls where supportable, and record reduced payload visibility and review ownership.
Incorrect Answers
A:Relaxing upstream certificate validation can address a proven certificate-chain failure, but the supplied FortiGate event is a proprietary TLS-handshake extension incompatible with intermediary decryption. A valid or ignored certificate cannot make the proxy parse an unsupported extension. Preserve certificate checks where supported and scope any approved exception.
B:Endpoint trust deployment resolves ordinary interception warnings when the client accepts substitute certificates. The vendor instead documents an unsupported handshake extension and the controlled certificate-only session succeeds. Trusting the signing CA does not implement missing TLS parser support. Verify compatibility and scope a narrow exception.
C:Protocol-version matching can explain a failed TLS negotiation when the two endpoints have incompatible cipher or version support. The supplied vendor evidence instead identifies a proprietary extension the intermediate decryption proxy cannot process; a higher minimum TLS version does not add support for that extension and can exclude otherwise functional clients. Confirm the failure and use a justified narrow exception.
Question 93
A client SYN reaches FortiGate on the LAN interface but no packet leaves the expected WAN interface. The engineer needs the actual firewall-policy and route decision. Which diagnostic is most useful?
- Assume the remote server dropped the packet without capturing outbound traffic.
- Run targeted debug flow/session lookup for the source, destination and protocol, correlating policy ID and route result.
- Filter only the high-level traffic log by destination category.
- Start a capture on the remote server and assume it can explain a SYN that FortiGate never transmitted on the egress interface.
Explanation
Correct Answer
B:Filter a debug-flow capture to the specific traffic tuple and examine the policy matching and forwarding information. Combine it with routing-table and sniffer checks to distinguish a denied policy, missing route, local-in traffic or existing-session behavior. Clear diagnostics afterward and retest a fresh session. Inspect the policy and route result for the precise source, destination, ingress interface and port.
Incorrect Answers
A:If a SYN never leaves the firewall, remote server behavior is not yet established. First locate the local denial, route failure or policy mismatch with actual FortiGate evidence. The FortiGate may be denying the flow or missing a route before any remote packet arrives.
C:Traffic summaries may show policy outcomes but are not enough to prove the local forwarding decision when no packet leaves the firewall. Correlate a targeted flow debug with route/policy ID and session status.
D:A remote server will not see a SYN that never left the FortiGate. Analyze the ingress packet and local route/policy decisions before involving distant endpoint packet capture.
Question 94
A public VIP formerly mapped to 10.50.0.8, but the web server was migrated to 10.50.0.20. External requests reach the firewall while the old host no longer exists. What is the minimal correction?
- Update the inbound WAN-to-DMZ firewall policy destination to a private address object for 10.50.0.20.
- Change only the VIP external/public IP while retaining the obsolete mapped destination 10.50.0.8 and original inbound firewall service.
- Update the VIP mapped IP to the new backend, ensuring matching firewall policy and internal reachability remain valid.
- Create a second VIP with the identical external address and TCP/443 tuple mapped to 10.50.0.20.
Explanation
Correct Answer
C:Change the intended VIP mapped address to the new server and verify its port, associated destination policy and connected route. Generate a new external connection and observe the translated destination and response. Keep source restrictions and other published VIPs unchanged. The destination translation must use the new backend and still match the published external port.
Incorrect Answers
A:The public connection first matches the configured VIP mapping, whose mapped backend still points to the nonexistent old server. Changing only a policy destination object does not update the intended VIP and can also prevent the profile-based publication policy from matching. Correct mapped IP, then verify policy and route.
B:Changing the public listener can break the published service while still forwarding to the defunct private host. Preserve the intended external tuple and replace the obsolete internal mapping.
D:FortiOS can permit overlapping VIP definitions, which makes the effective public destination selection ambiguous or shadowed. For a backend replacement, update or retire the old VIP mapping deliberately and test new connections rather than introduce two conflicting public service tuples.
Question 95
An unclassified vendor portal appears as Unrated or Uncategorized in FortiGate web-filter logs during onboarding. The enterprise wants to permit this one verified business domain while keeping other unrated sites restricted. What configuration is defensible?
- Confirm the FortiGuard category status and apply a narrowly scoped documented local category/rating override or URL filter exception for the verified domain, with testing and review.
- Review the Unrated category action on the onboarding group and switch it from Block to Monitor for that group during the vendor pilot.
- Create a FortiGuard local rating override for the parent domain that also contains multiple unrelated tenant sites.
- Add a static URL-filter Allow entry only for the vendor portal while leaving the matched FortiGuard Unrated category blocked.
Explanation
Correct Answer
A:New domains can lack a current FortiGuard rating, but that does not justify permitting all unknown destinations. Verify the actual URL/category event, business ownership and effective web-filter profile, then apply a targeted override or exception with an owner and review date. Test the vendor site and unrelated unrated sites separately.
Incorrect Answers
B:Monitor can permit traffic while logging the category result and may be useful in a deliberately authorized observation-only pilot. Here the organization must keep unrelated Unrated sites restricted. Changing the entire category for the group would permit every unclassified destination. Verify this portal and apply only a narrowly documented hostname-specific rating override or approved exceptional treatment.
C:Local rating overrides can appropriately correct categorization, but an overbroad parent/domain scope can affect unrelated sites that must remain restricted. A defensible onboarding exception should match the verified portal hostname and be tested against other Unrated destinations.
D:A static URL-filter Allow is not necessarily a bypass of a FortiGuard category Block later in the same profile. Unless the effective category/override action is reconciled, the approved site may remain blocked. Use the relevant local rating or explicitly authorized, narrow alternative with understood Exempt side effects.
Question 96
A FortiGate has a primary static default route via wan1 and a less-preferred backup via wan2. The wan1 Ethernet carrier remains up after the upstream ISP gateway loses reachability, so the primary route stays installed and traffic blackholes. What mechanism should be considered?
- Lower the wan1 primary static route distance so it always wins when its Ethernet interface reports link-up.
- Configure a supported link/gateway health monitor or SD-WAN member health rule tied to route availability and test withdrawal/failover when the upstream peer becomes unreachable.
- Inspect equal-cost default route candidates and add wan2 as an ECMP participant while wan1 retains its unresolved upstream health state.
- Review the wan2 static route priority and make the backup less preferred numerically until the primary Ethernet carrier drops.
Explanation
Correct Answer
B:A static route may remain eligible while the physical link is up, even if the upstream path is unusable. Use FortiOS-supported link monitoring or SD-WAN health tests to influence eligible routing according to the design, preserving the backup path and verifying actual route table and session egress under a controlled gateway failure.
Incorrect Answers
A:A lower administrative distance strengthens preference for the same route whose gateway has failed, and Ethernet carrier alone does not establish upstream reachability. The failure requires a real health test capable of withdrawing or de-prioritizing the failed path, not a stronger static preference.
C:Equal-cost routing can spread new sessions over eligible gateways, but a failed wan1 upstream path may remain selected for part of the traffic while physical carrier stays Up. The intended backup mechanism must identify gateway or link service failure and remove/de-prioritize the unusable member before steering reliably.
D:Administrative route preference controls candidates but cannot detect that a physically Up wan1 gateway is unreachable. Making wan2 even less preferred risks reinforcing the blackhole. Use a FortiOS gateway monitor or SD-WAN SLA and verify actual path change when the provider stops replying.
Question 97
A FortiGate branch has a route-based IPsec phase-two SA established to headquarters, but a route lookup for the protected headquarters prefix 172.20.30.0/24 selects only an ordinary internet default route. There is no policy-based routing override. What route change should the branch make?
- Check phase-two auto-negotiate status for the branch tunnel and enable it so the protected child association is proactively established.
- Widen the phase-two protected-subnet selectors to 0.0.0.0/0 on the branch to catch the headquarters /24.
- Install or correct the branch route for 172.20.30.0/24 toward the appropriate IPsec interface and verify tunnel-side policies and return routing.
- Add a new branch LAN-to-IPsec security policy for the headquarters prefix and leave the routing table unchanged.
Explanation
Correct Answer
C:For a route-based VPN, the FortiGate needs an eligible path to the remote protected prefix through the correct tunnel interface or another intentional dynamic route. Add the precise 172.20.30.0/24 route, inspect the installed route and confirm that both LAN-to-VPN policy and remote return path permit the flow.
Incorrect Answers
A:Automatic child-SA negotiation is appropriate for a tunnel that fails to establish until traffic starts. But the problem states the required child SA is already established and route lookup still uses the ordinary internet default for headquarters. Starting the SA again cannot install the missing protected-prefix route. Correct destination routing and then check tunnel firewall policies and reverse path.
B:Broad selectors can change which packets qualify for encryption when negotiated with the peer, but the actual failure is an installed routing-table path via the default internet route. Widening the SA does not by itself establish a usable static route for the protected destination and may overreach approved traffic.
D:A correct tunnel security policy is a separate forwarding prerequisite, but the packet must first select the IPsec interface as its egress. Because route lookup selects only the ordinary internet default, adding a permit without a suitable destination route does not fix the observed path.
Question 98
A FortiGate-VM is deployed as a security appliance in an Azure hub VNet. Spoke subnets still exchange traffic directly and bypass the firewall, although the FortiGate security policy would permit the flow if it arrived. Which Azure/FortiGate integration settings must be checked?
- Permit the intended HTTPS flow in the FortiGate security policy and Azure NSG, but leave both spoke effective route tables bypassing the FortiGate virtual-appliance next hop.
- Enable IP forwarding only inside FortiOS while keeping Azure NIC IP-forwarding permission and effective route-table steering unverified.
- Create an Azure NSG allowing TCP 443 to the firewall VM.
- Spoke user-defined routes pointing affected prefixes to the correct virtual appliance IP, enabled Azure NIC IP forwarding and FortiGate interfaces, policies and symmetric return routing.
Explanation
Correct Answer
D:A hub virtual appliance inspects only traffic actually steered to it. Verify applicable user-defined route tables on source and destination spokes, virtual appliance next-hop addresses and IP forwarding on relevant Azure NICs. Align FortiGate interfaces, routing and firewall rules and validate symmetric return paths to prevent bypass or asymmetric state loss.
Incorrect Answers
A:Azure NSGs and FortiGate firewall rules can authorize packets once they reach their layers, but they do not redirect a spoke connection through the appliance. Inspect the effective UDRs and routes toward the FortiGate NIC with Azure IP forwarding, and verify the return path.
B:FortiGate-VM forwarding settings are necessary but not sufficient. Azure NIC/IP-forwarding settings, UDR next-hop selection and symmetric return routing must also permit the intended traffic to traverse the appliance. Validate both cloud and FortiOS forwarding layers.
C:Network security groups can authorize or restrict packets at NIC/subnet scope, but an allow rule alone cannot replace the route insertion needed to force spoke traffic through the inspection VM. Inspect effective Azure routes and both directions of the flow.
Question 99
A visitor connects a laptop to a trusted FortiGate guest Wi-Fi VLAN. The network must require an interactive browser login against an approved identity group before allowing internet access; silent FSSO is not available for the visitor. Which authentication pattern fits?
- Create a destination NAT VIP toward the visitor laptop and use the public address as proof of login.
- Use a supported FortiGate captive-portal or identity-based firewall authentication flow on the guest access path, with group membership validated before the permit.
- Disable guest authentication entirely and interpret a DHCP lease as evidence of a successful user login.
- Permit a device because it received a valid DHCP lease and matches an allowed source-address object.
Explanation
Correct Answer
B:An interactive captive portal can ask a user to authenticate when they first access a protected network path. Configure the applicable interface or firewall authentication policy, permitted identity source and approved group, then verify that unauthorized sessions are redirected or denied and authorized sessions receive only intended access.
Incorrect Answers
A:VIP destination NAT maps a published address or service to an internal host. It does not authenticate the human user holding the laptop. Exposing the client through inbound translation would add risk while failing the requirement for a browser-based access decision.
C:A DHCP lease establishes that the host obtained network configuration, not that any person proved identity or group membership. Allowing guest internet solely on that basis bypasses the documented policy requirement. Keep address assignment separate from portal authentication and authorization.
D:A DHCP lease and source address establish connectivity or location, not a browser-authenticated user identity or authorization group. The guest policy explicitly requires interactive login before internet access; use the appropriate supported captive portal and verify permitted group membership.
Question 100
A FortiGate application-control policy must initially observe use of a newly introduced collaboration tool without disconnecting staff. The security team will review traffic for a week before choosing whether to block the application. Which rollout is most appropriate?
- Set the matching application signature or filter to an appropriate monitor/log action in the active application-control profile, collect actual events and then evaluate a measured block rule.
- Immediately deny every TCP 443 session for all users to guarantee the new collaboration service cannot run.
- Remove application-control inspection from the policy because traffic logs alone identify every encrypted application correctly.
- Change only the policy action from Accept to Deny for all application sessions.
Explanation
Correct Answer
A:Monitoring the specific application through an attached application-control sensor provides visibility into matched sessions, users and actual use before enforcement changes. Confirm the correct firewall policy and signatures, collect a representative sample and then review a justified block action or scoped exception with affected business owners.
Incorrect Answers
B:A broad TCP 443 deny would interrupt many unrelated HTTPS services and violates the requirement for a visibility-only observation period. Port-based blocking also cannot distinguish applications sharing that transport. Start with a relevant signature monitor action and review evidence.
C:Generic traffic logs can show IPs, ports and policy actions, but encrypted services may share TCP 443 and require supported application identification. Removing the application-control profile eliminates the intended classification evidence. Ensure the sensor matches the flow and its logs are enabled.
D:A Deny rule would interrupt use immediately and fails the rollout goal of monitoring a specific collaboration tool first. Attach the application-control profile, set the relevant signature to Monitor where supported, and record usage before a proposed targeted enforcement change.