Fortinet NSE5_SSE_AD-7.6 Practice Test 70
Question 690
An incident review for Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator concerns the following specific environment: A branch's local SASE dashboard contains recent threat detections, yet the central logging service has a two-hour ingestion gap. Which TWO actions form a technically sound fix-and-check plan for this exact incident?
- Instead configure: Inspect FortiSASE inline-CASB or application-security events for the recorded SaaS action and rule verdict.
- Use the shortcut: Assume visibility in the SASE local portal proves the SIEM received every event.
- Test the diagnosis with: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
- Correct the fault by: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end.
- Instead collect: Graph member-level loss samples and threshold changes at the specific outage timestamps.
Explanation
Correct Answer
C:This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence.
D:This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence. Local event generation and successful forwarding to an external collector are separate operational stages.
Incorrect Answers
A:This concerns a different operational control (Cloud-app control event) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response.
B:The direct remedial step is: Validate supported log-forwarding destination, transport, filters and ingestion confirmation end to end.
E:This concerns a different operational control (Packet-loss trend review) and can be sensible in its own incident, but the reported external log forwarding assurance problem requires a more direct response. Check the relevant evidence instead: Check local event timestamps, forwarding configuration, delivery errors and collector receipt for a unique test event.
Question 691
A privacy-controlled SASE report replaces user identifiers with anonymized values, but the incident team tries to correlate those values directly to directory usernames. An initial suggestion was to disable privacy protections for all users simply to make the dashboard more convenient. What is the most appropriate targeted intervention before expanding the incident scope? Select ONE best answer.
- Query identity/authentication logs and the upstream identity provider's corresponding events to isolate login failures.
- Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence.
- Disable privacy protections for all users simply to make the dashboard more convenient.
- Correlate historical health-check and member-state event timestamps with reported application incidents.
Explanation
Correct Answer
B:Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
Incorrect Answers
A:User authentication can fail independently of internet forwarding and SD-WAN quality. That addresses an alternative control; the reported Fortinet requirement instead calls for: Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence.
C:That option would disable privacy protections for all users simply to make the dashboard more convenient, but it addresses a different concern. Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged. The direct remedial step is: Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence.
D:A present healthy status does not reconstruct transient failures; historical events and SLA changes are needed to explain failover. That addresses an alternative control; the reported Fortinet requirement instead calls for: Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence.
Question 692
Consider this FortiSASE/SD-WAN 7.6 operational report: A privacy-controlled SASE report replaces user identifiers with anonymized values, but the incident team tries to correlate those values directly to directory usernames. The engineering proposal is: Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence. Which mechanism most directly accounts for the reported failure? Select ONE best answer.
- Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
- Aggregation can hide short service-impacting loss spikes that drive steering or application failures.
- Identity success and tunnel availability are distinct from device-compliance authorization.
- A URL deny may be an intended category verdict; the decision must be traced to its matching inspection policy.
Explanation
Correct Answer
A:A satisfactory result would be: The team produces a compliant incident summary without falsely reconstructing unavailable user identities.
Incorrect Answers
B:Evidence that tests the explanation: Graph member-level loss samples and threshold changes at the specific outage timestamps. That addresses an alternative control; the reported Fortinet requirement instead calls for: Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
C:Applied to the observed case: A managed laptop is denied SASE access and network engineers assume a tunnel fault without inspecting the endpoint's compliance state. That addresses an alternative control; the reported Fortinet requirement instead calls for: Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
D:Applied to the observed case: A user's permitted business website becomes blocked; the ticket contains only a browser screenshot with no matched web-filter category or rule. That addresses an alternative control; the reported Fortinet requirement instead calls for: Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
Question 693
The on-call engineer is evaluating the following behavior before changing production configuration: A privacy-controlled SASE report replaces user identifiers with anonymized values, but the incident team tries to correlate those values directly to directory usernames. Which targeted prechange observation would test the working diagnosis most decisively? Select ONE best answer.
- Read current SLA thresholds, metric values and rule membership at the same point in time.
- Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
- Correlate user, SaaS app action, profile or policy ID and the exact block/monitor verdict.
- Review device posture attributes, compliance evaluation timestamp and matched deny rule for the specific user.
Explanation
Correct Answer
B:Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged. This observation directly distinguishes the reported anonymized report interpretation problem from unrelated network or SASE symptoms.
Incorrect Answers
A:Applied to the observed case: An operations analyst sees a 90-ms latency graph but calls the link unhealthy without knowing the service's configured latency target. That addresses an alternative control; the reported Fortinet requirement instead calls for: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
C:Applied to the observed case: A risk team asks why an SaaS file upload was blocked while the help desk reviews only ordinary DNS lookup results. That addresses an alternative control; the reported Fortinet requirement instead calls for: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
D:This concerns a different operational control (Endpoint posture incident records) and can be sensible in its own incident, but the reported anonymized report interpretation problem requires a more direct response.
Question 694
After the authorized response to this incident, the operator must validate the effect: A privacy-controlled SASE report replaces user identifiers with anonymized values, but the incident team tries to correlate those values directly to directory usernames. What should be recorded as the strongest postchange acceptance evidence? Select ONE best answer.
- The investigation identifies whether a loss spike breached the traffic's defined service target.
- The root authentication cause is identified without altering unrelated network steering.
- The team produces a compliant incident summary without falsely reconstructing unavailable user identities.
- The report states whether each candidate met the configured service requirements for the incident.
Explanation
Correct Answer
C:The required mechanism is: Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
Incorrect Answers
A:This concerns a different operational control (Packet-loss trend review) and can be sensible in its own incident, but the reported anonymized report interpretation problem requires a more direct response.
B:This concerns a different operational control (Identity sign-in failure analytics) and can be sensible in its own incident, but the reported anonymized report interpretation problem requires a more direct response.
D:This concerns a different operational control (SLA target versus performance plots) and can be sensible in its own incident, but the reported anonymized report interpretation problem requires a more direct response.
Question 695
An operations ticket describes this condition: A privacy-controlled SASE report replaces user identifiers with anonymized values, but the incident team tries to correlate those values directly to directory usernames. The team needs to address the underlying fault and gather conclusive evidence. Which combination of remedial action and technical evidence correctly addresses this ticket? Select ONE best answer.
- Correct: Query the web-filter logs for the precise URL, user, policy, category and resulting enforcement action. Verify: Compare the logged URL category and action with the applied profile at the incident timestamp.
- Correct: Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence. Verify: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
- Correct: Compare existing versus fresh session start times and recorded egress before assessing the rule change. Verify: Inspect the session table and traffic records for connection creation time and selected member across the change.
- Correct: Query identity/authentication logs and the upstream identity provider's corresponding events to isolate login failures. Verify: Match user, authentication request time, identity method and response or trust error across systems.
Explanation
Correct Answer
B:Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged. The change should demonstrate: The team produces a compliant incident summary without falsely reconstructing unavailable user identities.
Incorrect Answers
A:This concerns a different operational control (Web-filter event diagnosis) and can be sensible in its own incident, but the reported anonymized report interpretation problem requires a more direct response.
C:Correct: Compare existing versus fresh session start times and recorded egress before assessing the rule change.
D:This concerns a different operational control (Identity sign-in failure analytics) and can be sensible in its own incident, but the reported anonymized report interpretation problem requires a more direct response. Correct: Query identity/authentication logs and the upstream identity provider's corresponding events to isolate login failures.
Question 696
An auditor expects exact endpoint identities in exported aggregate reports despite the organization's configured anonymization policy. An initial suggestion was to disable privacy protections for all users simply to make the dashboard more convenient. Which engineering change fixes the specific control gap rather than a neighboring symptom? Select ONE best answer.
- Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence.
- Use SD-WAN rule and session logs to identify the actual matching rule and selected member for the affected flow.
- Query the web-filter logs for the precise URL, user, policy, category and resulting enforcement action.
- Disable privacy protections for all users simply to make the dashboard more convenient.
Explanation
Correct Answer
A:Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged. Accept the remediation only when: The team produces a compliant incident summary without falsely reconstructing unavailable user identities.
Incorrect Answers
B:Link utilization summaries cannot by themselves establish why a particular session matched a steering rule. That addresses an alternative control; the reported Fortinet requirement instead calls for: Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence.
C:A URL deny may be an intended category verdict; the decision must be traced to its matching inspection policy. That addresses an alternative control; the reported Fortinet requirement instead calls for: Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence.
D:That option would disable privacy protections for all users simply to make the dashboard more convenient, but it addresses a different concern. Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged. The deciding evidence is: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
Question 697
Consider this FortiSASE/SD-WAN 7.6 operational report: An auditor expects exact endpoint identities in exported aggregate reports despite the organization's configured anonymization policy. The engineering proposal is: Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence. What concept makes the proposed correction technically appropriate in this situation? Select ONE best answer.
- Aggregation can hide short service-impacting loss spikes that drive steering or application failures.
- Session persistence can differ from new connection selection; timing matters to interpreting steering logs.
- Link utilization summaries cannot by themselves establish why a particular session matched a steering rule.
- Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
Explanation
Correct Answer
D:A satisfactory result would be: The team produces a compliant incident summary without falsely reconstructing unavailable user identities. The principle explains why the proposed direct fix is necessary: Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence.
Incorrect Answers
A:Evidence that tests the explanation: Graph member-level loss samples and threshold changes at the specific outage timestamps. That addresses an alternative control; the reported Fortinet requirement instead calls for: Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
B:Evidence that tests the explanation: Inspect the session table and traffic records for connection creation time and selected member across the change. That addresses an alternative control; the reported Fortinet requirement instead calls for: Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
C:Applied to the observed case: A branch team says critical app traffic used the wrong circuit, but their screenshots show only interface bandwidth totals without identifying the matched steering rule. That addresses an alternative control; the reported Fortinet requirement instead calls for: Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
Question 698
The on-call engineer is evaluating the following behavior before changing production configuration: An auditor expects exact endpoint identities in exported aggregate reports despite the organization's configured anonymization policy. What diagnostic comparison best establishes the reported control mismatch? Select ONE best answer.
- Inspect signature/category, action, matched user/policy and corresponding session/time fields in security events.
- Match user, authentication request time, identity method and response or trust error across systems.
- Inspect the session table and traffic records for connection creation time and selected member across the change.
- Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
Explanation
Correct Answer
D:Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
Incorrect Answers
A:Applied to the observed case: A security manager opens a traffic volume report and concludes that no malware block occurred because the volume panel lacks signature detail. That addresses an alternative control; the reported Fortinet requirement instead calls for: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
B:If confirmed, the targeted intervention is: Query identity/authentication logs and the upstream identity provider's corresponding events to isolate login failures. That addresses an alternative control; the reported Fortinet requirement instead calls for: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
C:If confirmed, the targeted intervention is: Compare existing versus fresh session start times and recorded egress before assessing the rule change. That addresses an alternative control; the reported Fortinet requirement instead calls for: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
Question 699
After the authorized response to this incident, the operator must validate the effect: An auditor expects exact endpoint identities in exported aggregate reports despite the organization's configured anonymization policy. Which observable outcome most convincingly confirms a successful remediation? Select ONE best answer.
- The root authentication cause is identified without altering unrelated network steering.
- Fresh sessions demonstrably follow the new design while older session behavior is accounted for.
- The team produces a compliant incident summary without falsely reconstructing unavailable user identities.
- The review can tie a specific threat verdict to the session without conflating it with aggregate traffic.
Explanation
Correct Answer
C:The required mechanism is: Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged. This is an outcome-level acceptance check rather than a proxy such as link light or portal sign-in.
Incorrect Answers
A:The required mechanism is: User authentication can fail independently of internet forwarding and SD-WAN quality. That addresses an alternative control; the reported Fortinet requirement instead calls for: The team produces a compliant incident summary without falsely reconstructing unavailable user identities.
B:The required mechanism is: Session persistence can differ from new connection selection; timing matters to interpreting steering logs. That addresses an alternative control; the reported Fortinet requirement instead calls for: The team produces a compliant incident summary without falsely reconstructing unavailable user identities.
D:The required mechanism is: Traffic logging explains sessions, while threat or security events provide inspection verdict and detection context. That addresses an alternative control; the reported Fortinet requirement instead calls for: The team produces a compliant incident summary without falsely reconstructing unavailable user identities.
Question 700
An incident review for Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator concerns the following specific environment: An auditor expects exact endpoint identities in exported aggregate reports despite the organization's configured anonymization policy. Which THREE actions or observations belong in this scenario-specific remediation and acceptance plan?
- Targeted change: Verify report anonymization settings and use an authorized, privacy-compliant correlation workflow for incident evidence.
- Use another control's outcome: The investigation distinguishes an enforced SaaS activity restriction from a reachability problem.
- Apply shortcut: Disable privacy protections for all users simply to make the dashboard more convenient.
- Diagnostic evidence: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
- Substitute unrelated change: Correlate FortiClient endpoint posture and FortiSASE policy events before treating the failure as a transport issue.
- Acceptance test: The team produces a compliant incident summary without falsely reconstructing unavailable user identities.
Explanation
Correct Answer
A:Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged. This is one of the three distinct requirements: a targeted action, specific diagnostic evidence, and an outcome-based acceptance check.
D:Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged. Diagnostic evidence: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
F:Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged. Acceptance test: The team produces a compliant incident summary without falsely reconstructing unavailable user identities.
Incorrect Answers
B:This concerns a different operational control (Cloud-app control event) and can be sensible in its own incident, but the reported anonymized report interpretation problem requires a more direct response. Check the relevant evidence instead: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.
C:That option would apply shortcut: Disable privacy protections for all users simply to make the dashboard more convenient, but it addresses a different concern. Anonymization intentionally changes identifier visibility; missing raw identities in the report does not prove traffic was not logged.
E:This concerns a different operational control (Endpoint posture incident records) and can be sensible in its own incident, but the reported anonymized report interpretation problem requires a more direct response. Check the relevant evidence instead: Compare report privacy settings, raw event access permissions and approved identity-correlation capabilities.