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

Yes, custom connectors are imported into IdentityNow via the UI. After development and testing, the custom connector configuration is uploaded to the platform through the IdentityNow interface. This allows administrators to define how the connector interacts with external systems and specify settings like account aggregation, correlation, and provisioning.

Key Reference from SailPoint Documentation:

Connector Import Process: Custom connectors are uploaded into IdentityNow through the UI, where they can then be configured and used to connect to external systems.

No, the Generic Cloud Connector is not the most suitable connector type for this use case. The system described is a modern, cloud-based web application that exposes a SCIM 2.0 interface with OAuth 2.0 client credentials for authentication. The Generic Cloud Connector is typically used for systems that do not have specialized connectors but can integrate via general APIs or REST endpoints. Since the application supports SCIM 2.0, which is a standardized protocol for managing identities, the SCIM 2.0 Connector would be the more appropriate choice, as it is specifically designed for this type of integration.

References:

SailPoint IdentityNow SCIM 2.0 Connector Guide.

SailPoint IdentityNow Connector Overview Documentation.

No, IdentityNow administrators do not have the option to choose how often updates to their tenant occur. As part of SailPoint’s multi-tenant SaaS platform, updates are managed and controlled by SailPoint and are pushed out automatically to all tenants. Administrators do not have the ability to schedule or defer updates, as this ensures all customers are running on the latest and most secure version of the software.

References:

SailPoint IdentityNow SaaS Release and Update Policy.

SailPoint IdentityNow Multi-Tenant Environment Overview.

Yes, a certification item can be reassigned multiple times during a certification campaign. If a reviewer is unable to certify an item or needs another individual to review the access, they can reassign the certification to a different reviewer. This reassignment functionality allows flexibility in handling access certifications and ensuring the right person evaluates the access. There are no limits on how many times an item can be reassigned, making it a versatile feature within the certification process.

References:

SailPoint IdentityNow Certification Reassignment Feature Documentation.

SailPoint IdentityNow Certification Workflow Guide.

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, this example does not accurately describe the complete data flow in IdentityNow. While it correctly mentions identity aggregation and the building of an identity model, the third step, "Accounts are provisioned to source systems," is not always part of the identity aggregation process. Provisioning is typically a separate workflow initiated by access requests or certification decisions, not directly tied to identity aggregation. Additionally, the periodic synchronization of identity attributes happens as part of identity refreshes but is not necessarily tied to provisioning accounts in all cases.

References:

SailPoint IdentityNow Aggregation and Identity Model Documentation.

SailPoint IdentityNow Provisioning Workflow Guide.

SailPoint IdentityNow API documentation is indeed located at https://docs.sailpoint.com . This official documentation site contains all the information developers need to interact with IdentityNow through APIs. It includes guidelines on how to authenticate, make requests, and use the API endpoints to automate and integrate with other systems.

Key Reference from SailPoint Documentation:

SailPoint API Documentation: The site docs.sailpoint.com hosts the official API documentation for SailPoint IdentityNow, covering all aspects of using IdentityNow's APIs.

The /home/sailpoint/proxy.yaml file is used for proxy settings, not for configuring the Virtual Appliance to use a static IP address. This file is typically modified to configure outbound proxy settings for the VA if it needs to route traffic through a proxy server. Static IP address configuration is handled elsewhere, at the operating system or network configuration level.

References:

SailPoint IdentityNow Virtual Appliance Proxy Configuration Documentation.

SailPoint IdentityNow Network Settings Documentation.

No, the search syntax @accounts( source.name:"AD" AND disabled:true ) is incorrect for SailPoint IdentityNow because the attribute disabled may not be universally recognized or applicable for all sources in the system. Using the state:"disabled" condition (as in previous correct answers) is a more reliable and system-compliant approach to find disabled accounts.

Key Reference from SailPoint Documentation:

Standard Account State Search: The correct search syntax involves using state:"disabled" instead of disabled:true for querying disabled accounts.

Yes, the search syntax @accounts( source.name:"AD" AND state:"disabled" ) is correct, as it matches the necessary criteria for finding disabled AD accounts. This query searches for accounts in the AD source where the account state is set to "disabled," which effectively filters for the desired result.

Key Reference from SailPoint Documentation:

Correct Syntax for Disabled Accounts: The search correctly identifies accounts with a disabled state using this syntax.