FortiSOAR Troubleshooting & Configuration

In a high-availability FortiSOAR deployment where the former primary node is stuck in a 'Faulted' state after being relegated to the secondary role, which dual set of actions are concurrently necessary to ensure complete cluster operation restoration, considering potential data synchronization inconsistencies and service failover intricacies?

Given a scenario where an administrator needs to collect and review all FortiSOAR log files for comprehensive troubleshooting, which dual approach, considering both GUI accessibility and backend system access, should be employed to guarantee complete log retrieval, even in cases of partial system failure or GUI unavailability?

Considering the intricacies of FortiSOAR's high availability (HA) architecture with an internal PostgreSQL database, which CLI command is exclusively applicable for managing failover scenarios and ensuring data integrity between nodes, especially when dealing with potential replication lag or database inconsistencies?

In the context of a highly customized FortiSOAR deployment, where automated actions are crucial for maintaining system health, within which playbook collection are system-level playbooks housed that FortiSOAR employs natively to automatically populate critical date fields when the status of incident or alert records transitions to 'Resolved' or 'Closed,' ensuring accurate audit trails and reporting?

Given a scenario where the syops-ha service unexpectedly terminates, triggering a potential disruption in high-availability synchronization and inter-node communication, after what precise duration will the heartbeat missed notification be dispatched to the administrator, taking into account configurable thresholds and default system monitoring intervals, to facilitate timely intervention and prevent prolonged operational degradation?

Considering stringent security requirements and the need for granular access control, specifically which default role on FortiSOAR inherently possesses root user privileges and unrestricted access to all system functions and data, and whether it is advisable to assign this role to standard administrative accounts for day-to-day operations or reserve it for emergency system maintenance purposes?

In a complex, multi-tenant FortiSOAR deployment necessitating strict data segregation and customized environments for each tenant, which architectural model is being employed when some tenants' data and applications reside on-premises while others are hosted in a public cloud, and how does this model impact resource allocation, security policies, and compliance requirements across the entire deployment?

When configuring SAML authentication within FortiSOAR to integrate with an organization’s existing identity provider, which minimal set of three attributes must be accurately mapped from the SAML assertion to corresponding user fields within FortiSOAR to guarantee successful user provisioning, authorization, and personalized user experience, considering the security implications of attribute misconfiguration and the operational impact of inaccurate user profiles?