Pass the SailPoint Professional Identity-Security-Administrator Questions and answers with ExamsMirror

No. The statement is too restrictive and misunderstands SailPoint's Search data models. The nested object @entitlements(...) is available in contexts where the searched object can contain multiple entitlements. Access profiles are one such category, but they are not the only applicable category. SailPoint's searchable-field documentation also defines entitlement nested fields for roles. Therefore, @entitlements(name:Manager_Access) cannot be characterized as inherently returning only access profiles associated with that entitlement.

The search category matters. Identity Search uses the @access(...) nested object to identify the access held by identities. For example, an identity holding a Manager_Access entitlement can be searched through an appropriate @access(...) expression. Conversely, when querying access-profile or role records, @entitlements(...) can filter those objects according to entitlements contained within them.

The original query is consequently invalid as a coherent identity query because it combines identity-oriented fields and @access(...) expressions with an entitlement-container nested construct belonging to different searchable object models.

Study Guide Reference: Platform — Searchable Fields, Nested Objects, Identity Search, Access Profiles and Role Search Models.

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

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.

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

This is a valid troubleshooting approach. An Active Directory provisioning failure such as "There is no such object on the server" indicates that the connector attempted an operation against an object or directory reference that Active Directory could not resolve. Potential causes include an account or group being deleted or moved, an outdated distinguished name, an invalid entitlement reference, replication timing, or a provisioning operation targeting an object that no longer exists.

Searching SailPoint's technical knowledge and community resources for the exact connector error is therefore useful because connector-specific errors often have previously documented causes, configuration considerations, and remediation patterns. This should complement—not replace—tenant-side investigation. An administrator should correlate the error with provisioning activity, source information, account state, and the target system. Identity Security Cloud provides Search and audit information for investigating provisioning activity, while SailPoint technical resources provide additional connector-specific context. Current SailPoint documentation explicitly identifies provisioning activity as auditable and searchable.

Study Guide Reference: Provisioning — Troubleshooting Provisioning Errors, Active Directory Connector Operations, SailPoint Support Resources.

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

The statement is false. Identity Security Cloud distinguishes between defining an identity attribute for the tenant and mapping that attribute within a specific identity profile. When an administrator creates a new custom identity attribute from the mappings configuration of an identity profile, the attribute itself becomes available across all identity profiles in the tenant .

SailPoint explicitly states that any identity attribute added under any identity profile appears in all identity profiles. However, administrators do not have to map or use that attribute in every profile. Each identity profile can define its own mapping because different identity populations can obtain attribute values from different authoritative or secondary sources.

For example, a custom Employee Region attribute could be mapped from an HR source for employees while being mapped from Active Directory for contractors—or left unmapped in a profile where it is unnecessary. This distinction is essential: the attribute definition is tenant-wide, whereas the mapping and resulting value are identity-profile-specific.

Therefore, claiming that the custom attribute applies only to the identity profile where it was created is incorrect.

Study Guide Reference: Identity and Lifecycle Management — Identity Profiles, Custom Identity Attributes and Attribute Mappings.

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

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 Profiles remain administratively manageable after identities have been created from their associated authoritative sources. Administrators can edit supported Identity Profile properties, including identity attribute mappings, lifecycle-related configuration, ownership information, and other profile settings. When a change affects identity data, Identity Security Cloud marks the profile as requiring processing, and the administrator can use Apply Changes to recalculate affected identities.

Identity Profiles can also be managed programmatically. SailPoint exposes APIs for updating and deleting Identity Profiles. Some fields have restrictions—for example, system-generated properties cannot be modified, and changes to authoritative-source configuration and identity-attribute configuration have specific processing constraints—but the existence of identities under the profile does not make the profile permanently immutable. The V3 API explicitly provides both update and delete Identity Profile operations.

Because at least the assertion that administrators cannot modify an Identity Profile after identities are assigned is demonstrably false, the overall proposed statement is false.

Study Guide Reference: Identity and Lifecycle Management — Identity Profiles, Editing Identity Profiles, Processing Identity Changes and Identity Profile Administration.

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

This is an appropriate diagnostic method within the Search model represented by the course scenario. The query narrows the investigation to events associated with provisioning, filters for events containing errors, constrains the timeframe to the date on which the failure occurred, and associates the result with the affected identity, Clarence.Harper. Opening the corresponding event allows the administrator to investigate the contextual information associated with the failed provisioning operation.

The underlying troubleshooting principle remains central to Identity Security Cloud administration: provisioning failures should be correlated with audit events and account activity rather than evaluated only from the short error message shown in a dashboard. SailPoint Search contains audit-event information and supports filtering against event data. Event records can provide operation details, status, target information, source context, and additional attributes. SailPoint also provides a Provisioning Activity audit-report capability specifically for reviewing provisioning events.

Study Guide Reference: Provisioning — Monitoring Provisioning, Search and Audit Events, Troubleshooting Failed Provisioning Operations.

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

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.

This is a valid use of Approval Management. A pending access request can become operationally blocked if the assigned reviewer—for example, the requester's manager—is unavailable. Administrators need a mechanism to prevent governance processes from stalling because of absence, organizational changes, or incorrect assignment.

Identity Security Cloud allows administrators to locate a pending access request and reassign its review responsibility to another suitable identity. The new reviewer becomes the current approver and can continue the approval process. Reassignment is recorded as part of the request's processing history, preserving accountability and auditability.

The same principle is also available to reviewers in appropriate circumstances: an assigned reviewer can reassign a request when another user is better suited to make the decision. For administrators, Approval Management provides centralized visibility and control over pending requests across the tenant. SailPoint explicitly documents that administrators can reassign requests and that reassignment is intended to maintain the timely flow of governance processes.

Study Guide Reference: Access Management — Approval Management, Reassigning Access Requests, Pending Approval Administration.

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