Most Recent SailPoint IdentityNow-Engineer Exam Questions & Answers

In SailPoint IdentityNow, provisioning is the process of granting or revoking access to systems and applications based on access requests or changes in user identity attributes. The scenario describes John Doe requesting access to the 'Sales' profile in Salesforce, which is approved by his manager.

However, simply approving an access request does not automatically trigger provisioning unless specific conditions are met:

Provisioning Policy: For the access to be provisioned, SailPoint IdentityNow requires a provisioning policy that defines the action to be taken after the approval process. This policy is often configured to specify whether access should be granted or denied after approval. If no provisioning policy is linked to the requested access, no action will be triggered.

Source Configuration: The Salesforce source (connector) in SailPoint IdentityNow must also be properly configured to handle provisioning tasks. Without proper configuration of the Salesforce source, no provisioning action will be sent even if the request is approved.

Manual Provisioning Workflow: In some cases, IdentityNow might be configured to require manual intervention after approval (e.g., triggering a manual provisioning workflow or an additional step) to enforce the provisioning action. If this configuration is missing, the approved request will not lead to automatic provisioning.

Since the scenario does not explicitly state that a provisioning policy or source configuration exists to handle the access request, the correct conclusion is that no provisioning would be sent out.

Key Reference from SailPoint Documentation:

Provisioning Concepts in IdentityNow: Documentation emphasizes that provisioning is triggered by defined workflows and provisioning policies that link the request to the connector source. Without these, the approval does not lead to actual provisioning.

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, checking that the port values configured on the source in SailPoint IdentityNow are correct and accessible is an essential troubleshooting step. A timeout error can occur if the virtual appliance (VA) cannot reach the source due to incorrect port configuration or network issues blocking communication. Verifying the correct port numbers and ensuring that the necessary ports are open on both the VA and the source's firewall is critical.

Key Reference from SailPoint Documentation:

Port Configuration for Source Connectivity: Ensuring that the proper port values are configured and accessible is one of the primary troubleshooting steps when facing timeout errors in IdentityNow.

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.

SailPoint IdentityNow Virtual Appliance Setup Guide.

SailPoint IdentityNow Virtual Appliance Networking Configuration.

The /home/sailpoint/config.yaml file is not used to configure the Virtual Appliance (VA) to use a static IP address. This file is generally used for other configuration purposes related to the SailPoint IdentityNow application settings, not for network configurations like setting static IP addresses. Network configurations are handled at the system or network service level within the VA's Linux environment.

SailPoint IdentityNow Virtual Appliance Configuration Guide.

SailPoint IdentityNow Networking Configuration Documentation.