Fortinet NSE5_FAZ_AN-7.6 Practice Questions with Explanations
Free Fortinet NSE5_FAZ_AN-7.6 practice questions. 16 of them, each with the correct answer, a full explanation, and the reason every other option is wrong.
NSE5_FAZ_AN-7.6 practice questions
Question 1
Which statement about automation connectors on FortiAnalyzer is true?
- A. An ADOM with the Fabric type comes with multiple connectors configured.
- B. The local connector comes online once you have a playbook task referencing it.
- C. The actions available with FortiOS connectors are determined by automation rules configured on FortiGate.
- D. The playbook module must be enabled before external connectors are displayed.
Show answer and explanation ▾
Correct answer: C
A FortiOS connector on FortiAnalyzer does not have a fixed action list of its own. The actions it offers to playbook tasks come from the automation stitches configured on the FortiGate that use the Incoming Webhook trigger. When an administrator creates or changes those stitches, the connector shows a matching set of actions FortiAnalyzer can call. This is why the FortiGate configuration, not FortiAnalyzer, decides what a FortiOS connector can do.
Why the other options are wrong:
- A. A Fabric ADOM does not come with several preconfigured connectors. The local connector is built in, the FortiOS connector is added after the first FortiGate is authorized in the ADOM, the FortiGuard connector is configured once a valid license is applied, and other connectors such as EMS are configured by the administrator.
- B. The local connector is built in and available by default. It does not wait for a playbook task to reference it before it comes online.
- D. No separate playbook module has to be enabled before external connectors appear. Configured connectors are listed under the automation connector pages.
Question 2
Which three modules does FortiAnalyzer automatically download content from with a valid SOC Automation service license? (Choose three.)
- A. Report templates
- B. Dashboards
- C. Event handlers
- D. Active Connectors
- E. Playbooks
- F. Incident templates
Show answer and explanation ▾
Correct answer: A, C, E
With a valid SOC Automation (Security Automation) service license, FortiAnalyzer automatically receives content packages from FortiGuard. These packages add ready-made objects to existing modules: report templates for the reporting module, event handlers for event management, and playbooks for automation. The content is applied automatically when a new release is available, so analysts get updated detections, reports and response workflows without building them by hand. Dashboards, connectors and incident templates are not delivered this way.
Why the other options are wrong:
- B. Dashboards are built and customized locally. They are not among the objects the SOC Automation service downloads.
- D. Connectors are configured by the administrator with the details of the target device or service. FortiGuard content packages do not create active connectors.
- F. FortiAnalyzer has no incident template module that receives FortiGuard content. Incidents are created by analysts or by playbooks.
Question 3
Which operation can you use SQL SELECT queries for?
- A. To alter tables in the database
- B. To purge log entries from the database
- C. To insert new data into an existing table
- D. To display the database schema
Show answer and explanation ▾
Correct answer: D
SELECT is the SQL statement that reads data. It returns rows and columns without changing anything stored in the database. Because the schema itself is held in queryable system tables, a SELECT query can be used to display the database schema, for example the tables and columns available. FortiAnalyzer datasets are built on SELECT queries for the same reason: they read log tables to produce chart data and never modify the logs.
Why the other options are wrong:
- A. Changing the structure of a table is done with ALTER TABLE. SELECT only reads data.
- B. Removing rows needs a DELETE statement or a log purge. A SELECT query cannot remove log entries.
- C. Adding rows to a table is done with INSERT. SELECT retrieves existing data and does not add any.
Question 4
Which two parameters does FortiAnalyzer use to identify an indicator of compromise (IOC)? (Choose two.)
- A. Application category
- B. IP address
- C. URL
- D. Policy ID
Show answer and explanation ▾
Correct answer: B, C
FortiAnalyzer finds indicators of compromise by matching the destinations in FortiGate logs, mainly web filter and traffic logs, against the FortiGuard threat database. The matched indicators are network destinations known to be malicious, so the deciding parameters are the IP addresses and URLs (and their domains) that hosts contacted. A host that reaches a known malicious IP address or URL is flagged as a compromised host, with a verdict and threat score.
Why the other options are wrong:
- A. An application category describes the type of application traffic. It is not a threat indicator that FortiAnalyzer matches against the FortiGuard database.
- D. A policy ID only identifies the firewall policy that handled the session. It says nothing about whether the destination is malicious.
Question 5
Which statement describes archive logs on FortiAnalyzer?
- A. Logs that are parsed and normalized by FortiAnalyzer and available in the log view
- B. Logs received from other FortiAnalyzer devices
- C. Logs compressed and saved in files with the .gz extension
- D. Logs that are indexed and stored in the SQL database
Show answer and explanation ▾
Correct answer: C
FortiAnalyzer keeps logs in two forms. Analytics logs are indexed in the SQL database and power Log View, FortiView, event handlers and reports. Archive logs are the long-term copy: raw logs that are compressed and saved in flat files with the .gz extension. They use less disk space and are kept for retention and compliance. Before they can be queried again, they must be imported back into the database.
Why the other options are wrong:
- A. Parsed, normalized logs available for Log View are analytics logs, not archive logs.
- B. Logs forwarded from another FortiAnalyzer can be stored as analytics or archive logs. The source device does not define archive logs.
- D. Logs indexed and stored in the SQL database are analytics logs. Archive logs are compressed files outside the database.
Question 6
An analyst needs to move reports between two ADOMs.
Which two statements are true? (Choose two.)
- A. All charts and datasets associated with the report will be imported together.
- B. The date and time will be appended to the original report name to avoid conflicts.
- C. The ADOMs must be compatible types.
- D. The reports must be converted into templates first.
Show answer and explanation ▾
Correct answer: A, C
A report is moved by exporting it from one ADOM and importing it into another. The export bundles the report with the charts and datasets it uses, so the imported report works in the target ADOM without rebuilding those objects. Because datasets query log tables that depend on the device types in the ADOM, the source and destination ADOMs must be compatible types. A report built for FortiGate logs cannot be expected to run in an ADOM that holds a different log type.
Why the other options are wrong:
- B. Importing a report does not resolve name conflicts by appending the date and time to the original name.
- D. A report can be exported and imported as a report. It does not have to be converted into a template first.
Question 7
After generating a report you notice that the information you were expecting to see is not included in that report. However, you confirm that the logs are there.
Which two actions must you perform? (Choose two.)
- A. Test the dataset.
- B. Check the time frame covered by the report.
- C. Increase the report utilization quota.
- D. Enable auto-cache.
Show answer and explanation ▾
Correct answer: A, B
The logs exist, so the problem is in how the report selects them. First, test the dataset that feeds the chart: the dataset editor can run the SQL query against a chosen device and time period, showing whether it returns the expected rows. Second, check the time frame of the report. If the period does not cover the timestamps of the logs, the data is left out even though it is stored on FortiAnalyzer. Together these two checks cover the query logic and the time scope.
Why the other options are wrong:
- C. FortiAnalyzer has no report utilization quota that limits which data appears. Disk quotas control log storage, not report content.
- D. Auto-cache speeds up report generation by building hcache in advance. It does not change which data a report includes.
Question 8
When managing incidents on FortiAnalyzer, which fact must an analyst be aware of?
- A. The status of the incident is always linked to the status of the attached event.
- B. A playbook can be run from the Incidents page.
- C. Incidents must be acknowledged before they can be analyzed.
- D. Indicators found on the Incidents page can be enriched only from the Indicators page.
Show answer and explanation ▾
Correct answer: B
Incidents on FortiAnalyzer can be worked directly from the Incidents page. From there an analyst can open an incident, attach events, add notes and run a playbook on it manually. This lets the analyst start enrichment or containment steps, such as gathering more data or blocking an address, without leaving the incident. Playbooks set to an on-demand trigger are the ones that can be run this way.
Why the other options are wrong:
- A. An incident has its own status, set by the analyst or a playbook. It is not always tied to the status of the attached events.
- C. There is no requirement to acknowledge an incident before analyzing it. The analyst can open and investigate it at any time.
- D. Indicators can also be enriched from within the incident itself. They are not restricted to the Indicators page.
Question 9
You are trying to configure a task in the playbook editor to run a report. However, when you try to select the desired report you do not see it listed.
What is the reason?
- A. The report template needs to be switched to one that is available for playbooks.
- B. You must create a trigger to run the report first.
- C. The playbook is currently running and the report will be available after it is finished.
- D. The report does not have auto-cache and extended log filtering enabled.
Show answer and explanation ▾
Correct answer: D
The local connector's Run Report action only lists reports that are ready to run on demand from automation. A report qualifies only if both Enable Auto-cache and Extended Log Filtering are turned on in its settings. If either option is off, the report does not appear in the task's report list. Turning both options on in the report's settings makes it selectable in the playbook task.
Why the other options are wrong:
- A. There is no special class of report templates reserved for playbooks. Eligibility depends on the report's auto-cache and extended log filtering settings.
- B. The playbook trigger starts the playbook. It has no effect on which reports appear in a Run Report task.
- C. A running playbook does not hide reports in the editor. The list is filtered by the report settings, not by run state.
Question 10
Which three types of indicators can FortiAnalyzer identify? (Choose three.)
- A. Email address
- B. Host name
- C. Domain
- D. URL
- E. IP address
Show answer and explanation ▾
Correct answer: C, D, E
FortiAnalyzer identifies indicators by matching network destinations in logs against the FortiGuard threat intelligence database. The indicator types it extracts and tracks are domains, URLs and IP addresses. These appear on the Indicators page and in compromised host verdicts, where each indicator is linked to the endpoints that contacted it. Email addresses and host names are not among the indicator types it detects.
Why the other options are wrong:
- A. Email addresses are not an indicator type FortiAnalyzer extracts. Its indicator detection is built on domains, URLs and IP addresses.
- B. A host name identifies the local endpoint involved. It is not a threat indicator matched against FortiGuard data.
Getting these right? Take the first 31 with you.
The free PDF is the first half of the full Fortinet NSE5_FAZ_AN-7.6 pack: 31 questions with every answer explained, as one PDF in your inbox.
Get the free PDFQuestion 11
What are two effects of enabling auto-cache in a FortiAnalyzer report? (Choose two.)
- A. The size of newly generated reports is optimized to conserve disk space.
- B. The hcache data is updated automatically when new logs are received.
- C. The report generation time is reduced.
- D. FortiAnalyzer local cache is used to store generated reports.
Show answer and explanation ▾
Correct answer: B, C
Reports run SQL queries against the log database, and large time ranges can make those queries slow. When auto-cache is enabled for a report, FortiAnalyzer builds the hcache (the intermediate query results for the report's charts) in the background and keeps it updated automatically as new logs arrive. When the report runs, most of the data has already been computed, so the report is generated much faster. The cost is extra processing and some extra disk space for the cache tables. The final report output is the same.
Why the other options are wrong:
- A. Auto-cache does not compress or shrink reports. It uses extra disk space for hcache tables in exchange for faster generation.
- D. The hcache holds intermediate query results in the database. It is not a local store for finished report files.
Question 12
How does FortiAnalyzer block indicators?
- A. It uses a webhook to allow FortiGate to send the block list.
- B. It uses a FortiClient EMS connector to send the block list.
- C. It uses a FortiManager connector to send the block list.
- D. It uses an automation script to update FortiGate with the block list.
Show answer and explanation ▾
Correct answer: C
In Incidents & Events, an analyst can select indicators and click Block. FortiAnalyzer does not push this block list to FortiGate devices itself. It needs an authorized FortiManager connector, which sends the indicators to FortiManager. FortiManager then uses them in threat feeds, security profiles and firewall policies and installs them on the managed FortiGate devices. If the FortiManager connector is missing or down, the Block option is unavailable. FortiManager must also run the same firmware version as FortiAnalyzer for the block list to be pushed to FortiGate devices.
Why the other options are wrong:
- A. Webhooks are used to trigger FortiOS automation stitches. FortiGate does not send FortiAnalyzer the block list this way.
- B. The FortiClient EMS connector is used for endpoint actions such as quarantine. It is not the path for blocking indicators.
- D. FortiAnalyzer does not run a custom script for this. The documented mechanism is the FortiManager connector.
Question 13
Which two statements about local logs on FortiAnalyzer are true? (Choose two.)
- A. Playbook logs for all ADOMs are in the root ADOM.
- B. Application control logs are ADOM specific.
- C. Local logs are not displayed in FortiView.
- D. Event logs are available in the root ADOM.
Show answer and explanation ▾
Correct answer: B, D
FortiAnalyzer records its own activity as local logs. Option B refers to the FortiAnalyzer local application logs, which record playbook and incident activity. They are generated and stored separately for each ADOM and are viewed in Log View under the ADOM that produced them, so they are ADOM specific. FortiAnalyzer local event logs, such as system and administrative events, are available in the root ADOM, where administrators can view the local event logs together with the root ADOM's own application logs.
Why the other options are wrong:
- A. Playbook activity is recorded in application logs that are generated and stored separately for each ADOM, so the root ADOM holds only its own playbook logs, not those of every ADOM.
- C. Fortinet documents no rule that keeps local logs out of FortiView; the documented facts about local logs concern which ADOM stores and shows the event and application logs.
Question 14
When there are no matching parsers for a device log, what does FortiAnalyzer do?
- A. Stores the log but doesn't normalize it
- B. Applies the generic SYSLOG parser
- C. Drops the log
- D. Archives the log for future analysis
Show answer and explanation ▾
Correct answer: A
FortiAnalyzer uses log parsers to normalize incoming device logs into Fabric logs in the SIEM database. When the appropriate parser is not available or not enabled, the logs are not parsed and are not inserted into the SIEM database as Fabric logs. They are still kept, and analysts can find and use them only by their device and log type. In other words, the log is stored but left un-normalized, so features that depend on normalized Fabric fields cannot use it until a matching parser is enabled.
Why the other options are wrong:
- B. FortiAnalyzer does not fall back to a generic SYSLOG parser; an unmatched log is simply not parsed and remains available only by its device and log type.
- C. The log is not discarded; FortiAnalyzer still stores it and it stays searchable by device and log type.
- D. There is no special archive step for unparsed logs; they follow normal log storage, just without normalization into Fabric logs.
Question 15
What are the two methods you can use to send notifications when an event is generated by an event handler? (Choose two.)
- A. Send an alert through the FortiGuard server.
- B. Send an alert through Fabric connectors.
- C. Send SMS notification.
- D. Send SNMP trap.
Show answer and explanation ▾
Correct answer: B, D
When an event handler generates an event, its notification settings decide how the event is sent out. Besides email and syslog, FortiAnalyzer can send an SNMP trap to a configured SNMP manager. It can also send the alert through Fabric connectors, such as a FortiOS connector or a messaging or ITSM service. These methods let the alert reach monitoring systems and other Security Fabric products automatically.
Why the other options are wrong:
- A. FortiGuard supplies threat intelligence and content packages. It is not used as a relay for event handler alerts.
- C. SMS is not a notification method for event handlers. Alerts go out by email, syslog, SNMP trap or Fabric connectors.
Question 16
You created a playbook on FortiAnalyzer that uses a FortiOS connector.
When you configure FortiGate, which type of trigger must you use so that the actions in an automation stitch are available in the FortiOS connector?
- A. Fabric Connector event
- B. Incoming webhook
- C. IP ban
- D. FortiAnalyzer Event Handler
Show answer and explanation ▾
Correct answer: B
A FortiOS connector lets a FortiAnalyzer playbook call actions on a FortiGate. Those actions come from FortiGate automation stitches whose trigger is Incoming Webhook. The webhook trigger exposes the stitch so that FortiAnalyzer can call it remotely. Once such stitches exist, their actions appear in the FortiOS connector and can be chosen in playbook tasks. Stitches with any other trigger, such as local FortiGate events or the FortiAnalyzer Event Handler trigger, are not offered to the connector.
Why the other options are wrong:
- A. A Fabric Connector event trigger fires on connector events on the FortiGate. It does not expose the stitch for calls from FortiAnalyzer.
- C. The IP ban trigger fires when FortiGate bans an address. It is a local event, not a way for FortiAnalyzer to call the stitch.
- D. The FortiAnalyzer Event Handler trigger reacts to events pushed from FortiAnalyzer. It does not make stitch actions available to the FortiOS connector.
That was 16 of 63.
The full Fortinet NSE5_FAZ_AN-7.6 pack has all 63 questions, each with the answer, the explanation and why the other options are wrong, plus a questions-only copy for timed runs. $39.00 USD, paid once, with free monthly updates and a pass-or-your-money-back guarantee.
Get the full packNot ready yet? Get the first 31 free as one PDF by email. Get the Half Pack →