Fortinet NSE4_FGT_AD-7.6 Practice Test 6
Question 50
A newly joined personal laptop can authenticate to a company cloud access service but fails its security posture requirement for a confidential internal app. Which response preserves the intended access policy?
- Add the user to the private-app allow group immediately and skip the explicit endpoint-posture condition that failed.
- Treat a successful FortiSASE tunnel connection as evidence of passing the ZTNA posture tag.
- Require approved endpoint enrollment and posture compliance before granting the private-app session.
- Override the private-app enforcement policy for all managed and unmanaged devices until the one laptop finishes enrollment.
Explanation
Correct Answer
C:Verify enrollment in the approved client or agent workflow and test the measured posture conditions, such as supported security controls and device registration. Route a compliant endpoint through the authorized access policy and deny or remediate noncompliant devices. Capture the policy reason so users can fix enrollment without weakening access.
Incorrect Answers
A:Identity group membership cannot satisfy a separate device-posture gate by itself. The conditional access design requires both the approved user and the verified endpoint state before a confidential private-app session is permitted.
B:A connected FortiSASE client may have valid transport and identity while posture classification still rejects the endpoint. Inspect enrollment, the assigned ZTNA tag or compliance rule and resulting private-access policy match before granting the application.
D:A tenant-wide policy bypass would affect other users and endpoints unrelated to this one device. Remediate the laptop enrollment or failing posture criteria, then verify it matches the approved private-app rule without reducing controls for compliant or noncompliant peers.
Question 51
An FSSO-based firewall policy intended for finance staff appears to grant access to employees outside Finance. FSSO is collecting logon events successfully. What should the administrator verify?
- Whether the user-group filters and collected AD membership really limit the identities mapped to the Finance rule.
- Raise the user authentication timeout while leaving a broad FSSO collected AD group mapped to the Finance permit.
- Trust any client whose IP is in the Finance VLAN, ignoring the actual FSSO user and directory group for that address.
- Rebuild the Finance firewall address object while keeping the current broad collector user-group and policy identity match unchanged.
Explanation
Correct Answer
A:A login event is not itself proof of Finance membership. Review collector group filtering, directory group resolution, the FortiGate FSSO connector and the identity object in the matching policy. Confirm who actually maps to the group using allowed and disallowed user accounts, then narrow the configuration without breaking identity collection.
Incorrect Answers
B:Authentication duration controls how long learned identity may persist, not which AD members are mapped to the Finance-only policy. Check the collector group filter, actual user-to-IP association and the group in the matched firewall rule.
C:Network location cannot prove the logged-on user belongs to Finance. A shared or recycled address may inherit the wrong policy if FSSO group identity is not checked. Correct the actual AD membership and user mapping.
D:Address objects can constrain permitted source networks but do not repair an FSSO group that erroneously includes people outside Finance. Verify the group collected by FSSO, effective rule and user monitor entry for an unauthorized employee.
Question 52
Two FortiGate IPsec peers can ping each other, but the IKE log reports authentication failed. Which interpretation best directs troubleshooting?
- Inspect UDP 500/4500 reachability and adjust firewall rules for the peer's public address.
- Increase IKE retransmission limits and dead-peer-detection timers at both gateways.
- Align the phase-two protected subnet selectors and ESP proposals on the two peers.
- Check the matching authentication material, peer identifiers and certificate trust because transport reachability does not establish peer authentication.
Explanation
Correct Answer
D:Distinguish network connectivity from cryptographic identity checks. Compare the configured PSK or certificate, local and expected remote ID, and corresponding IKE proposal. Use debug evidence to identify the rejected step, then test phase-two negotiation and routes only after phase-one authentication succeeds. A mismatched authentication ID can reject a reachable IKE peer before any private-subnet data is transmitted.
Incorrect Answers
A:Reachability and transport filtering are legitimate early checks when no IKE responses arrive. In this case, however, an IKE authentication-failed event was already recorded. Transport availability does not explain the explicit peer credential or identity rejection, so compare configured authentication material and IDs.
B:Retransmission and DPD settings can help with slow or failing paths, but extra exchanges repeat the same cryptographically invalid authentication if peer IDs, PSKs or certificate trust disagree. An authentication-failed log calls for correlating identity and credential settings on the two peers, not first extending timers.
C:A child-SA mismatch can prevent protected traffic once IKE authentication has succeeded. The supplied log points to peer-authentication rejection, an earlier distinct failure. Correct or substantiate PSK, certificate validation and local/remote IKE IDs before changing phase-two selector definitions.
Question 53
An IPS vulnerability signature is relevant to a web server exposed in one DMZ. The team wants high confidence protection without accidentally blocking unrelated internal applications. Which approach best fits?
- Inspect the DMZ server’s outbound IPS sensor and enable the relevant exploit signature on its DMZ-to-WAN return policy.
- Configure a targeted IPS sensor or signature filter for the vulnerable service and verify its action on the matching DMZ policy.
- Apply the matching IPS signature in Monitor mode to the inbound DMZ policy and alert the SOC on every hit.
- Turn off the exact vulnerable signature on the exposed server policy to avoid false positives without testing whether an exemption is warranted.
Explanation
Correct Answer
B:Map the affected software and protocol to the applicable FortiGuard IPS signatures and attach the sensor to the actual policy protecting that server. Review whether the rule logs, monitors or blocks; test malicious and legitimate traffic. Keep signature updates and exposure remediation as separate parts of the plan.
Incorrect Answers
A:The DMZ server may have legitimate outbound flows requiring protection, so an outbound sensor is not inherently useless. The exploit described arrives from the internet and is inspected according to the inbound WAN-to-DMZ rule. Applying the signature only to the return direction does not ensure the attack-bearing request is decoded and blocked. Place the sensor on the actual incoming policy.
C:Monitoring captures potentially valuable exploit evidence and permits a learning period, but a Monitor action does not enforce the requested prevention of the known exploit against the vulnerable host. The scenario calls for a targeted blocking action, verified inspection and controlled false-positive testing.
D:Suppressing the signature removes the requested exploit detection. False positives should be substantiated by logs/representative traffic and handled with a narrow override if needed; start with applicable blocking signature and tested protocol visibility.
Question 54
Several administrators use the same super_admin account to change FortiGate security policies. Auditors cannot attribute changes to an individual. What is the best management control?
- Create separate named administrators with role-appropriate profiles and authenticated management access, while retaining a controlled emergency account.
- Rotate the shared super_admin password each week, leaving all operators using the same administrative username in configuration-change logs.
- Assign individual MFA tokens but keep the same shared FortiGate super_admin username for everyone and rely on GUI login logs alone for attribution.
- Create individually named FortiGate administrators for all staff but grant every account an unrestricted super_admin profile regardless of job responsibilities.
Explanation
Correct Answer
A:Named accounts make actions attributable and let the appliance enforce least privilege according to each administrator profile. Protect sign-in with available strong authentication and trusted management sources, and keep an audited break-glass process. Verify the change log identifies each operator rather than merely the shared role.
Incorrect Answers
B:Rotation can reduce the lifetime of a compromised shared password, but logs will still attribute every change to the single shared identity. To establish individual accountability, create separately authenticated named administrators with proper profiles and record change events.
C:Independent MFA tokens may strengthen an authentication factor, but a shared administrator identity still compromises reliable per-user policy-change attribution without a supported separately logged identity trail. Use named roles and actual user-specific login accounts.
D:Separate usernames improve attribution, but the proposal unnecessarily gives every staff member full access to security policies, users and routing. The better design pairs named identities with least-privilege profiles and a controlled, audited break-glass administrator account.
Question 55
A new firewall policy seems to allow TCP 443 from the branch LAN to a server, but sessions continue to match a different deny rule. What is the best first diagnostic step?
- Inspect traffic events generated by the intended HTTPS ACCEPT policy and enable its log-all-sessions setting for new branch attempts.
- Review whether the HTTPS service object includes TCP/443 and expand it to ALL protocols before rerunning the branch connection.
- Compare the actual source and destination, ingress and egress interfaces, protocol/port, schedule and policy order with a trace of a new session.
- Move the branch HTTPS allow above the observed deny, keeping its existing source, destination and service selectors.
Explanation
Correct Answer
C:FortiGate ordinary firewall policies are ordered and evaluate multiple match fields, not just destination service. Use session and debug-flow evidence to identify the selected policy ID, then correct only the mismatched interfaces, objects, schedule or order. Test a fresh session because existing session state can preserve a previous decision.
Incorrect Answers
A:Logging the intended permit can be helpful if that rule actually matches. The incident states that a different deny handles the new sessions; the missing logs therefore do not establish which match field is wrong. Trace the actual tuple, source and destination interfaces, schedule and policy order before modifying logging.
B:Checking the selected service is a valid policy-match diagnostic, but expanding to ALL without identifying the actual deny can open unauthorized protocols and still fail if the source, interface, address, schedule or rule order is wrong. Compare new-session policy lookup fields before making any broad permit change.
D:Changing rule order could help if a broader deny shadows a matching allow, but a wrong ingress interface, egress zone, destination address, service or schedule still prevents the permit from matching at any position. First compare the actual session and policy lookup fields before changing precedence.
Question 56
An HTTPS service presents a certificate for api.partner.example, but the client connects to portal.partner.example and reports a name mismatch. The firewall inspection CA is already trusted. What should the operator conclude?
- Full SSL inspection is impossible because a firewall cannot check hostname identities.
- The upstream server identity presented for the requested hostname must be corrected or the intended hostname used; local CA trust is a different condition.
- Install the FortiGate full-inspection signing CA again, while leaving the upstream server certificate missing portal.partner.example from its SAN names.
- Disable certificate-hostname verification for every inspected site so the wrong api.partner.example name can be accepted for portal.partner.example.
Explanation
Correct Answer
B:Trust of the FortiGate substitute signing CA addresses client trust of intercepted certificates, whereas the upstream certificate must also be appropriate for the server being reached. Compare SNI, URL, SAN entries and the actual server certificate chain. Correct a wrong virtual host or requested hostname rather than allowing blanket bypasses.
Incorrect Answers
A:Inspection can validate server certificate information and may generate substitute certificates for inspected sessions. A requested-server hostname mismatch remains a distinct server-identity problem; it is not solved by claiming such verification is impossible.
C:Trust in a FortiGate-generated substitute issuer is distinct from validating the hostname in the actual server certificate. Because the client connects to portal.partner.example while the certificate covers api.partner.example, an extra signing CA does not fix the SAN mismatch. Correct hostname or certificate identity.
D:A global hostname-check bypass would conceal mismatched or impersonated servers. Confirm the intended requested name, actual SAN and SNI, then fix the upstream certificate or use the correct endpoint without removing identity verification for unrelated sites.
Question 57
An SD-WAN member is flagged dead by its configured health check, although a technician can traceroute to unrelated public destinations over that ISP. What should be tested?
- Assume the SD-WAN health state is incorrect whenever any traceroute works.
- Replace only a different member’s SLA detection server while retaining the actual failed member’s unreachable probe target and existing health-check binding.
- Remove all health-checks so the link remains preferred regardless of outages.
- Probe the configured SLA server, protocol, route and member binding, comparing the actual health-check results with general internet reachability.
Explanation
Correct Answer
D:Performance SLA reflects measurements to configured detection targets or measured sessions, not every possible destination. Inspect the selected member, probe protocol, server reachability, failed thresholds and SD-WAN route status. Use member-specific diagnostics and, if appropriate, redundant probe targets to avoid false path failures. A link may be usable for other destinations yet fail a particular detection server or threshold.
Incorrect Answers
A:One working traceroute demonstrates reachability along its own path, not that a specific probe target or selected SD-WAN member is healthy. The configured detection server could be unreachable, filtered or responding differently.
B:Updating a monitor on another member cannot repair the bad state of the SD-WAN path being investigated. Compare the exact failed health-check target, probe protocol, routing member and thresholds before changing that member’s configuration.
C:Without meaningful health checks the system may continue selecting a broken or severely degraded path. It would hide the diagnostic symptom rather than repair a failed server, protocol or routing condition.
Question 58
An IPsec debug shows IKE phase 1 established, but there is no child security association and the peers propose different protected subnet pairs. What should be reconciled?
- Phase-2 traffic selectors and compatible ESP/PFS parameters on both peers.
- Re-enter the already accepted IKE phase-one PSK first.
- Add a broad 0.0.0.0/0 default route over the tunnel, even though the child SA has not been negotiated for the required private subnet pairs.
- Disable phase-two PFS on just one peer and leave the observed local/remote protected-subnet proposals inconsistent.
Explanation
Correct Answer
A:Once phase-one authentication is successful, the child-SA negotiation must agree on the protected traffic selector ranges and encryption/integrity/PFS settings as supported by both peers. Compare local/remote subnets from each viewpoint, inspect the rejection logs, then verify routing and policies once the SA establishes.
Incorrect Answers
B:The log proves phase-one IKE authentication already completed, so resetting those credentials will not reconcile the failed child-SA selector exchange. Compare phase-two local and remote address ranges and the ESP/PFS proposal each peer actually sends.
C:A static route becomes relevant for forwarding after a compatible child SA exists. Sending all destinations toward an unestablished tunnel cannot negotiate the missing protected subnet selectors, and a broad default may divert unrelated traffic.
D:PFS settings must be compatible on both peers when enabled, and changing one side unilaterally could create another negotiation failure. The scenario additionally identifies different subnet selector pairs, so explicitly align those ranges and the complete phase-two proposals.
Question 59
A FortiGate has been configured to send security logs to FortiAnalyzer, but the analyzer inventory shows the new device as unregistered and no searchable logs appear. Which sequence is most useful?
- Enable start-of-session traffic logs on the FortiGate and generate a test connection for FortiAnalyzer.
- Validate analyzer reachability and the FortiGate logging configuration, then verify the device is registered/authorized on FortiAnalyzer.
- Rebuild the analyzer's log-search index and increase the retention period for the new device.
- Set an explicit FortiGate source IP for logging and choose the expected outgoing route to the analyzer.
Explanation
Correct Answer
B:Central logging needs a reachable destination, appropriate logging configuration and acceptance of the sending FortiGate on the analyzer. Confirm connectivity and the configured analyzer endpoint, inspect registration/authorization status, and generate a known event. Then verify the log type, timestamp and device identity in search results.
Incorrect Answers
A:Generating a known traffic event is useful after the device is admitted, but it cannot repair an unregistered or unauthorized FortiGate at the analyzer. Establish logging-transport reachability and the device registration/authorization state first, then use a test event to verify collection.
C:Search indexes and retention affect data already accepted by a collector. The device is unregistered and no event ingress has been established, so altering storage settings cannot fix the underlying authorization or transport failure. Resolve device admission and confirm receipt before tuning queries.
D:A stable source interface and correct route may be necessary in a multihomed design, but they are not established as the cause of the reported unregistered inventory status. Validate both reachability and FortiAnalyzer device authorization before making a source-interface change; then test delivered events.
Question 60
A FortiGate policy uses web filtering to display a block message for prohibited categories. However, an HTTPS client continues to see the permitted page. Which combination should be verified first?
- Modify the category block-page replacement text without verifying that the correct web-filter profile and action actually matched the HTTPS session.
- Switch the web-filter category action from Block to Monitor in an attempt to force a deny page for the same HTTPS client.
- The effective firewall policy and web-filter action, together with the inspection method needed to evaluate the intended HTTPS URL.
- Enable logging on an unrelated web-filter profile that is not attached to the policy carrying the HTTPS session.
Explanation
Correct Answer
C:Web-filter action applies through a security profile on the firewall policy matching the traffic. Check the actual policy ID, URL or category decision, profile action and whether encrypted inspection reveals enough of the requested site or path. Compare block and permitted test pages, and evaluate supported replacement-message behavior for HTTPS.
Incorrect Answers
A:Replacement-message styling affects the page shown after an eligible security decision, but cannot create a missing deny action. Establish which policy and web profile matched and whether TLS visibility supports the intended category or URL, then inspect replacement behavior.
B:Monitor is intended for observation with permitted traffic, not for enforcing a category block. A browser continuing to load content is consistent with monitor action; inspect the category action, effective policy and applicable HTTPS inspection instead.
D:Changing an unused profile does not affect the current session or generate a block page. Confirm the profile attached to the actually matched firewall rule, its action and supported replacement-message behavior for HTTPS.