Identity-Security-Administrator Exam Dumps : SailPoint Certified Identity Security Administrator

This is a valid description of Separation of Duties (SoD) as an identity-governance control. SoD policies define combinations of access that should not be held by the same identity because combining those privileges could enable fraud, unauthorized transactions, or circumvention of internal controls. A detective implementation analyzes existing access and identifies identities that already violate a defined policy, allowing administrators to investigate, mitigate, revoke access, or document an approved exception.

Preventive policy evaluation applies the same governance principle before problematic access is granted. During an access-request or provisioning process, the proposed access can be evaluated against policy rules so that a potential conflict is identified before the access change is completed. SailPoint documents SoD policies as conflicting-access definitions and also documents preventive policy evaluation in its governance model. These controls provide measurable evidence that an organization is actively enforcing access-risk policies rather than merely documenting them.

Study Guide Reference: Supporting Governance — Separation of Duties, Policy Rules, Detective and Preventive Controls.

===============

Resetting the source and re-aggregating users is not the appropriate initial remediation. Aggregation is primarily an inbound data collection process: it reads account information from the source into Identity Security Cloud. It does not, by itself, perform the outbound disable operation that should occur when an identity enters the Terminated lifecycle state.

The administrator should first verify that the affected identities actually entered the expected lifecycle state and that the Terminated lifecycle-state configuration specifies that the database source account is to be disabled. SailPoint allows a lifecycle state to enable, disable, or delete accounts on selected sources. The source must also support the required account-disable operation.

The administrator should then review provisioning/account activity for failures and validate that provisioning is enabled and operating correctly for the database connector. Re-aggregation could later be useful to confirm the source's actual account state, but resetting the entire source is unnecessarily disruptive and does not correct the root cause of a failed lifecycle provisioning operation.

Therefore, the proposed troubleshooting action does not directly address why the Terminated lifecycle event failed to disable the account.

Study Guide Reference: Provisioning — Lifecycle-State Provisioning, Account Disable Operations, Provisioning Troubleshooting and Source Aggregation.

===============

This is not the standard Identity Security Cloud method for configuring role assignment criteria. Role membership can be automatically determined using defined identity or account-based criteria, or administrators can explicitly specify identities through an Identity List depending on the role configuration.

The Identity List mechanism is designed to identify users who should receive the role rather than create a separate universal exclusion list containing identities who must never receive it. When automatic assignment criteria are configured, identities satisfying those criteria can become role members based on the associated identity attributes, account attributes, or other supported conditions.

If a particular identity must not receive a role, administrators should design the role-assignment criteria so that the identity does not satisfy the required conditions or use another appropriate assignment strategy. Introducing an unsupported exclusion mechanism could create incorrect expectations about how role membership is calculated.

Roles are intended to package business-relevant access and automatically assign that access to identities meeting defined organizational criteria.

Study Guide Reference: Access Management — Roles, Role Assignment Criteria, Standard Criteria, Identity Lists.

===============