FCP_FAZ_AN-7.6
Free FCP_FAZ_AN-7.6 practice questions
10 questions from our FCP_FAZ_AN-7.6 practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, Features and Concepts
A new FortiGate is configured to send its logs to FortiAnalyzer. In Device Manager, the FortiGate appears in the list of unauthorized devices and none of its logs are visible in Log View. What must the administrator do so that FortiAnalyzer starts storing and displaying the logs?
- ACreate a log fetcher profile that pulls the logs from the FortiGate local disk
- BRebuild the SQL database of the root ADOM so that the new device is indexed
- CAuthorize the FortiGate in Device Manager and assign it to the correct ADOM Correct answer
- DEnable log forwarding on FortiAnalyzer with the FortiGate serial number as the target
Answer and explanation: FortiAnalyzer does not accept logs from a device until an administrator authorizes it and places it in an ADOM; after that, logs are stored and visible. Rebuilding the SQL database only re-inserts logs that were already received. Log fetching retrieves logs from another FortiAnalyzer, not from a FortiGate disk. Log forwarding sends logs out of FortiAnalyzer, so it does nothing for incoming logs.
Question 2 of 10, Features and Concepts
A managed security service provider uses one FortiAnalyzer for several customers. Each customer's analysts must see only their own logs, and each customer needs its own storage limit. Which approach meets both requirements?
- ACreate a separate report folder per customer and grant each analyst read access only to the folder that matches the customer
- BKeep all devices in the root ADOM and create one log group per customer so that each analyst only selects the group of their own company
- CForward each customer's logs to an external syslog server and let the analysts access only the server that holds their logs
- DEnable ADOMs, place each customer's devices in a separate ADOM, restrict analysts to their ADOM and set a disk quota per ADOM Correct answer
Answer and explanation: ADOMs separate devices, logs and SOC objects, administrators can be restricted to specific ADOMs, and each ADOM has its own storage quota and data policy. Log groups are a viewing convenience and do not restrict access or storage. Report folders organize reports but not logs. Forwarding to external servers removes the analysis features and does not answer the requirement on FortiAnalyzer.
Question 3 of 10, Features and Concepts
A regional FortiAnalyzer must forward its logs to the central FortiAnalyzer, but WAN bandwidth must be preserved during business hours. A delay of up to a day before the central unit has the logs is acceptable. Which configuration meets these requirements?
- ALog forwarding in CEF format to the central unit, because CEF messages are smaller than native log records
- BLog fetching from the central unit, with a fetch request that an administrator starts manually every Monday morning
- CLog forwarding to the central FortiAnalyzer in aggregation mode with a daily upload time outside business hours Correct answer
- DLog forwarding to the central FortiAnalyzer in real-time mode with compression enabled on the forwarding entry
Answer and explanation: Aggregation mode collects logs and sends them to another FortiAnalyzer at a scheduled time, so the transfer can be placed outside business hours. Real-time forwarding sends continuously during business hours, even if compressed. A manual weekly fetch exceeds the acceptable delay and depends on an administrator. CEF forwarding targets syslog-style collectors and still sends in real time.
Question 4 of 10, Log Analysis
An analyst must find all sessions from host 10.1.1.5 that a FortiGate firewall policy blocked during the last 24 hours. Which search is the most direct?
- ATraffic logs filtered on source IP 10.1.1.5 and action close
- BIntrusion prevention logs filtered on source IP and action dropped
- CTraffic logs filtered on source IP 10.1.1.5 and action deny Correct answer
- DEvent logs filtered on source IP 10.1.1.5 and subtype system
Answer and explanation: Sessions blocked by a firewall policy are recorded in traffic logs with the action deny, so filtering traffic logs on the source address and that action returns them. System event logs describe device activity, not blocked sessions. Intrusion prevention logs show blocked attacks, not policy denies. The action close marks sessions that were allowed and ended normally.
Question 5 of 10, Log Analysis
Device Manager shows that a FortiGate has not sent logs for two hours, but the device is running. Which command on the FortiGate checks its connection to FortiAnalyzer?
- Adiagnose debug application miglogd -1
- Bexecute log fortianalyzer test-connectivity Correct answer
- Cget system status
- Dexecute ping-options source 10.0.0.1
Answer and explanation: The FortiAnalyzer connectivity test on the FortiGate checks the connection and registration status with FortiAnalyzer. Debugging the logging daemon gives verbose output that is useful later but is not the first test. Ping options only set ping parameters. System status shows version and serial information, not the FortiAnalyzer connection.
Question 6 of 10, SOC Operation and Automation
When a new incident is created, a playbook must collect the events of the affected endpoint and add them to that incident. Which design achieves this?
- AEvent trigger, then a local connector task to get events for the endpoint, then a task that creates a new incident with those collected events
- BIncident trigger, then a local connector task to get events for the endpoint, then a task that attaches them using the incident ID from the trigger Correct answer
- CSchedule trigger, then a local connector task to get events for all endpoints, then a task that attaches them to the newest incident
- DIncident trigger, then a FortiOS connector task to get events from the FortiGate, then a task that attaches them using the incident ID
Answer and explanation: The incident trigger provides the incident and endpoint details, the local connector retrieves matching events, and the attach task uses the trigger's incident ID so the data lands in the right incident. An event trigger with a create task makes a new incident instead of updating the existing one. The FortiOS connector acts on FortiGates and does not query FortiAnalyzer events. A scheduled run against all endpoints may attach data to the wrong incident.
Question 7 of 10, SOC Operation and Automation
A SOC wants to detect a host that triggers an IPS alert and then, within ten minutes, connects to a known botnet command-and-control server. Which configuration best detects this pattern?
- AA basic event handler that matches either IPS or botnet logs from the same host and uses a threshold of two events
- BTwo basic event handlers, one for IPS and one for botnet logs, whose events the analysts compare manually afterwards
- CA playbook with a schedule trigger that runs every ten minutes and searches for IPS logs from any internal host
- DA correlation event handler with two subrules evaluated in sequence within a 10-minute window and grouped by source IP Correct answer
Answer and explanation: A correlation handler links several conditions, such as an IPS alert followed by botnet traffic, within a time window and for the same grouped field. Two basic handlers would raise separate events and leave correlation to people. A basic handler with an OR filter fires on two logs of either type, not on the sequence. A scheduled playbook that searches only IPS logs does not detect the second step.
Question 8 of 10, SOC Operation and Automation
A playbook task must quarantine an endpoint through FortiClient EMS when a high-severity incident is created. What must be in place on FortiAnalyzer before this task can run?
- AA FortiOS connector on the FortiGate that protects the EMS server
- BAn authorized FortiClient EMS connector in the Fabric connectors list Correct answer
- CA local connector action that writes the endpoint to a quarantine list
- DAn ITSM webhook connector that sends incident data to the EMS server
Answer and explanation: Playbook actions against endpoints, such as quarantine, are provided by the FortiClient EMS connector, which must be configured and authorized. An ITSM webhook only sends notifications and cannot call EMS actions. A FortiOS connector acts on FortiGate devices, not on EMS. The local connector runs FortiAnalyzer actions and cannot quarantine endpoints.
Question 9 of 10, Reports
A weekly report over a very large volume of traffic logs takes hours to generate. Which change is most likely to shorten generation time without reducing report content?
- AEnable auto-cache for the report so that cached data is built in the background as logs arrive Correct answer
- BChange the output format from PDF to HTML so that FortiAnalyzer does not need to render pages
- CIncrease the analytics retention period so that more data stays in the SQL database for queries
- DAdd more charts to each page so that FortiAnalyzer can query several charts at the same time
Answer and explanation: Auto-cache builds the report cache (hcache) incrementally in the background, so less work remains when the report runs. More analytics retention increases the data available but does not speed queries. Output format changes rendering only, which is a small part of generation time. Adding charts increases work rather than reducing it.
Question 10 of 10, Reports
A report finishes successfully, but one chart shows no data for a branch FortiGate even though Log View shows matching logs from that device in the same time period. What is the most likely cause?
- AThe report device setting does not include that FortiGate Correct answer
- BThe report is generated in HTML instead of PDF format
- CThe ADOM archive retention is shorter than one month
- DThe FortiGate sends its logs with reliable logging enabled
Answer and explanation: A report only queries the devices that are selected in its settings, so an excluded FortiGate produces no data. Archive retention affects raw log files, not the analytics data visible in Log View. The output format does not change the query results. Reliable logging only affects transport and does not hide logs from reports.