NSE6_FSR-7.3 Sample Questions Answers

Comprehensive and Detailed Explanation From FortiSOAR 7.3 Exact Extract study guide:

According to the FortiSOAR 7.3 Administration and Deployment Guides, specifically in the "Licensing FortiSOAR" and "Security Management" sections:

Licensing Enforcement:FortiSOAR strictly enforces the number of active users based on the installed license. The license specifies themaximum number of active usersallowed in the system at any given point in time.

User Status (Active vs. Inactive):When the number of active users reaches the limit defined by the license, any additional users created or imported will be set to anInactivestatus by default. An administrator cannot change their status to "Active" until an existing active user is deactivated or deleted, or the license is upgraded to support more users.

Locked Status (Option A):It is important to distinguish between "Inactive" and "Locked." Users becometemporarily lockedout of FortiSOAR when they exceed the configured number of authentication attempts (defaulting to 5 times) within a specific period. A locked user profile will typically display a "Locked" indicator or a checkbox to "Unlock" rather than a simple "Inactive" status.

Other Options:While an email ID is required for account creation, its validity does not automatically trigger an "Inactive" status (Option B). Similarly, a required password reset (Option C) forces a password change upon login but does not disable the account.

In FortiSOAR, the "Application Administrator" role is a default role that holds broad privileges, including the ability to assign permissions to other teams. This role is fundamental to system administration and is recommended not to be removed as it provides crucial administrative capabilities. Removing or modifying this role could impact FortiSOAR's ability to manage user roles and permissions effectively, which could hinder system operations and user management​.

Comprehensive and Detailed Explanation From FortiSOAR 7.3 Exact Extract study guide:

According to the FortiSOAR 7.3 Administration Guide under the "Audit Logs" and "Role-Based Access Control (RBAC)" sections, managing the lifecycle of system logs requires elevated administrative privileges.

To perform a manual purge of audit logs, the system validates permissions across two specific areas:

Audit Log Activities Module:The user must haveDeletepermissions on this specific module because it is the repository where the actual log records are stored. Without "Delete" rights here, the application cannot remove the database entries.

Security Module:Because the purging of audit logs is a sensitive security operation that affects the system's accountability trail, FortiSOAR requires theDeletepermission on theSecuritymodule. This acts as a secondary administrative guardrail to ensure only authorized security administrators can permanently remove audit trails.

Permissions on thePeopleorUsersmodules (Options C and D) are used for managing user profiles and account attributes, but they do not grant the authority to manipulate system-level audit databases.

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-activityenvironments where log data accumulates quickly. Purging these logs helps maintain a cleaner and more efficient system​.

In a FortiSOAR HA cluster, if the former primary node is relegated to a secondary role but is stuck in a Faulted state, it indicates that the node has lost sync or faced a failure during a role change. To restore its functionality, first, you should remove it from the cluster using the csadm ha leave-cluster command. Once it has left the cluster, you can use the csadm ha join-cluster command to re-add the node as a secondary node. This process will allow it to sync back up with the cluster and resume its role as intended​.

The FortiSOAR queue and shift management feature enables several key activities for managing shifts and queues. Administrators can initiate shift handovers, allowing for smooth transitions between shift leads and members. They can also designate specific roles within shifts, including shift leads and members, to define responsibilities. Additionally, queue rules can be established based on certain conditions, ensuring that incidents and tasks are assigned according to predefined criteria, which helps streamline operations and improve response times​.

In FortiSOAR, when a user is configured with "Concurrent" access type, their ability to log in depends on the availability of concurrent user seats. This means the user can only log in if there are available seats in the concurrent pool. If all seats are occupied, the user must wait until a seat becomes free. This configuration allows multiple users to share a pool of licenses, making it suitable for environments where not all users need constant access​.