Free Practice Questions for SailPoint IdentityNow-Engineer Exam

No, custom connectors are not developed and compiled inside IdentityNow. Custom connectors are typically developed outside of the IdentityNow platform using a development environment and then tested and packaged before being uploaded to the platform. These connectors can be developed using tools provided by SailPoint, but the actual development process occurs externally, not directly within the IdentityNow environment.

Key Reference from SailPoint Documentation:

Custom Connector Development: Custom connectors are developed outside of the IdentityNow platform and then integrated into it for use.

IQService does not run on the Virtual Appliance (VA). It is a separate service that must be installed on a Windows Server within the environment that has access to the target system, particularly for Active Directory and other Windows-based systems. IQService acts as a proxy between the IdentityNow tenant and these target systems, allowing operations such as password management and account provisioning to be executed on systems that do not support native connectors on the VA. It communicates with the VA but is not hosted on it.

References:

SailPoint IdentityNow IQService Installation Guide.

SailPoint IdentityNow Target Connector Architecture.

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.

No, the vs_agent.log file is not typically used to diagnose secure tunnel communication issues. The vs_agent.log file is related to virtual appliance services and tasks but does not provide detailed information about the secure tunnel or communication errors. For troubleshooting the secure tunnel, the relay.log file is more appropriate.

Key Reference from SailPoint Documentation:

Log File Purposes: The vs_agent.log does not capture information about secure tunnel communication issues. Instead, the relay.log is the correct log file for such issues.

Yes, the fact that the disaster recovery (DR) VAs are not being utilized until a disaster recovery event occurs is a disadvantage. In this strategy, the DR VAs remain idle, leading to underutilization of resources. These VAs could otherwise handle workloads during normal operations to improve efficiency, distribute load, or reduce latency, especially if they are geographically closer to specific target systems. Relying on DR VAs only during failover scenarios limits their potential to optimize performance and balance loads in day-to-day operations.

References:

SailPoint IdentityNow Virtual Appliance Clustering and Disaster Recovery Documentation.

SailPoint IdentityNow High Availability and DR Strategies.

Yes, the file /etc/systemd/network/static.network (or a similarly named file depending on the Linux distribution used by the Virtual Appliance) is typically used to configure a static IP address for the VA. This file is part of the systemd network configuration, and modifying it allows you to specify static IP settings, such as the IP address, netmask, gateway, and DNS servers, for the Virtual Appliance's network interface.

To set a static IP address, you would need to modify this file and restart the network service for the changes to take effect.

References:

SailPoint IdentityNow Virtual Appliance Network Configuration Guide.

Linux systemd Network Configuration Documentation.

https://identityNowacme.com is not typically considered a vanity URL. While it includes the "identityNow" term, it does not appear to follow the format of a vanity URL, which generally includes a company-specific subdomain (like my) and a custom domain (example.com). In this case, the URL is more generic and lacks the branding or simplicity typically associated with vanity URLs.

Key Reference from SailPoint Documentation:

Vanity URL Structure in IdentityNow: Vanity URLs typically feature a customized subdomain that reflects the organization’s branding, and identityNowacme.com does not fit this pattern.

No, this statement is incorrect. While IdentityNow does use TLS (Transport Layer Security) for securing data in transit, TLS is not a hashing algorithm; it is a protocol used for encryption to ensure secure communication over networks. Additionally, IdentityNow uses hashing algorithms for securely storing passwords and answers to security questions (e.g., SHA-256 or bcrypt), but it does not use TLS for hashing these values. Hashing algorithms are one-way functions that help store sensitive data securely by converting them into irreversible fixed-length representations.

TLS protects data during transmission by encrypting it, while hashing is used for securing stored data such as passwords.

References:

SailPoint IdentityNow Encryption and Security Practices Documentation.

SailPoint IdentityNow Password Hashing and Encryption Mechanisms Guide.

No, when deploying the Virtual Appliance (VA) using the AWS deployment option, the IdentityNow engineer does not need to convert the VA image. SailPoint provides an AWS-compatible Amazon Machine Image (AMI) that can be directly used to deploy the VA in AWS without any additional conversion steps. The AMI is shared with the customer’s AWS account, allowing for a streamlined deployment process.

Key Reference from SailPoint Documentation:

VA Deployment in AWS: SailPoint provides a ready-to-use AMI for AWS deployments, and no image conversion is necessary for this deployment method.

Yes, SailPoint uses a proprietary fairness algorithm to manage and distribute workloads in its multi-tenant environment. This algorithm ensures that resources are allocated fairly among tenants, preventing any single tenant from consuming excessive resources at the expense of others. It helps maintain system performance and stability, balancing the processing load and providing equitable access to shared infrastructure in a multi-tenant setup.

References:

SailPoint IdentityNow Multi-Tenant Architecture Documentation.

SailPoint IdentityNow Resource Allocation and Fairness Algorithm Guide.