SailPoint Identity-Security-Administrator Exam Dumps

According to objectives 3.3 (Know identity attribute mappings and how they function within an identity profile) and 3.4 (Recognize which options are available for configuring mappings in an identity profile), identity profiles support sophisticated mapping configurations including priority-based source resolution, fallback logic, and conditional attribute transformations.

Options 1, 2, and 4 are all correct approaches—they describe using identity profile mapping features to implement priority-based source resolution with fallback mechanisms and conditional logic for different entity types. These capabilities allow a single identity profile to handle complex multi-source scenarios with conditional logic and attribute transformation.

Option 3 is incorrect because creating three separate identity profiles is not necessary and violates the principle of using a single authoritative identity profile. The identity profile architecture is designed to handle multi-source complexity within a single profile configuration.

Option 5 is incorrect because while connector transformations play a role, the proper place to configure these business rules is at the identity profile level where attribute mappings are defined. Identity profiles are specifically designed for this aggregation and prioritization logic across multiple sources.

The statement is incorrect. A SaaS-based application does not inherently require a 'cloud-based VA.' Identity Security Cloud supports SaaS connectors that can connect supported cloud applications directly without requiring the customer to deploy a Virtual Appliance cluster.

SailPoint explicitly states that organizations can use a SaaS connector when they want to upload data to Identity Security Cloud from a source without a Virtual Appliance cluster. In contrast, VA-based connectors are used when direct connector communication must occur from the customer's controlled environment.

Furthermore, a SailPoint VA is not normally a SailPoint-hosted cloud appliance. SailPoint provides the virtual appliance image, but the VA is deployed on infrastructure procured or controlled by the customer. SailPoint manages and updates the appliance software while the customer provides the hosting environment and network connectivity.

Some cloud-hosted applications can still use VA-based connectors depending on network topology and connector design, but being a SaaS application alone does not impose a VA requirement.

Study Guide Reference: Virtual Appliances --- VA-Based versus SaaS Connectors, VA Deployment Architecture and Cloud Application Connectivity.

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

When troubleshooting provisioning errors related to a specific virtual appliance, the correct approach is to first assess the appliance's health and gather diagnostic information through logging. According to objective 2.2 (Monitor the health of virtual appliances) and 2.3 (Perform basic troubleshooting), you should check the VA health dashboard and enable detailed connector logging to understand what is failing.

While increasing timeouts (option 1) might eventually help, it treats the symptom rather than identifying the root cause. Immediately failing over (option 3) is premature without understanding the issue. Restarting (option 4) is a last resort and should only occur after investigation confirms it will help. The best practice is to monitor health metrics and enable enhanced logging to diagnose the provisioning failures, which aligns with objectives 2.2, 2.3, and 4.4 (enable logging and different logging levels for specific connectors).

This is a valid network-isolation troubleshooting step. Virtual Appliances depend on continuous outbound network connectivity to Identity Security Cloud. A VPN, firewall, proxy, routing policy, or network-security device positioned in the communication path can prevent the VA from reaching required SailPoint endpoints even when the VA itself is otherwise healthy.

Testing connectivity with and without the VPN helps determine whether the VPN path, its routing tables, security policies, DNS handling, or tunnel configuration is responsible for the failure. SailPoint requires VA outbound connectivity, including HTTPS communication over TCP port 443, and documents network connectivity as a primary dependency for proper VA operation. Network connectivity errors should therefore be investigated by validating the path between the appliance and required endpoints.

This does not mean permanently bypassing required enterprise security controls. The objective is diagnostic isolation: establish whether connectivity succeeds when the suspected network component is removed from the path, then correct the underlying VPN or routing configuration.

Study Guide Reference: Virtual Appliances --- VA Network Troubleshooting, Outbound Connectivity, VPN and Firewall Configuration.

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

The statement is explicitly incorrect. Identity Security Cloud allows users to hold multiple User Levels in many circumstances, and permissions from compatible User Levels are cumulative. However, SailPoint defines several combinations that cannot be assigned simultaneously because their delegated administrative scopes conflict.

One of the specifically prohibited combinations is Role Admin and Source Sub-Admin. SailPoint's User Level documentation lists this pair among the User Levels that cannot coexist on the same user. Other prohibited combinations include Role Sub-Admin with Source Admin, Role Sub-Admin with Role Admin, and Source Sub-Admin with Source Admin.

The distinction is important. A Role Admin has broad role-management privileges, whereas a Source Sub-Admin receives scoped administrative capabilities based on Governance Group associations with particular sources. Combining certain global and scoped administrative models could create inconsistent authorization behavior, so SailPoint prevents those assignments.

Administrators should therefore consult the User Level compatibility matrix before granting multiple elevated permissions rather than assuming that every User Level can be stacked.

Study Guide Reference: Platform --- User Level Permissions, User Level Compatibility, Role Admin and Source Sub-Admin.

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