Free SailPoint IdentityIQ-Engineer Practice Exam with Questions & Answers | Set: 7

Yes. A self-service registration workflow needs a Registration Identity Provisioning Policy because the policy defines what identity data must be collected, displayed, validated, or constrained during registration. LCM Registration is not merely a generic workflow button; it needs a controlled data-entry model for creating or initiating an identity record through self-service. The Registration Identity Provisioning Policy provides that model by defining registration fields, required inputs, allowed values, validation behavior, and potentially default or derived values. Without it, the workflow lacks the structured policy definition needed to support registration-specific identity creation. This is separate from ordinary Create Identity or Edit Identity policies because self-service registration usually has different security and usability requirements. Public or semi-public registration should expose only carefully selected fields and should validate values tightly. Therefore, the proposed configuration is required for the self-service registration use case. References/topics: IdentityIQ Engineer — LCM Registration, self-service registration workflow, Identity Provisioning Policies, registration fields, validation logic.

No. Specifying which applications support new account requests is not normally achieved by changing control variables in the out-of-the-box LCM workflows. That behavior is driven by application configuration, provisioning support, account creation policies, schemas, QuickLink configuration, and requestability settings. LCM workflow control variables influence how an already-launched workflow behaves: approval handling, policy checking, provisioning behavior, notifications, foreground/background behavior, trace/debug options, and similar execution controls. They do not define whether an application itself supports account creation. For an application to support new-account requests, the application must support provisioning, have the relevant create-account capability/configuration, and expose the request path through LCM/QuickLink settings. Putting this into workflow control variables would be the wrong design layer. References/topics: IdentityIQ Engineer — LCM workflows, control variables, application provisioning configuration, Create Account policy, Manage Accounts/Manage User Access.

The Rapid Setup user interface configuration options in IdentityIQ can be used to disable an account and remove all its entitlements on a particular application during Leaver events. Rapid Setup is designed to simplify the configuration of common identity lifecycle processes, including handling leaver (termination) events. When configuring these events, you can specify actions such as disabling accounts and removing entitlements from specific applications as part of the termination process.

SailPoint IdentityIQ Rapid Setup Guide

SailPoint IdentityIQ Lifecycle Manager Guide (Sections on Lifecycle Event Configuration)

Yes, the statement is true. Both logging and auditing in SailPoint IdentityIQ can have a negative influence on performance because they involve additional function calls within the application. These processes generate data that needs to be stored, which can impact performance if not managed properly. Extensive logging and auditing, particularly at high levels of detail, can lead to increased I/O and storage usage, potentially slowing down system operations.

SailPoint IdentityIQ Performance Tuning Guide

SailPoint IdentityIQ Logging and Auditing Guide (Impact on Performance)

No. The proposed XML is not correct because the reference class is wrong. In IdentityIQ, rule libraries are represented through rule objects used as reusable BeanShell libraries. When a rule references a common library, the referenced object should be a Rule object, not a nonstandard sailpoint.object.RuleLibrary class. The correct pattern is to reference the library as a rule by name under the rule’s referenced-rules section. Rule libraries allow shared methods and reusable code to be included across multiple rules, which is important for reducing duplication and maintaining consistent logic. However, XML object references must use the correct IdentityIQ object class. If the class does not correspond to the persisted object type, the import or runtime resolution can fail. The concept of referencing a common rules library is valid, but this specific code is not. References/topics: IdentityIQ Engineer — Rule libraries, ReferencedRules XML, Rule object references, BeanShell code reuse, XML object configuration.

This is not a valid step for creating a custom audit event and associated report. A Custom Certification Event Schedule relates to certification scheduling or certification-event processing, not to defining a new audit action in the audit framework. A ruleRunner task can execute a rule, but simply creating a certification event schedule and ruleRunner task does not establish a custom audit event type, does not register the event in AuditConfig, and does not create a report capable of querying that audit data. For a custom audit event, the engineer must define the audit action/event, ensure the code path writes the audit event with the appropriate attributes, and then create or configure a report that can retrieve and display those audit records. The proposed solution is pointed at the wrong subsystem. It confuses certification scheduling automation with audit event definition and reporting. References/topics: IdentityIQ Engineer — AuditConfig, AuditAction, custom audit events, audit reporting, ruleRunner task limitations.

No. The account attribute is intended to function as a privileged-account flag , so the resulting value should represent one Boolean state for each account: privileged or not privileged. Nothing in the stated requirements indicates that the attribute needs to contain multiple simultaneous values.

IdentityIQ uses the Multi-Valued property for attributes that legitimately contain collections of values. Typical examples include group memberships, roles, permissions, or entitlement attributes where a single account can hold many values at once. A privilege flag does not have that structure.

Selecting Multi-Valued would change how IdentityIQ interprets and processes the attribute. Instead of treating it as a single value such as true or false, IdentityIQ would treat the attribute as a collection. That complicates rule comparisons, policy evaluation, search behavior, and attribute handling without satisfying any stated business requirement.

The fact that data may be evaluated from more than one source does not make the resulting attribute multi-valued. Multiple input sources can still produce one calculated Boolean result.

Therefore, Multi-Valued is not needed.

References/topics: IdentityIQ Engineer — single-valued versus multi-valued schema attributes, Boolean privilege flags, entitlement attributes, application schema design.

=======

No. Rapid Setup provides a simplified attribute-based manager correlation mechanism, but it does not provide the Rapid Setup user with a custom Manager Correlation Rule configuration option.

For manager correlation in Rapid Setup, the engineer selects an application attribute containing the manager reference, chooses the comparison operator, and maps that value to an IdentityIQ identity attribute. For example, an application ' s managerEmail attribute could be mapped to the IdentityIQ email attribute. Rapid Setup permits one manager-correlation method for each application.

IdentityIQ itself does support a Manager Correlation Rule , but that is a different configuration path. SailPoint documents Manager Correlation Rule as an application rule used when a simple manager-attribute mapping is insufficient. Such rule-based logic is configured through the application ' s normal Rules configuration rather than through Rapid Setup.

This distinction is important because the existing bank already asks whether account correlation using a rule can be performed through Rapid Setup and correctly answers No. The video proposition specifically changes the subject to manager correlation , making it a separate DOMC question.

References/topics: IdentityIQ Engineer — Rapid Setup, Manager Correlation, attribute-based correlation, Manager Correlation Rule, application Rules tab.

=======

Yes, defining account correlation via a rule is an action that can be performed as part of configuring an application definition in SailPoint IdentityIQ. Account correlation rules are often used to determine how accounts from different sources are linked to identities within IdentityIQ. These rules allow for complex logic to be applied when matching accounts to identities, beyond simple attribute matching.

SailPoint IdentityIQ Administration Guide (Section on Account Correlation)

SailPoint IdentityIQ Application Configuration Guide (Using Rules for Account Correlation)

Yes, " Business Role " is a default role type available in SailPoint IdentityIQ that a manager can request during the access request process. Business Roles typically represent a collection of entitlements or access rights that align with specific job functions or responsibilities within an organization. Managers can use this role type to extend or modify the access granted to an employee.

SailPoint IdentityIQ Role Management Guide

SailPoint IdentityIQ Administration Guide (Sections on Role Types and Access Request)