This is a correct troubleshooting step. Enabling Entitlement Requests globally makes entitlement requesting available to the organization, but it does not automatically make every aggregated entitlement available in the Request Center. Individual entitlements must also be marked as requestable.

SailPoint specifically supports managing this setting from the source. An administrator can navigate to Admin > Connections > Sources , select the source, open Entitlement Management > Entitlements , locate the required entitlement, and verify whether it is marked as requestable. The entitlement can then be updated through the applicable Actions menu. SailPoint also exposes requestable status centrally from the Access Model > Entitlements page.

Because the missing access corresponds to recently added directory groups, the administrator should also ensure that an entitlement aggregation has successfully loaded the groups into Identity Security Cloud. If the group exists but is not requestable, users will not receive the expected direct entitlement-request experience.

Therefore, checking the entitlement's Requestable status is a technically appropriate diagnostic action.

Study Guide Reference: Sources — Entitlement Management, Entitlement Aggregation, Requestable Entitlements and Access Request Configuration.

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

Waiting for an identity refresh is not the correct remediation for a missing source entitlement. Identity processing and entitlement aggregation perform different functions. Identity processing recalculates identity-related information and access relationships based on information already known to Identity Security Cloud; it does not independently discover a newly created entitlement that has never been successfully loaded from the external source.

New entitlement objects are discovered through entitlement aggregation or through supported account aggregation behavior, depending on the source and connector. SailPoint defines entitlement aggregation as the process of loading entitlement data from an external source into Identity Security Cloud. The completed aggregation records how many entitlements were discovered.

If an expected entitlement is absent, the administrator should inspect the source's entitlement configuration and schema, review aggregation status/history, confirm that the external entitlement exists, and run or troubleshoot an entitlement aggregation. SailPoint's troubleshooting guidance specifically directs administrators to perform entitlement aggregation when entitlement metadata is not being imported correctly.

Study Guide Reference: Sources — Entitlement Aggregation, Entitlement Schemas, Aggregation Troubleshooting and Identity Processing.

This is not the primary purpose of an Identity Profile. In Identity Security Cloud, an Identity Profile establishes how identities are created and governed from an authoritative source . It determines the authoritative source associated with a population, maps source account attributes into identity attributes, defines authentication and security settings, and configures lifecycle-state behavior. SailPoint states that configuring an Identity Profile makes the associated source authoritative and creates identities from accounts on that source.

Assigning permissions based on business roles belongs instead to the access model . Roles can bundle access profiles and associated entitlements and can be automatically assigned to identities by Standard Criteria or by explicitly selecting identities through an Identity List.

An Identity Profile may indirectly affect access through lifecycle-state provisioning, but this is materially different from assigning specific permissions based on roles. Consequently, the proposed statement confuses identity population and lifecycle configuration with role-based access assignment.

Study Guide Reference: Identity and Lifecycle Management — Identity Profiles, Authoritative Sources, Identity Attribute Mapping and Lifecycle Configuration.

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

The proposed description is correct. Identity Security Cloud Search supports field-specific queries that allow administrators to search identity attributes directly. The expression attributes.location restricts the search to the location identity attribute rather than searching across all indexed identity fields.

The quotation marks around "sao paulo" indicate that the search engine should evaluate the value as a phrase. This means the query is intended to identify identities whose location attribute contains the phrase Sao Paulo rather than independently searching for the words sao and paulo in unrelated positions.

Field qualification is important when administrators need precise search results. Without the attributes.location prefix, a general search could potentially return matches from other searchable attributes or indexed properties. Combining the specific identity attribute with a quoted phrase produces a more targeted search result.

Therefore, the query accurately retrieves identities whose location information matches the Sao Paulo phrase.

Study Guide Reference: Platform — Identity Security Cloud Search, Building Search Queries, Identity Attribute Searches.

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

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.

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

The statement is correct. During an Identity Security Cloud certification, the reviewer evaluates each required access item and records the appropriate decision—for example, approving or revoking access. The certification cannot be properly completed while required review items remain undecided.

