Fortinet NSE5_SSE_AD-7.6 Practice Test 47
Question 460
An incident review for Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator concerns the following specific environment: A bank's corporate web-use policy denies newly classified risky categories, yet the matched SASE web-filter category action is set to allow. Which TWO actions form a technically sound fix-and-check plan for this exact incident?
- Correct the fault by: Set the intended web-filter category action within the profile applied to the matching SIA access policy.
- Instead configure: Apply supported geographic policy conditions for the authorized user/service scope and account for location-signal limitations.
- Test the diagnosis with: Compare the requested URL category, configured action and observed matched web-filter log entry.
- Use the shortcut: Change DNS TTL values and expect that to convert a monitor-only category into a block.
- Instead collect: Compare attack-signature event logs and the IPS sensor policy with controlled test traffic on the relevant path.
Explanation
Correct Answer
A:URL category verdicts depend on the profile's category action and its attachment to the active policy. This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence.
C:URL category verdicts depend on the profile's category action and its attachment to the active policy. The expected result is: Blocked-category test requests are denied and approved business categories retain intended access.
Incorrect Answers
B:This concerns a different operational control (Geofencing condition) and can be sensible in its own incident, but the reported url category enforcement problem requires a more direct response.
D:That option would use the shortcut: Change DNS TTL values and expect that to convert a monitor-only category into a block, but it addresses a different concern. URL category verdicts depend on the profile's category action and its attachment to the active policy.
E:This concerns a different operational control (Intrusion prevention) and can be sensible in its own incident, but the reported url category enforcement problem requires a more direct response. Check the relevant evidence instead: Compare the requested URL category, configured action and observed matched web-filter log entry.
Question 461
A tenant's web filter restricts sites by URL category but unmanaged remote-control applications still run over allowed sites. An initial suggestion was to assume a generic URL reputation category automatically enforces every application signature. Which implementation or configuration decision most directly corrects the stated problem? Select ONE best answer.
- Apply a supported IPS sensor with approved signature actions to the inspected matching traffic.
- Assume a generic URL reputation category automatically enforces every application signature.
- Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility.
- Bind the approved content-inspection security profile or profile group to the policy that actually matches the protected traffic.
Explanation
Correct Answer
C:URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
Incorrect Answers
A:IPS examines network attack behavior and signatures that are not equivalent to file antivirus or website categories. That addresses an alternative control; the reported Fortinet requirement instead calls for: Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility.
B:That option would assume a generic URL reputation category automatically enforces every application signature, but it addresses a different concern. URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
D:Creating a security profile does not inspect permitted traffic until an applicable access policy enforces it. That addresses an alternative control; the reported Fortinet requirement instead calls for: Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility.
Question 462
Consider this FortiSASE/SD-WAN 7.6 operational report: A tenant's web filter restricts sites by URL category but unmanaged remote-control applications still run over allowed sites. The engineering proposal is: Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility. Which technical principle best explains the expected behavior and why the direct correction is necessary? Select ONE best answer.
- URL category verdicts depend on the profile's category action and its attachment to the active policy.
- Location restrictions require an enforced, reliable geolocation condition; user identity alone does not impose country boundaries.
- URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
- Creating a security profile does not inspect permitted traffic until an applicable access policy enforces it.
Explanation
Correct Answer
C:A satisfactory result would be: Disallowed application behavior is identified and controlled while authorized applications remain available.
Incorrect Answers
A:Applied to the observed case: A school wants to block gambling sites, but the SASE web-filter profile still uses monitor-only action for that category. That addresses an alternative control; the reported Fortinet requirement instead calls for: URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
B:Applied to the observed case: A restricted business application should be inaccessible from a disallowed region, but the relevant SASE policy omits location-based access conditions. That addresses an alternative control; the reported Fortinet requirement instead calls for: URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
D:This concerns a different operational control (Security profile attachment) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
Question 463
The on-call engineer is evaluating the following behavior before changing production configuration: A tenant's web filter restricts sites by URL category but unmanaged remote-control applications still run over allowed sites. What evidence should the engineer gather FIRST to distinguish the suspected fault from unrelated issues? Select ONE best answer.
- Compare the requested URL category, configured action and observed matched web-filter log entry.
- Inspect the SaaS application/action classification and the inline CASB decision for an authorized test upload.
- Inspect detected application IDs, application-control verdicts and security profile binding for the test session.
- Compare FortiClient posture findings, applied compliance rule and SASE policy decision for a failing test endpoint.
Explanation
Correct Answer
C:URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable. This observation directly distinguishes the reported application control problem from unrelated network or SASE symptoms.
Incorrect Answers
A:This concerns a different operational control (URL category enforcement) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
B:SaaS activity restrictions need visibility and action-level policy rather than a blanket allow for the SaaS destination. That addresses an alternative control; the reported Fortinet requirement instead calls for: Inspect detected application IDs, application-control verdicts and security profile binding for the test session.
D:Managed endpoint compliance must be evaluated and associated with access decisions; enrollment alone is not proof of a healthy device. That addresses an alternative control; the reported Fortinet requirement instead calls for: Inspect detected application IDs, application-control verdicts and security profile binding for the test session.
Question 464
After the authorized response to this incident, the operator must validate the effect: A tenant's web filter restricts sites by URL category but unmanaged remote-control applications still run over allowed sites. Which result would most directly demonstrate that the change achieved its intended outcome? Select ONE best answer.
- Approved benign connections continue while the designated exploit-pattern test receives the planned IPS action.
- Access is permitted from approved regions and blocked from the designated prohibited regions according to policy.
- Access is restored only after the required security control is healthy and a compliant evaluation succeeds.
- Disallowed application behavior is identified and controlled while authorized applications remain available.
Explanation
Correct Answer
D:The required mechanism is: URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
Incorrect Answers
A:This concerns a different operational control (Intrusion prevention) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
B:This concerns a different operational control (Geofencing condition) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
C:The required mechanism is: Temporary denial for failed posture protects access until the device satisfies the actual control and policy reevaluates it. That addresses an alternative control; the reported Fortinet requirement instead calls for: Disallowed application behavior is identified and controlled while authorized applications remain available.
Question 465
An operations ticket describes this condition: A tenant's web filter restricts sites by URL category but unmanaged remote-control applications still run over allowed sites. The team needs to address the underlying fault and gather conclusive evidence. Which proposed correction-and-evidence pair offers the most defensible way to close this case? Select ONE best answer.
- Correct: Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility. Verify: Inspect detected application IDs, application-control verdicts and security profile binding for the test session.
- Correct: Set the intended web-filter category action within the profile applied to the matching SIA access policy. Verify: Compare the requested URL category, configured action and observed matched web-filter log entry.
- Correct: Bind the approved content-inspection security profile or profile group to the policy that actually matches the protected traffic. Verify: Compare matched FortiSASE policy ID and associated active inspection profiles with traffic/security log verdicts.
- Correct: Configure and attach an approved DLP rule or profile aligned to the sensitive-data definitions and supported inspected channels. Verify: Inspect DLP pattern/classification results and matched policy for controlled synthetic sensitive data.
Explanation
Correct Answer
A:URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable. The change should demonstrate: Disallowed application behavior is identified and controlled while authorized applications remain available.
Incorrect Answers
B:Correct: Set the intended web-filter category action within the profile applied to the matching SIA access policy.
C:Creating a security profile does not inspect permitted traffic until an applicable access policy enforces it. That addresses an alternative control; the reported Fortinet requirement instead calls for: Correct: Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility. Verify: Inspect detected application IDs, application-control verdicts and security profile binding for the test session.
D:This concerns a different operational control (DLP sensitive-data policy) and can be sensible in its own incident, but the reported application control problem requires a more direct response. Here the controlling principle is: URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
Question 466
A compliance team requires blocking a specific collaboration application's unwanted feature but its SASE policy controls only website reputation, not application identity. An initial suggestion was to assume a generic URL reputation category automatically enforces every application signature. What is the most appropriate targeted intervention before expanding the incident scope? Select ONE best answer.
- Apply a supported IPS sensor with approved signature actions to the inspected matching traffic.
- Choose the supported preventive policy action for the identified SaaS behavior and verify it is enforced, not merely observed.
- Assume a generic URL reputation category automatically enforces every application signature.
- Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility.
Explanation
Correct Answer
D:URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
Incorrect Answers
A:This concerns a different operational control (Intrusion prevention) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
B:Logging or monitoring a SaaS activity provides visibility but does not by itself prevent that activity. That addresses an alternative control; the reported Fortinet requirement instead calls for: Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility.
C:That option would assume a generic URL reputation category automatically enforces every application signature, but it addresses a different concern. URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
Question 467
Consider this FortiSASE/SD-WAN 7.6 operational report: A compliance team requires blocking a specific collaboration application's unwanted feature but its SASE policy controls only website reputation, not application identity. The engineering proposal is: Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility. Which mechanism most directly accounts for the reported failure? Select ONE best answer.
- Data classification and exfiltration policy require data-aware inspection, beyond destination-category filtering.
- Location restrictions require an enforced, reliable geolocation condition; user identity alone does not impose country boundaries.
- URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
- Temporary denial for failed posture protects access until the device satisfies the actual control and policy reevaluates it.
Explanation
Correct Answer
C:A satisfactory result would be: Disallowed application behavior is identified and controlled while authorized applications remain available.
Incorrect Answers
A:This concerns a different operational control (DLP sensitive-data policy) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
B:This concerns a different operational control (Geofencing condition) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
D:This concerns a different operational control (Noncompliance remediation flow) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
Question 468
The on-call engineer is evaluating the following behavior before changing production configuration: A compliance team requires blocking a specific collaboration application's unwanted feature but its SASE policy controls only website reputation, not application identity. Which targeted prechange observation would test the working diagnosis most decisively? Select ONE best answer.
- Compare the applied TLS inspection mode with logs showing inspected TLS connections and payload-based security results.
- Inspect detected application IDs, application-control verdicts and security profile binding for the test session.
- Compare the requested URL category, configured action and observed matched web-filter log entry.
- Compare the exact activity policy action and CASB event verdict with an authorized test transaction.
Explanation
Correct Answer
B:URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable. If confirmed, the targeted intervention is: Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility.
Incorrect Answers
A:Applied to the observed case: An operations team expects encrypted-download malware detection while its SASE policy performs certificate-only inspection of TLS connections. That addresses an alternative control; the reported Fortinet requirement instead calls for: Inspect detected application IDs, application-control verdicts and security profile binding for the test session.
C:This concerns a different operational control (URL category enforcement) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
D:This concerns a different operational control (SaaS monitoring versus enforcement) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
Question 469
After the authorized response to this incident, the operator must validate the effect: A compliance team requires blocking a specific collaboration application's unwanted feature but its SASE policy controls only website reputation, not application identity. What should be recorded as the strongest postchange acceptance evidence? Select ONE best answer.
- Target devices report the new policy version and are evaluated against the updated posture requirement.
- Disallowed application behavior is identified and controlled while authorized applications remain available.
- Approved benign connections continue while the designated exploit-pattern test receives the planned IPS action.
- Controlled approved test traffic is processed by the intended profile and relevant security verdicts appear.
Explanation
Correct Answer
B:The required mechanism is: URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.
Incorrect Answers
A:The required mechanism is: Editing a central endpoint profile is not enough if the affected agents have not been assigned or received the updated configuration. That addresses an alternative control; the reported Fortinet requirement instead calls for: Disallowed application behavior is identified and controlled while authorized applications remain available.
C:The required mechanism is: IPS examines network attack behavior and signatures that are not equivalent to file antivirus or website categories. That addresses an alternative control; the reported Fortinet requirement instead calls for: Disallowed application behavior is identified and controlled while authorized applications remain available.
D:This concerns a different operational control (Security profile attachment) and can be sensible in its own incident, but the reported application control problem requires a more direct response.
Question 470
An incident review for Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator concerns the following specific environment: A compliance team requires blocking a specific collaboration application's unwanted feature but its SASE policy controls only website reputation, not application identity. Which TWO actions form a technically sound fix-and-check plan for this exact incident?
- Instead configure: Configure and attach an approved DLP rule or profile aligned to the sensitive-data definitions and supported inspected channels.
- Correct the fault by: Apply appropriate application-control signatures and actions in the matched SASE inspection policy, considering TLS visibility.
- Instead collect: Compare the requested URL category, configured action and observed matched web-filter log entry.
- Use the shortcut: Assume a generic URL reputation category automatically enforces every application signature.
- Test the diagnosis with: Inspect detected application IDs, application-control verdicts and security profile binding for the test session.
Explanation
Correct Answer
B:URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable. The expected result is: Disallowed application behavior is identified and controlled while authorized applications remain available.
E:URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable. This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence.
Incorrect Answers
A:This concerns a different operational control (DLP sensitive-data policy) and can be sensible in its own incident, but the reported application control problem requires a more direct response. Check the relevant evidence instead: Inspect detected application IDs, application-control verdicts and security profile binding for the test session.
C:This concerns a different operational control (URL category enforcement) and can be sensible in its own incident, but the reported application control problem requires a more direct response. Check the relevant evidence instead: Inspect detected application IDs, application-control verdicts and security profile binding for the test session.
D:That option would use the shortcut: Assume a generic URL reputation category automatically enforces every application signature, but it addresses a different concern. URL category controls and application-aware controls classify different aspects of traffic and are not interchangeable.