IdentityNow-Engineer SailPoint Certified IdentityNow Engineer Free Practice Exam Questions (2025 Updated)

Reviewing the Identities without Managers report is not directly related to troubleshooting incomplete identities on an authoritative source. The "Identities without Managers" report is specifically useful for identifying identities that are missing a manager assignment, which might be relevant for access reviews or other management-related tasks. However, when troubleshooting incomplete identities, the focus is typically on missing attributes or data mappings, not the manager attribute specifically.

Therefore, this report is not the most appropriate action for this particular issue.

References:

SailPoint IdentityNow Reporting and Identity Data Review Documentation.

SailPoint IdentityNow Troubleshooting Incomplete Identities.

The virtual appliance (VA) private key is not stored in both the IdentityNow tenant and the VA. The VA private key, which is critical for secure communications, is stored only on the Virtual Appliance (VA) itself. It is used to authenticate and encrypt communications between the VA and the IdentityNow tenant. Storing such sensitive information in the IdentityNow tenant would violate best practices for key management and security.

Instead, the IdentityNow tenant only holds the public key or a reference to the key to facilitate secure exchanges with the VA. The private key remains secured locally within the VA, protecting it from potential security vulnerabilities associated with external storage.

References:

SailPoint IdentityNow Virtual Appliance Architecture Guide.

SailPoint IdentityNow Security and Encryption Documentation.

Clearing the authentication checkbox for a source in SailPoint IdentityNow is not a typical troubleshooting step for a timeout error. This option is related to whether or not authentication is required for the source connection. A timeout error typically points to a network issue (e.g., port, firewall, or network latency), not authentication problems. The engineer should instead focus on network-related configurations such as checking port access or firewall settings.

Key Reference from SailPoint Documentation:

Source Connectivity Troubleshooting: Timeout errors are generally caused by network issues rather than authentication problems, so adjusting authentication settings is not recommended for resolving such errors.

No, reconfiguration within IdentityNow is not required to connect to the disaster recovery (DR) VAs, which makes this scenario not a disadvantage. When properly configured, all VAs (including DR VAs) in a cluster are part of the same logical unit, meaning that failover to the DR VAs should happen seamlessly without manual intervention or significant reconfiguration. IdentityNow handles the failover automatically, directing traffic to the DR VAs when primary VAs become unavailable.

While there might be some overhead in a manual failover scenario for certain configurations, the use of a single VA cluster helps mitigate this by ensuring the system can failover without needing complex reconfigurations for every source.

References:

SailPoint IdentityNow Virtual Appliance Failover and Disaster Recovery Configuration.

SailPoint IdentityNow High Availability Architecture Guide.

Yes, SailPoint follows a continuous delivery and rolling update model for IdentityNow, which allows for the rapid development and deployment of new features, security updates, and bug fixes. Updates are rolled out automatically to tenants as part of this process, ensuring that customers always have the latest version of the platform. This continuous approach minimizes downtime and allows SailPoint to address security vulnerabilities and improve functionality in a timely manner.

References:

SailPoint IdentityNow Continuous Delivery and Deployment Documentation.

SailPoint IdentityNow Release Management and Update Policy Guide.

IQService does not run on the Virtual Appliance (VA). It is a separate service that must be installed on a Windows Server within the environment that has access to the target system, particularly for Active Directory and other Windows-based systems. IQService acts as a proxy between the IdentityNow tenant and these target systems, allowing operations such as password management and account provisioning to be executed on systems that do not support native connectors on the VA. It communicates with the VA but is not hosted on it.

References:

SailPoint IdentityNow IQService Installation Guide.

SailPoint IdentityNow Target Connector Architecture.

Yes, reviewing the /home/sailpoint/log/relay.log file can help diagnose issues related to the secure tunnel in SailPoint IdentityNow. The relay.log file captures information about the communication between the IdentityNow Virtual Appliance (VA) and the SailPoint cloud. This secure tunnel is responsible for ensuring encrypted communication, and any issues with establishing or maintaining the connection can often be found in this log.

Key Reference from SailPoint Documentation:

Relay Log for Troubleshooting: The relay.log is the primary log file to review for communication issues between the Virtual Appliance and SailPoint IdentityNow cloud, including secure tunnel failures.

Yes, custom connector configurations in SailPoint IdentityNow can have account correlation settings defined. Account correlation is used to link accounts from different sources to the correct identity in IdentityNow. When configuring a custom connector, it is possible to define how accounts from the connected system are correlated to existing identities based on attributes like usernames or other unique identifiers.

Key Reference from SailPoint Documentation:

Custom Connector Configuration: SailPoint allows for the definition of account correlation settings in custom connectors to ensure proper linking of external accounts to internal identities.

In SailPoint IdentityNow, email notifications related to source events (such as successful connections or other operational states) are not automatically sent immediately after a successful source connection. The system focuses on error conditions or alerts based on source status changes or failures. While successful source operations may be logged, notifications are not configured by default to trigger upon every successful action.

Key Reference from SailPoint Documentation:

Source Event Notifications: SailPoint's notifications for source-related events primarily focus on error handling rather than successful operations, which are generally logged for reference but do not trigger immediate notifications.

Not all customers are restricted to a maximum of one non-production tenant. The number of non-production tenants that a customer can have depends on their specific licensing agreement with SailPoint. Some customers may be allowed multiple non-production tenants for various purposes like testing, development, and staging.

Key Reference from SailPoint Documentation:

Tenant Provisioning Guidelines: SailPoint provides flexibility in the number of non-production tenants based on customer agreements, allowing for multiple environments when needed.

Yes, this is the recommended way to test lifecycle state transitions in IdentityNow. To validate how lifecycle states function, administrators can manually set up and enable lifecycle states for testing purposes. By selecting a test identity that is not already in the target state, manually transitioning that identity to the target state using the admin user interface provides a direct and controlled way to observe the transition. The results can be verified in the identity's activity page, where changes in the lifecycle state will be logged, helping to ensure that the lifecycle state functions as expected.

References:

SailPoint IdentityNow Lifecycle Manager Documentation.

SailPoint IdentityNow Lifecycle State Configuration Guide.