SailPoint's current user documentation states that after the reviewer has reviewed each item , the reviewer is taken to the sign-off page to complete the certification. The reviewer then selects Finish to submit the decisions and move the certification into the completed state. SailPoint's certification overview likewise describes the sequence as reviewing assigned access, approving or revoking items, and then signing off on those decisions.

Sign-off has governance significance beyond the user-interface transition. Revocation decisions that have not been signed off are not treated as finalized remediation instructions. SailPoint explicitly warns that unsigned revoke decisions are not applied and can be treated as undecided when a campaign is administratively completed.

Therefore, completion of the required decisions is the prerequisite that brings the reviewer to the certification sign-off stage.

Study Guide Reference: Supporting Governance — Access Certifications, Review Decisions, Certification Sign-Off and Campaign Completion.

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

The statement accurately describes the function of an Identity Provider in a federated authentication architecture. An IdP authenticates users and provides trusted identity or authentication information to a Service Provider. This enables the Service Provider to rely on an established trust relationship instead of independently validating the user's primary credentials.

In a SAML-based implementation, the Identity Provider authenticates the user and generates a signed SAML assertion. The assertion contains information that allows the Service Provider to determine that the user's authentication has been successfully completed. Depending on configuration, additional identity attributes can also be included.

Identity Security Cloud can operate as a SAML Service Provider and rely on an organization's external Identity Provider for user authentication. This allows enterprises to centralize authentication and integrate SailPoint access with existing single sign-on infrastructure.

The critical concepts are trust, centralized authentication, and secure transfer of authentication assertions between the IdP and Service Provider. The proposed statement correctly identifies each of these fundamental IdP responsibilities.

Study Guide Reference: Access Management — Federated Identity, Identity Providers, SAML Authentication, Service Provider Integration.

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

This is a valid and specifically documented cause of missing entitlements during flat-file aggregation. When multiple rows represent different entitlements belonging to the same account, Identity Security Cloud expects the rows for that account to be grouped together according to the account identifier.

SailPoint's aggregation troubleshooting documentation explicitly addresses the condition in which only one or an incomplete set of entitlements is aggregated for accounts from a delimited file. The documented remediation is to ensure that the file is sorted by account ID . SailPoint's Generic Flat File prerequisites similarly state that all accounts and entitlements must be sorted by the account name so that all entitlement rows for an account appear together.

This requirement matters because the aggregation parser must correctly recognize consecutive records as belonging to the same logical account while assembling its multi-valued entitlement attributes. If the same account appears in separated regions of the file, the complete entitlement set may not be assembled as expected.

Therefore, sorting and grouping all rows for each account together is a fundamental preprocessing requirement when supplying multi-valued entitlement information through flat files.

Study Guide Reference: Sources — Flat File Aggregation, Delimited Files, Multi-Valued Entitlements and Aggregation Troubleshooting.

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

The statement does not describe the purpose of a SailPoint Virtual Appliance. A VA is primarily a secure connectivity and connector-execution component . It allows an Identity Security Cloud tenant to communicate with enterprise sources and applications that require connectivity from within the customer's controlled environment.

SailPoint describes a VA as a Linux-based virtual machine that connects the tenant to applications and sources by using SailPoint APIs, connectors, and integrations. The VA continuously makes outbound calls to the SailPoint cloud for operations such as polling its cluster queue, performing data aggregation, executing provisioning operations, and receiving software updates.

The VA architecture does reduce the need to expose internal systems directly to inbound cloud connections, but that is fundamentally different from eliminating databases that contain PII. Enterprise applications, identity repositories, HR systems, directories, and other governed sources may continue to store personally identifiable information according to their own business and regulatory requirements.

Therefore, PII database elimination is neither the VA's purpose nor a consequence of deploying one.

Study Guide Reference: Virtual Appliances — VA Architecture, Secure Source Connectivity, Outbound Communication and Connector Execution.

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

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.

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