FCP_FAZ_AN-7.6 Exam dumps PDF | Exam-Dumps.net (Page: 2)

QUESTION: 9

You created a playbook on FortiAnalyzer that uses a FortiOS connector.

When configuring the FortiGate side, which type of trigger must be used so that the actions in an automation stich are available in the FortiOS connector?

FortiAnalyzer Event Handler
Fabric Connector event
FortiOS Event Log
Incoming webhook

Answer(s): D

Explanation:

When using FortiAnalyzer to create playbooks that interact with FortiOS devices, an Incoming Webhook trigger is required on the FortiGate side to make the actions in an automation stitch accessible through the FortiOS connector. The incoming webhook trigger allows FortiAnalyzer to initiate actions on FortiGate by sending HTTP POST requests to specified endpoints, which in turn trigger automation stitches defined on the FortiGate.

Here's an analysis of each option:

Option A: FortiAnalyzer Event Handler

This is incorrect. The FortiAnalyzer Event Handler is used within FortiAnalyzer itself for handling log events and alerts, but it does not trigger automation stitches on FortiGate.

Option B: Fabric Connector event

This is incorrect. Fabric Connector events are related to Fortinet's Security Fabric integrations but are not specifically used to trigger FortiGate automation stitches from FortiAnalyzer.

Option C: FortiOS Event Log

This is incorrect.
While FortiOS event logs can be used for monitoring, they are not designed to trigger automation stitches directly from FortiAnalyzer.

Option D: Incoming webhook

This is correct. The Incoming Webhook trigger on FortiGate enables it to receive requests from FortiAnalyzer, allowing playbooks to activate automation stitches defined on the FortiGate device. This method is commonly used to integrate actions from FortiAnalyzer to FortiGate via the FortiOS connector.

Reference:

According to FortiOS and FortiAnalyzer documentation, when integrating FortiAnalyzer playbooks with FortiGate automation stitches, the recommended trigger type on FortiGate is an Incoming Webhook, allowing FortiAnalyzer to interact with FortiGate's automation framework through the FortiOS connector.

Reveal Solution Next Question

QUESTION: 10

When managing incidents on FortiAnlyzer, what must an analyst be aware of?

You can manually attach generated reports to incidents.
The status of the incident is always linked to the status of the attach event.
Severity incidents rated with the level High have an initial service-level agreement (SLA) response time of 1 hour.
Incidents must be acknowledged before they can be analyzed.

Answer(s): A

Explanation:

In FortiAnalyzer's incident management system, analysts have the option to manually manage incidents, which includes attaching relevant reports to an incident for further investigation and documentation. This feature allows analysts to consolidate information, such as detailed reports on suspicious activity, into an incident record, providing a comprehensive view for incident response.

Let's review the other options to clarify why they are incorrect:

Option A: You can manually attach generated reports to incidents

This is correct. FortiAnalyzer allows analysts to manually attach reports to incidents, which is beneficial for providing additional context, evidence, or analysis related to the incident. This functionality is part of the incident management process and helps streamline information for tracking and resolution.

Option B: The status of the incident is always linked to the status of the attached event

This is incorrect. The status of an incident on FortiAnalyzer is managed independently of the status of any attached events. An incident can contain multiple events, each with different statuses, but the incident itself is tracked separately.

Option C: Severity incidents rated with the level High have an initial service-level agreement (SLA) response time of 1 hour

This is incorrect.
While incidents have severity levels, specific SLA response times are typically set according to the organization's incident response policy, and FortiAnalyzer does not impose a default

SLA response time of 1 hour for high-severity incidents.

Option D: Incidents must be acknowledged before they can be analyzed

This is incorrect. Incidents on FortiAnalyzer can be analyzed even if they are not yet acknowledged. Acknowledging an incident is often part of the workflow to mark it as being actively addressed, but it is not a prerequisite for analysis.

Reference:

According to FortiAnalyzer documentation, analysts can attach reports to incidents manually, making option A correct. This feature enables better tracking and documentation within the incident management system on FortiAnalyzer.

Reveal Solution Next Question

QUESTION: 11

Why must you wait for several minutes before you run a playbook that you just created?

