Identity-Security-Administrator VCE Exam Download

This is not the standard Identity Security Cloud method for configuring role assignment criteria. Role membership can be automatically determined using defined identity or account-based criteria, or administrators can explicitly specify identities through an Identity List depending on the role configuration.

The Identity List mechanism is designed to identify users who should receive the role rather than create a separate universal exclusion list containing identities who must never receive it. When automatic assignment criteria are configured, identities satisfying those criteria can become role members based on the associated identity attributes, account attributes, or other supported conditions.

If a particular identity must not receive a role, administrators should design the role-assignment criteria so that the identity does not satisfy the required conditions or use another appropriate assignment strategy. Introducing an unsupported exclusion mechanism could create incorrect expectations about how role membership is calculated.

Roles are intended to package business-relevant access and automatically assign that access to identities meeting defined organizational criteria.

Study Guide Reference: Access Management — Roles, Role Assignment Criteria, Standard Criteria, Identity Lists.

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

This proposed API call is not valid for retrieving Virtual Appliance connector logs. The identifier shown in the log entry is a managed-cluster ID , yet the proposed URL incorrectly places that ID under the /v3/sources/ API resource. Managed clusters and sources are separate Identity Security Cloud objects and use different API endpoints.

SailPoint's documented Managed Clusters API provides operations for obtaining cluster details and for retrieving or modifying the cluster's log configuration , such as GET /managed-clusters/{id}/log-config and PUT /managed-clusters/{id}/log-config. It does not document a GET /v3/sources/{managedClusterId}/logs endpoint for exporting VA connector log files.

For connector troubleshooting, enhanced logging can be enabled against the appropriate managed cluster, the problematic operation reproduced, and the resulting VA/connector logs collected through the supported VA troubleshooting process. The administrator must also ensure that the correct cluster associated with the affected source is being investigated.

Therefore, the proposed endpoint confuses a managed cluster with a source and does not represent a supported log-export API.

Study Guide Reference: Virtual Appliances — Managed Clusters, Connector Logging, VA Troubleshooting and SailPoint REST APIs.

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

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.

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

This is a valid description of Separation of Duties (SoD) as an identity-governance control. SoD policies define combinations of access that should not be held by the same identity because combining those privileges could enable fraud, unauthorized transactions, or circumvention of internal controls. A detective implementation analyzes existing access and identifies identities that already violate a defined policy, allowing administrators to investigate, mitigate, revoke access, or document an approved exception.

Preventive policy evaluation applies the same governance principle before problematic access is granted. During an access-request or provisioning process, the proposed access can be evaluated against policy rules so that a potential conflict is identified before the access change is completed. SailPoint documents SoD policies as conflicting-access definitions and also documents preventive policy evaluation in its governance model. These controls provide measurable evidence that an organization is actively enforcing access-risk policies rather than merely documenting them.

Study Guide Reference: Supporting Governance — Separation of Duties, Policy Rules, Detective and Preventive Controls.

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