Pass the SailPoint Identity Security Engineer IdentityNow-Engineer Questions and answers with ValidTests

Yes, IdentityNow releases are controlled and coordinated by SailPoint. SailPoint manages the software release cycle for IdentityNow, which follows a SaaS (Software-as-a-Service) delivery model. This means updates, new features, patches, and other improvements are automatically rolled out by SailPoint without requiring manual intervention by customers. The release schedule is typically structured around planned maintenance windows and communicated to customers in advance. SailPoint ensures these updates are deployed securely and efficiently to all tenants.

References:

SailPoint IdentityNow SaaS Release Management Guide.

SailPoint IdentityNow Product Updates and Release Notes.

Yes, defining an account schema is an essential step when implementing a JDBC connector. The schema defines the structure of the identity data being pulled from the database, including the attributes that will be mapped to identity profiles in IdentityNow. The schema can be defined either by using the "Discover Schema" option, which automatically identifies available attributes, or by manually configuring the schema attributes if specific custom mappings are required.

References:

SailPoint IdentityNow JDBC Connector Schema Configuration Guide.

SailPoint IdentityNow Source Schema Discovery Documentation.

Yes, the search syntax @accounts( source.name:"AD" AND state:"disabled" ) is correct for finding identities with disabled AD accounts. In this case, the query filters accounts based on the state being "disabled," which is valid and effective for identifying disabled accounts.

Key Reference from SailPoint Documentation:

Search by Account State: Using state:"disabled" is an accurate way to search for disabled accounts in SailPoint IdentityNow.

Yes, SailPoint IdentityNow sends a notification if a source has been in an error state for a sustained period, typically after fifteen minutes. This type of alert helps administrators to be aware of prolonged connection or operational issues with a source, so they can take corrective action promptly. The notification system is designed to escalate issues that may impact synchronization, provisioning, or access-related processes.

Key Reference from SailPoint Documentation:

Error State Notifications: SailPoint IdentityNow sends alerts for sources in error states, including when the error persists for a predefined period such as 15 minutes, helping administrators to respond to ongoing issues.

Yes, the fact that the disaster recovery (DR) VAs are not being utilized until a disaster recovery event occurs is a disadvantage. In this strategy, the DR VAs remain idle, leading to underutilization of resources. These VAs could otherwise handle workloads during normal operations to improve efficiency, distribute load, or reduce latency, especially if they are geographically closer to specific target systems. Relying on DR VAs only during failover scenarios limits their potential to optimize performance and balance loads in day-to-day operations.

References:

SailPoint IdentityNow Virtual Appliance Clustering and Disaster Recovery Documentation.

SailPoint IdentityNow High Availability and DR Strategies.

Yes, using a query select statement with a clause to match the incoming account to an existing account is a key configuration for the Single Account SQL Query in a JDBC connector. This query is used to fetch specific account details from the database and must be written in such a way that it uniquely identifies each account, ensuring accurate correlation between the data in the source and the identities in IdentityNow. Properly configuring this SQL query ensures the right accounts are matched and managed.

References:

SailPoint IdentityNow JDBC Connector Single Account Query Configuration Guide.

SailPoint IdentityNow SQL Query Best Practices Documentation.

No, the provided steps are incorrect. Specifically:

Step 1: Before importing the Virtual Appliance (VA) image, you need to first download or procure the VA image from SailPoint. Only then can you proceed with importing the image into the virtualization platform.

Step 6: After changing the password for the SailPoint user, the next logical step is to configure the networking settings (if needed) to ensure the VA can communicate with the IdentityNow tenant.

Step 12: The final step should not be to download the VA image again. Instead, after configuring the config.yaml, you should test the connection to ensure the VA can properly communicate with IdentityNow.

Corrected Steps:

Download / procure the VA image.

Configure networking configurations (as needed).

Click Test Connection on the VA configuration.

References:

SailPoint IdentityNow Virtual Appliance Setup Guide.

SailPoint IdentityNow Virtual Appliance Networking Configuration.

The default non-production tenant does not have the same full performance scalability as a production tenant. Non-production environments are typically configured with reduced resources since they are intended for testing, development, or demonstration rather than handling large-scale, live workloads.

Key Reference from SailPoint Documentation:

Performance Differences Between Tenants: SailPoint non-production tenants are generally scaled down compared to production environments to reflect their testing and demonstration purposes, not for high-performance or large-scale operations.

Yes, a non-production tenant is typically used for testing new features before they are deployed to the production environment. This allows administrators to validate functionality, identify potential issues, and ensure the features work as expected without affecting the live users and operations.

Key Reference from SailPoint Documentation:

Testing New Features in Non-Production: SailPoint advises using non-production environments for testing new functionalities to safeguard production environments from untested changes.

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.