Fortinet NSE4_FGT_AD-7.6 Practice Test 24
Question 230
A user on the same host can open HTTPS to an application server but not its SSH management port. Both attempts reach the same FortiGate policy area. Which check best isolates the difference?
- Inspect the existing HTTPS firewall service object and add SSH TCP/22 to it for the entire original source group.
- Enable HTTPS deep inspection and assume the certificate profile also authorizes the server's SSH service.
- Review the HTTPS rule’s NAT setting and apply the same translated source IP to the new SSH session.
- Compare the failed SSH TCP/22 service and source tuple to the effective policy; permit only authorized management hosts.
Explanation
Correct Answer
D:FortiGate firewall policy matching includes the service protocol and destination port, not only the two IP addresses. A permitted HTTPS session can coexist with a denied new SSH session on TCP 22. Trace the actual rule ID and object/service definitions; if remote administration is approved, create a narrowly scoped SSH permit without broadening unrelated services.
Incorrect Answers
A:Changing the shared service could permit SSH from every host previously authorized only for HTTPS. The symptom needs a separate authorization check: compare the actual management source, destination and TCP/22 with the matching policy, and grant SSH only to approved administrative hosts.
B:TLS content inspection for HTTPS is not a firewall service allow for TCP 22. FortiOS evaluates service definitions and then any applicable inspection; the two services must be examined separately.
C:NAT may affect return routing, but the scenario distinguishes HTTPS from SSH to the same host and the existing rule explicitly matches the HTTPS service. Copying the source translation cannot make TCP/22 an authorized service. Check the rule’s service selector and a narrow management policy first.
Question 231
An exploit request reaches an HTTPS web application. The firewall uses certificate inspection without decrypting application payload. An administrator reports that IPS inspected the attack body. What should be checked?
- Use the HTTPS server certificate name and accepted firewall-policy log as the supporting evidence that the IPS engine decrypted an exploit-bearing HTTP request body.
- Raise IPS signature severity coverage on the certificate-inspection-only policy and retest the encrypted exploit, without enabling authorized payload visibility.
- Establish payload decryption on the HTTPS ingress policy before claiming IPS evaluated the encrypted exploit request.
- Enable a static URL-filter Allow override for the HTTPS web application and treat an accepted hostname as evidence that IPS decrypted the exploit body.
Explanation
Correct Answer
C:An IPS sensor cannot inspect HTTPS application payload hidden by encryption when the selected SSL profile provides only certificate-level metadata. Confirm which firewall policy, SSL/SSH inspection mode and IPS sensor actually process the inbound server flow, including exceptions and client trust. Use permitted deep inspection or supported alternatives before asserting payload-signature coverage, then validate with safe test traffic and recorded IPS actions.
Incorrect Answers
A:Certificate metadata and a forwarding Accept prove neither payload decryption nor inspection by a content signature. Confirm supported server-side SSL inspection on the matched rule before interpreting IPS payload detections.
B:Severity tuning affects signatures selected for analysis, but cannot let those signatures read application bytes still protected by TLS. A genuine payload-inspection claim needs a matching decryption path and event evidence.
D:Static URL filtering classifies or allows site destinations; it does not expose encrypted HTTP attack bytes to payload-dependent IPS signatures. Confirm a supported server-side decryption path on the effective policy and inspect the IPS event before claiming prevention.
Question 232
A company is rolling FortiSASE out to employees, but the initial policy blocks an approved CRM SaaS application. Which rollout strategy limits user impact?
- Pilot a narrowly scoped CRM group and correct its FortiSASE policy verdict after reading access, inspection and posture logs.
- Roll out the new FortiSASE CRM restriction to all employees but lower alert severity for the already blocked SaaS sessions until the helpdesk receives complaints.
- Exclude all SaaS traffic from FortiSASE inspection rather than identify which CRM domain or application condition failed.
- Exclude the entire CRM SaaS provider domain family from all FortiSASE inspection policies for every device rather than tracing the specific blocking rule.
Explanation
Correct Answer
A:A progressive FortiSASE rollout should prove the real CRM user journey on representative managed endpoints, with a known pilot group and captured enforcement event. Identify whether destination classification, TLS inspection, application policy or posture caused the block. Apply a narrowly scoped approved correction, verify allowed CRM and blocked control tests, and then expand with rollback readiness.
Incorrect Answers
B:Reducing alert noise does not restore an authorized business application or limit deployment blast radius. A small test cohort with exact policy and TLS/posture failure evidence is required before broad rollout.
C:A global SaaS bypass defeats other content and access protections. Verify specific traffic logs, policy match and narrow approved exceptions. Compare the affected tenant identity, device posture, endpoint routing, private/public access rule and the exact web or app decision in FortiSASE logs.
D:A broad bypass may make the app reachable but can exempt unrelated provider services and eliminate security controls for all users. Isolate the approved CRM dependency, matched action and narrow exception scope.
Question 233
At peak office hours, a FortiGate outbound source-NAT overload pool starts reporting allocation failures for new connections while existing permitted sessions continue. The pool has many active mapped source ports and its public addresses are still routable. Which diagnostic should the engineer perform before changing firewall permissions?
- Inspect current session lifetimes and increase the TCP idle timeout on the heavily used SNAT overload pool.
- Expand inbound VIP port-forward mappings on the same public addresses and expect the additional destinations to increase outbound source-NAT overload capacity.
- Inspect SNAT port allocation pressure and failure counters, then adjust the eligible address pool without widening security rules.
- Review the active SNAT pool and consolidate its public addresses into one preferred interface IP for easier monitoring.
Explanation
Correct Answer
C:An outbound SNAT overload pool can exhaust usable translated source ports or session resources during peak connection demand even while the forwarding rule permits traffic. Inspect per-pool allocated ports, active NAT sessions, source/destination patterns, platform limits and the observed failed connection error. Adjust capacity or distribution using supported controls and verify new connections succeed without disrupting existing translation or return routing.
Incorrect Answers
A:Session timing can affect port reuse, but extending idle state generally retains mappings longer and does not increase the available source-port budget. The case already reports allocation failures while public addresses remain routable. Examine current SNAT port occupancy and failure counts before pool sizing or timeout tuning.
B:VIPs translate inbound destinations and do not add outbound SNAT source-port inventory. The problem is explicitly insufficient new translated source allocations under peak load, not a missing inbound service mapping.
D:A smaller translated-address pool can reduce available overload ports when there are many simultaneous sessions. Simpler accounting does not solve the reported resource exhaustion. Determine eligible port allocation per public IP, mapping churn and peak demand before increasing capacity or changing translated identities.
Question 234
The compliance team forbids TLS decryption for specified medical portals, while other corporate web traffic remains deeply inspected. Which exception scope should be used?
- Make a named medical-portal SSL decryption exception only for authorized destinations, retaining normal inspection for other sites.
- Move all corporate outbound HTTPS to certificate-only inspection, including departments not covered by the medical-portal compliance prohibition.
- Create an SSL exemption for every destination categorized as Health and Medical without checking whether it belongs to the approved portal list.
- Keep deep inspection active for the medical portal but suppress its TLS inspection logs, claiming logging changes meet the non-decryption requirement.
Explanation
Correct Answer
A:A legal or privacy exemption for specific medical web destinations should constrain decryption by approved FQDN or category scope, not disable inspection everywhere. Check the SSL/SSH inspection profile's supported exemption match, upstream certificate handling and the actual policy selected by the session. Prove the medical portal is exempt while other eligible HTTPS traffic remains inspected, documenting the privacy rationale and review owner.
Incorrect Answers
B:Certificate-only can avoid decrypting HTTPS, but the stated exemption covers only specified medical portals. Applying it universally would remove required payload scanning on unrelated corporate traffic.
C:Category-wide exemptions may cover unrelated sites and expand the privacy exception beyond compliance authority. Bind the exemption to validated portal destinations and eligible users while retaining controls elsewhere.
D:Hiding event records does not prevent the interception of sensitive content. Enforce an actual supported decryption exemption and verify the portal's negotiated session behavior. Prove the medical portal is exempt while other eligible HTTPS traffic remains inspected, documenting the privacy rationale and review owner.
Question 235
A packet capture shows application traffic exiting wan2 even though a static route seems to prefer wan1. SD-WAN and a policy route also exist. What should be examined?
- Trace policy-routing and SD-WAN selection for this flow before interpreting the apparent wan1 static-route distance.
- Review the wan1 static default route and lower its administrative distance without checking the matching policy route or SD-WAN service.
- Inspect wan2 SD-WAN link counters and temporarily disable that member to see whether the application shifts to wan1.
- Raise the static priority on the wan2 default route while leaving the installed application policy route and SD-WAN rule untouched.
Explanation
Correct Answer
A:An installed static route, policy route and SD-WAN service rule may steer the same destination differently depending on active FIB eligibility and match precedence. Correlate the packet's full tuple with route-table candidates, selected policy route, first matching SD-WAN service and member SLA status. Use a controlled new session and packet captures to prove the intended egress interface and return path after a scoped change.
Incorrect Answers
B:A lower distance changes ordinary routing preference for same-prefix candidates, but FortiOS may follow a higher-precedence policy route or SD-WAN service for this application. The observed wan2 egress must be explained by the actual matched steering rule and session, not only the static route table.
C:Removing a working WAN may reveal an alternative path, but it can disrupt unrelated traffic and conceal the actual cause. Because policy routing and SD-WAN rules are present, identify the specific source/destination/service match and selected member in current sessions before modifying active link membership.
D:A static-route priority change could affect ordinary same-prefix selection, but cannot be assumed to supersede a specific matching policy route or SD-WAN service. Identify the higher-level steering match, selected member and effective route before editing any static route parameters.
Question 236
Small TCP control packets traverse a FortiOS 7.6.0 route-based IPsec tunnel, but larger TCP application responses stall after ESP/NAT-T encapsulation. Captures show retransmission and fragmentation near the physical WAN MTU. Which investigation best distinguishes effective tunnel MTU, pre-7.6.1 MSS handling and the behavior of oversized packets?
- Increase TCP window scaling and receive buffers on both application endpoints while retaining the current IPsec encapsulation size and path-MTU behavior.
- Correlate FortiOS 7.6.0 TCP MSS handling and the actual encapsulated ESP/NAT-T packet sizes with path MTU, DF/ICMP Fragmentation Needed behavior and fragmentation in controlled large-packet tests.
- Increase the IPsec child-SA lifetime and disable periodic rekeys so long downloads remain in one encryption association across fragmented packet bursts.
- Inspect the current tunnel interface MTU and set it equal to the physical WAN MTU to preserve large TCP segments through the ESP/NAT-T encapsulation.
Explanation
Correct Answer
B:ESP encryption and NAT traversal add overhead, so a segment that fits the physical WAN may exceed the effective IPsec path MTU. FortiOS 7.6.0 and earlier can adjust TCP MSS automatically when traffic crosses a tunnel; the change described for 7.6.1 must not be applied retroactively. Use captured TCP negotiations, actual on-wire packet sizes, DF or fragmentation messages, offload and supported tunnel settings to identify which dependency breaks large transfers, then test an appropriately scoped configuration adjustment.
Incorrect Answers
A:Window size can affect throughput but does not make a packet larger than the effective ESP-encapsulated path MTU deliverable. The fragmentation evidence requires MSS/PMTUD and underlay MTU diagnosis.
C:Rekey timing affects security association renewal, not the maximum packet size that survives ESP or NAT-T overhead. Test DF packets and ICMP too-big behavior instead of changing cryptographic maintenance.
D:Checking interface MTU is a useful part of diagnosing fragment-related stalls. Setting tunnel MTU equal to physical WAN MTU ignores the extra bytes added by ESP and possible UDP encapsulation, so large packets can still exceed the usable path size. On FortiOS 7.6.0, TCP MSS adjustment behavior differs from 7.6.1 and later: trace the exact encapsulated packet sizes, DF/ICMP handling and session behavior before a supported scoped correction.
Question 237
A FortiGate running an older supported build needs to move to FortiOS 7.6 during a short maintenance window. The operator has a backup but has not checked the vendor's intermediate upgrade path or available rollback. What preparation most directly reduces configuration and availability risk?
- Upgrade directly to the newest available 7.6 image on the appliance and verify only afterward whether intermediate versions are required.
- Rely only on saved GUI screenshots and omit a verified configuration backup.
- Run the upgrade during the short window using the verified configuration backup but omit hardware, HA, licensing and supported intermediate build checks.
- Follow the vendor Upgrade Path Tool and maintain off-device backup, intermediate build verification and rollback.
Explanation
Correct Answer
D:A direct version jump may skip necessary intermediate FortiOS conversions. Verify the vendor upgrade path for the actual hardware and starting firmware, preserve a restorable configuration backup, check license compatibility and available storage, and stage the required images and maintenance rollback. Test core routes, HA, VPN and policy functions after the controlled upgrade instead of assuming one-step installation is supported.
Incorrect Answers
A:An unsupported upgrade jump can cause configuration incompatibility or downtime. Fortinet provides a supported path between specific starting and target builds; validate it before maintenance.
B:Screenshots cannot restore complete interfaces, security policy objects, certificates and operational settings. A compatible protected backup and tested recovery method are needed before the upgrade. Review firmware compatibility, current configuration export, rollback options, management access and HA roles if the appliance participates in a cluster.
C:A backup protects some recoverability, yet it does not guarantee the target image fits the platform or cluster sequence. The operator still needs validated upgrade path, capacity and rollback requirements.
Question 238
An LDAP-backed firewall group accidentally imports all directory users when only a restricted Support group should have access. Which mapping should be repaired?
- Restrict the LDAP search base and Support DN filter; validate an included and excluded directory account.
- Inspect the application server’s own Support authorization group and rely on that group while keeping the broad firewall LDAP mapping.
- Change the firewall service from HTTPS to ALL so the authentication process can query every department.
- Review the LDAP connector’s source interface and apply a dedicated translated IP to improve directory search consistency.
Explanation
Correct Answer
A:An LDAP-backed FortiGate firewall group should select only the authorized directory group rather than every identity returned by a remote server. Inspect the bind/search result and configured remote-group distinguished name or equivalent matching scope; verify the intended member and excluded users. Retest from accounts inside and outside the Support group to prove the final firewall rule implements authorization beyond successful password authentication.
Incorrect Answers
B:Application-layer authorization may provide another necessary control, but the stated requirement is to restrict the FortiGate identity policy itself to Support. A broad imported user group allows extra users to reach the protected application path. Correct search scope and directory group mapping at the firewall.
C:Transport permission for application traffic is not a group membership filter. Broadening service scope makes the policy less restrictive, not more accurate. Inspect the bind/search result and configured remote-group distinguished name or equivalent matching scope; verify the intended member and excluded users.
D:Source routing can affect LDAP server reachability, but the symptom is overinclusive group membership rather than an unanswered bind. Changing the source address cannot restrict directory search to the Support DN or nested scope. Verify the LDAP base DN, group filter, exact memberships and matching firewall group.
Question 239
The FortiGate suddenly classifies several new sites as unrated during a FortiGuard outage. Locally blocked URLs still work. What should the administrator distinguish?
- Check FortiGuard rating availability separately from local URL-rule matching before labeling an unrated site permitted.
- Inspect the web-filter static URL list for each locally blocked destination and temporarily disable its Block entry during the FortiGuard outage.
- Set all unknown-site category decisions to Allow permanently.
- Review the FortiGuard web-rating cache and create an emergency unrated-site Allow category for the affected user policy.
Explanation
Correct Answer
A:FortiGuard web rating errors can arise from subscription, DNS or service reachability issues while static local URL denies continue to operate. Separate the remote category lookup failure from the locally configured URL action, and inspect the selected profile's rating-error behavior. Restore approved rating connectivity and test both an unrated destination and a known local deny without bypassing unrelated web policy.
Incorrect Answers
B:A local static URL Block can continue working while remote category-rating services fail, so removing it would discard functioning protection and would not restore FortiGuard lookup connectivity. Separate the rating service and entitlement diagnostics from the independent local URL-pattern verdicts; preserve existing approved blocks.
C:A temporary rating failure is not a policy justification for unconditionally trusting new destinations. Restore rating reachability and document the allowed error action. Separate the remote category lookup failure from the locally configured URL action, and inspect the selected profile's rating-error behavior.
D:The rating-cache status is relevant during a FortiGuard outage, but a blanket category Allow can grant access to destinations whose risk is unknown and does not explain functioning local static Block entries. Identify the actual lookup error, policy fallback behavior and approved incident response before broadening permission.
Question 240
An application-control event shows that a streaming app matched the Finance policy and the sensor action was Monitor. The session remains available even though the security team expected a denial. What setting should be reviewed before assuming that the application signature failed?
- Use a narrow application-control Block action on the actual matched streaming signature, testing a fresh connection.
- Update the application-control database and leave the matching streaming signature in Monitor, expecting the refreshed signature to enforce a Block automatically.
- Disable the matching firewall-policy ACCEPT action to stop all traffic regardless of application.
- Change the forwarding rule’s permitted service from TCP/443 to TCP/80 while leaving the streaming signature action at Monitor on the matched HTTPS policy.
Explanation
Correct Answer
A:Application-control Monitor records a classified session without necessarily blocking it; Block or other supported actions change the enforced outcome. Confirm the actual application signature, sensor action, selected policy and whether the session began before a recent sensor update. Generate a new controlled connection and compare application-control event action with observed client delivery before declaring prevention effective.
Incorrect Answers
B:Signature freshness changes identification quality but not an explicit Monitor action that permits matching traffic. Correct the effective sensor action for this signature and verify a fresh session.
C:A blanket deny can block legitimate services on the same port and sidestep the intended application-specific decision. Use the supported per-application action in the matched profile. Confirm the actual application signature, sensor action, selected policy and whether the session began before a recent sensor update.
D:Port restrictions may affect other web activity but do not express the intended per-application denial. The logs already identify the streaming signature under an Allow policy, so change the correct sensor enforcement action.