SailPoint IdentityNow-Engineer - SailPoint Certified IdentityNow Engineer

Turning off the Virtual Appliance’s (VA) internal firewall is not recommended as a standard troubleshooting step in SailPoint IdentityNow. The VA’s firewall is crucial for maintaining the security of the environment, and disabling it can expose the system to unnecessary risks. Instead, an IdentityNow engineer should verify the VA’s network configuration and ensure that the required ports are open for communication between the VA and the source.

Key Reference from SailPoint Documentation:

VA Configuration and Network Troubleshooting: Troubleshooting connection issues typically involves checking network connectivity and firewall rules, not turning off the internal firewall.

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.

Yes, reviewing the log files in the /home/sailpoint/log directory is a standard troubleshooting step for diagnosing a failed VA. The log files, such as relay.log, vs_agent.log, and others, can provide detailed error messages and insights into what might be causing the VA failure, such as connectivity issues, service failures, or configuration problems.

Key Reference from SailPoint Documentation:

Log Files for VA Troubleshooting: SailPoint's best practices for troubleshooting VA issues involve reviewing log files to check for error messages or warnings that can help identify the root cause of the failure.

Yes, using a query select statement with a clause to match the incoming account to an existing account is a key configuration for the Single Account SQL Query in a JDBC connector. This query is used to fetch specific account details from the database and must be written in such a way that it uniquely identifies each account, ensuring accurate correlation between the data in the source and the identities in IdentityNow. Properly configuring this SQL query ensures the right accounts are matched and managed.

References:

SailPoint IdentityNow JDBC Connector Single Account Query Configuration Guide.

SailPoint IdentityNow SQL Query Best Practices Documentation.

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.

References:

SailPoint IdentityNow Source Configuration and Build Map Documentation.

SailPoint JDBC and Delimited File Source Configuration Guides.

No, this statement describes Manager Certification rather than Manager Correlation. Manager Certification refers to an approval process in which managers are required to periodically review and approve the access rights of their direct reports. This is a governance feature used to ensure that employees only have the access they need, and it helps managers validate their team’s access periodically. Manager Correlation, on the other hand, is about linking identities to their managers based on attributes.

Key Reference from SailPoint Documentation:

Manager Certification vs. Manager Correlation: While Manager Certification involves periodic review and approval of access by managers, Manager Correlation is strictly about linking identities to their respective managers based on defined attributes.

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.

References:

SailPoint IdentityNow SaaS Release Management Guide.

SailPoint IdentityNow Product Updates and Release Notes.

Yes, evaluating available campaign administration filters is a best practice before generating the campaign preview. Campaign filters allow administrators to control the scope of the campaign by filtering users, entitlements, or other criteria, which is crucial for tailoring the certification to the right audience. By evaluating and applying filters, administrators ensure that only the relevant users and entitlements are included in the certification campaign, leading to more effective and targeted certifications.

References:

SailPoint IdentityNow Campaign Administration Guide.

SailPoint IdentityNow Certification Campaign Filtering and Scope Documentation.

The search syntax @accounts( source.name:"AD" AND disabled:false ) is not correct for finding disabled AD accounts. This query would return accounts that are not disabled because it is filtering for disabled:false. To find disabled accounts, the filter should specify disabled:true.

Key Reference from SailPoint Documentation:

Search Syntax for Disabled Accounts: To search for disabled accounts, the condition should check for disabled:true.

No, deleting the access profile is not the correct way to meet the requirement of removing approval for access requests. The access profile defines the entitlements and permissions that users can request for an application. Deleting it would remove the entire ability to request access, rather than just removing the approval workflow. The correct step would be to modify the approval settings in the access profile (as explained in Question 44), not to delete it.

Key Reference from SailPoint Documentation:

Access Profile Management: Modifying approval settings in the access profile is the appropriate step to meet management's new requirement, not deleting the profile itself.