Fortinet FCP_FAZ_AN-7.6 Practice Test 66
Question 650
Repeated exploit attempts from different scanners require source-target correlation rather than a total ADOM event count. The observed fault is: Unscoped event totals can merge unrelated scans into one purported targeted attack. How should the administrator restore and verify the intended state?
- The corrective action is to conflate monitor-only IPS action with blocked exploitation.
- The corrective action is to alert on all allowed DNS sessions as confirmed IPS exploitation.
- The corrective action is to refine signature and grouping conditions and validate a real attack-like test sequence.
- The corrective action is to ignore the affected destination when asserting repeated targeted attack.
Explanation
Correct Answer
C:Recheck IPS signature IDs, action, affected target, source IP, count and alert link to logs. Correlation depends on grouping event fields that represent a coherent threat sequence.
Incorrect Answers
A:Conflate monitor-only IPS action with blocked exploitation. Unscoped event totals can merge unrelated scans into one purported targeted attack. Instead, refine signature and grouping conditions and validate a real attack-like test sequence.
B:Alert on all allowed DNS sessions as confirmed IPS exploitation. Unscoped event totals can merge unrelated scans into one purported targeted attack. Instead, refine signature and grouping conditions and validate a real attack-like test sequence.
D:Ignore the affected destination when asserting repeated targeted attack. Unscoped event totals can merge unrelated scans into one purported targeted attack. Instead, refine signature and grouping conditions and validate a real attack-like test sequence.
Question 651
A threat intelligence IOC is known but traffic to the matching destination never generates an event handler hit. Which configuration decision most directly resolves this situation?
- Configure a supported event condition combining current IOC and session evidence with relevant device or ADOM scope.
- Treat any random destination IP as a verified current IOC.
- Match only the FortiAnalyzer appliance address as the remote destination.
- Ignore indicator expiration and use a permanent global block list by default.
Explanation
Correct Answer
A:This is the targeted correction for outbound suspicious destination indicator match. IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
Incorrect Answers
B:An expired or mis-mapped indicator can produce missed alerts or persistent false positives. Use configure a supported event condition combining current IOC and session evidence with relevant device or ADOM scope.
C:Match only the FortiAnalyzer appliance address as the remote destination. IOC-based detection relies on correctly mapped observable fields and current intelligence validity. Relevant observations are IOC identity and validity, destination field, matched logs and handler execution.
D:An expired or mis-mapped indicator can produce missed alerts or persistent false positives. The supported correction is configure a supported event condition combining current IOC and session evidence with relevant device or ADOM scope.
Question 652
A threat intelligence IOC is known but traffic to the matching destination never generates an event handler hit. What evidence most strongly confirms the operational condition?
- IOC identity and validity, destination field, matched logs and handler execution.
- A connector icon without authorization or current API response.
- A severity label without source evidence and affected asset identity.
- An automation playbook name with no job history or target outcome.
Explanation
Correct Answer
A:The planned operation is configure a supported event condition combining current IOC and session evidence with relevant device or ADOM scope. These observations directly test outbound suspicious destination indicator match under the actual system state.
Incorrect Answers
B:A connector icon without authorization or current API response. The relevant evidence is IOC identity and validity, destination field, matched logs and handler execution. IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
C:A severity label without source evidence and affected asset identity. The relevant evidence is IOC identity and validity, destination field, matched logs and handler execution. IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
D:An automation playbook name with no job history or target outcome. The relevant evidence is IOC identity and validity, destination field, matched logs and handler execution. IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
Question 653
A threat intelligence IOC is known but traffic to the matching destination never generates an event handler hit. What FortiAnalyzer behavior explains the correct decision?
- A connector listed in inventory always has valid permissions and network reachability.
- A delivered notification email always means the remote endpoint was quarantined.
- IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
- A saved playbook without an eligible trigger automatically performs all tasks.
Explanation
Correct Answer
C:This is why configure a supported event condition combining current IOC and session evidence with relevant device or ADOM scope. Verification depends on IOC identity and validity, destination field, matched logs and handler execution.
Incorrect Answers
A:A connector listed in inventory always has valid permissions and network reachability. That generalization is incorrect in the context of outbound suspicious destination indicator match. The relevant behavior is IOC-based detection relies on correctly mapped observable fields and current intelligence validity. Check IOC identity and validity, destination field, matched logs and handler execution.
B:A delivered notification email always means the remote endpoint was quarantined. That generalization is incorrect in the context of outbound suspicious destination indicator match. The relevant behavior is IOC-based detection relies on correctly mapped observable fields and current intelligence validity. Check IOC identity and validity, destination field, matched logs and handler execution.
D:A saved playbook without an eligible trigger automatically performs all tasks. That generalization is incorrect in the context of outbound suspicious destination indicator match. The relevant behavior is IOC-based detection relies on correctly mapped observable fields and current intelligence validity. Check IOC identity and validity, destination field, matched logs and handler execution.
Question 654
A threat intelligence IOC is known but traffic to the matching destination never generates an event handler hit. An operator instead chooses this incorrect shortcut: Treat any random destination IP as a verified current IOC. Which resulting risk should the reviewer identify?
- An expired or mis-mapped indicator can produce missed alerts or persistent false positives.
- Reviewing the playbook job result caused the original malicious event.
- The only effect is a cosmetic incident title change.
- An approved narrow connector scope caused every unrelated Internet outage.
Explanation
Correct Answer
A:The intended preventive choice is configure a supported event condition combining current IOC and session evidence with relevant device or ADOM scope. IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
Incorrect Answers
B:This does not account for the actual outbound suspicious destination indicator match weakness. The more relevant failure is an expired or mis-mapped indicator can produce missed alerts or persistent false positives.
C:This does not account for the actual outbound suspicious destination indicator match weakness. Confirm with IOC identity and validity, destination field, matched logs and handler execution.
D:This does not account for the actual outbound suspicious destination indicator match weakness. In this specific situation, a threat intelligence IOC is known but traffic to the matching destination never generates an event handler hit.
Question 655
A threat intelligence IOC is known but traffic to the matching destination never generates an event handler hit. The observed fault is: An expired or mis-mapped indicator can produce missed alerts or persistent false positives. How should the administrator restore and verify the intended state?
- Match only the FortiAnalyzer appliance address as the remote destination.
- Ignore indicator expiration and use a permanent global block list by default.
- Refresh matching logic and indicator source and prove a known test event matches.
- Treat any random destination IP as a verified current IOC.
Explanation
Correct Answer
C:This fixes the described operational problem with observable validation. IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
Incorrect Answers
A:Match only the FortiAnalyzer appliance address as the remote destination. An expired or mis-mapped indicator can produce missed alerts or persistent false positives. Instead, refresh matching logic and indicator source and prove a known test event matches.
B:Ignore indicator expiration and use a permanent global block list by default. An expired or mis-mapped indicator can produce missed alerts or persistent false positives. Instead, refresh matching logic and indicator source and prove a known test event matches.
D:Treat any random destination IP as a verified current IOC. An expired or mis-mapped indicator can produce missed alerts or persistent false positives. Instead, refresh matching logic and indicator source and prove a known test event matches.
Question 656
An analyst needs to alert on outbound sessions to a specified malicious domain only while the indicator is still valid. Which administrator action meets the documented requirement?
- For this FortiAnalyzer investigation, configure a supported event condition combining current IOC and session evidence with relevant device or ADOM scope.
- For this FortiAnalyzer investigation, match only the FortiAnalyzer appliance address as the remote destination.
- For this FortiAnalyzer investigation, ignore indicator expiration and use a permanent global block list by default.
- For this FortiAnalyzer investigation, treat any random destination IP as a verified current IOC.
Explanation
Correct Answer
A:This is the targeted correction for outbound suspicious destination indicator match. Verify using IOC identity and validity, destination field, matched logs and handler execution.
Incorrect Answers
B:Match only the FortiAnalyzer appliance address as the remote destination. IOC-based detection relies on correctly mapped observable fields and current intelligence validity. Relevant observations are IOC identity and validity, destination field, matched logs and handler execution.
C:An expired or mis-mapped indicator can produce missed alerts or persistent false positives. In this specific situation, an analyst needs to alert on outbound sessions to a specified malicious domain only while the indicator is still valid.
D:An expired or mis-mapped indicator can produce missed alerts or persistent false positives. This change does not provide the specified control.
Question 657
An analyst needs to alert on outbound sessions to a specified malicious domain only while the indicator is still valid. Which observations should the engineer inspect before declaring success?
- The supporting evidence is IOC identity and validity, destination field, matched logs and handler execution.
- The supporting evidence is an approved change request without recorded workflow execution.
- The supporting evidence is a connector icon without authorization or current API response.
- The supporting evidence is a severity label without source evidence and affected asset identity.
Explanation
Correct Answer
A:The planned operation is configure a supported event condition combining current IOC and session evidence with relevant device or ADOM scope. IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
Incorrect Answers
B:An approved change request without recorded workflow execution. The relevant evidence is IOC identity and validity, destination field, matched logs and handler execution. IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
C:A connector icon without authorization or current API response. The relevant evidence is IOC identity and validity, destination field, matched logs and handler execution. IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
D:A severity label without source evidence and affected asset identity. The relevant evidence is IOC identity and validity, destination field, matched logs and handler execution. IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
Question 658
An analyst needs to alert on outbound sessions to a specified malicious domain only while the indicator is still valid. Which platform statement is MOST accurate for this scenario?
- The governing concept is that a saved playbook without an eligible trigger automatically performs all tasks.
- The governing concept is that a connector listed in inventory always has valid permissions and network reachability.
- The governing concept is that every IOC match is confirmed active malware compromise.
- The governing concept is that IOC-based detection relies on correctly mapped observable fields and current intelligence validity.
Explanation
Correct Answer
D:This is why configure a supported event condition combining current IOC and session evidence with relevant device or ADOM scope.
Incorrect Answers
A:A saved playbook without an eligible trigger automatically performs all tasks. That generalization is incorrect in the context of outbound suspicious destination indicator match. The relevant behavior is IOC-based detection relies on correctly mapped observable fields and current intelligence validity. Check IOC identity and validity, destination field, matched logs and handler execution.
B:A connector listed in inventory always has valid permissions and network reachability. That generalization is incorrect in the context of outbound suspicious destination indicator match. The relevant behavior is IOC-based detection relies on correctly mapped observable fields and current intelligence validity. Check IOC identity and validity, destination field, matched logs and handler execution.
C:Every IOC match is confirmed active malware compromise. That generalization is incorrect in the context of outbound suspicious destination indicator match. The relevant behavior is IOC-based detection relies on correctly mapped observable fields and current intelligence validity. Check IOC identity and validity, destination field, matched logs and handler execution.
Question 659
An analyst needs to alert on outbound sessions to a specified malicious domain only while the indicator is still valid. An operator instead chooses this incorrect shortcut: Treat any random destination IP as a verified current IOC. Which consequence BEST explains the flaw in the proposed change?
- The material failure is that an approved narrow connector scope caused every unrelated Internet outage.
- The material failure is that preserving the task audit trail created all earlier endpoint infections.
- The material failure is that an expired or mis-mapped indicator can produce missed alerts or persistent false positives.
- The material failure is that the only effect is a cosmetic incident title change.
Explanation
Correct Answer
C:The intended preventive choice is configure a supported event condition combining current IOC and session evidence with relevant device or ADOM scope.
Incorrect Answers
A:This does not account for the actual outbound suspicious destination indicator match weakness. In this specific situation, an analyst needs to alert on outbound sessions to a specified malicious domain only while the indicator is still valid.
B:This does not account for the actual outbound suspicious destination indicator match weakness. Preserving the task audit trail created all earlier endpoint infections.
D:This does not account for the actual outbound suspicious destination indicator match weakness. The only effect is a cosmetic incident title change.
Question 660
An analyst needs to alert on outbound sessions to a specified malicious domain only while the indicator is still valid. The observed fault is: An expired or mis-mapped indicator can produce missed alerts or persistent false positives. Which remediation best corrects the root cause?
- The corrective action is to refresh matching logic and indicator source and prove a known test event matches.
- The corrective action is to ignore indicator expiration and use a permanent global block list by default.
- The corrective action is to treat any random destination IP as a verified current IOC.
- The corrective action is to match only the FortiAnalyzer appliance address as the remote destination.
Explanation
Correct Answer
A:This fixes the described operational problem with observable validation. Recheck IOC identity and validity, destination field, matched logs and handler execution.
Incorrect Answers
B:Ignore indicator expiration and use a permanent global block list by default. An expired or mis-mapped indicator can produce missed alerts or persistent false positives. Instead, refresh matching logic and indicator source and prove a known test event matches.
C:Treat any random destination IP as a verified current IOC. An expired or mis-mapped indicator can produce missed alerts or persistent false positives. Instead, refresh matching logic and indicator source and prove a known test event matches.
D:Match only the FortiAnalyzer appliance address as the remote destination. An expired or mis-mapped indicator can produce missed alerts or persistent false positives. Instead, refresh matching logic and indicator source and prove a known test event matches.