FortiAnalyzer needs that time to parse the new playbook.
FortiAnalyzer needs that time to debug the new playbook.
FortiAnalyzer needs that time to back up the current playbooks.
FortiAnalyzer needs that time to ensure there are no other playbooks running.

Answer(s): A

Explanation:

When a new playbook is created on FortiAnalyzer, the system requires some time to parse and validate the playbook before it can be executed. Parsing involves checking the playbook's structure, ensuring that all syntax and logic are correct, and preparing the playbook for execution within FortiAnalyzer's automation engine. This initial parsing step is necessary for FortiAnalyzer to load the playbook into its operational environment correctly.

Here's why the other options are incorrect:

Option A: FortiAnalyzer needs that time to parse the new playbook

This is correct. The delay is due to the parsing and setup process required to prepare the new playbook for execution. FortiAnalyzer's automation engine checks for any issues or dependencies within the playbook, ensuring that it can run without errors.

Option B: FortiAnalyzer needs that time to debug the new playbook

This is incorrect. Debugging is not an automatic process that FortiAnalyzer undertakes after playbook creation. Debugging, if necessary, is a manual task performed by the administrator if there are issues with the playbook execution.

Option C: FortiAnalyzer needs that time to back up the current playbooks

This is incorrect. FortiAnalyzer does not automatically back up playbooks every time a new one is created. Backups of configuration and playbooks are typically scheduled as part of routine maintenance and are not triggered by playbook creation.

Option D: FortiAnalyzer needs that time to ensure there are no other playbooks running

This is incorrect. FortiAnalyzer can manage multiple playbooks running simultaneously, so it does not require waiting for other playbooks to finish before initiating a new one. The waiting time specifically relates to the parsing process of the newly created playbook.

Reference:

FortiAnalyzer documentation states that after creating a playbook, a brief delay is expected as the system parses and validates the playbook. This ensures that any syntax errors or logical inconsistencies are resolved before the playbook is executed, making option A the correct answer.

Reveal Solution Next Question

QUESTION: 12

Exhibit.

What can you conclude about the output?

The message rate being lower that the log rate is normal.
Both messages and logs are almost finished indexing.
There are more traffic logs than event logs.
The output is ADOM specific

Answer(s): A

Explanation:

In this output, we see two diagnostic commands executed on a FortiAnalyzer device:

diagnose fortilogd lograte: This command shows the rate at which logs are being processed by the

FortiAnalyzer in terms of log entries per second.

diagnose fortilogd msgrate: This command displays the message rate, or the rate at which individual messages are being processed.

The values provided in the exhibit output show:

Log rate (lograte): Consistently high, showing values such as 70.0, 132.1, and 133.3 logs per second over different time intervals.

Message rate (msgrate): Lower values, around 1.4 to 1.6 messages per second.

Explanation

Interpretation of log rate vs. message rate: In FortiAnalyzer, the log rate typically refers to the rate of logs being stored or indexed, while the message rate refers to individual messages within these logs. Given that a single log entry can contain multiple messages, it's common to see a lower message rate relative to the log rate.

Understanding normal operation: In this case, the message rate being lower than the log rate is expected and typical behavior. This discrepancy can arise because each log entry may bundle multiple related messages, reducing the message rate relative to the log rate.

Conclusion

Correct Answe r: A. The message rate being lower than the log rate is normal.

This aligns with the normal operational behavior of FortiAnalyzer in processing logs and messages.

There is no indication that both logs and messages are nearly finished indexing, as that would typically show diminishing rates toward zero, which is not the case here. Additionally, there's no information in this output about specific ADOMs or a comparison between traffic logs and event logs. Thus, options B, C, and D are incorrect.

Reference:

FortiOS 7.4.1 and FortiAnalyzer 7.4.1 command guides for diagnose fortilogd lograte and diagnose fortilogd msgrate.

Reveal Solution Next Question

QUESTION: 13

Exhibit.

A fortiAnalyzer analyst is customizing a SQL query to use in a report.

Which SQL query should the analyst run to get the expected results?

A)

B)

C)

D)

Option A
Option B
Option C
Option D

Answer(s): A

Explanation:

The requirement here is to construct a SQL query that retrieves logs with specific fields, namely "Source IP" and "Destination Port," for entries where the source IP address matches 10.0.1.10. The correct syntax is essential for selecting, filtering, ordering, and grouping the results as shown in the expected outcome.

