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

This statement is false. BeanShell rules in IdentityIQ do not universally have to produce a meaningful output. A rule’s expected return behavior depends on the rule type and the context in which the rule is executed. Some rules are designed to return a Boolean, String, Map, ProvisioningPlan, Identity, or another object. Other rules perform side effects, such as modifying a plan, transforming values, logging, altering an object, or executing validation logic, and may return null or no useful result. The Word bank contains a related but different rule-output concept: a BeanShell rule does not always need to return an object derived from sailpoint.object.SailPointObject; it may return several other object types or null. The proposed statement is even broader and still incorrect because IdentityIQ rule output is rule-type dependent, not mandatory in a generic sense. References/topics: IdentityIQ Engineer — BeanShell rules, rule registry, return values, rule execution context, input/output contracts.

The statement that " All certifications include generation, the active period, sign-off, and the end period " is true. These stages are fundamental to the certification process in SailPoint IdentityIQ:

Generation: This is the initial stage where the certification campaign is created. During this phase, the system generates the list of items (such as access, roles, or entitlements) that need to be reviewed.

Active Period: Once the certification is generated, it enters the active period. During this time, the designated reviewers are responsible for examining the items in the certification, making decisions (such as approving or revoking access), and providing any necessary comments.

Sign-off: After the active period, the certification moves into the sign-off stage. Here, the final approver(s) review the decisions made during the active period and formally approve or reject the certification outcomes.

End Period: Finally, the end period marks the conclusion of the certification campaign. The certification is closed, and the results are archived. Any necessary actions, such as revoking access or triggering workflows based on the certification decisions, are implemented.

These stages are essential to the structured process that ensures all access rights are properly reviewed and either maintained or adjusted according to the organization ' s policies.

SailPoint IdentityIQ Certification Administrator ' s Guide

SailPoint IdentityIQ Certification Process Documentation

SailPoint IdentityIQ Administration Guide (Sections on Certification Lifecycle and Workflow)

time → show how much time a command takes to run

source → execute a file of commands

run → launch a background task

import → import objects from a file

Yes. Sub-workflows are an established IdentityIQ workflow-design mechanism for decomposing a large business process into smaller, reusable units. Instead of placing provisioning, approval, initialization, policy-checking, notification, and other logic into one oversized master workflow, an engineer can move logically independent functions into workflows designated as Subprocess workflows. The parent workflow then invokes those subprocesses at the appropriate processing steps.

SailPoint specifically identifies simplification of the master workflow as one of the benefits of subprocess workflows. The design also improves maintainability because individual subprocesses can be understood, tested, modified, and reused independently. Reusability is particularly important in Lifecycle Manager implementations because several business processes can require the same approval, provisioning, or initialization behavior. IdentityIQ workflow steps can use a Subprocess action to launch another defined workflow and wait until it completes. Variables and results can also be exchanged between parent and subprocess workflows.

The statement is therefore technically correct: subprocesses are not merely permitted; breaking complex workflows into manageable reusable components is a core reason for using them.

References/topics: IdentityIQ Engineer — Workflow Basics, subprocess workflows, master workflows, reusable business processes, Workflow Step action types.

=======

Yes. Hierarchy is a valid relationship concept for IdentityIQ roles when a role model has a multiple-level structure. IdentityIQ roles are not limited to flat entitlement collections. Role models can be built with layered relationships, where higher-level roles represent broader business access and lower-level roles represent more technical or application-specific access. This is common in mature role-based access control designs: a business role may include IT roles, which in turn may include entitlements or application roles. A hierarchical structure allows organizations to express access in business terms while still mapping that access down to technical resources. The important engineering point is that the role model must be carefully designed to avoid circular dependencies, overbroad inheritance, and difficult certification outcomes. Hierarchical role relationships support maintainable access modeling when used properly, especially in enterprises that are actively using role-based provisioning and role reviews. References/topics: IdentityIQ Engineer — role hierarchy, role relationships, Bundle object, business roles, IT roles, role-based access model.

Yes. For a Risk Policy violation, Certify is a valid action when the user handling the violation has the necessary permissions. IdentityIQ policy types can expose different response options, and the available disposition is not identical for every policy category.

Certify allows the responsible governance user to initiate certification-related review rather than simply accepting the violation or immediately remediating access. This is useful when a risk violation identifies access or identity conditions that warrant a formal review by an appropriate certifier before a final access decision is made.

This question must also be kept separate from the Account Policy propositions in the Word bank. The bank contains Account Policy propositions such as Schedule Policy Composition Certification—which it marks invalid—and Allow, which it marks valid. The policy type in the video is specifically Risk Policy , and DOMC evaluates the proposed action in that policy-type context.

Therefore, Certify is a valid option for the stated Risk Policy violation.

References/topics: IdentityIQ Engineer — Risk Policy, policy violations, Certify action, Compliance Manager, certification launch, violation disposition.

=======

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:

