Most Recent SailPoint IdentityNow-Engineer Exam Questions & Answers

A non-production tenant is commonly used for demonstrating functionality, as well as for testing and development purposes. In a SailPoint IdentityNow environment, non-production tenants provide a sandbox environment where customers and engineers can safely explore the system, simulate use cases, and demonstrate functionality without impacting the live production environment.

Key Reference from SailPoint Documentation:

Non-Production Tenant Usage: SailPoint recommends non-production tenants for testing, demonstrating functionality, and conducting proofs of concept, ensuring that the production environment remains unaffected.

Turning off the Virtual Appliance's (VA) internal firewall is not recommended as a standard troubleshooting step in SailPoint IdentityNow. The VA's firewall is crucial for maintaining the security of the environment, and disabling it can expose the system to unnecessary risks. Instead, an IdentityNow engineer should verify the VA's network configuration and ensure that the required ports are open for communication between the VA and the source.

Key Reference from SailPoint Documentation:

VA Configuration and Network Troubleshooting: Troubleshooting connection issues typically involves checking network connectivity and firewall rules, not turning off the internal firewall.

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, an SoD policy can define mitigating controls. Mitigating controls are measures put in place to reduce the risk of having conflicting duties. For example, if it's not possible to completely segregate duties due to resource constraints or other business factors, mitigating controls such as enhanced auditing, periodic reviews, or dual approvals can be defined to manage the risk. SailPoint IdentityNow allows for the creation of SoD policies that include such mitigating controls to ensure compliance with security and governance requirements.

Key Reference from SailPoint Documentation:

Mitigating Controls in SoD Policies: SailPoint supports the definition of mitigating controls within SoD policies to manage and reduce risks when full separation of duties cannot be achieved.

SailPoint IdentityNow APIs are not authenticated using client certificates. Instead, they use OAuth 2.0 for secure authentication and authorization. API consumers are required to obtain an access token, which is used to authenticate requests made to the IdentityNow API. The token is typically obtained by sending client credentials (client ID and client secret) to the IdentityNow authorization server, which grants the token for API access.

Key Reference from SailPoint Documentation:

API Authentication: SailPoint IdentityNow uses OAuth 2.0 for API authentication rather than client certificates. Detailed steps on how to implement OAuth-based authentication are available in SailPoint's API documentation.