Free Practice Questions for SailPoint IdentityNow-Engineer Exam

Yes, an SoD policy can define mitigating controls. Mitigating controls are measures put in place to reduce the risk of having conflicting duties. For example, if it's not possible to completely segregate duties due to resource constraints or other business factors, mitigating controls such as enhanced auditing, periodic reviews, or dual approvals can be defined to manage the risk. SailPoint IdentityNow allows for the creation of SoD policies that include such mitigating controls to ensure compliance with security and governance requirements.

Key Reference from SailPoint Documentation:

Mitigating Controls in SoD Policies: SailPoint supports the definition of mitigating controls within SoD policies to manage and reduce risks when full separation of duties cannot be achieved.

Yes, password interception is available for the Active Directory (AD) source in SailPoint IdentityNow. Password interception allows IdentityNow to capture password changes made on the AD source so that it can synchronize the new passwords across other connected systems and applications. This feature ensures password consistency and compliance across the organization’s identity infrastructure.

Key Reference from SailPoint Documentation:

Password Interceptor for AD: SailPoint supports password interception for Active Directory, enabling the platform to capture and synchronize password changes from AD to other systems in real time.

Yes, one of the key advantages of microservice architecture is the ability to resolve issues or failures quickly. Microservices are designed to be independent, loosely coupled services. If an issue arises in one service, it can be isolated and addressed without affecting the entire system. This compartmentalization enables faster resolution since each service can be debugged, redeployed, or scaled independently, resulting in quicker recovery from failures. This is a core benefit of microservice-based systems, including those used in SailPoint IdentityNow.

References:

SailPoint IdentityNow Microservices Architecture Overview.

Benefits of Microservices in SaaS Platforms.

Yes, an access profile allows the definition of an approval process. When an access profile is created, administrators can configure specific approval workflows that must be followed before the access is granted. This includes designating approvers or specifying multiple levels of approval, depending on the organization's policies. This capability is useful for ensuring that sensitive access requests are properly reviewed and approved.

References:

SailPoint IdentityNow Access Request and Approval Workflow Guide.

SailPoint IdentityNow Access Profile Configuration Documentation.

Yes, this example accurately describes an IdentityNow data flow for password changes in an Active Directory environment. When a user changes their password in IdentityNow, the request is sent to the virtual appliance, which then communicates with the IQService host. The IQService is responsible for making changes to Active Directory. This flow reflects the standard procedure for password management using IdentityNow with Active Directory, where the virtual appliance and IQService coordinate to complete the password change.

References:

SailPoint IdentityNow Password Management Documentation.

SailPoint IdentityNow IQService and Virtual Appliance Data Flow Guide.

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, https://my.example.com is an example of a vanity URL. Vanity URLs are customized, branded URLs designed to be easily recognizable, memorable, and aligned with a company’s branding. In this case, the subdomain my and the domain example.com create a branded, user-friendly URL. Vanity URLs are often used for simplifying access to services like IdentityNow and for improving user experience.

Key Reference from SailPoint Documentation:

Vanity URL Usage in IdentityNow: SailPoint allows customers to configure vanity URLs to provide a more personalized and branded login experience for their users.

No, IdentityNow administrators do not have the option to choose how often updates to their tenant occur. SailPoint operates a multi-tenant SaaS model, where updates are rolled out centrally by SailPoint on a predefined schedule. SailPoint controls and manages updates to ensure consistency and security across all tenants. This means that all tenants receive updates automatically as part of SailPoint’s continuous delivery model, without the ability for individual admins to control or delay updates.

References:

SailPoint IdentityNow SaaS Release Management Guide.

SailPoint IdentityNow Multi-Tenant Environment Overview.

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.