Which two statements about local logs on FortiAnalyzer are true? (Choose two.)
Select an option, then click Submit answer.
Reference / correct answer:
Application control logs are ADOM specific.
Most accepted answer: B. Application control logs are ADOM specific.
Community votes: A=2, B=3, C=1, D=2
Selected Answer: CD A –Incorrect - Playbook logs are not generated per specific ADOM. Application logs are ADOM-specific and do not all reside in the root ADOM. B – Incorrect - The Study Guide states that application logs are ADOM-specific (not just application control logs). C –Correct - Local logs (archive logs) are not displayed in FortiView. FortiView uses only analytics logs. D –Correct - Event logs are available in the root ADOM. The Study Guide confirms that administrators can view event logs in the root ADOM with system-wide information. upvoted 2 times
Selected Answer: AB A. Playbook logs for all ADOMs are in the root ADOM (Correct): FortiAnalyzer centralizes the execution logs of automation workflows and Playbooks from all Administrative Domains (ADOMs) inside the root ADOM, allowing a global monitoring view for the administrator. B. Application control logs are ADOM specific (Correct): Local logs related to application control capture app behavior events that strictly belong to and are isolated within the context of each specific ADOM. upvoted 2 times
Selected Answer: BD Page 59 says administrators can view both local event logs and application logs in the root ADOM; FortiAnalyzer event logs are system-wide, while application logs are ADOM-specific. upvoted 2 times
Selected Answer: AB Based on FortiAnalyzer, the two true statements regarding local logs are that playbook logs for all ADOMs are accessible in the root ADOM and event logs provide system-wide information, while application logs are ADOM-specific. upvoted 1 times