Fortinet NSE4_FGT_AD-7.6 Practice Test 37
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.
Question 361
A FortiGate's outbound IP pool uses 198.51.100.240/29, but its ISP only routes 203.0.113.16/29 to the firewall. The matching policy logs ACCEPT and outgoing packets have 198.51.100.241 as their translated source, yet no replies return. What should the administrator validate before widening the firewall policy?
- Retain an arbitrary public source NAT prefix not advertised by the ISP and add it to the FortiGate IP-pool address object to ensure source translation succeeds locally.
- Select a public source-NAT pool actually routed back by the ISP and verify return packets, translated sessions and anti-spoofing controls.
- Inspect the public HTTPS destination’s FortiGuard web rating and permit its category while retaining 198.51.100.241 as the translated source.
- Expand the outbound firewall Accept to all destinations and services while retaining the translated pool 198.51.100.240/29 that the ISP does not route.
Explanation
Correct Answer
B:A translated source address must be owned or routable on the external network, and responses must return through a path that can reverse the translation. Compare the active firewall policy or central SNAT rule, selected IP-pool address range, outgoing interface, ISP routing and any upstream anti-spoofing behavior. Replace an invalid pool or arrange proper upstream reachability. Increasing the address pool size without fixing public-prefix routing will not restore sessions.
Incorrect Answers
A:FortiGate syntax acceptance does not make an external prefix routable back or exempt it from upstream anti-spoofing. Use legitimately routed source addresses.
C:A web category can affect the firewall security-profile verdict, but these sessions already log forwarding ACCEPT and leave with a translated public source that the ISP does not route back. Reclassifying the destination cannot teach the provider how to return packets for an unadvertised SNAT prefix. Select a properly routed egress source pool and confirm reply captures and provider anti-spoofing.
D:A forwarding permit cannot cause public replies to reach an unrouted source prefix. Correct the approved NAT address pool and upstream return path first.
Question 362
A static URL deny uses *.example.net, but the required block is limited to upload.example.net and any nested hosts beneath it. Other approved sibling hosts, such as approved.example.net, must remain accessible. What change is appropriate in FortiOS 7.6.0?
- Keep the broad *.example.net URL Block but add an Allow category for every employee web site so the intended upload host can be reached.
- Inspect the FortiGuard category on approved.example.net and switch it to Allow within the current profile while keeping *.example.net blocked.
- Replace *.example.net with a simple URL-filter Block entry for example.net to narrow the existing pattern.
- Replace the broad wildcard Block with a hostname-scoped Simple Block for upload.example.net; test approved.example.net and any upload subdomains that may also match in FortiOS 7.6.0.
Explanation
Correct Answer
D:The original *.example.net Block unnecessarily matches approved sibling hosts. In FortiOS 7.6.0, a hostname-scoped Simple entry for upload.example.net is substantially narrower and can still match that host’s own subdomains; do not claim that a later-version exact-only subdomain toggle is available. Check flow/proxy inspection behavior, actual logged URL and filter order. Test upload.example.net, an upload child host if relevant, and approved.example.net before deployment.
Incorrect Answers
A:Broad category permissions do not reliably override a matching explicit hostname wildcard and could expose unrelated content. Narrow the static URL match itself.
B:The observed overblocking is caused by an explicit broad static URL wildcard, which may still deny traffic despite a permitted category. A category action does not necessarily override a static URL Block. Replace the wildcard with a host-scoped upload.example.net deny and test both intended and approved subdomains.
C:A Simple rule naming the parent example.net can also match its subdomains in FortiOS 7.6.0, including the approved.example.net sibling that must remain accessible. That expands the Block rather than narrowing it to upload.example.net. Use the intended specific hostname in a supported URL filter type and verify the actual matching profile and positive/negative host tests.
Question 363
A new route-based IPsec tunnel to a branch has a valid route and firewall policies. TCP health checks and 200-byte UDP queries succeed, but a UDP application sending 1,472-byte datagrams with the IPv4 DF bit set repeatedly stalls. Captures show a smaller WAN path MTU after IPsec overhead and no usable ICMP Fragmentation Needed feedback reaches the sender. Which diagnosis and scoped remediation address this UDP-specific failure?
- Check IPsec encapsulated UDP size, DF/PMTUD and ICMP Fragmentation Needed before changing tunnel MTU or application datagrams; test both DF and fragmentation behavior over the active protected route.
- Lower only the TCP MSS on the tunnel and assume the UDP datagram emitted by the affected application automatically follows the TCP setting.
- Increase the IPsec phase-two SA lifetime and retry count to avoid UDP datagram fragmentation while retaining the same underlay MTU and application payload size.
- Inspect the branch public WAN route and prefer the normal ISP default for the affected UDP application while leaving its private tunnel destination unchanged.
Explanation
Correct Answer
A:A 1,472-byte inner UDP datagram can exceed the effective underlay MTU after ESP and any NAT-T overhead. DF prevents required fragmentation, and an absent or filtered ICMP Type 3 Code 4 prevents effective PMTUD feedback. Compare outer/inner packet sizes and fragmentation counters; restore supported control messages or lower application datagram size/appropriate MTU settings, then verify large UDP success on the intended encrypted path. FortiOS 7.6.0 has automatic TCP MSS behavior for oversized TCP through IPsec, but MSS does not constrain UDP.
Incorrect Answers
B:MSS constrains TCP segmentation, not UDP datagram length. Measure the actual UDP size, DF status and ESP encapsulation overhead to correct its MTU path.
C:Cryptographic SA timers do not change the maximum encapsulated packet size. The observed UDP/ICMP issue requires MTU and application datagram handling.
D:A default route is useful for ordinary internet traffic but does not satisfy the requirement to keep the application protected inside the site-to-site VPN. The tunnel already passes small packets while 1,472-byte DF UDP datagrams exceed the effective encapsulated path MTU with missing fragmentation-needed feedback. Switching to public routing would bypass protection rather than diagnose DF, PMTUD, packet size and supported fragmentation behavior.
Question 364
A profile-based NGFW FortiGate uses a WAN-facing VIP to map public TCP/443 to an internal HTTPS server. A new WAN-to-DMZ policy targets only an ordinary address object containing the server's private IP and never references the configured VIP; debug flow shows the incoming connection fails to match that publication policy. What should the administrator examine?
- Use the private backend address object as destination on a LAN-to-WAN firewall rule while leaving the public WAN-facing VIP unmapped in the inbound policy.
- Inspect the existing inbound WAN-to-DMZ ACCEPT policy and enable central source NAT for clients, without referencing the configured WAN VIP as its destination.
- Change the VIP internal mapped TCP port to match the existing inbound policy service while leaving its required public service translation unverified.
- In profile-based NGFW mode, reference the correct configured WAN-facing VIP as the inbound firewall-policy destination and validate its external TCP/443 service, mapped backend, resulting DNAT and policy match.
Explanation
Correct Answer
D:In the specified profile-based NGFW deployment, the inbound publication policy normally uses the matching VIP as its destination. Check the external IP, interface binding, port forwarding and mapped address, then confirm the effective WAN-to-DMZ rule references the correct VIP. Use a fresh debug-flow session to identify any earlier matching or implicit-deny behavior. In NGFW policy-based/central-NAT deployments policy matching can be configured differently; the scenario explicitly limits itself to profile-based mode.
Incorrect Answers
A:Inbound publication must match the original external destination through the VIP and correct post-DNAT policy treatment. A LAN-to-WAN rule is unrelated.
B:Source NAT can change the address received by a published server and sometimes helps deliberate hairpin designs. The observed fault is destination-policy selection for incoming public TCP/443 in profile-based NGFW mode: the inbound rule targets only the private mapped address instead of the VIP object. Central SNAT cannot make that rule match the expected VIP publication. Set the correct VIP destination and verify DNAT flow.
C:Changing a backend port without verifying its listener can break the application, and does not fix a missing VIP object in the policy destination.
Question 365
A new latency-sensitive collaboration rule is placed below an existing catch-all internet SD-WAN rule. Its hit count stays zero. What should be changed?
- Increase the collaboration rule’s numeric priority while leaving it below the existing catch-all SD-WAN rule that already matches new collaboration sessions.
- Inspect the collaboration application service port and move its traffic to TCP/8443 while leaving the catch-all SD-WAN rule ahead of the app-specific rule.
- Review SD-WAN probe status and disable health checks for the catch-all member without moving the collaboration-specific rule.
- Move the collaboration-specific SD-WAN service rule above the general catch-all and validate its source, application, SLA and member selection with a fresh session.
Explanation
Correct Answer
D:An earlier catch-all SD-WAN service rule may select a path before a lower, more-specific collaboration rule can match. Reorder the specific rule ahead of the general fallback, retaining valid member SLA and route settings, then inspect service diagnostics for fresh collaboration traffic. Do not rely on numeric rule IDs or silent priority labels without checking actual evaluation order.
Incorrect Answers
A:SD-WAN service rules have ordered matching; a lower rule cannot override an earlier catch-all solely from a numeric interface preference. Move the narrower rule above.
B:Changing the application port might affect service matching if the original session had been misclassified, but this case explicitly identifies the earlier catch-all SD-WAN rule as the matched service. Port migration will not correct ordered rule precedence and could break clients. Move the specific collaboration service above the catch-all and validate fresh-session rule hits.
C:Health measurement influences which member is eligible after the selected service rule runs. It does not automatically make a lower collaboration rule win over an earlier matching catch-all. Disabling probes loses quality evidence and may worsen failures. Fix service precedence and check the actual session match.
Question 366
An IPsec peer changes its authentication certificate. The tunnel no longer establishes and IKE logs show certificate validation errors. Which response is appropriate?
- Verify the replaced IKE peer certificate’s CA chain, name/ID, validity and revocation before restoring trusted negotiation.
- Allow any peer certificate on the IPsec gateway temporarily and rely on a matching public source address for the intended identity after renewal.
- Inspect the remote peer certificate fingerprint change and retain only the retired fingerprint as the trusted identity while repeatedly initiating IKE.
- Review phase-two selector coverage and broaden the protected remote subnet after the IKE certificate validation failure.
Explanation
Correct Answer
A:When an IPsec peer renews its certificate, authentication must be evaluated against the new certificate chain and identity rather than bypassed. Check the configured CA trust, certificate validity dates, revocation expectations and any peer-ID restriction, then compare IKE authentication diagnostics. Import or trust the properly authorized issuing material as needed. Do not disable certificate verification merely to make the tunnel green, because that would weaken peer identity assurance.
Incorrect Answers
B:Public addresses are not sufficient authenticated peer identity. Verify the renewed certificate issuer, peer name and validity rather than accepting arbitrary certificates.
C:A pinned fingerprint can protect against unexpected peer certificates, but a legitimately rotated certificate has different cryptographic material. Keeping the retired value cannot validate the new signed peer identity; confirm authorized CA chain, certificate name, validity and intended revocation policy before safely updating trust.
D:Child-SA selectors govern protected network scope after a successful peer authentication. The recorded IKE failure happens while validating the newly presented certificate, not while selecting subnets. Widening network access cannot resolve trusted issuer, expected identity or validity and may needlessly expose additional traffic.
Question 367
A destination presents an expired certificate. Clients can browse through a no-inspection profile but are blocked under a stricter SSL inspection policy. What explains the discrepancy?
- Permit the expired server certificate under deep inspection because a client previously opened the site successfully using a separate policy with weaker inspection.
- Move the destination into a trusted FortiGuard business category and assume that overrides the server certificate expiry check in every SSL inspection profile.
- Increase the firewall policy's idle session timeout so the server certificate's validity period effectively extends.
- Compare the actual SSL inspection certificate-validation actions and exceptions on the two policies; investigate the expired origin chain without disabling verification globally.
Explanation
Correct Answer
D:An expired certificate may appear to have no impact when the deployed inspection mode does not validate the certificate in the way the team expects, when an exception is applied, or when different clients take different paths. Verify the matched SSL/SSH inspection profile, server-certificate checks, client trust, session reuse and specific log decision. Test a new connection with an intentionally expired lab certificate. Do not conclude that expiry validation works based solely on an application remaining reachable.
Incorrect Answers
A:Success through a less restrictive path does not establish upstream certificate validity. Compare actual SSL profile behavior and preserve origin identity checks.
B:Web classification and TLS server identity validation are separate controls. A category rating does not extend or fix the expired certificate.
C:Session lifetime is not a certificate expiration control. A strict inspection profile can reject the handshake regardless of forwarding-policy timeout settings. Extending a session timer has no influence on the certificate NotAfter field validated during TLS negotiation.
Question 368
FortiGate GUI logins for named local administrators already require FortiToken MFA, but a privileged remote administrator can still authenticate to the FortiGate CLI over SSH through a separately configured remote-AAA path using only a password. The policy requires every privileged login method to enforce a second factor. What should be changed and proven?
- Increase privileged-password lifetime and leave remote SSH/AAA login as password-only because the FortiGate GUI already has enforced FortiToken MFA.
- Restrict the GUI to a management subnet and treat the source address as an equivalent second authentication factor.
- Enable strict login lockout on SSH but retain password-only remote administrative authentication, treating fewer guesses as equivalent to MFA.
- Require and test supported multi-factor authentication on the privileged SSH/remote-AAA path as well as on GUI logins, while maintaining restricted management sources and emergency recovery.
Explanation
Correct Answer
D:An existing MFA prompt on the GUI for local administrators does not establish that a different remote AAA path used for SSH requires a second factor. Inspect the actual remote administrator authentication integration and whether its supported RADIUS or identity provider flow enforces MFA for privileged CLI access. Test that password-only SSH login fails while the approved second factor succeeds; keep per-person accounts, profiles and emergency recovery.
Incorrect Answers
A:Authentication paths must each meet the privileged MFA requirement. GUI MFA does not prove the separate SSH/AAA route challenges for a second factor.
B:A trusted host narrows reachability but does not prove possession of an independent factor. Use the approved FortiToken or identity integration as required. Management-subnet restriction reduces exposure but cannot prove possession of the configured second authentication factor.
C:Lockout reduces brute-force attempts but remains a single knowledge factor. Validate supported second-factor enforcement on SSH/AAA with restricted management sources.
Question 369
A debug-flow record shows a public VIP destination on ingress and a private server address after DNAT. An analyst believes the packet was redirected to the wrong client. How should fields be interpreted?
- Flag the private post-DNAT server address as a suspected spoofed client because it differs from the public VIP destination captured on the WAN interface.
- Use the translated source IP field to infer the original destination.
- Disable the VIP while collecting new traffic logs so public destination addresses remain visible on the internal server interface for compliance tracing.
- Match ingress public VIP destination to the post-DNAT private server and original client in the same session.
Explanation
Correct Answer
D:NAT may cause packet captures and session logs to show both original and translated addresses. Inspect the direction and field meaning before interpreting a destination or source after translation. Correlate the client tuple with the VIP or SNAT/IP-pool rule and the matched firewall policy, then validate the reverse translation. Investigating the translated address as if it were the endpoint's configured private address can lead to incorrect route or security-policy changes.
Incorrect Answers
A:Destination translation is the intended effect of a VIP. Inspect original versus translated destination fields in the same session before attributing an incident.
B:Source translation and destination translation affect different tuple fields. A faithful diagnosis needs both client-facing and server-facing addressing from session evidence. A translated source field cannot reconstruct the original destination in a DNAT flow; use original-destination and translated-destination values.
C:Disabling publication breaks the service and is not required to reconstruct the original tuple. Preserve pre/post translation fields and matched policy evidence.
Question 370
A FortiGate web-inspection rollout switches an application policy from flow to proxy mode. During peak downloads the web proxy process and first-byte latency increase sharply, but a required content-filter feature may be proxy-only. What measurements and feature checks should guide tuning or a controlled return to flow inspection?
- Measure proxy WAD CPU and first-byte latency against mandatory inspection features; test a scoped, supported flow-mode alternative only if security behavior remains equivalent.
- Switch every security policy to flow mode immediately after a latency complaint without checking whether any required web-filter action is proxy-only.
- Increase the session timeout for every application.
- Change SD-WAN default-route priority for the affected web application after proxy inspection is enabled, without measuring its SSL processing or first-byte delay.
Explanation
Correct Answer
A:Proxy inspection can buffer and reconstruct content, producing additional latency for some file-heavy applications, but certain required filtering features may rely on its feature set. Correlate WAD/process resource diagnostics with representative downloads and determine whether flow inspection supports each mandatory control. Test a scoped profile change with security and performance measurements rather than globally disabling inspection. In FortiOS 7.6.0, proxy-based inspection is unsupported on physical FortiGate models with 2 GB RAM or less; confirm model capacity before selecting that mode (VM behavior differs).
Incorrect Answers
B:Flow mode can reduce processing in some deployments but may lack required proxy features. Measure WAD costs and test a supported feature-equivalent adjustment.
C:Idle expiration may not cause a per-request inspection delay. Examine CPU, concurrent scans, file sizes and policy mode to locate the actual bottleneck.
D:Route changes may affect network latency but cannot prove a regression rooted in proxy buffers or WAD CPU. Isolate proxy versus path timing first.