Most Recent SailPoint IdentityNow-Engineer Exam Questions & Answers

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, 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, 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.

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.

In this scenario, the Virtual Appliances (VAs) should not reside in the DMZ (B), which is typically used for hosting services that need to be exposed to both internal and external networks, like web servers or email gateways. However, VAs require more direct and secure access to internal resources like Active Directory and databases. The VA needs to reside where it has secure and reliable connectivity to internal resources like Active Directory and database servers, which would be in the internal network.

Key Reference from SailPoint Documentation:

VA Placement Guidance: Virtual Appliances are placed within the internal network, where they can securely connect to Active Directory, databases, and other internal applications for synchronization and provisioning tasks.