This can be a valid reason, depending on the manager-review campaign mechanism being used. In a search-based certification campaign where Manager is selected as the reviewer, Identity Security Cloud determines the reviewer from each identity's manager relationship. If an identity does not have a manager defined, SailPoint documents that the certification is reassigned to the creator of the campaign . If the campaign creator is an administrator, the certification therefore appears assigned to that administrator instead of a manager.

The absence of a manager can originate from authoritative HR data, an incomplete manager attribute mapping, failed manager correlation, or otherwise missing manager information on the identity.

A distinction is important: traditional Manager Campaigns require identities to have managers defined and identities without managers are normally excluded. SailPoint recommends using a Search-based campaign with Manager selected as reviewer when identities without managers must still be included.

Given the scenario explicitly states that the certification was reassigned to an admin, missing manager information is therefore a technically valid explanation for the observed fallback assignment.

Study Guide Reference: Supporting Governance — Certifications, Manager Review, Search-Based Campaigns and Identities Without Managers.

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

This is a valid troubleshooting action. Identity Security Cloud provides administrators with centralized visibility into pending access requests through Approval Management / Approvals Administration . An administrator can select an access request and inspect its processing details rather than relying only on the status visible to the requester.

The request's Process view displays the progression of the approval and provisioning workflow. It identifies completed, active, and future steps and can show which approver or governance group currently owns an outstanding review. Where multiple reviewers are involved, administrators can expand approval stages to inspect individual reviewer status. The Assignees information also identifies who is currently responsible for approving the request.

This makes the administrative view particularly useful when a request appears "stuck." The administrator can determine whether it is waiting for approval, escalation, provisioning, or another processing stage and then take an appropriate supported action such as reminding or reassigning an approver.

Therefore, reviewing the request's administrative process flow is an appropriate first-line diagnostic step.

Study Guide Reference: Access Management — Approvals Administration, Tracking Access Requests, Approval Workflow and Pending Request Troubleshooting.

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

The statement is valid for identities whose role assignment is actively enforcing the role's access. Identity Security Cloud roles represent collections of access that can include entitlements and access profiles. When role access is expanded, the role's existing members are expected to receive the additional required access so their actual source access continues to satisfy the role definition.

Role configuration changes are not necessarily applied to every identity immediately at the moment the administrator saves the role. SailPoint states that access additions are handled by identity processing . Administrators can select Apply Changes on the Roles page to initiate processing across identities, or the change can be applied when relevant identity processing subsequently occurs. During that processing, the system recalculates the role-based access requirements and provisions new access to applicable source accounts.

This behavior is important to understand operationally: editing a role changes its access model, and Identity Security Cloud must then propagate those additions to identities holding the role.

Study Guide Reference: Access Management — Roles, Managing Role Access, Role Change Processing and Automated Provisioning.

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

The proposed statement is incorrect because the displayed search syntax is malformed. To search for identities whose account count falls within an inclusive numerical range, Identity Security Cloud uses range-query syntax with properly matched square brackets.

The correct expression is:

accountCount:[1 TO 4]

Square brackets indicate that both endpoints are included. Therefore, a correctly formatted query would return identities with account counts of 1, 2, 3, or 4. The displayed expression, however, is missing the closing square bracket and does not follow the documented range syntax correctly.

The accountCount field represents the number of accounts associated with an identity across connected sources. Range searches are useful when administrators need to identify identities with unusually low or high account ownership, investigate orphaned access patterns, or perform access-analysis activities.

Because the specific proposed command is syntactically incomplete, it cannot reliably be treated as the documented query that returns identities with one through four accounts.

Study Guide Reference: Platform — Search Query Syntax, Range Queries, Identity Search Fields.

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

No. Current Identity Security Cloud behavior does not automatically assign sp:scopes:all when an administrator or user creates a Personal Access Token without explicitly selecting scopes. SailPoint documents that when no scopes are selected, the default scope is assigned. That default provides permission only for API endpoints that do not require authorization; it is not equivalent to unrestricted access under sp:scopes:all.

The sp:scopes:all scope must be intentionally selected when required. Even then, it does not grant arbitrary privileges beyond the token owner's authority. Instead, it authorizes API scopes that are available through the user levels assigned to the user who created the PAT. Consequently, PAT permissions remain bounded by that identity's effective Identity Security Cloud privileges.

This behavior supports the principle of least privilege. SailPoint recommends selecting only the scopes necessary for the application or integration using the token rather than broadly assigning sp:scopes:all.

Therefore, leaving all scope checkboxes unselected does not implicitly grant all available API scopes.

Study Guide Reference: Platform — Personal Access Tokens, OAuth/API Scopes, sp:scopes:all and Least-Privilege API Authentication.

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

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.

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

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 incorrect. A role does not have to be requestable in Identity Security Cloud. Requestability is an optional capability used when organizations want users to obtain a role through the Request Center.

Roles can instead be assigned automatically according to Standard Criteria or an Identity List. When an identity satisfies automated assignment conditions, the role and associated access can be granted through identity processing without the user submitting an access request.

SailPoint specifically states that organizations can allow users to request roles when the role cannot easily be auto-assigned or when someone who does not meet its ordinary assignment criteria might legitimately require the access. To enable this behavior, an administrator edits the role's Access Requests configuration and turns on Allow Access Requests . The presence of an enable/disable setting itself demonstrates that requestability is optional rather than mandatory.

A role can therefore exist purely as automatically assigned business access, purely as requestable access where appropriate, or be configured according to the organization's access-governance design.

Study Guide Reference: Access Management — Roles, Access Requests, Requestable Roles and Automated Role Assignment.

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

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.

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

The statement is valid. In Identity Security Cloud, entitlements represent individual access rights or permissions that exist on connected sources. The specific form of an entitlement depends on the target system. Examples can include Active Directory groups, application roles, permission sets, security groups, database privileges, or other source-specific access constructs.

Entitlements form a fundamental layer of SailPoint's access model. Administrators can combine one or more entitlements from the same source into an access profile. Access profiles can then be incorporated into roles to create higher-level business access models.

Because SailPoint aggregates entitlement information from connected sources, administrators can govern these access rights through certifications, access requests, provisioning processes, role management, and policy analysis. Entitlement metadata can also provide meaningful descriptions and ownership information so reviewers understand the access being governed.

Therefore, describing entitlements as specific access rights on a source precisely reflects their role in Identity Security Cloud's access governance architecture.

Study Guide Reference: Access Management — Entitlements, Access Profiles, Roles and Access Model Fundamentals.

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