Several users have informed you that the FortiSOAR GUI Is not reachable. When troubleshooting,
which step should you take first?
C
Explanation:
When troubleshooting the issue of the FortiSOAR GUI not being reachable, the first step should be to
check the status of the nginx service, which is responsible for managing web requests. Using the
command systemctl status nginx will provide information on whether the service is running and any
potential issues or errors related to it. This approach is more efficient as it directly addresses the
service responsible for the web interface, making it possible to diagnose and resolve common issues
such as service failure, configuration errors, or connectivity problems.
What are two system-level logs that can be purged using application configuration? (Choose two.)
C, D
Explanation:
In FortiSOAR, system-level logs that can be purged include both "Audit logs" and "Executed Playbook
logs." These types of logs can be configured to be purged periodically to free up storage space and
ensure that unnecessary logs do not impact system performance. The application configuration
allows administrators to schedule automatic purges, which can be especially useful in high-activity
environments where log data accumulates quickly. Purging these logs helps maintain a cleaner and
more efficient system.
The Create Record and Update Record steps are categorized under which playbook step'
C
Explanation:
In FortiSOAR playbooks, the "Create Record" and "Update Record" steps are categorized under the
"Core" category of playbook steps. Core steps are essential actions that are frequently used in
playbooks to interact with records in the FortiSOAR database. They include fundamental operations
such as creating, reading, updating, or deleting records within modules. These steps are crucial for
the automation of tasks such as data management, where playbooks need to create new entries or
update existing data as part of incident response workflows.
When configuring the system proxy on FortiSOAR. which two URLs should be accessible from the
proxy server? (Choose two.)
C, D
Explanation:
When configuring the system proxy for FortiSOAR, it is essential to ensure connectivity to certain
URLs to maintain system updates and licensing. For FortiSOAR, access to
https://iepo.fortisoar.fortinet.com is required for incident enrichment and analysis, while
https://globalupdate.fortinet.net is necessary for global updates to keep the system up-to-date with
the latest threat information. These connections allow FortiSOAR to communicate with Fortinet's
servers to fetch updated threat intelligence and system updates, which are critical for the operational
effectiveness of FortiSOAR.
When configuring an HA cluster with an externalized PostgreSQL database, which two tiles on the
database server need to be configured to trust all FortiSOAR nodes' incoming connections? (Choose
two.)
A, C
Explanation:
In a FortiSOAR High Availability (HA) cluster setup with an externalized PostgreSQL database, it is
necessary to configure the database server to allow incoming connections from all FortiSOAR nodes.
This configuration involves modifying the pg_hba.conf file to set up host-based authentication and
control which IP addresses can connect. The postgresql.conf file must also be adjusted to enable
listening on all necessary IP addresses, which is critical for FortiSOAR nodes to connect to the
database server securely and reliably. Together, these configurations ensure that all FortiSOAR nodes
can access the database, facilitating effective HA functionality.
For which two modules on FortiSOAR can you create SLA templates7 (Choose two.)
A, B
Explanation:
In FortiSOAR, SLA (Service Level Agreement) templates can be created for specific modules, including
Alerts and Indicators. These templates are essential for tracking response and resolution times,
ensuring compliance with defined service levels. By configuring SLAs on the Alerts and Indicators
modules, organizations can monitor the time taken to address these items, which is critical in
maintaining efficient incident response and management practices. The SLA templates can be
customized according to specific business requirements and are applied to records within these
modules to enforce timely actions.
Refer to the exhibit.
Which two statements about the recommendation engine are true? (Choose two.)
B, D
Explanation:
The Recommendation Engine in FortiSOAR is designed to assist in alert triage by suggesting values
for certain fields based on historical data and machine learning models. In this case, the engine is
trained to predict both the Severity and Type fields, suggesting values that align with past incidents
and threat intelligence. Although the current alert severity is High, the recommendation engine has
suggested adjusting it to Medium based on the pattern of similar past alerts, indicating a less critical
threat level than initially perceived. This functionality helps analysts by providing data-driven
insights, which can optimize alert handling and resource allocation.
Refer to the exhibit.
When importing modules to FortiSOAR using the configuration wizard, what actions are applied to
fields it you select Merge with Existing as the Bulk action?
D
Explanation:
When importing modules into FortiSOAR using the configuration wizard and selecting "Merge with
Existing" as the bulk action, the behavior for field handling is as follows: any fields that already exist
in the system are overwritten with the imported values. New fields from the imported module are
added to the system, while fields that are not part of the imported module remain unaffected and
are retained in the system. This option ensures that existing data structures are updated with new
information without losing existing, but non-imported, fields.
Which service on FortiSOAR is the playbook scheduler?
B
Explanation:
In FortiSOAR, the service responsible for the playbook scheduling functionality is colcrybeatd. This
service manages the timing and execution of scheduled playbooks, allowing for the automation of
various tasks at specified intervals. It ensures that playbooks execute according to their configured
schedules, which can include tasks such as data ingestion, threat detection, or incident response
actions. Proper functioning of this service is essential for the reliable automation of time-dependent
processes within FortiSOAR.
A security analyst has reported unauthorized access to System Configuration. You must review the
user's current level of access, and then restrict their access according to your organization's
requirements. As part of your auditing process, which two actions should you perform? (Choose
two.)
B, D
Explanation:
To audit and restrict a user’s access within FortiSOAR, particularly in response to unauthorized access
reports, it's necessary to review the user’s effective role permissions. This involves checking which
roles grant the user access to the System Configuration module and adjusting as needed.
Additionally, reviewing the user's team hierarchy ensures that the user’s access aligns with the
organization’s policies. Misconfigurations in team relationships can sometimes inadvertently provide
elevated access; hence, confirming that the team setup is correct is a critical part of the auditing
process.
An administrator is issuing the following command on a node trying to join a FortiSOAR duster as a
standby: csadm ha join-cluster --status active —role secondary --primary-node 10.0.1.160
The node fails to join the cluster. What is the issue?
D
Explanation:
When joining a FortiSOAR cluster as a standby node, the correct status value should be passive. Using
active would imply that the node is trying to join as an active node, which could cause conflicts in the
cluster setup. In FortiSOAR, standby nodes must be set as passive to ensure they are recognized
correctly and to avoid conflicts with the primary node or other active nodes within the cluster.
Therefore, setting the status to passive will resolve the issue and allow the node to join the cluster as
intended.
When deleting a user account on FortiSOAR, you must enter the user ID in which file on FortiSOAR?
D
Explanation:
When deleting a user account in FortiSOAR, the user ID must be entered into the usersToDelete.txt
file. This file is specifically used to list users that are marked for deletion. Once the user IDs are listed
in this file, the system can process the deletion of these accounts as part of its user management
operations. This method ensures that only specified users are deleted, as referenced in FortiSOAR's
administrative controls.
Which two statements about upgrading a FortiSOAR HA cluster are true7 (Choose two.)
C, D
Explanation:
Upgrading a FortiSOAR HA cluster follows the same procedure regardless of whether it is configured
in an active-active or active-passive setup. The process generally involves upgrading one node at a
time to minimize service disruption. Best practices recommend upgrading the passive secondary
node first before moving to the active primary node. This sequence helps maintain cluster stability
and ensures that at least one node remains operational during the upgrade.
Which SMS vendor does FortiSOAR support for two-factor authentication?
D
Explanation:
For two-factor authentication (2FA) via SMS, FortiSOAR supports integration with Telesign. This
vendor provides SMS-based 2FA services, enabling FortiSOAR to leverage Telesign's API for sending
verification codes as part of its security features. Telesign’s service is compatible with FortiSOAR,
ensuring secure user authentication when accessing the platform or certain features.
Which three actions can be performed from within the war room? (Choose three)
A, C, D
Explanation:
In FortiSOAR's War Room, users can perform several actions to manage incidents effectively. They
can view a graphical representation of records linked to an incident in the Artifacts lab, which helps
visualize connections and dependencies. Additionally, the War Room supports tagging investigation
results as evidence, allowing for a structured approach to incident documentation. Users can also
manage tasks via the Task Manager tab, facilitating task creation, assignment, and tracking within the
incident response workflow.