SailPoint IdentityIQ Console Guide (section on connector troubleshooting).

source:

This command allows you to authenticate as another user within the IdentityIQ system. It ' s useful for testing user-specific actions or behaviors without logging out and back in.Reference: SailPoint IdentityIQ Admin Guide (section on user authentication and delegation).

list:

This function returns a list of objects or entities within the system. In IdentityIQ, objects could include applications, roles, policies, and more.Reference: SailPoint IdentityIQ Console Reference Guide (list and query commands).

provision:

The provision command evaluates and executes a provisioning plan. This is the actual process that implements changes in user access across connected systems based on the identity lifecycle event.Reference: SailPoint IdentityIQ Provisioning Guide (execution of provisioning plans).

By matching these commands to their respective functions, the detailed functionalities of IdentityIQ’s console tools are properly understood for administrative and troubleshooting purposes.

Yes, an Escalation Rule can be used to handle the scenario of automatically reassigning parts of an access review to a different certifier. In SailPoint IdentityIQ, Escalation Rules are often employed within certification campaigns to manage situations where a primary certifier has not completed their review within a specified timeframe. The rule can trigger actions such as reassigning the review items to a different certifier, thus ensuring that the certification process continues smoothly without delays.

Therefore, the correct answer is A. Yes.

The statement is true. In the SailPoint IdentityIQ Reporting user interface, report templates are located on the " Reports " tab. These templates define the structure and parameters of reports but do not contain actual report data. Instances of reports, which are the actual generated reports containing data based on the templates, are located on the " My Reports " tab. The " My Reports " tab is used for viewing and managing reports that have been generated for a specific user.

SailPoint IdentityIQ Reporting Guide

SailPoint IdentityIQ Administration Guide (Section on Reporting Interface)

An Account Group Membership Certification is designed to certify group memberships within accounts, typically focusing on the validation of access within specific account groups (e.g., Active Directory groups).

This type of certification does not directly address the accuracy of role composition or the correctness of entitlements assigned within roles. Since the bank ' s goal is to ensure that all roles include the correct entitlements, an Account Group Membership Certification is not suitable for this purpose.

Thus, the correct answer is B. No.

Yes. IdentityIQ roles can be configured to include permissions as part of the access represented by the role. A role is fundamentally a logical collection of access that can include application entitlements and permission-based profile definitions. SailPoint describes roles as collections of permissions that group underlying system access into meaningful business or technical units.

Within a role profile, IdentityIQ supports Attribute Permissions in addition to attribute rules. Permissions define rights against targets on an application. An engineer can select rights such as create, read, update, delete, or execute and associate those rights with the appropriate target. These permission definitions become part of the role profile and therefore form part of the access granted through the role.

This should not be confused with IdentityIQ administrative SPRight objects. Application-level permissions contained in a role profile are governed access on target systems, whereas SPRights control functionality inside IdentityIQ itself. IdentityIQ roles can also grant capabilities and scopes when that feature is enabled.

Therefore, configuring a role to contain a set of permissions is a valid role configuration.

References/topics: IdentityIQ Engineer — Role Modeling, role profiles, attribute permissions, entitlements, targets and rights.

=======

This is a valid process. The requirement has two parts: detect a specific Division transition and confirm that the identity is a manager. A rule-based lifecycle event trigger is appropriate when the condition is more complex than a simple single-attribute check. The rule can inspect the previous and new values of the Division attribute and return true only when the value changes from IT to Senior IT. It can also evaluate the identity’s managerStatus value on the Identity Cube to confirm that the user is a manager. Returning true from the rule allows IdentityIQ to launch the associated workflow only for identities that satisfy both conditions. This approach avoids the flaw of triggering on the wrong attribute and gives the engineer precise control over the lifecycle event condition. The key is that the rule must be written against the correct before-and-after identity data available during refresh or lifecycle-event evaluation. References/topics: IdentityIQ Engineer — rule-based lifecycle triggers, identity attribute changes, Identity Cube attributes, workflow launch rules, mover-event logic.

This implementation is correct in structure. The code first resolves the Application object named MagicBox, then creates an IdentityService, then calls service.getLinks(identity, application) to retrieve the account links for that identity on the application. Because the requirement is to return all account names, using getLinks and iterating over the returned List < Link > is the right pattern. Each Link represents an account on an application, and getNativeIdentity() returns the account’s native identifier, which is the account name or unique account key from the target application. The null check prevents a null-pointer issue if no links are returned. In a production-quality version, an engineer might also handle a missing application object and ensure Java collection imports are available, but those do not invalidate the core implementation pattern shown. Compared with the flawed single-link version, this solution correctly handles multiple accounts. References/topics: IdentityIQ Engineer — IdentityService API, Application object lookup, Link collection retrieval, nativeIdentity, BeanShell utility methods.

Yes. Reviewing provisioning transactions and their processing states is a principal purpose of the Provisioning tab in the IdentityIQ Administrator Console. The engineer can use this administrative view to inspect provisioning activity and distinguish transactions according to states such as pending, failed, or completed/successful.

