Identity-Security-Administrator Questions and Answers

The statement accurately reflects the Search-based reporting model represented by Identity Security Cloud. Search is not limited to interactive investigation. Administrators can create a useful search query, save it, and configure a recurring subscription so that Identity Security Cloud generates and distributes the results automatically on a defined schedule.

The important workflow is that the query must first be executed and stored as a saved search. A subscription can then be attached to that saved search, with configuration for scheduling, timezone, and recipients. The scheduled execution returns records from the results category or tab that was selected when the saved search was created.

This functionality effectively turns a valid, reusable Search query into a scheduled reporting mechanism. It is particularly useful for recurring governance monitoring, audit review, identity-analysis tasks, entitlement investigations, and event reporting. SailPoint documentation states that automatic scheduled emails can contain the results of a saved search query and that subscriptions can be configured on recurring schedules.

Study Guide Reference: Platform — Search, Saved Searches, Scheduled Search Reports and Subscriptions.

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

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.

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

Yes. This is an appropriate scenario for applying Separation of Duties (SoD). The fundamental purpose of SoD is to prevent a single identity from accumulating combinations of privileges that provide excessive control over a sensitive business or technical process. Assigning one person responsibility for user administration, application administration, and data backup management creates significant concentration of privilege. Such a person could potentially create or modify accounts, change application configuration or permissions, and manipulate or restore protected data without independent oversight.

Identity Security Cloud supports SoD policies by defining two sets of conflicting access. A violation occurs when an identity possesses qualifying access from both sides of the policy. Administrators can then investigate, remediate, or formally manage exceptions. SailPoint describes SoD as an internal control intended to reduce risk by preventing identities from possessing inappropriate combinations of access.

Therefore, separating these powerful administrative capabilities among different responsible individuals is consistent with least privilege and defense-in-depth governance.

Study Guide Reference: Supporting Governance — Separation of Duties, Conflicting Access, SoD Policies and Privileged Access Governance.

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

The statement accurately describes the cryptographic trust model underlying SAML federation. In a typical SAML configuration, the Identity Provider (IdP) authenticates the user and issues a SAML assertion. The Service Provider (SP) validates the assertion, particularly its digital signature, by using certificate/public-key information associated with the trusted IdP. Private keys remain protected by their owners; the corresponding certificates containing public keys can be exchanged through configuration or SAML metadata.

For Identity Security Cloud operating as a SAML Service Provider, SailPoint requires administrators to obtain the IdP's signing certificate and configure it in Identity Security Cloud. SailPoint also provides Service Provider metadata that can be supplied to the IdP. This establishes the federation relationship and allows the participating systems to validate SAML messages according to the configured trust model. The critical concept is that passwords are not shared between the IdP and SP. Authentication assertions are trusted because they originate from an established federation partner and can be cryptographically validated.

Study Guide Reference: Access Management — Authentication Methods, SAML Federation, Identity Provider and Service Provider Trust.

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

The statement is correct. Identity Security Cloud allows administrators to configure a requestable role so that reviewers must provide justification when denying the requested access.

When configuring a role for access requests, administrators can enable the role for requests, define its approval process, and configure Require Comments behavior. SailPoint specifically provides an option named When a reviewer denies the request . Enabling this setting requires the reviewer to enter a comment or reason when rejecting the role request.

This requirement strengthens governance and auditability. A denial without explanation provides limited evidence about why the access was considered inappropriate. Requiring a comment records the business or security reasoning behind the decision, which can later assist administrators, access owners, auditors, and compliance personnel in understanding the approval history.

Comment requirements can also be configured at other stages, including when the requester submits the access request. Similar denial-comment controls exist for directly requestable entitlements.

Therefore, requiring a reviewer to document the reason for rejection is a supported role-request configuration.

Study Guide Reference: Access Management — Requestable Roles, Approval Processes, Require Comments and Access Request Governance.

This statement accurately describes one of the principal purposes of the Virtual Appliance. Identity Security Cloud is a SaaS platform, but many enterprise identity sources are located inside customer-controlled networks and cannot safely accept direct inbound connections from an external cloud service. The VA provides the secure intermediary required for these integrations.

