SailPoint SailPoint Certified IdentityNow Engineer IdentityNow-Engineer Exam Dumps: Updated Questions & Answers (October 2025)

The Web Services connector in SailPoint IdentityNow does not support SAML authentication. SAML is primarily used for Single Sign-On (SSO) authentication for web applications, whereas the Web Services connector in IdentityNow typically supports Basic Authentication, OAuth, or custom header-based authentication for API-based integrations. SAML authentication is generally used for federated identity management rather than for API-based interactions.

References:

SailPoint IdentityNow Web Services Connector Configuration Guide.

SailPoint IdentityNow Authentication Methods for Connectors.

The use case describes a user logging into IdentityNow via an external identity provider’s login, where information is exchanged via federation. This correctly aligns with the concept of passthrough authentication.

Passthrough authentication often uses protocols like SAML (Security Assertion Markup Language) or OAuth for federation. In this case, the identity provider (IdP) handles the authentication and then passes the necessary authentication tokens or assertions back to SailPoint IdentityNow, granting the user access without directly requiring their password to be stored or authenticated by IdentityNow. This is a typical use case of federation and passthrough authentication.

References:

SailPoint IdentityNow Documentation on SAML and OAuth Federation.

SailPoint IdentityNow Federation and Passthrough Authentication Configuration Guides.

To implement an identity model for a given authoritative source, the correct sequence of steps is essential. Based on the image provided, the five key steps in the correct order are as follows:

Create a source, and aggregate the data.

The first step involves setting up the source system and aggregating its data into SailPoint IdentityNow.

Create an identity profile and associate it to the source.

After creating the source, an identity profile needs to be created, which will define the identity schema and associate it with the source.

Define identity mappings, including adding transforms.

This step involves configuring the mappings between source attributes and IdentityNow attributes, possibly adding transformation logic.

Preview the identity mappings with aggregated data.

This step allows you to check how the mappings are applied to actual aggregated data, ensuring correctness.

Finalize a source create profile.

Once all configurations are validated, the source profile is finalized, making it ready for production use.

These steps form the required workflow for successfully setting up and implementing an identity model for an authoritative source.

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.

Live access reviews, which involve reviewing and certifying user access to various resources, should be performed in a production environment. This is because access reviews are directly related to active identities and entitlements in a live system, ensuring compliance and security in real-time operations.

Key Reference from SailPoint Documentation:

Access Reviews in Production: SailPoint recommends conducting live access reviews in production environments to ensure that the access being reviewed reflects the actual, current access of users in the system.

Yes, SailPoint IdentityNow APIs can be accessed and utilized by external clients such as cURL or Postman. These tools are commonly used for testing and interacting with RESTful APIs, and they work seamlessly with IdentityNow's API framework. For example, developers can use Postman or cURL to make API calls for various actions like managing identities, querying data, and triggering provisioning events.

Key Reference from SailPoint Documentation:

API Integration with Tools: SailPoint IdentityNow supports third-party tools like cURL and Postman for API interaction, as these clients can handle HTTP requests, which is how IdentityNow's APIs communicate.

No, an SoD (Separation of Duties) policy does not require a control matrix to be defined. While a control matrix can be a useful tool for organizations to visualize and enforce SoD policies by mapping roles to potential conflicting access rights, it is not a mandatory component of an SoD policy. An SoD policy primarily focuses on preventing conflicts of interest by ensuring that no individual has access to perform conflicting tasks within a business process (e.g., approving and processing payments). The control matrix is a recommended method for managing SoD but not a requirement.

Key Reference from SailPoint Documentation:

SoD Policy Overview: SailPoint recommends structuring SoD policies to focus on preventing conflicting access but does not mandate the use of a control matrix, which is an optional best practice for visualizing these controls.

No, microservice architecture does not inherently make identities take up less space in the cloud. Microservices are primarily focused on improving scalability, resilience, and modularity by breaking down an application into smaller, independent services. While this architecture may optimize resource usage and improve performance, it does not specifically reduce the storage space required for identities or data. Data storage concerns are more related to optimization techniques like data deduplication or compression rather than the architecture style itself.

References:

SailPoint IdentityNow Microservices Architecture Guide.

SailPoint IdentityNow Cloud Storage and Data Management Documentation.

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.

Yes, an access profile can be acknowledged during certifications. During access certification campaigns, reviewers can review access profiles as part of the items that need to be certified. They can either approve or revoke access to the access profiles, just like they would with individual entitlements. This ensures that users' access to these bundled entitlements is regularly reviewed and compliant with organizational policies.

References:

SailPoint IdentityNow Certification Campaigns Guide.

SailPoint IdentityNow Access Profile Certification Documentation.