Identity-Security-Administrator Exam Dumps - SailPoint Professional Questions and Answers

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.

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

The statement correctly describes the communication model used by SailPoint Virtual Appliances. The critical architectural principle is that communication between a customer-hosted VA and Identity Security Cloud is initiated outbound from the VA . SailPoint does not establish unsolicited inbound connections from its cloud environment directly into the customer's VA.

SailPoint specifically documents that each VA makes continuous outbound-only calls to the cloud environment and polls the cluster queue for requested actions , including aggregation and provisioning work. The appliance retrieves the work assigned to its cluster, executes the appropriate connector operation against the customer source, and communicates the resulting information back to Identity Security Cloud.

This polling model is significant from a network-security perspective because customers do not need to create inbound firewall rules allowing Identity Security Cloud to initiate sessions into their internal environment. Instead, the VA requires appropriate outbound connectivity to SailPoint's required endpoints.

Therefore, describing VAs as initiating communication to their cluster queue accurately reflects the supported VA architecture.

Study Guide Reference: Virtual Appliances — VA Cluster Architecture, Cluster Queue Polling, Outbound-Only Communication and Connector Operations.

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

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.

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

Yes. This is a classic Separation of Duties scenario. The individual requesting a significant system configuration change should not also possess the authority to independently approve that same change. Combining requester and approver responsibilities eliminates an important independent-control checkpoint and allows one person to initiate and authorize a potentially high-impact administrative operation.

SailPoint's official SoD guidance specifically uses major system configuration changes as an example: significant configuration changes should be approved by someone other than the person requesting the change. SoD policies are designed to identify and govern combinations of access that would enable such conflicting responsibilities.

From a governance perspective, the requester initiates the business or technical need, while an independent reviewer determines whether the requested change is appropriate, authorized, and sufficiently controlled. Separating these functions reduces fraud, accidental misconfiguration, privilege abuse, and unauthorized system modification. Where conflicting access already exists, Identity Security Cloud can identify the associated SoD violation for investigation and remediation.

Therefore, allowing the requester to approve their own major system change represents exactly the type of control conflict that SoD is intended to prevent.

Study Guide Reference: Supporting Governance — Separation of Duties, Requester/Approver Conflicts, Internal Controls and SoD Policy Enforcement.

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

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 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 statement correctly describes the standard escalation behavior represented by the access-request escalation model. Identity Security Cloud can automatically escalate an approval when the assigned reviewer fails to act within the configured timeframe. This prevents an access request from remaining indefinitely with an unavailable or unresponsive approver.

Under the standard escalation pattern, the first and second escalations can route the request to successive manager levels of the assigned reviewer. The third escalation routes the approval to the configured fallback approver. Administrators control escalation timing, frequency, escalation reviewers, and fallback behavior through approval settings. This mechanism operates alongside reminder notifications and request timeout controls.

The fallback approver is particularly important because it provides a final governance path when ordinary escalation cannot resolve the request. SailPoint's current documentation explicitly describes the first two manager escalations followed by a third escalation to the fallback approver when custom approval settings are not configured.

Study Guide Reference: Access Management — Access Requests, Global Reminder and Escalation Policy, Approval Escalation and Fallback Approvers.

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

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.

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

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.

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

The statement is not accurate as written. Configuration Hub restoration does use a draft , but an administrator cannot simply add arbitrary missing configuration objects to an existing draft through the normal draft-editing process.

The supported restoration workflow is to select the required backup, create a deployment draft, review the differences between the backup and the live tenant, optionally edit supported object details or remove objects that should not be deployed, and then deploy the draft. Configuration Hub automatically evaluates dependencies and identifies reference issues while preparing the draft.

Current SailPoint documentation specifically states that administrators can edit JSON definitions of existing draft objects or remove objects/object types. If an administrator removes an object from the draft and later discovers that this was a mistake, the supported action is to create a new draft from the backup and start again . There is no general "add missing object" operation to repopulate an existing draft.

Therefore, reviewing the draft is correct, but the proposed mechanism of editing and adding missing objects makes the overall statement invalid.

Study Guide Reference: Platform — Configuration Hub, Backups, Configuration Drafts and Restoring Tenant Configuration.

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