SailPoint defines the VA as a Linux-based virtual machine deployed on the customer's infrastructure that connects Identity Security Cloud to organizational sources and applications through supported APIs, connectors, and integrations. The architecture is designed around outbound-only communication from the VA toward SailPoint's cloud environment. SailPoint does not initiate a direct inbound connection to the VA.

This architecture enables account and entitlement aggregation, account correlation support, provisioning, password-related operations, and other connector activities against internal sources while avoiding the need to expose those systems directly through the firewall.

SaaS connectors can eliminate the VA requirement for supported cloud services, but VA-based connectors remain fundamental when direct customer-network connectivity is required.

Study Guide Reference: Virtual Appliances — VA Purpose, On-Premises Source Connectivity, Outbound-Only Architecture and Source Integration.

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

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.

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

Yes. SailPoint explicitly documents that an individual Identity Security Cloud user can maintain up to 10 Personal Access Tokens (PATs) . PATs provide client credentials that can be used by scripts, applications, integrations, and API tools to authenticate to Identity Security Cloud without requiring an interactive login for each API request.

Each PAT has its own Client ID and Secret and can therefore be dedicated to a particular integration or automation workload. Separating tokens by purpose improves security administration because one compromised or obsolete integration token can be revoked without disrupting unrelated systems. Administrators should use meaningful descriptions, appropriate expiration dates, and the minimum required API scopes for each token.

The token's secret is displayed when the PAT is created and must be securely recorded at that time because the secret cannot subsequently be retrieved from the interface. A lost secret requires replacement of the affected token. Identity Security Cloud also records information such as token usage, enabling administrators to identify unused credentials that should be removed.

Study Guide Reference: Platform — Personal Access Tokens, API Authentication, Token Limits, Scope Management and Credential Security.

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

The statement correctly describes Identity Security Cloud's default self-approval prevention behavior when the requester is assigned as an individual reviewer . SailPoint does not normally permit a person to approve their own access request. This applies whether the request is submitted directly for themselves or whether the affected access recipient otherwise appears as a reviewer in the approval sequence.

When the requester or recipient is assigned an approval directly as an individual, Identity Security Cloud automatically reassigns that review responsibility to the individual's manager . If a valid manager is unavailable, the system can continue through alternative fallback mechanisms, eventually reaching an administrator when necessary.

There is an important distinction for Governance Groups: if the requester belongs to a Governance Group configured as reviewer, the requester is normally omitted while other group members remain eligible to approve. Only when that user is effectively the group's sole valid reviewer does manager reassignment occur.

An optional API setting can permit auto-approval for individual reviewers, but the default behavior described by the scenario is manager reassignment.

Study Guide Reference: Access Management — Preventing Self-Approval, Approval Reassignment, Manager Review and Access Request Governance.

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

Gather data from requestor to build search query.

Run the query to gather results.

Save and name the search query.

Schedule saved search query on a month cadence as requested.

The sequence follows the correct Identity Security Cloud Search workflow. First, the administrator must gather the audit requirements from the requestor, including which distribution list, identities, access attributes, or other conditions must be evaluated. Those requirements are then translated into an appropriate Search query. Second, the query must be executed so the administrator can confirm that it returns the intended records before automating it.

After validating the output, the administrator saves and names the query. Identity Security Cloud requires the query to exist as a saved search before a recurring subscription can be configured. Finally, the saved search is scheduled according to the requested monthly cadence. SailPoint supports subscriptions to saved searches with Daily, Weekly, and Monthly schedules and allows administrators to specify the numerical days of the month and execution times. Therefore, scheduling must occur after the query has been constructed, tested, and saved.

Study Guide Reference: Platform — Search, Building Search Queries, Saved Searches, Search Subscriptions and Scheduled Reporting.

The statement is valid. A Governance Group is intended to provide a collection of identities that can make governance decisions about access. If the group has no valid members, there is nobody within that group who can perform the required approval action.

SailPoint explicitly states that before a Governance Group reviews access, it must be configured and have members . When the Governance Group's turn arrives during an access request or certification, its members receive notification and any eligible member can act on behalf of the group.

Identity Security Cloud has fallback and reassignment mechanisms for situations where reviewers cannot be resolved, but administrators should not design approval configurations around an empty Governance Group. Doing so creates unnecessary routing failures, escalation, or reassignment and weakens the intended ownership model.

