SailPoint Identity-Security-Administrator - SailPoint Certified Identity Security Administrator

The statement is incorrect. A disabled role is not the appropriate state for validating actual automated role assignment through identity processing. Identity Security Cloud documents that disabling a role prevents future automated assignment and removes the role association from identities. Consequently, keeping the role disabled and performing identity processing does not provide a valid operational test of whether the configured membership criteria will assign the role as intended.

For an automatically assigned role, administrators define the assignment criteria, configure the required access, and enable the role. Identity Security Cloud then evaluates identities against the assignment criteria during identity processing. An administrator can manually initiate this evaluation by selecting Apply Changes from the Roles page. Identities satisfying the criteria receive the role and its configured access; identities that no longer satisfy the criteria can have the assignment removed.

Administrators should carefully validate role criteria before broad production application, but disabling the role specifically prevents it from functioning as an automated role assignment.

Study Guide Reference: Access Management — Role Management, Role Assignment Criteria, Enabling Roles and Identity Processing.

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

This is not a valid description of how a canceled access request is handled. A cancellation terminates the request before it completes. Once an access request has entered a concluded Canceled state, it is no longer simply a pending approval waiting for an administrator to substitute a decision for the assigned reviewer.

Approval Management does give administrators powerful controls over pending governance work. Administrators can inspect requests, reassign current approvers, send reminders, cancel requests, and, where supported, overwrite the current approval step. Overwriting an approver is fundamentally different from reversing an already canceled request: the administrator is acting on the current approval step of an active request.

SailPoint documentation explicitly identifies Canceled as a concluded status and defines cancellation as termination of the request. The administrator's overwrite capability applies to an approval step, not to resurrecting a request after cancellation. A new request would normally be required when access is still needed after the original request has been terminated.

Study Guide Reference: Access Management — Approval Management, Access Request Status, Administrative Approval Actions.

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

The statement is valid. Multi-Factor Authentication (MFA) strengthens authentication by requiring more than a single verification mechanism before access is granted. Authentication factors are generally categorized as something the user knows, something the user possesses, or something the user inherently is. Requiring multiple factors substantially reduces the effectiveness of a compromised password because possession of that password alone is insufficient to complete authentication.

Identity Security Cloud supports MFA through an external authenticator application. When MFA is configured for an Identity Profile, affected users register an authenticator and subsequently provide a generated verification code during authentication. SailPoint also distinguishes sign-in MFA from two-factor verification used for password resets and account unlocking, where administrators can explicitly require users to complete two configured verification methods.

Therefore, the video's characterization of MFA as requiring two or more forms of verification correctly reflects the underlying security principle. MFA should not be confused with authorization: authentication establishes identity, whereas authorization determines what authenticated identities are permitted to access.

Study Guide Reference: Access Management — Multifactor Authentication, Authentication Factors, Strong Authentication and Identity Profile Sign-In Methods.

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

This proposed API call is not valid for retrieving Virtual Appliance connector logs. The identifier shown in the log entry is a managed-cluster ID , yet the proposed URL incorrectly places that ID under the /v3/sources/ API resource. Managed clusters and sources are separate Identity Security Cloud objects and use different API endpoints.

SailPoint's documented Managed Clusters API provides operations for obtaining cluster details and for retrieving or modifying the cluster's log configuration , such as GET /managed-clusters/{id}/log-config and PUT /managed-clusters/{id}/log-config. It does not document a GET /v3/sources/{managedClusterId}/logs endpoint for exporting VA connector log files.

For connector troubleshooting, enhanced logging can be enabled against the appropriate managed cluster, the problematic operation reproduced, and the resulting VA/connector logs collected through the supported VA troubleshooting process. The administrator must also ensure that the correct cluster associated with the affected source is being investigated.

Therefore, the proposed endpoint confuses a managed cluster with a source and does not represent a supported log-export API.

Study Guide Reference: Virtual Appliances — Managed Clusters, Connector Logging, VA Troubleshooting and SailPoint REST APIs.

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

This is an appropriate corrective action for a PKIX certification-path failure. When the Active Directory connector communicates with a domain controller using TLS, the Virtual Appliance must trust the certificate presented by that server. A PKIX path validation failed or unable to find valid certification path to requested target error indicates that Java cannot construct a trusted certificate chain from the server certificate to a trusted certification authority.

Consequently, verifying that the correct CA or server certificate is available to the VA is a fundamental troubleshooting step. SailPoint supports TLS between Virtual Appliances and compatible sources and documents certificate management on the VA for situations where trusted certificates need to be added manually. Current configuration also attempts to copy supported TLS certificates automatically to the VA cluster, but administrators must still validate certificate trust when TLS handshakes fail.

