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

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.

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.

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

This is a valid troubleshooting action. Identity Security Cloud depends on the source's entitlement schema to understand what entitlement objects and attributes should be collected. If the schema or entitlement-type configuration is incorrect, a newly created entitlement might not be recognized correctly during aggregation.

In the current Identity Security Cloud interface, this functionality is represented under Entitlement Management > Entitlement Types and Schemas . Each entitlement type has a schema that defines attributes such as its identifier, name, display name, description, and other source-specific properties. The account schema also identifies which account attributes represent entitlements. Consequently, schema configuration directly affects how source entitlement information is interpreted and linked to accounts.

Administrators should therefore confirm that the expected entitlement type exists, verify that its entitlement ID and entitlement-name attributes are mapped correctly, and then perform an entitlement aggregation. SailPoint specifically recommends examining and correcting entitlement schema mappings when entitlement information is not being aggregated correctly.

Study Guide Reference: Sources — Entitlement Types and Schemas, Entitlement Aggregation, Source Entitlement Configuration.

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

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.

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

This statement accurately describes core Identity Governance and Administration capabilities. Effective IGA provides centralized visibility into identities, accounts, entitlements, roles, applications, and the relationships between identities and their access. This allows security and governance teams to determine who has access, how that access was obtained, whether it remains appropriate, and where excessive or conflicting privileges exist.

IGA also provides policy-driven control. Organizations can implement lifecycle-based provisioning and deprovisioning, access-request approvals, role-based access, periodic certification campaigns, privileged-access governance, and Separation of Duties policies. These mechanisms enable organizations to enforce least privilege while maintaining an auditable record of access-related decisions.

SailPoint describes IGA as providing visibility and oversight of user access across systems and applications while strengthening security through policy-based controls, access reviews, provisioning automation, and SoD. SailPoint also describes its identity-security capabilities as providing detailed visibility into identities, access privileges, and policies throughout an organization.

Therefore, access visibility combined with policy-based governance is a defining IGA capability.

Study Guide Reference: General knowledge for Identity Security Administrators — IGA Fundamentals, Access Visibility, Governance Policies, Least Privilege and Access Controls.

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

This is a valid remediation step. Identity Security Cloud allows certifications to be reassigned when the original reviewer cannot complete the assigned review. A reviewer leaving the organization is precisely the type of situation in which reassignment is appropriate because governance decisions must still be completed by an authorized reviewer.

SailPoint documents that an administrator can open an active certification campaign, identify a certification whose reviewer has not signed off, and use Reassign to select another qualified user. The system also protects against self-certification by validating that the new reviewer is not being asked to certify their own access. A certification that has already been signed off cannot simply be reassigned in the same manner.

Administrators can additionally configure work reassignment to redirect certifications and other governance work when users are unavailable. This supports temporary absences as well as permanent situations where an identity should no longer receive governance work.

Therefore, administrator-initiated reassignment is the correct way to preserve campaign completion and accountability.

Study Guide Reference: Supporting Governance — Certification Campaigns, Reassigning Certifications, Reviewer Availability and Self-Review Prevention.

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

Yes. Removing the @entitlements(name:Manager_Access) portion produces a valid identity-oriented query structure. Identity Search supports the @access(...) nested object because an identity can possess multiple access items. SailPoint specifically documents @access(displayName:...) for identifying identities that possess a named access item and @access(source.name:...) for locating identities whose access originates from a particular source. Nested access queries can be combined with ordinary identity fields by using Boolean operators.

The remaining query therefore applies three conditions correctly: the identity must have been created during the specified 24-hour range, and the identity must satisfy either the New_Hire_Access condition or the Acme_HRMS source-access condition.

The problem with the original expression is the @entitlements(...) nested object. In SailPoint's searchable data models, @entitlements is used when examining objects such as access profiles or roles that contain entitlements; it is not the appropriate nested object for identity-level access searches. Identity-level entitlement holdings are searched through @access(...).

Study Guide Reference: Platform — Search, Nested Queries, Identity Access Fields and Boolean Query Construction.

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

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.

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

This approach satisfies the stated provisioning requirements. Identity Security Cloud roles can use identity attributes such as department as assignment criteria. Therefore, a standard role can be configured so that identities whose department equals Finance automatically qualify for the role, regardless of whether their employment type is employee or contractor.

The role can then contain the Office 365 E3 entitlement, either directly or through an appropriate access profile. When an identity satisfies role membership criteria, Identity Security Cloud automatically assigns the role and provisions its associated access to the identity's applicable source account. When the identity ceases to meet the criteria, the role and associated provisioned access can be removed.

This design does not indiscriminately assign a default Office 365 license to contractors throughout the organization. It targets Finance identities and grants the specific E3 access required by the scenario. It also avoids deliberately assigning both the default license and E3 license to the same Finance identity.

Study Guide Reference: Provisioning — Automated Role Assignment, Identity Attribute Criteria, Role-Based Provisioning and Entitlement Assignment.

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