The recommended governance model is therefore to create the group, assign appropriate responsible identities as members, maintain membership as organizational responsibilities change, and only then use that group as a reviewer, owner, or governance decision point.

Study Guide Reference: Access Management — Governance Groups, Group Membership, Access Request Reviewers and Approval Configuration.

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

Yes. Identity Security Cloud's Account Activity view is designed to provide administrators with a chronological operational view of provisioning actions. SailPoint documents that account activities are displayed by default in descending order of Last Modified date , which places the most recently updated provisioning activity first. This is useful during troubleshooting because current or recently failed operations are immediately visible.

The activity table exposes operational fields such as Status, Action, Requester, Recipient, Sources, Last Modified, and Stage. Administrators can use the tabular controls to reorganize the displayed information for analysis, including changing sort direction on sortable columns. This makes it possible to investigate provisioning operations from perspectives other than chronological order—for example, grouping similar requesters, recipients, sources, statuses, or actions.

Selecting an individual activity exposes additional request information, including provisioning errors and the progression of the request through its processing stages. This capability is important when determining whether an account create, modify, enable, disable, or entitlement operation completed successfully or stalled.

Study Guide Reference: Provisioning — Monitoring Provisioning, Account Activity, Last Modified Sorting and Provisioning Troubleshooting.

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

The statement is correct. A user does not need an administrative User Level such as Certification Admin or Org Admin merely to review a certification that has legitimately been assigned to them. Certification administration and certification reviewing are separate permission concepts.

The SailPoint User Level Access Matrix shows that the ordinary End User experience includes access to the Certifications functionality. This permits users to open certifications assigned to them, evaluate the relevant access items, record approval or revocation decisions, and sign off on the certification. Elevated Certification Admin permissions are instead required for administrative functions such as managing certification campaigns and broader certification configuration.

This design is essential because certification reviewers are commonly business managers, entitlement owners, source owners, Governance Group members, or other business stakeholders who should not require broad administrative privileges merely to participate in governance reviews.

Therefore, if a standard user has been properly assigned certification-review responsibility, ordinary user permissions are sufficient to perform that review.

Study Guide Reference: Platform — User Levels, End User Permissions, Certification Reviewers and Certification Administration.

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

The statement is incorrect. Identity Security Cloud does not automatically transfer a departed reviewer's certification responsibilities to that reviewer's manager merely because of the reporting relationship. Certification ownership is explicitly assigned, and the authorized replacement process is reassignment rather than implicit managerial inheritance.

If the original reviewer cannot finish a certification, an administrator can reassign that pending certification to another qualified identity. Identity Security Cloud validates the reassignment to prevent the new reviewer from certifying their own access. A manager can also configure work reassignment for their team members when that functionality is enabled, but that still establishes an explicit reassignment rather than granting the manager unrestricted authority to enter every certification belonging to the employee.

After a campaign deadline, administrators also have campaign-level options for resolving undecided items, including completing the campaign according to the configured maintain-or-revoke behavior.

Therefore, the correct response to a departed reviewer is to use supported reassignment or campaign-completion procedures, not assume the reviewer's manager automatically acquires all pending certifications.

Study Guide Reference: Supporting Governance — Certification Reassignment, Work Reassignment, Campaign Deadlines and Reviewer Responsibilities.

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

The statement is incorrect. A SaaS-based application does not inherently require a "cloud-based VA." Identity Security Cloud supports SaaS connectors that can connect supported cloud applications directly without requiring the customer to deploy a Virtual Appliance cluster.

SailPoint explicitly states that organizations can use a SaaS connector when they want to upload data to Identity Security Cloud from a source without a Virtual Appliance cluster . In contrast, VA-based connectors are used when direct connector communication must occur from the customer's controlled environment.

Furthermore, a SailPoint VA is not normally a SailPoint-hosted cloud appliance. SailPoint provides the virtual appliance image, but the VA is deployed on infrastructure procured or controlled by the customer. SailPoint manages and updates the appliance software while the customer provides the hosting environment and network connectivity.

