Get SailPoint IdentityNow-Engineer Exam Practice Questions - Real and Updated

Answer : A

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.

SailPoint IdentityNow SaaS Release Management Guide.

SailPoint IdentityNow Product Updates and Release Notes.

Answer : B

The provided use case incorrectly describes the provisioning process on a source that has provisioning disabled. If provisioning is disabled for a source, automated provisioning via the Virtual Appliance and connectors is not possible. The Virtual Appliance cannot retry or carry out the provisioning in this case, as the system explicitly prevents automated provisioning operations on sources marked as non-provisionable.

When a source has provisioning disabled, the system only supports manual provisioning, where a task is opened in IdentityNow for a person to manually execute the provisioning steps. The Virtual Appliance does not handle provisioning for disabled sources, so the described scenario where it retries the request and carries out provisioning is inaccurate.

SailPoint IdentityNow Provisioning Configuration Guide.

SailPoint IdentityNow Virtual Appliance and Connector Operations Documentation.

Answer : B

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.

Answer : B

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.

Answer : A

In this use case, provisioning is initiated, but the source has provisioning disabled, meaning automated provisioning cannot proceed. The process described is accurate: when provisioning is assigned to a source where provisioning is disabled, IdentityNow does not execute the provisioning through its automated system. Instead, a manual task is generated for a human to complete the provisioning process. This manual intervention ensures that the necessary access changes can still occur, albeit through human oversight rather than an automated connector.

This scenario aligns with how IdentityNow handles sources that are flagged as non-provisionable. The provisioning logic is still calculated within the system, but actual implementation requires manual steps when the source is configured in this way.

SailPoint IdentityNow Provisioning Architecture.

SailPoint IdentityNow Manual Provisioning Workflow Documentation.