IdentityIQ-Engineer Exam Dumps - SailPoint Certified IdentityIQ Engineer

When setting up a new IdentityIQ test environment, it is important to assess the needs of the customer, including whether they would benefit from using a deployment accelerator.

Deployment accelerators are pre-configured sets of rules, policies, and workflows that can significantly reduce the time and effort required to deploy IdentityIQ in a test or production environment. These accelerators are particularly useful for rapidly setting up environments that align with common industry practices or specific compliance requirements.

Asking the customer whether they need a deployment accelerator is a valid and important question during the initial setup phase, as it helps to determine the best approach to configuring the test environment efficiently. Therefore, the correct answer is A. Yes.

No. IdentityIQ BeanShell rules do not all have the same input and output contract. Rule arguments and expected return values depend on the rule type and the execution context in which IdentityIQ invokes the rule.

For example, a correlation rule requires information relevant to account/identity correlation, while provisioning-related rules operate with provisioning plans, applications, accounts, or provisioning results. Workflow rules receive variables associated with the workflow context. Other rule types may return a Boolean, String, Identity, Map, object collection, transformed value, or no meaningful value at all.

IdentityIQ ' s Rule Registry and Rule Editor exist partly to expose this distinction. The Word bank itself states that the typical input variables for a rule are presented according to the Rule Registry, meaning they are determined by rule type rather than being universally identical. It also contains separate propositions concerning Rule Registry descriptions and Rule Editor Arguments.

Therefore, standardizing every BeanShell rule around identical arguments and returns would contradict IdentityIQ ' s rule architecture.

References/topics: IdentityIQ Engineer — BeanShell rules, Rule Registry, Arguments, Returns, rule type, runtime context.

=======

The statement that supported platforms of an older version of IdentityIQ will always be supported in newer versions of IdentityIQ is incorrect. As SailPoint releases new versions of IdentityIQ, the list of supported platforms (such as specific versions of Java, databases, application servers, etc.) may change. Newer versions of IdentityIQ might deprecate support for older platforms or require newer versions of software components. It is essential to consult the Release Notes or the Supported Platforms documentation for the specific IdentityIQ version to ensure compatibility.

Thus, the correct answer is B. No.

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.

No. A standard Correlation Rule and a Manager Correlation Rule perform different functions in IdentityIQ. The scenario specifically requires resolving a manager reference—an employee ' s manager employee number must be matched to the correct Identity despite several employee-number formats. That is manager correlation, not ordinary account-to-identity correlation.

A Correlation Rule is used when IdentityIQ needs custom logic to associate an application account with an Identity and simple attribute-based account correlation is insufficient. By contrast, SailPoint defines a Manager Correlation Rule specifically for establishing the Manager–Direct Report relationship between Identity objects when simple manager attribute mapping cannot accommodate the required matching logic.

Here, the presence of several employee-number formats is exactly the type of complexity that makes custom manager-correlation logic appropriate. The rule can normalize or otherwise interpret those formats and return the identity representing the correct manager.

This proposition is separate from the earlier video proposition using “Write a ManagerCorrelation rule,” which is the correct solution. Under DOMC rules, changing the proposed rule type creates a separate question.

Therefore, writing a generic Correlation Rule does not correctly target the required manager-resolution process.

References/topics: IdentityIQ Engineer — Manager Correlation Rule, Correlation Rule, manager relationships, application aggregation, account correlation, Identity Cube relationships.

=======

Yes. Rapid Setup supports standard lifecycle-event actions for Leaver processing, including application-specific account actions and delayed account deletion. This enables an implementation to disable an account when the Leaver event occurs and configure account deletion for a later point, such as 30 days afterward.

This pattern is useful because many organizations do not immediately delete accounts when employment ends. Immediate disablement blocks interactive access while preserving the account temporarily for investigation, handover, retention, reconciliation, or recovery requirements. After the retention interval expires, deletion can remove the target-system account according to the configured lifecycle policy.

The important distinction is that this is a standard timing sequence for the same lifecycle population , rather than complex branching where different categories of users receive entirely different actions. The Word bank already contains a different Rapid Setup proposition involving disabling accounts for one group while deleting accounts for another group during termination, and marks that more complex population-dependent scenario invalid. It also separately tests disable-plus-entitlement-removal during Leaver.

Therefore, this delayed-delete Leaver proposition is unique and valid.

References/topics: IdentityIQ Engineer — Rapid Setup, Leaver events, Disable Account, Delete Account, delayed deletion, lifecycle configuration.

=======

Yes, the text on the login page of IdentityIQ is set through message keys in the message catalog. The message catalog in IdentityIQ contains localized text strings that are used throughout the user interface, including on the login page. By modifying the appropriate message keys in the catalog, you can customize the text that appears on the login page to match the organization ' s branding or messaging requirements.

Therefore, the correct answer is A. Yes.

The statement that " An Application object is not required to aggregate external user account information into IdentityIQ " is false. In SailPoint IdentityIQ, an Application object is essential for aggregating (importing) external user account information. The Application object defines the connection settings, schema, and mapping that enable IdentityIQ to connect to external systems and retrieve identity data. Without an Application object, IdentityIQ would not have the necessary configuration to establish a connection and aggregate user data from external sources.

SailPoint IdentityIQ Administration Guide (Section on Applications and Aggregation)

SailPoint IdentityIQ Integration and Configuration Guide