Analysis of the Options:

Option A

SELECT srcip AS "Source IP", dstport AS "Destination Port": This syntax selects srcip and dstport, renaming them to "Source IP" and "Destination Port" respectively in the output.

FROM $log: Specifies the log table as the data source.

WHERE $filter AND srcip = '10.0.1.10': This line filters logs to only include entries with srcip equal to 10.0.1.10.

ORDER BY dstport DESC: Orders the results in descending order by dstport.

GROUP BY srcip, dstport: Groups results by srcip and dstport, which is valid SQL syntax.

This option meets all the requirements to get the expected results accurately.

Option B

WHERE $filter AND Source IP != '10.0.1.10': Uses != instead of =. This would exclude logs from the specified IP 10.0.1.10, which is contrary to the expected result.

Option C

The ORDER BY clause appears before the FROM clause, which is incorrect syntax. SQL requires the FROM clause to follow the SELECT clause directly.

Option D

The GROUP BY clause should follow the FROM clause. However, here, it's located after WHERE, making it syntactically incorrect.

Conclusion:

Correct Answe r: A. Option A

This option aligns perfectly with standard SQL syntax and filters correctly for srcip = '10.0.1.10', while ordering and grouping as required.

Reference:

FortiAnalyzer 7.4.1 SQL query capabilities and syntax for report customization.

Reveal Solution Next Question

QUESTION: 14

Exhibit.

What can you conclude about these search results? (Choose two.)

They can be downloaded to a file.
They are sortable by columns and customizable.
They are not available for analysis in FortiView.
They were searched by using text mode.

Answer(s): A,D

Reveal Solution Next Question

QUESTION: 15

Exhibit.

What can you conclude from this output?

There is not disk quota allocated to quarantining files.
FGT_B is the Security Fabric root.
The allocated disk quote to ADOM1 is 3 GB.
Archive logs are using more space than analytic logs.

Answer(s): B

Reveal Solution Next Question

QUESTION: 16

Exhibit.

Assume these are all the events that exist on the FortiAnalyzer device.

How many events will be added to the incident created after running this playbook?

Eleven events will be added.
Seven events will be added
No events will be added.
Four events will be added.

Answer(s): D

Explanation:

In the exhibit, we see a playbook in FortiAnalyzer designed to retrieve events based on specific criteria, create an incident, and attach relevant data to that incident. The "Get Event" task configuration specifies filters to match any of the following conditions:

Severity = High

Event Type = Web Filter

Tag = Malware

Analysis of Events:

In the FortiAnalyzer Event Monitor list:

We need to identify events that meet any one of the specified conditions (since the filter is set to "Match Any Condition").

Events Matching Criteria:

Severity = High:

There are two events with "High" severity, both with the "Event Type" IPS.

Event Type = Web Filter:

There are two events with the "Event Type" Web Filter. One has a "Medium" severity, and the other has a "Low" severity.

Tag = Malware:

There are two events tagged with "Malware," both with the "Event Type" Antivirus and "Medium" severity.

After filtering based on these criteria, there are four distinct events:

Two from the "Severity = High" filter.

One from the "Event Type = Web Filter" filter.

One from the "Tag = Malware" filter.

Conclusion:

Correct Answe r: D. Four events will be added.

This answer matches the conditions set in the playbook filter configuration and the events listed in the Event Monitor.

Reference:

FortiAnalyzer 7.4.1 documentation on event filtering, playbook configuration, and incident management criteria.

Reveal Solution Next Question

Fortinet FCP_FAZ_AN-7.6 Exam (page: 2) Fortinet NSE 5 - FortiAnalyzer 7.6 Analyst Updated on: 19-Feb-2026

QUESTION: 9

Explanation:

Reference:

QUESTION: 10

Explanation:

Reference:

QUESTION: 11

Explanation:

Reference:

QUESTION: 12

Explanation:

Reference:

QUESTION: 13

Explanation:

Reference:

QUESTION: 14

QUESTION: 15

QUESTION: 16

Explanation:

Reference:

Fortinet FCP_FAZ_AN-7.6 Exam (page: 2)
Fortinet NSE 5 - FortiAnalyzer 7.6 Analyst
Updated on: 19-Feb-2026