Is this an appropriate use case for the Build Map?
Solution: To provide the ability to modify to modify the map data of an account for a JDBC or a Delimated File source.
Yes, using the Build Map is appropriate for modifying map data of an account for a JDBC or Delimited File source. The Build Map allows you to define how data from a source system (like JDBC or a Delimited File) is transformed and mapped into IdentityNow's data model. This step is crucial when creating or modifying mappings between source fields and IdentityNow identity attributes, ensuring accurate data representation.
Modifying map data is essential for handling specific transformations or adjustments when synchronizing data from these sources to ensure that identity data is complete and correct.
SailPoint IdentityNow Source Configuration and Build Map Documentation.
SailPoint JDBC and Delimited File Source Configuration Guides.
When an engineer goes to Global > System Settings and clicks on System Notifications, the following page opens:
What email notifications are enabled if the engineer selects Sources?
Solution: A notification is immediately sent after successful
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.
Is this statement true about deploying and configuring IdentityNow's virtual appliance (VA)?
Solution: When deploying the VA in Azure, the identityNow engineer will need to utilize the Azure command --line interface(CLI) to deploy the VA image.
No, when deploying the Virtual Appliance (VA) in Azure, the IdentityNow engineer does not necessarily need to use the Azure CLI to deploy the VA image. While using the Azure CLI is one option, SailPoint provides multiple ways to deploy the VA in Azure, including using the Azure portal or ARM (Azure Resource Manager) templates. The process does not mandate using the CLI specifically.
Key Reference from SailPoint Documentation:
Azure VA Deployment Methods: SailPoint supports multiple methods for deploying the VA in Azure, including through the Azure portal or ARM templates, without requiring the CLI.
An IdentityNow engineer has the following problem:
IdentityNow shows status failed on a virtual appliance (VA).
Is this one of the steps that should be taken troubleshoot the issue?
Solution: Log in to the console of the VA and verify that the VA has connectivity to the internet.
Yes, verifying that the Virtual Appliance (VA) has connectivity to the internet is a critical step when troubleshooting a 'failed' status in IdentityNow. The VA requires internet connectivity to communicate with SailPoint IdentityNow's cloud services for synchronization, updates, and other key functions. If the VA is unable to reach the internet, it can lead to a failed status. Logging in to the VA's console to test network connectivity (e.g., using ping or curl commands) is an important step in diagnosing the issue.
Key Reference from SailPoint Documentation:
VA Internet Connectivity Troubleshooting: SailPoint recommends checking the network connectivity as one of the first steps when the VA shows a failed status.
An IdentityNow engineer needs to find identities with disabled AD accounts by using IdentityNow's search features. Is this the correct search syntax to perform this task?
Solution:
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.