This visibility is particularly important for troubleshooting asynchronous provisioning. A failed transaction may require investigation into connector errors, target-system responses, invalid attribute values, authentication failures, or workflow/provisioning-plan problems. A pending transaction may indicate queued processing or an operation awaiting further execution. Successful transactions provide confirmation and historical visibility into completed processing.

The Provisioning tab is therefore an operational troubleshooting interface for provisioning transactions; it is not merely a configuration page.

This should also be distinguished from another proposition already present in the Word bank: the bank explicitly states that the Provisioning tab can be used to manually retry the provisioning attempt for pending transactions . The video proposition here tests a different capability—viewing transactions across their various states—so it remains a separate DOMC item.

References/topics: IdentityIQ Engineer — Administrator Console, provisioning transactions, failed provisioning, pending transactions, transaction history, provisioning troubleshooting.

=======

Owner is a required and important application configuration element in IdentityIQ. Application ownership establishes accountability for the connected system and is used across governance operations such as access reviews, application owner certifications, approval routing, policy handling, and administrative responsibility. IdentityIQ’s governance model depends heavily on ownership metadata because applications are not merely technical connector records; they are governed objects. Assigning an owner allows IdentityIQ to determine who is responsible for application access, certification decisions, and operational oversight. While some low-level object imports may technically create incomplete objects, from the application setup perspective an engineer should treat Owner as required. Without an owner, downstream governance functions become weak or ambiguous because IdentityIQ cannot reliably route application-specific reviews or approvals to the responsible business or technical authority. The proposed option is therefore valid as a required setup item. References/topics: IdentityIQ Engineer — application definition, application owner, governance accountability, certification ownership, access approval routing.

The statement is false. While it is true that logging and auditing require extra function calls and generate data, the suggestion that this data can be compressed to avoid storage issues and improve performance is misleading. In practice, while compression might save storage space, it does not inherently improve performance, particularly because the overhead of compression and decompression could negate the performance benefits. Effective performance management in IdentityIQ involves more nuanced approaches, such as optimizing the level of detail in logs, managing log rotation, and tuning the system for efficient I/O operations.

SailPoint IdentityIQ Logging and Auditing Guide

SailPoint IdentityIQ Performance Tuning Guide

No. IdentityIQ ' s standard audit-event configuration is managed primarily through the Audit Configuration page, not through the Administrator Console. SailPoint documents the navigation for audit configuration under Global Settings > Audit Configuration , where administrators choose which General Actions, Identity Attribute Changes, Link Attribute Changes, Class Actions, and other supported activities are collected in the audit log.

The Administrator Console serves a different operational purpose. It is used for areas such as task-result management, provisioning transaction monitoring, host/environment monitoring, application health, and status information for SailPoint modules and extensions. Although some activities viewed or performed there may themselves generate audit records when auditing is enabled, that does not make the Administrator Console the central audit-configuration interface.

This distinction is important for an IdentityIQ engineer. Audit Configuration controls what governance events are recorded; Advanced Analytics provides mechanisms to search the resulting audit events; Administrator Console focuses primarily on operational monitoring and administration. Therefore, replacing “Audit Configuration page” with “Administrators Console page” changes the statement from correct to incorrect.

References/topics: IdentityIQ Engineer — Audit Configuration, audit actions, Administrator Console, Environment Monitoring, Advanced Analytics.

=======

No. The challenge period is not designed to let the reviewer ' s manager challenge the reviewer ' s certification decisions. Its purpose is to give the affected user whose access is being removed an opportunity to respond to the revocation.

When a certification enters the optional challenge phase, IdentityIQ generates a work item and notification for users affected by revocation decisions. The affected identity can accept the loss of the role, entitlement, or account-group access, or challenge the revocation. Any challenged items must subsequently be handled as part of the certification lifecycle.

A reviewer ' s manager can be relevant to certification processing, but through different mechanisms. For example, escalation can transfer an unfinished access review to another identity, commonly the certifier ' s manager, and multi-level sign-off can introduce another approver after the original certifier. Those mechanisms must not be confused with the challenge phase.

Therefore, the proposition assigns challenge rights to the wrong actor. The person whose access is subject to revocation—not the original reviewer ' s manager—is the participant for whom the challenge period exists.

References/topics: IdentityIQ Engineer — certification challenge phase, revocation decisions, affected identity, escalation, multi-level sign-off.

=======

One of the primary purposes of an IdentityIQ certification is to provide reviewers with a snapshot of a user ' s system access at a given point in time. This snapshot allows managers, auditors, or other designated reviewers to verify whether the access privileges assigned to a user are appropriate, based on their job responsibilities and compliance requirements. By reviewing this snapshot, organizations can identify and remediate any inappropriate or excessive access, thus maintaining a secure and compliant environment.

Therefore, the correct answer is A. Yes.