Some cloud-hosted applications can still use VA-based connectors depending on network topology and connector design, but being a SaaS application alone does not impose a VA requirement.

Study Guide Reference: Virtual Appliances — VA-Based versus SaaS Connectors, VA Deployment Architecture and Cloud Application Connectivity.

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

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 statement correctly describes the purpose of Separation of Duties (SoD) policies. In identity governance, a toxic combination is a set of access privileges that becomes excessively risky when possessed by the same identity. A typical example would be combining permission to create a supplier with permission to approve payments to that supplier. Either permission may be legitimate independently, while the combined privileges create an unacceptable control conflict.

Identity Security Cloud implements SoD by allowing administrators to construct policies containing conflicting sets of access. Human identities possessing access from both sides of the defined conflict can generate policy violations that administrators and designated violation owners can investigate, remediate, or mitigate. SailPoint describes SoD as an internal control that provides visibility into risky access combinations and helps organizations identify where policy violations exist.

Therefore, SoD policies are specifically designed to identify and govern the toxic combinations of privileges described in the statement.

Study Guide Reference: Supporting Governance — Separation of Duties, Conflicting Access, Toxic Combinations and SoD Policy Violations.

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

This is an essential and valid troubleshooting step. Lifecycle-state provisioning is triggered according to the lifecycle state calculated for an identity. If Identity Security Cloud does not actually consider the affected user to be in the Terminated state, the account-disable operations configured for that lifecycle state will not be initiated.

The administrator should therefore inspect the identity and confirm that its Lifecycle State value resolves to Terminated. If it does not, the next investigation should focus on the identity profile's lifecycle-state configuration, authoritative source attribute mapping, transforms or rules used to calculate lifecycle state, and whether the identity has been properly reprocessed after the source data changed.

Once an identity enters the configured lifecycle state, Identity Security Cloud can apply account actions defined under Settings for Previous Accounts , including disabling accounts across all sources or specified sources. SailPoint specifically uses Terminated and Archived states as examples where access removal and account disablement are commonly configured.

Consequently, validating the identity's actual lifecycle-state value is one of the first diagnostic checks that should be performed before investigating downstream connector or provisioning failures.

Study Guide Reference: Identity and Lifecycle Management — Lifecycle States, Terminated Identities, Lifecycle Attribute Calculation and Account Actions.

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

The statement does not accurately describe how governance-group approval and escalation operate. When a governance group is configured as an approver, the request is associated with the group's members, and a member of that governance group can perform the approval on behalf of the group. The system is not designed to send the request exclusively to the manager of one active group member.

Escalation behavior is also broader than the proposed statement suggests. SailPoint documents that when governance-group approvals are escalated to a manager level, the request can be escalated to each member's manager . If a particular member does not have a manager, that member's approval can remain assigned while other members' assignments are escalated. If none of the members has a manager, the applicable approvals can progress to the configured fallback approver.

Therefore, "only to the manager of an active member" incorrectly reduces a multi-member governance-group escalation process to one manager and does not reflect the documented routing behavior.

Study Guide Reference: Access Management — Governance Group Approvals, Escalation Chains, Access Request Reviewers.

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

The statement is correct. Identity Security Cloud supports two documented methods for defining role assignment: Standard Criteria and Identity List . SailPoint explicitly presents these options under Define Assignment > Choose Criteria Type when configuring automated role assignment.

Standard Criteria is the dynamic, data-driven option. Administrators can construct criteria using supported identity attributes, account attributes, or entitlements. Operators such as Equals, Does Not Equal, Contains, Starts With, and Ends With can be used where applicable, and multiple conditions can be organized with AND/OR logic. During identity processing, qualifying identities are assigned the role automatically.

Identity List provides a direct membership approach. Administrators search for and explicitly select the identities that should receive the role. It is appropriate when membership cannot conveniently be expressed through business attributes or when a controlled list of named identities is required.

After assignment configuration is saved and the role is enabled, Identity Security Cloud evaluates the role during identity processing; administrators can also initiate processing using Apply Changes.

Study Guide Reference: Access Management — Role Assignment, Standard Criteria, Identity List and Automated Role Provisioning.

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

1. Define what values are needed to onboard a user in a managed system.

Select a match:

Create Account

