IdentityIQ-Engineer SailPoint Certified IdentityIQ Engineer Free Practice Exam Questions (2025 Updated)

Here’s how the SailPoint IdentityIQ console commands correspond to their respective functions:

connectorDebug: debug the connector to identify issues in the connector.

source: authenticate to IdentityIQ as another user.

list: list objects.

provision: evaluate and execute a provisioning plan.

Comprehensive Detailed Explanation with All IdentityIQ Engineer References

connectorDebug:

Running a build with the updated schema placed inside it isnotthe correct procedure to generate the database script to extend Application attributes in the IdentityIQ database during the initial installation. To extend the schema, you typically need to define the changes in a specific XML schema file and then generate the corresponding database scripts using IdentityIQ tools designed for schema extension. A build process does not inherently generate the required database scripts for extending attributes.

References:

SailPoint IdentityIQ Schema Configuration Guide

SailPoint IdentityIQ Installation and Setup Guide

The "Total Memory" value displayed on the JVM Memory page indicates the amount of memory currently allocated to the JVM heap. In the image provided, the "Total Memory" is shown as725.617 MB. This is the amount of memory that the JVM heap is currently using, meaning it has been allocated and is available for the JVM to use.

References:

SailPoint IdentityIQ Performance Tuning and Monitoring Guide

SailPoint IdentityIQ Administration Guide (JVM and Memory Management Sections)

The statement suggests moving the XML file intoIIQ_HOME/WEB-INF/databaseas part of the process to import SailPoint XML file objects into IdentityIQ. However, this isnota valid step for importing XML objects.

The correct procedure to import SailPoint XML objects typically involves the following steps:

Use theiiq consolecommand-line tool provided by SailPoint to import the XML file.

The command typically looks like:iiq console import .xml.

The XML file does not need to be moved to any specific directory likeWEB-INF/databasefor the import process.

Moving the XML file into theWEB-INF/databasedirectory does not align with the documented process and does not facilitate the import. The correct answer isB. No.

Changing the Email Notification Type to POP3 under Global Settings > Configure IdentityIQ Settings > Mail Settings is not a correct procedure for testing generated emails in a non-production system. POP3 is an email retrieval protocol, not a method for sending or redirecting email notifications from IdentityIQ. IdentityIQ requires an SMTP server to send emails, andPOP3 is typically used by email clients to retrieve emails from a server, not by a server to send emails.

For testing purposes in a non-production environment, you would typically configure the SMTP server settings to either redirect emails to a specific testing mailbox or use a "Redirect to File" option, if available, to capture emails locally.

Thus, the correct answer isB. No.

Adding a new object attribute to the ApplicationObjectConfigin IdentityIQ isnotsufficient on its own to generate the database script needed to extend Application attributes. This action updates the configuration within IdentityIQ for how the application object is managed, but it does not produce the necessary SQL scripts to modify the underlying database schema. The actual database schema must be extended using specific IdentityIQ tools and commands likeiiq extendedSchema.

References:

SailPoint IdentityIQ Configuration Guide (ObjectConfig and Schema Management)

SailPoint IdentityIQ Administration Guide (Database Schema Extension)

The statement isfalse. In SailPoint IdentityIQ, there is no strict limitation on nesting sub-workflows (subprocesses) up to 3 levels. You can nest sub-workflows as deeply as required by your business logic and system design. However, it is advisable to manage the complexity of nested workflows to ensure maintainability and performance, but there is no enforced limit of 3 levels for nesting.

References:

SailPoint IdentityIQ Workflow Guide

SailPoint IdentityIQ Administration Guide (Sections on Workflow Design Best Practices)

The Rapid Setup user interface in SailPoint IdentityIQ is designed to simplify and streamline common configuration tasks, particularly during the initial setup of IdentityIQ environments. However, it has certain limitations in terms of granularity and customization.

In this case, the requirement is to disable an account on a particular application for one set of users and delete the account for another set of users during administrative terminations. The Rapid Setup interface does not provide options to differentiate between user groups for different actions (disable vs. delete) within the same termination event.

This level of specificity—applying different actions based on user group membership—would require a more advanced setup, possibly involving custom rules or workflows rather than using the Rapid Setup options. Therefore, the correct answer isB. No.

Yes, the Provisioning tab under the "Administrator Console" in IdentityIQ can be used to view the specific operations on each attribute being provisioned. This tab provides detailed visibility into the provisioning operations, including which attributes are being modified, created, or removed as part of the provisioning process. This is essential for administrators to monitor and troubleshoot provisioning tasks.

References:

SailPoint IdentityIQ Administration Guide (Provisioning Tab Overview)

SailPoint IdentityIQ Provisioning Guide

The statement that a BeanShell rule in IdentityIQ must always return an object derived from the abstract classsailpoint.object.SailPointObjectis incorrect. While many rules in IdentityIQ may return objects that derive fromSailPointObject, it is not a strict requirement. Rules can return various types of objects depending on their purpose and context. For example, a rule might return aString,Boolean,Map, or evennull, depending on what the rule is designed to accomplish.

Therefore, the correct answer isB. No.

The "Name" configuration option isrequiredwhen setting up a SCIM 2.0 application in SailPoint IdentityIQ. The "Name" field is a mandatory identifier for the application within IdentityIQ. This name is used throughout the system to reference the application and is critical for configuration, management, and integration processes. Without specifying a name, IdentityIQ cannot properly identify and interact with the SCIM 2.0 application.

References:

SailPoint IdentityIQ SCIM 2.0 Application Configuration Guide

SailPoint IdentityIQ Administration Guide (Application Setup and Naming Conventions)

The primary and secondary colors in the IdentityIQ user interface are not set through the IdentityIQ Configuration > Miscellaneous page. Instead, these colors are typically configured through thestyle.cssor other custom CSS files that are part of the IdentityIQ UI customization process. Administrators can define and modify the color scheme, fonts, and other style elements by editing the relevant CSS files or using the Branding feature within IdentityIQ.

Therefore, the correct answer isB. No.

The statement isfalse. In SailPoint IdentityIQ, syslog events can indeed be sent to Log4j. The system allows for flexible configuration where logging can be directed to multiple outputs, including both syslog and Log4j. This flexibility enables organizations to route logs according to their needs while maintaining security and compliance.

References:

SailPoint IdentityIQ Logging and Auditing Guide

SailPoint IdentityIQ Administration Guide (Syslog Configuration and Log4j Integration)

Yes, specifying which access items may be requested can be achieved via configuration of control variables in the out-of-the-box Lifecycle Manager (LCM) workflows. In IdentityIQ, control variables within LCM workflows allow administrators to define the scope and criteria for access requests, including restricting or specifying which entitlements, roles, or applications can be requested by users. This is part of the request configuration process, where the access items that users can see and request are defined.

Therefore, the correct answer isA. Yes.

Placing a QuickLink object directly on a workflow is not a valid step in the development of a custom QuickLink. QuickLinks are used to provide users with easy access to specific tasks or workflows through the IdentityIQ interface, but the QuickLink itself is not embedded within the workflow. Instead, the QuickLink is created as a separate object and associated with the desired workflow or task that it is meant to launch.

The correct approach would involve creating a QuickLink that points to the workflow and then controlling access to the QuickLink by restricting it to a specific QuickLink population (e.g., "Managers"). Therefore, the correct answer isB. No.