The certificate chain, expiration, hostname, and issuing CA should also be checked. Once the VA trusts the appropriate chain, the TLS handshake can complete successfully.

Study Guide Reference: Virtual Appliances — TLS Configuration, Certificate Trust, Active Directory Secure Connectivity and PKIX Troubleshooting.

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

The statement is explicitly incorrect. Identity Security Cloud allows users to hold multiple User Levels in many circumstances, and permissions from compatible User Levels are cumulative. However, SailPoint defines several combinations that cannot be assigned simultaneously because their delegated administrative scopes conflict.

One of the specifically prohibited combinations is Role Admin and Source Sub-Admin . SailPoint's User Level documentation lists this pair among the User Levels that cannot coexist on the same user. Other prohibited combinations include Role Sub-Admin with Source Admin, Role Sub-Admin with Role Admin, and Source Sub-Admin with Source Admin.

The distinction is important. A Role Admin has broad role-management privileges, whereas a Source Sub-Admin receives scoped administrative capabilities based on Governance Group associations with particular sources. Combining certain global and scoped administrative models could create inconsistent authorization behavior, so SailPoint prevents those assignments.

Administrators should therefore consult the User Level compatibility matrix before granting multiple elevated permissions rather than assuming that every User Level can be stacked.

Study Guide Reference: Platform — User Level Permissions, User Level Compatibility, Role Admin and Source Sub-Admin.

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

The statement is not valid in the normal Identity Security Cloud identity model. An authoritative source is specifically used to establish identities. When a source is associated with an identity profile and thereby designated as authoritative, Identity Security Cloud creates an identity from each qualifying authoritative account. The authoritative account therefore forms the identity's authoritative foundation rather than behaving as an ordinary account that must subsequently be correlated to an existing identity.

Uncorrelated accounts normally arise from non-authoritative or secondary sources when Identity Security Cloud cannot match an aggregated account to an existing authoritative identity by using configured correlation criteria. SailPoint defines an uncorrelated account as an account that has not been linked to an authoritative identity. Such accounts must be resolved before their associated access can be properly governed.

Although unusual administrative edge cases can affect existing authoritative-account associations, this does not change the fundamental certification concept: authoritative accounts establish identities, while correlation attaches accounts from other sources to those identities.

Study Guide Reference: Identity and Lifecycle Management — Authoritative Sources, Identity Profiles, Account Correlation and Uncorrelated Accounts.

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

The statement is incorrect. Identity Security Cloud does not use majority voting within a Governance Group for an access-request approval step. When a Governance Group is configured as a reviewer, only one eligible member of that Governance Group is required to approve or deny the request on behalf of the group .

SailPoint explains that when an access request reaches a Governance Group, its members receive the applicable review assignment. Once one member makes the decision, the review is treated as completed for that Governance Group and disappears from the other members' pending approval lists.

This should not be confused with a multi-step approval process containing several separate reviewers. If the access item is configured with multiple required reviewer stages, each required stage must approve before provisioning occurs. However, a Governance Group itself represents one reviewer stage, and that stage does not require approval from 50%, a majority, or every member.

Therefore, requiring a majority of Governance Group members is not how standard Identity Security Cloud Governance Group approvals operate.

Study Guide Reference: Access Management — Governance Group Approvals, Access Requests, Multi-Approver Processes and Group Review Decisions.

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

The statement is correct. Attribute synchronization is configured at the source level because administrators must determine which account attributes on a specific governed source should remain synchronized with corresponding Identity Security Cloud identity attributes.

SailPoint's documented configuration path begins by navigating to Admin > Connections > Sources and selecting or editing the appropriate source. Within the source's Account Management section, the administrator opens Attribute Sync . Identity Security Cloud then displays the account attributes that are eligible for synchronization based on the source's Create Account definition and identity-attribute mappings. The administrator selects the attributes that should synchronize and can initiate the appropriate synchronization process.

Attribute Sync applies to existing correlated accounts. It does not independently create accounts, and an uncorrelated account cannot participate because Identity Security Cloud has no authoritative identity relationship from which to determine the target attribute values.

Therefore, accessing the source through Admin > Connections > Sources and configuring Attribute Sync from its account-management configuration is precisely the supported administrative approach.

Study Guide Reference: Provisioning — Configuring Attribute Sync, Source Account Management, Identity Attribute Mapping and Correlated Accounts.

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