2. Update an identity's phone number in Active Directory.

Select a match:

Attribute Sync

3. Customizable logic to match an account to an existing identity.

Select a match:

Correlation Rule

4. Supports user management in Active Directory.

Select a match:

IQService

The correct mappings correspond directly to the functions of SailPoint Identity Security Cloud provisioning and integration components. Create Account defines the account attributes and values that Identity Security Cloud uses when provisioning a new account on a managed source. SailPoint states that the Create Account configuration specifies which attributes are populated and how their values are determined.

Attribute Sync keeps account attributes on a target source synchronized with identity attributes. Therefore, if an identity's mapped phone-number attribute changes, Attribute Sync can provision the corresponding change to Active Directory.

A Correlation Rule provides customizable logic for matching source accounts to existing identities when straightforward attribute correlation is insufficient. Correlation fundamentally determines which identity owns a source account.

Finally, IQService is SailPoint's Windows service used with Active Directory to support provisioning and Windows-specific management operations. SailPoint explicitly requires IQService for Active Directory provisioning and related Windows functionality.

Study Guide Reference: Provisioning — Create Account; Attribute Sync; Account Correlation; IQService and Active Directory Integration.

This statement is correct and closely matches SailPoint's official definition of a source. Identity Security Cloud does not treat an external enterprise system itself as being physically contained within the tenant. Instead, it creates a source definition representing that application, database, directory, HR system, or other managed environment.

The source definition supplies the governance context through which Identity Security Cloud interacts with the underlying system. A connector gathers account and access information and associates that data with the source. Identity Security Cloud can then correlate source accounts to identities, aggregate entitlements, model access, perform certifications, support access requests, and—in the case of writable connectors—provision changes back to the external system.

SailPoint's current source-management documentation explicitly defines a source as the Identity Security Cloud representation of a third-party enterprise application, database, or directory-management system maintaining its own user accounts or personnel records.

This distinction between source and connector is important: the source is the governed system representation, while the connector provides the technical mechanism used to communicate with that system.

Study Guide Reference: Sources — Source Definitions, Connector Definitions, Source Accounts and Enterprise System Integration.

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

This is a valid integration approach. Identity Security Cloud does not require every authoritative source to correspond to a purpose-built SaaS connector. For custom or legacy systems, generic integration mechanisms can expose the authoritative account or personnel information needed to construct identities.

A Delimited File source can load account information exported from a system into Identity Security Cloud. SailPoint describes the Delimited File connector as a general-purpose mechanism that reads account data from files and supports customizable account schemas. A database-backed custom HR application can instead be integrated through an appropriate JDBC/database connector when its personnel information is accessible through relational tables.

After creating the source, an Identity Profile can be associated with it to make that source authoritative. SailPoint states that when a source is configured as authoritative through an Identity Profile, an Identity Security Cloud identity is created for each applicable authoritative account.

The administrator must still design a reliable schema, uniquely identify contractors, configure required identity attributes, and determine suitable correlation and lifecycle mappings. Nevertheless, Delimited File and JDBC-style integrations are legitimate approaches for legacy authoritative data.

Study Guide Reference: Sources — Authoritative Sources, Generic Connectors, Delimited File Integration, JDBC Integration and Identity Profiles.

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

The statement is correct. In SAML federation, the Entity ID uniquely identifies a participant in the trust relationship. When Identity Security Cloud is configured to use an external Identity Provider, the Identity Provider Entity ID entered in SailPoint must correspond to the EntityID specified in the IdP's SAML metadata.

This identifier helps Identity Security Cloud determine which trusted Identity Provider issued the authentication assertion. If the configured Entity ID does not match the expected IdP identifier, authentication processing can fail because the received federation information does not correspond to the configured trust relationship.

Administrators must also configure other SAML components correctly, including the Identity Provider login endpoint and signing certificate. The signing certificate enables Identity Security Cloud to validate the authenticity and integrity of SAML assertions received from the IdP.

It is also important to distinguish between the IdP Entity ID and the Identity Security Cloud Service Provider Entity ID. Each identifies a different side of the SAML relationship.

Study Guide Reference: Access Management — SAML Authentication, Identity Provider Configuration, Entity IDs and Federation Trust.

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