IdentityIQ-Engineer SailPoint Certified IdentityIQ Engineer Questions and Answers

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)

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. Setting the length of an IdentityIQ extended String attribute to 9000 is not a supported general mechanism for storing an identity image. The length value in IdentityExtended.hbm.xml influences how Hibernate maps the String property to a database column. It therefore has database-specific consequences and must not be treated as an arbitrary storage-capacity control.

The standard IdentityIQ extended-attribute configuration uses String properties with much smaller lengths—for example, length= " 450 " —specifically so the resulting columns remain suitable for searching and indexing. SailPoint ' s own configuration commentary warns that database platforms have different VARCHAR limitations and that sufficiently large String definitions may cause Hibernate to map the value to a LOB/blob-like type that cannot be used in the same way for searches.

An image is binary content and should not be modeled merely by making an extended searchable String column extremely large. Even an encoded image can exceed practical database/index limits and introduces unnecessary Identity Cube and persistence overhead.

Therefore, length= " 9000 " is not a prescribed IdentityIQ image-storage configuration.

References/topics: IdentityIQ Engineer — IdentityExtended.hbm.xml, extended properties, Hibernate mappings, VARCHAR limits, searchable attributes, database schema design.

=======

Adding a new object attribute to the Application ObjectConfig in IdentityIQ is not sufficient 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 like iiq extendedSchema.

SailPoint IdentityIQ Configuration Guide (ObjectConfig and Schema Management)

SailPoint IdentityIQ Administration Guide (Database Schema Extension)

The statement is false. 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.

SailPoint IdentityIQ Logging and Auditing Guide

SailPoint IdentityIQ Administration Guide (Syslog Configuration and Log4j Integration)

The statement is incorrect. When writing and executing source mapping rules to populate identity attributes, the rule itself does not need to persist the identity attribute to the database. In SailPoint IdentityIQ, once the value for an identity attribute has been calculated by a source mapping rule, IdentityIQ automatically handles the persistence of this attribute to the database as part of the aggregation or provisioning process. The developer does not need to explicitly persist the attribute; this is managed by the system.

SailPoint IdentityIQ Source Mapping Guide

SailPoint IdentityIQ Administration Guide (Aggregation and Attribute Mapping Sections)

No. IdentityExtended.hbm.xml defines extended persistence mappings for additional Identity attributes; it does not represent the complete set of attributes available on the Identity object. Therefore, seeing custom mappings such as employeeId and status in the displayed configuration does not mean that these are the only identity attributes in the installation.

IdentityIQ requires several fundamental identity attributes for normal product operation. SailPoint specifically identifies core attributes including ID, manager, email, firstname, and lastname in Identity Mapping configuration. These standard properties exist independently of customer-defined extended fields. The numbered extended properties and custom named properties shown in IdentityExtended.hbm.xml supplement that standard Identity object model rather than replacing it.

The Word bank contains a different proposition for this same IdentityExtended.hbm.xml scenario concerning how many additional searchable attributes can be configured, demonstrating that the extended mapping is specifically concerned with schema extension rather than defining the entire Identity object.

Therefore, the conclusion that firstname and lastname would be missing simply because they are not shown in this extended mapping is incorrect.

References/topics: IdentityIQ Engineer — Identity object, Identity Mappings, IdentityExtended.hbm.xml, core identity attributes, extended attributes, searchable attributes.

=======

No. This proposed lifecycle sequence does not fit the standard Rapid Setup configuration available for a Mover event. A mover represents a change in an existing identity ' s organizational state—for example, a department, location, position, or other employment change—where access typically needs to be recalculated or adjusted rather than handled as terminating access.

The proposed process instead describes a termination-style account lifecycle: immediately disable an account and subsequently delete that account after a 30-day retention period. That pattern is appropriate to Leaver/termination processing, where access is first blocked and an account may subsequently be removed after a configured retention period.

The distinction is reinforced by the question bank. It already contains a different Mover proposition—“Disable an account and remove all its entitlements on a particular application during Mover events”—and marks that Rapid Setup scenario No. The video proposition changes the operation to delayed account deletion, so it remains a distinct DOMC item rather than a duplicate.

Therefore, standard Rapid Setup Mover configuration does not provide the stated disable-then-delete-after-30-days behavior.

References/topics: IdentityIQ Engineer — Rapid Setup, Mover lifecycle events, Leaver lifecycle events, account disablement, delayed account deletion, lifecycle-event configuration.

Yes, this action can be performed as part of configuring an application definition in IdentityIQ. When defining an application, you can specify provisioning policies, including which users should be provisioned with a basic account as part of a joiner event. This is typically done by setting up account creation rules or provisioning policies that trigger when a new user (joiner) is detected, ensuring they receive the necessary basic accounts and entitlements.

Therefore, the correct answer is A. Yes.

An Application Owner Certification is primarily used to certify entitlements and roles associated with specific applications. It involves application owners reviewing access within their applications, which is useful for ensuring that access aligns with the intended security policies for that application.

However, in the context of ensuring that roles include the correct entitlements across the entire role model, a more suitable certification type would be a Role Composition Certification. This type specifically focuses on validating the composition of roles, including the entitlements they aggregate.

Therefore, an Application Owner Certification will not fully achieve the goal of ensuring all roles include the correct entitlements. The correct answer is B. No.

Creating a custom audit event and setting up an associated report involves steps such as defining the audit event, modifying the audit configuration, and creating a custom report using the SailPoint IdentityIQ reporting framework. Simply creating a Data Export task does not fulfill these requirements. A Data Export task is used for exporting data from IdentityIQ and is unrelated to the creation of custom audit events or custom reports. Refer to the SailPoint IdentityIQ Reporting Guide and the IdentityIQ Audit Framework documentation for more information on correctly creating and configuring custom audit events and reports.

The configuration option " Comment Character " is not required when setting up a SCIM 2.0 application in SailPoint IdentityIQ. The " Comment Character " option is generally used for handling comment lines in flat files or CSV file-based connectors. Since SCIM 2.0 is a RESTful API-based protocol designed for managing identities in a standardized way, this option does not apply to SCIM 2.0 integrations. Therefore, it is not a necessary configuration when working with SCIM 2.0 applications.

SailPoint IdentityIQ SCIM 2.0 Integration Guide

SailPoint IdentityIQ Application Configuration Guide (SCIM and REST API sections)

This is not a clean joiner lifecycle event. A joiner event normally represents a person newly entering the organization or being newly onboarded into managed access, usually requiring new identity setup, new accounts, baseline access, roles, approvals, and provisioning. The proposed scenario describes a contractor whose previous relationship ended, whose accounts were disabled, and who now has a new contract requiring previous accounts to be enabled. That is closer to a rehire/reactivation or account-enable lifecycle event than a first-time joiner. The distinction matters in IdentityIQ because a true joiner process may create accounts and assign initial access, while a rehire/reactivation process may restore, enable, or reassess previously existing accounts and access. Treating this as a joiner could create duplicate accounts or duplicate access instead of properly reactivating existing Links/accounts. References/topics: IdentityIQ Engineer — Lifecycle Manager, joiner event, rehire/reactivation, account enablement, identity lifecycle workflow design.

Mail Server Certificate is not a universally required IdentityIQ mail setting for successful SMTP communication. IdentityIQ needs the SMTP host/server information, the SMTP port, and, where required by the environment, authentication details such as username and password, plus TLS/SSL-related settings. A mail server certificate may be relevant in environments using encrypted SMTP where the certificate chain must be trusted by the JVM truststore, but that does not make “Mail Server Certificate” a required IdentityIQ configuration field in every SMTP setup. Many SMTP relay configurations work with host and port only, or with host, port, and credentials. The key engineering distinction is between mandatory connection parameters and optional security/trust configuration. If TLS validation fails, certificate trust may need to be configured at the Java/application-server layer, but it is not the baseline required IdentityIQ mail-server setting. References/topics: IdentityIQ Engineer — email notifications, SMTP configuration, mail host, SMTP port, authentication, TLS/SSL trust configuration.

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.

Yes, this is indeed one of the primary purposes of an IdentityIQ certification. Certifications are conducted to attest to a user ' s system access, ensuring that each user has appropriate and justified access rights to applications, data, and systems within the organization. This is central to IdentityIQ’s access governance and compliance processes.

SailPoint IdentityIQ Certification Guide

SailPoint IdentityIQ Governance Overview

The statement " All Identity Mappings must use a rule to set the identity attribute " is incorrect. While source mapping rules can be used to populate identity attributes dynamically, it is not mandatory for all identity mappings to rely on a rule. Identity mappings can also be configured using direct mappings, where attributes from a source are directly mapped to IdentityIQ attributes without any rule-based logic.

Therefore, the correct answer is B. No.

The statement that a user ' s access to the Identity Warehouse is controlled by the QuickLink Populations they are a member of is incorrect. QuickLink Populations in IdentityIQ are used primarily for grouping identities for specific operations, such as access reviews, certifications, or specific application provisioning, rather than directly controlling access to the Identity Warehouse.

Access to the Identity Warehouse is governed by role-based access controls (RBAC), scopes, and the user ' s entitlements within IdentityIQ. These determine what data and functionality a user can access, including the information in the Identity Warehouse.

Thus, the correct answer is B. No.

This statement is not correct. IdentityIQ syslog event searching is not limited only to Incident Code lookups. Incident Code is useful when a user-facing error displays a code that can be traced back to a logged system event, but syslog analysis is broader than that. Administrators and engineers use syslog data to investigate operational errors, workflow failures, connector issues, provisioning errors, aggregation failures, authentication problems, and application exceptions. Advanced Analytics and log-search capabilities are intended to help filter and locate system events using more than a single incident-code value. Treating Incident Code as the only searchable attribute would make syslog analysis nearly useless for routine troubleshooting where no user-facing incident code is available. The correct engineering view is that Incident Code is one important search key, not the exclusive search mechanism. References/topics: IdentityIQ Engineer — syslog search, Advanced Analytics, incident code troubleshooting, system-error diagnosis, operational logging.

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 is B. No.

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.

=======

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. This is a valid Identity search use case because the relationship between an employee and their manager is normally represented on Identity objects through attributes such as manager, manager ID, supervisor, or reporting relationship. If the identity cube contains the manager relationship, Identity search or Advanced Analytics can be used to filter identities whose manager equals a specific person and then count the returned identities. This is completely different from using Syslog for the same purpose. The Word bank rejects Syslog for this scenario because Syslog is a logging facility, not an organizational data query mechanism. But the video asks about the Identity search type, and Identity search is the correct object domain for employee reporting relationships. The engineer must ensure that the manager attribute is populated and searchable or otherwise available to the search interface. References/topics: IdentityIQ Engineer — Identity search, manager attribute, identity cube, reporting relationships, Advanced Analytics filters.

The correct sequence of steps to turn on Certifications logging at the severity log level of trace is as follows:

Edit the file: [IdentityIQ installation] > WEB-INF > classes > log4j.properties.

This step involves accessing the configuration file where logging parameters are managed. The log4j.properties file is crucial for adjusting logging settings such as the log level for specific modules in SailPoint IdentityIQ.

Uncomment the out-of-the-box logger #log4j.logger.sailpoint.api.Certification=info.

This step enables the logger for Certification by removing the comment from the respective line in the log4j.properties file. This makes the logger active for the certification process.

Change the log level to trace and save.

After uncommenting the logger, change the log level from info to trace. The trace level provides the most detailed logging, capturing comprehensive information about the certification process for troubleshooting.

Restart the application server.

Restarting the application server is necessary for the changes in the log4j.properties file to take effect. SailPoint IdentityIQ reads the updated configuration during the startup process.

Comprehensive Detailed Explanation with All IdentityIQ Engineer References

Editing the log4j.properties file is a standard practice in SailPoint IdentityIQ for configuring logging. This file, located in the WEB-INF/classes directory, controls how and what IdentityIQ logs for different components.

Uncommenting the specific logger is needed to ensure that the system is logging the events related to certification. The commented line #log4j.logger.sailpoint.api.Certification=info can be found in the default configuration and needs to be activated for proper logging.

Setting the log level to trace is crucial because trace provides the most detailed logging, which is essential for deep debugging or tracking granular details about the certifications in IdentityIQ.

Restarting the server ensures that the changes to the logging configuration are applied, as the settings in log4j.properties are only read during the startup phase.

SailPoint IdentityIQ Log Management and Troubleshooting Guide (section on adjusting log levels and configurations).

Yes. The Run Rule facility is useful for isolated BeanShell experimentation and debugging. An engineer can retrieve or construct an IdentityIQ object, invoke methods or modify values in the rule, convert or return the resulting object/XML representation, and inspect the output to understand how the operation affected the object ' s structure.

The critical distinction is between testing object manipulation and displaying the resulting representation versus using Run Rule as a general-purpose persistence tool. The existing Word bank correctly rejects the broader statement that Run Rule ' s benefit is creating, modifying, or deleting SailPoint database objects. It separately recognizes displaying the return value of simple code as a valid Run Rule benefit.

The video proposition is aligned with the second use case. Printing an object ' s XML after invoking methods on it gives the engineer a controlled way to inspect changes and understand SailPoint object behavior while developing or troubleshooting BeanShell logic.

Production caution remains necessary because arbitrary rules can call persistence APIs and cause side effects.

References/topics: IdentityIQ Engineer — Debug-Object, Run Rule, BeanShell testing, SailPointObject XML, object manipulation, return values.

=======

The statement is false. 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.

SailPoint IdentityIQ Workflow Guide

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

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)

The proposed solution suggests changing the Email Notification Type to " Redirect to file using FTP protocol " under Global Settings > Configure IdentityIQ Settings > Mail Settings. However, IdentityIQ does not provide an option to redirect emails to a file using the FTP protocol directly through the Global Settings in the application.

Typically, to test generated emails in a non-production environment, you would change the Email Notification Type to " Redirect to File " (if the option is available) or configure an SMTP server with a different setup that captures emails in a file or a specific mailbox designed for testing purposes. The specific steps for testing email generation may vary, but the solution as stated does not align with standard IdentityIQ practices.

Thus, the correct answer is B. No.

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.

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.

=======

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.

No. Identity search should not be used to diagnose system errors presented in the UI. A UI error is normally investigated through syslog, application logs, stack traces, incident codes, debug logging, or server-side log files. Identity search returns identity records and identity-related data; it does not expose detailed exception traces, system error messages, connector failures, workflow stack traces, or servlet/application errors. The Word bank’s Syslog version confirms the correct direction: Syslog can be used to identify details of a system error presented in the UI because IdentityIQ logs detailed errors and stack traces there. Since this video item changes the search type to Identity, the answer changes. Identity search may help locate the user affected by a failed operation, but it is not the tool for retrieving the error details themselves. References/topics: IdentityIQ Engineer — Identity search, Syslog search, incident code, UI error troubleshooting, logging and diagnostics.

Yes. This is the classic joiner lifecycle event. The person has not previously been with the company, has now been hired, and needs new access and new accounts. In IdentityIQ Lifecycle Manager terms, a joiner process usually starts from an authoritative-source change such as a new HR record. The process may create or activate the Identity Cube, assign birthright roles, request or automatically provision accounts, calculate policies, trigger approvals, and send notifications. Unlike rehire or reinstatement scenarios, there are no existing disabled accounts to restore. The access model should be built from onboarding rules, role assignment logic, provisioning policies, application create policies, and approval workflows. This is exactly why joiner workflows exist: to standardize new-person onboarding and ensure access is created consistently, securely, and audibly. References/topics: IdentityIQ Engineer — joiner lifecycle event, LCM onboarding, birthright access, account creation, provisioning policy, role assignment.

Yes. Once the custom audit action and report definition have been created and loaded into IdentityIQ, configuring and scheduling the resulting custom report through Intelligence > Reports is a valid step in completing the reporting solution.

IdentityIQ ' s reporting framework exposes standard and custom report definitions through the Reports UI. A report can be opened and configured with the required filters or parameters, saved as an appropriate report instance, executed immediately, or scheduled for future and recurring execution. SailPoint documents that reports can be scheduled to execute once, hourly, daily, weekly, monthly, quarterly, or annually.

For a custom audit-report implementation, this scheduling step logically follows the underlying development work: the custom AuditAction must first be defined, executable logic must actually create AuditEvent records using that action, and a custom report definition must be created that queries the required audit data. Scheduling the report does not replace any of those earlier implementation steps, but it is a legitimate final operational step once the custom report exists.

Therefore, this proposed solution is one valid step toward accomplishing the stated goal.

References/topics: IdentityIQ Engineer — custom AuditEvent reporting, custom TaskDefinition reports, Intelligence > Reports, report scheduling, recurring compliance reporting.

The " Name " configuration option is required when 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.

SailPoint IdentityIQ SCIM 2.0 Application Configuration Guide

SailPoint IdentityIQ Administration Guide (Application Setup and Naming Conventions)

Setting the configuration option " Edit Mode: Read Only " on the account attribute would not meet the requirements as specified. The requirement to " Calculate from: Keystore application, responsibility-code attribute " implies that the attribute needs to be dynamically calculated or updated based on another attribute. If the attribute is set to " Read Only, " it cannot be modified, which would prevent it from being calculated or updated as needed. Therefore, " Edit Mode: Read Only " should not be used in this scenario.

SailPoint IdentityIQ Administration Guide (Sections on Account Attributes and Attribute Calculation)

SailPoint IdentityIQ Configuration Guide (Field Properties and Edit Modes)

Yes, the current version and patch level of IdentityIQ can be found through the Debug-About page. The Debug-About page in SailPoint IdentityIQ provides critical information about the system, including the software version, patch level, and other configuration details. This page is a useful resource for administrators to quickly verify the IdentityIQ version and ensure that the correct patches have been applied.

Therefore, the correct answer is A. Yes.

The statement suggests moving the XML file into IIQ_HOME/WEB-INF/database as part of the process to import SailPoint XML file objects into IdentityIQ. However, this is not a valid step for importing XML objects.

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

Use the iiq console command-line tool provided by SailPoint to import the XML file.

The command typically looks like: iiq console import < filename > .xml.

The XML file does not need to be moved to any specific directory like WEB-INF/database for the import process.

Moving the XML file into the WEB-INF/database directory does not align with the documented process and does not facilitate the import. The correct answer is B. No.

No. An individual SPRight is a granular IdentityIQ product right, but roles do not normally grant an arbitrary standalone SPRight directly as a role entitlement. IdentityIQ groups SPRights into Capabilities , which provide logical collections of rights associated with administrative or functional job responsibilities.

The Role Editor provides a Granted IdentityIQ User Rights section where an engineer can associate IdentityIQ capabilities and scopes with a role. When that role is assigned and role provisioning is processed through Identity Refresh, the corresponding capabilities and scopes can be granted to the identity. This is the supported role-level abstraction.

The distinction matters because an SPRight controls granular access to specific IdentityIQ UI functions, tools, pages, or operations, while a Capability groups one or more SPRights into a maintainable authorization construct. Directly treating a single SPRight as an ordinary role option bypasses the intended rights-to-capability model.

Therefore, although a role can grant IdentityIQ user rights indirectly through configured capabilities, the proposed statement that the role is configured to include a single SPRight object is not the valid role configuration model.

References/topics: IdentityIQ Engineer — SPRight, Capability, Granted IdentityIQ User Rights, Role Editor, authorization model.

=======

Schedule Policy Composition Certification is not a valid action for handling an individual Account Policy violation. A policy violation owner acts on a violation by making a decision about that violation: allow it, remediate it, mitigate it, or route it according to configured compliance processes. A Policy Composition Certification is a separate governance activity used to review the construction or definition of policies; it is not an immediate action available on a single violation record. The proposed solution also mismatches the policy type. The stem concerns an Account Policy violation, which typically relates to account-count or account-condition rules, not policy-composition review. The Word bank separately identifies Account policies as limiting the number of accounts a user can have on a system. Scheduling a certification might help long-term governance hygiene, but it does not dispose of the current policy violation. References/topics: IdentityIQ Engineer — Account Policy violations, violation owner actions, certification types, policy composition certification, compliance remediation workflow.

In SailPoint IdentityIQ, what users can see and do is indeed partly controlled by their authorized scope. Authorized scopes define the range of objects (such as identities, roles, applications) that a user has access to. Scopes can be applied to limit access based on specific criteria, ensuring that users only interact with the data and functionalities relevant to their role or responsibility within the organization.

For example, a user with access to a specific scope may only view or manage identities within a certain department or geographical location, depending on how the scope is configured.

Therefore, the correct answer is A. Yes.

Yes. IdentityIQ email templates use the Apache Velocity Template Language (VTL) , and these forms are valid Velocity reference syntaxes. $identityName is the normal shorthand reference. ${identityName} uses formal notation, which is particularly useful when the variable reference must be clearly separated from immediately adjacent characters. This permits the reference to be embedded or concatenated into surrounding text without Velocity interpreting the additional characters as part of the variable name.

The exclamation-mark form is a quiet reference . With $!identityName—or the formal quiet form $!{identityName}—Velocity suppresses the literal reference when the underlying value is null. This is useful in email templates because optional values should not produce visible strings such as $identityName when no value was supplied.

SailPoint ' s IdentityIQ documentation explicitly presents $identityName, ${identityName}, and $!identityName as VTL variable-reference forms and notes that the alternate forms are required in special situations. IdentityIQ email templates pass template arguments into the VelocityContext for this substitution.

References/topics: IdentityIQ Engineer — EmailTemplate objects, Apache Velocity, VTL references, formal references, quiet references.

=======

Yes. If a user already has an account on an application and needs the ability to request an additional/new account through Manage User Access, the relevant LCM/QuickLink configuration must permit requesting new accounts. The proposed setting, “Allow requesting new accounts,” is specifically aligned with that requirement. Manage User Access and Manage Accounts behavior is controlled through Lifecycle Manager quicklink and population configuration, which determines what actions are visible and available to eligible users. Without enabling new-account requests for the appropriate QuickLink population, the user may only be able to manage existing account access or request entitlements for current accounts, not initiate a new account request on that application. This setting must also align with the application’s provisioning support and account creation policy. The configuration grants the UI/request capability; successful fulfillment still depends on application schema, create policy, approvals, and provisioning workflow. References/topics: IdentityIQ Engineer — LCM, Manage User Access, Manage Accounts QuickLink, QuickLink population, new account request, provisioning policy.

The statement that the Debug-Logging page does not have to be reloaded when the log4j file is altered while the application server is running is incorrect. In SailPoint IdentityIQ, if you modify the log4j configuration file while the application is running, you generally need to reload the Debug-Logging page to reflect those changes. Without reloading, the page will not display the updated logging configurations, and the changes will not take effect until the application server or the logging system within the server acknowledges those changes.

Therefore, the correct answer is B. No.

Yes. IdentityIQ provides several core identity properties that are directly available as standard search criteria without requiring them to be implemented as customer-defined extended searchable attributes. These include First Name, Last Name, Display Name, Email, and Manager . Identity Search exposes these properties separately from the configurable section called Searchable Attributes , which contains additional identity attributes created and designated as searchable during deployment.

This distinction is important when interpreting IdentityExtended.hbm.xml. The extended Hibernate mapping is primarily concerned with additional database-backed attributes that a customer wants to search efficiently. It does not mean that every searchable identity property must consume one of the numbered extended1, extended2, and similar columns.

Current IdentityIQ documentation lists Last Name, First Name, Display Name, Email, and Manager directly among Identity Search criteria, with separately configured searchable attributes presented in their own category. Therefore, the proposed solution correctly identifies standard searchable identity information supplied by IdentityIQ.

References/topics: IdentityIQ Engineer — Identity Search, Identity Mapping, standard identity attributes, searchable extended attributes, IdentityExtended.hbm.xml.

=======

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.

This proposed solution is not correct. In IdentityIQ, features and functional access are controlled primarily through capabilities, not scopes. Capabilities determine whether a user can perform administrative or functional actions such as managing identities, accessing reports, configuring applications, launching tasks, or using privileged pages. Scopes, by contrast, are generally used to restrict which objects or data a user can see or act upon. For example, a scoped administrator may only be able to view or administer identities, applications, or work items within an assigned organizational boundary. That is object/data visibility control, not feature enablement. Saying that scopes control “the features that are used” confuses two different authorization layers. The correct IdentityIQ distinction is: capabilities control functional permissions, while scopes constrain object access boundaries. References/topics: IdentityIQ Engineer — authentication, authorization, capabilities, scopes, delegated administration.

A Post-Iterate Rule in SailPoint IdentityIQ is a type of connector rule that is executed after each account from the source system (e.g., SQL Loader application) has been read during the aggregation process. This rule allows for additional processing or customization of the data after the account has been iterated over. According to SailPoint IdentityIQ documentation, configuring a Post-Iterate Rule enables the execution of logic after each account ' s data has been processed, confirming that the given statement is valid. Refer to the SailPoint IdentityIQ Connector Development Guide for detailed information on rule execution during aggregation.

Yes, the typical input variables for a rule are listed in the BeanShell rule editor in IdentityIQ, based on the rule registry. When you create or edit a rule in IdentityIQ using the BeanShell editor, the available input variables that are relevant to the rule type are typically pre-defined and listed based on the rule registry. These input variables provide context and data that the rule can operate on, and their availability helps guide the rule development process.

Therefore, the correct answer is A. Yes.

This is a valid implementation pattern. The workflow requirement has three routing outcomes, and the proposed solution expresses them as three explicit transition elements. The first transition routes to Stop when the approval flag is false, which corresponds to the Reject or back action. The second transition routes to Audit when the comment variable is not null or empty, using sailpoint.tools.Util.isNotNullOrEmpty(comment). That satisfies the condition that the Approve action was used and the returned form field has a value. The final transition to Provision has no condition, making it the default fallback when the prior transition conditions are not satisfied. This is the correct style for workflow routing because the destination steps are explicitly declared through the to attribute, and the conditional routing is attached to each transition rather than relying on an invalid free-form return block. References/topics: IdentityIQ Engineer — workflow transitions, when conditions, script expressions, form approval routing, default workflow transition behavior.

Yes. Bundle is the IdentityIQ object model class used for roles, and it can be extended to store client-specific role metadata through the supported extended schema process. Custom role programs often require extra attributes on roles, such as risk category, ownership tier, regulatory classification, business unit, lifecycle state, approval model, or migration metadata. Updating the corresponding Hibernate mapping file is part of how persistent object extensions are introduced. However, the mapping update is only one step. The engineer must generate the database schema update script, apply it to the database in the correct operational state, and update ObjectConfig so IdentityIQ understands and exposes the custom attribute properly. The Word bank describes this same extension sequence: update the mapping layer, generate the schema script, run it on the IdentityIQ database, then update ObjectConfig after restart. Therefore, Bundle is a valid object for this type of client-specific data extension. References/topics: IdentityIQ Engineer — Bundle object, role extension, Hibernate mapping, extended schema, ObjectConfig, database schema update.

Yes. Out-of-the-box LCM workflows commonly support configurable notification behavior, and email templates can be selected or referenced through workflow variables, arguments, or workflow configuration. IdentityIQ workflows use email templates to generate notification content for approvals, requests, provisioning outcomes, policy violations, reminders, and other lifecycle events. The ability to control which template is used allows implementers to customize communications without rewriting the whole workflow. This is a valid use of workflow configuration because the workflow is responsible for sending or triggering notifications during lifecycle processing. The engineer still needs to ensure the referenced EmailTemplate object exists, contains the correct variables for the workflow context, and is suitable for the intended recipient. But conceptually, specifying the email template for notifications is exactly the type of behavior that can be controlled through LCM workflow configuration rather than through application schema or identity-attribute configuration. References/topics: IdentityIQ Engineer — LCM workflow variables, EmailTemplate objects, notification configuration, approval emails, workflow-controlled messaging.

Yes. Configuring a role to contain a set of entitlements is fundamental to IdentityIQ role modeling. IdentityIQ defines a role as a collection of access that enables an identity to perform a business or technical function. For IT-oriented roles in particular, entitlement profiles define the access that is provisioned when the role is assigned. An entitlement can represent a specific value of an account attribute, such as membership in an Active Directory group, or a permission on a target application.

The Role Editor includes an Entitlements section in which engineers can create profiles and associate multiple entitlements with the role. SailPoint documentation specifically states that a profile is a set of entitlements on an application and that the engineer can specify as many entitlements as required for a role. This allows complex access requirements to be packaged into a governed reusable role rather than individually assigning each entitlement to every identity.

Therefore, the proposed solution is valid.

References/topics: IdentityIQ Engineer — Role Editor, IT Roles, entitlement profiles, role provisioning, role-based access model.

=======

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.

No. The key phrase is “inherited from an assigned Business Role.” IdentityIQ distinguishes between roles that are directly requestable and technical access that an identity receives because another role requires or contains it.

An IT Role can certainly be part of the IdentityIQ role model and can provide technical entitlement access. A Business Role can also be related to lower-level roles through required or permitted role relationships. However, when an IT Role is inherited automatically because an assigned Business Role requires it, that inherited access is not independently presented as a new role for the manager to request—the Business Role assignment is what drives the inherited role relationship.

Permitted roles are different because they can define additional role access that becomes eligible or meaningful in the context of another role. That distinction between automatic inheritance and requestability is important in access-model design.

The Word bank already contains the same manager-request stem with Business Role, which it marks valid, and another with HR Role, which it marks invalid. This inherited-IT-role proposition is separate.

References/topics: IdentityIQ Engineer — Business Roles, IT Roles, required roles, permitted roles, inherited role access, access requests.

=======

No. ManagedAttribute objects represent managed entitlement or account-group values from applications. They are not generally viewed on the Policy tab of the View Identity QuickLink. The Policy tab is used for policy-related information such as policy violations or compliance policy context, not for listing all entitlements associated with the identity. A user’s entitlements and accounts are normally viewed through identity access/account-related tabs or identity cube access views, depending on UI configuration. This proposed statement confuses ManagedAttribute entitlement data with policy-violation data. A ManagedAttribute may be involved in a policy violation, certification item, access request, or entitlement display, but that does not mean all ManagedAttribute objects associated with an Identity are visible from the Policy tab. The correct engineering distinction is: ManagedAttribute equals governed entitlement metadata; Policy tab equals policy/compliance information. References/topics: IdentityIQ Engineer — ManagedAttribute, Identity Cube, View Identity QuickLink, entitlement display, policy violations.

Yes. In IdentityIQ, a ManagedAttribute represents managed entitlement metadata associated with an application attribute/value, and it can have an Identity object assigned as its owner . Ownership is an important governance property because the entitlement owner can participate in approval routing, certifications, access-request decisions, remediation, and general accountability for the managed access.

This does not mean every ManagedAttribute is automatically owned by an Identity, nor does it mean its owner must be the same identity that owns the associated Application. Application ownership and entitlement ownership are independent governance relationships. For example, an Active Directory application may have one application owner while individual AD groups represented as ManagedAttributes have different business owners.

The wording “can have” is therefore important. IdentityIQ supports an Identity as the owner of the ManagedAttribute. Depending on configuration, ownership can be populated manually, through aggregation/customization, or through entitlement-management processes.

Do not confuse this relationship with the ManagedAttribute ' s required application context: the ManagedAttribute identifies governed access originating from an Application, while its owner identifies responsibility for that access.

References/topics: IdentityIQ Engineer — ManagedAttribute object, Entitlement Catalog, entitlement ownership, Application ownership, approval routing, entitlement certifications.

=======

Yes. A Manager Correlation Rule is specifically intended for situations where IdentityIQ must establish the manager/direct-report relationship but a straightforward attribute-to-attribute mapping is insufficient. In a simple implementation, IdentityIQ can correlate an application attribute containing the manager identifier directly to an identity attribute. Here, however, the organization has inherited several employee-number formats through mergers. That requires normalization, transformation, conditional comparison, or other custom matching logic before the manager identity can be resolved.

SailPoint explicitly documents that Manager Correlation normally uses an application attribute and an identity attribute, but when the matching requirement is more complex than a simple field match, a Manager Correlation Rule can implement the correlation programmatically. The rule can normalize the different employee-number formats, generate appropriate comparison values, search for the matching Identity object, and return the manager relationship required during identity processing. A normal account Correlation Rule addresses account-to-identity correlation and is therefore not the precise rule type for this requirement.

References/topics: IdentityIQ Engineer — Manager Correlation Rule, authoritative-source aggregation, Identity Cube manager relationships, complex correlation logic, Application Definition Rules.

=======

In SailPoint IdentityIQ, when dealing with a policy violation of the type " Role Separation of Duties (SOD) Policy, " there are specific actions that the policy violation owner can take. These options typically include:

Mitigate: Applying a mitigating control to the violation.

Remediate: Addressing the violation by removing or altering access.

Accept: Acknowledging the violation without making changes, which usually requires justification.

Forward: Assigning the violation to another individual or group for resolution.

The option " Schedule Policy Composition Certification " is not a valid action for addressing a Role SOD Policy violation directly. The concept of scheduling a certification is related to periodic review processes, not immediate policy violation handling. Certification campaigns are scheduled and executed to review roles, entitlements, or policies, but this is not an action taken in response to a specific policy violation.

Thus, " Schedule Policy Composition Certification " is not an appropriate or valid option in this context, and the correct answer is B. No.

The statement is incorrect. Email templates in SailPoint IdentityIQ are not restricted to just Identity object attributes or methods. They can access attributes and methods of any object passed to the template through its input arguments, including WorkItems, CertificationItems, and others. The template system allows the use of various objects’ properties as long as they are properly referenced within the script or template context.

No, this is not a valid action. When setting up or using the Services Standard Build (SSB) for a SailPoint IdentityIQ instance, the client ' s identityiq.war file should not be placed in the home directory of the build. The WAR file should be deployed to the appropriate application server ' s deployment directory, not in the home directory of the build itself. The SSB process typically involves more structured deployment processes that adhere to best practices for application deployment.

SailPoint IdentityIQ Services Standard Build Guide

SailPoint IdentityIQ Deployment Best Practices

No. IdentityIQ certifications are used to review and attest access, roles, entitlements, account group memberships, policy violations, or other governance items. They are not designed to ensure “SailPoint” itself is compliant with ISO 9001, and ISO 9001 is not a government regulation in the way the proposed solution states. ISO 9001 is a quality management standard, not an access-governance regulation that IdentityIQ certifications directly enforce. An organization may use IdentityIQ certification evidence as part of broader compliance programs, but the certification’s direct purpose is access review: confirming that users have appropriate access and that inappropriate access is revoked, remediated, or justified. The wording is wrong both in target and scope. The certification process supports customer governance/compliance objectives, not SailPoint corporate ISO compliance. References/topics: IdentityIQ Engineer — certification purpose, access review, compliance evidence, entitlement review, role review, governance controls.

Yes. A Boolean datatype is appropriate because the stated purpose is to flag privileged accounts . A flag normally represents a binary condition: the account either satisfies the privileged-account criteria or it does not. Consequently, true and false accurately represent the resulting classification.

The engineer can derive this Boolean from the Financial application ' s privileged attribute and/or calculate the result through logic involving the Keystore application ' s responsibility-code attribute. Once populated, the Boolean value can be referenced reliably from rules and policy conditions and can participate in searchable/analytics configuration when the associated attribute is configured appropriately.

This distinction also resolves the earlier Attribute Type: string proposition. A String could technically hold textual values, but the requirement here is specifically a Boolean privilege flag. Therefore, for this DOMC scenario, Boolean is the configuration that matches the requirement , while String should be answered No.

The bank already tests source mapping and edit mode for the same scenario but does not contain this Boolean proposition.

References/topics: IdentityIQ Engineer — account schema, Boolean attributes, privileged-account classification, source mapping, rules, policies.

=======

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 statement is too absolute. IdentityIQ does not always require the scheduled challenge-period duration to expire before sign-off can occur.

When a challenge period is enabled and revocation decisions exist, the related challenge processing must reach an appropriate completed state before the access review can be signed off. However, IdentityIQ documentation explicitly permits sign-off while the certification is in the challenge phase when all items are complete, all applicable revocation decisions have progressed through the challenge procedure, and no open decisions remain.

Expiration of the configured challenge period is another condition that permits the certification to proceed, but it is not the only possible path. In other words, there is an important difference between saying that challenge processing must be complete and saying that the reviewer must always wait until the full scheduled challenge period expires.

SailPoint ' s Access Review documentation lists both conditions independently: completed challenge processing can permit sign-off, or the challenge period can expire.

Therefore, the proposition “cannot be signed off until after the challenge period ends” is technically false.

References/topics: IdentityIQ Engineer — challenge phase, certification sign-off, completed challenges, revocation procedure, certification lifecycle.

=======

Yes, this is an example of a mover lifecycle event. A mover lifecycle event typically occurs when an individual ' s role or employment status within the organization changes, requiring updates to their accounts and access rights. In this scenario, a contractor whose accounts were previously disabled due to contract expiration needs those accounts re-enabled upon securing a new contract. This reactivation and adjustment of access rights based on a change in employment status fits the definition of a mover event.

Therefore, the correct answer is A. Yes.

Yes, Identity Provisioning Policies can indeed be used to include allowed-values definitions or validation logic on fields within SailPoint IdentityIQ. This ensures that only valid or authorized values can be specified for certain fields, such as when using the " Create Identity " feature to add a new identity. This functionality helps enforce data integrity and compliance with organizational policies by restricting the inputs to predefined or validated options.

SailPoint IdentityIQ Administration Guide (Sections on Identity Provisioning Policies and Field Validation)

SailPoint IdentityIQ Configuration Guide (Policy Enforcement and Validation)

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.

=======

The statement that the application server must be restarted after reloading the logging file through the Debug-Logging page is incorrect. SailPoint IdentityIQ allows you to reload the logging configuration from the Debug-Logging page without restarting the application server. The Debug-Logging page provides a way to dynamically reload the logging settings, including those in the log4j file, so that changes can take effect immediately without the need for a server restart.

Therefore, the correct answer is B. No.

No. Launching certification campaigns is not default Lifecycle Manager functionality. Lifecycle Manager focuses on identity lifecycle and access-request operations such as joiner, mover, leaver processing, access requests, account management, approvals, and provisioning workflows. Certification campaigns belong to IdentityIQ’s access review and compliance/certification capabilities, not LCM’s default functional scope. Certifications are used to review access, roles, entitlements, policy violations, or account/group membership and then require reviewers to approve, revoke, or otherwise act on access. LCM may interact with certification results indirectly because remediation from a certification can trigger provisioning or access changes, but launching the campaign itself is a certification/compliance function. This question tests whether the engineer separates lifecycle-request processing from access-review governance. Mixing them up leads to poor module design and incorrect implementation expectations. References/topics: IdentityIQ Engineer — Lifecycle Manager, access request, provisioning workflows, certification campaigns, Compliance Manager.

No. An Account Group is not a mechanism for selecting a particular subset of user accounts during an Account Aggregation. IdentityIQ distinguishes between Account Aggregation and Account Group Aggregation . Account Aggregation reads account records from the target application and creates or updates Link objects, including the account ' s attributes and entitlements. The population or scope of accounts being aggregated is controlled by connector/application configuration such as search scope, source filters, iteration filters, partitions, or other connector-specific aggregation parameters.

Account Group Aggregation has a different purpose. It reads group or application-object information from applications that have an appropriate group schema. The resulting group information is used to represent governed entitlement objects, support group certifications, and expose group-related information within IdentityIQ.

Consequently, an Account Group is not used as a selector for saying “aggregate these particular accounts” during an Account Aggregation. That requirement must be implemented through the account aggregation configuration itself.

References/topics: IdentityIQ Engineer — Account Aggregation, Account Group Aggregation, Link objects, aggregation filters, group schemas.

=======

No. Create Entitlement is not one of the standard IdentityIQ Lifecycle Manager batch request operation types used for bulk access cleanup. The requirement concerns modifying users ' access: some identities need entitlements added while others need excessive access removed. IdentityIQ provides specific batch operations for those tasks.

SailPoint ' s supported batch request operations include Create Identity, Modify Identity, Create Account, Delete Account, Enable/Disable Account, Unlock Account, Add Role, Remove Role, Add Entitlement , Remove Entitlement , and Change Password. “Create Entitlement” does not appear as a standard batch request operation in this list. The distinction is fundamental: an entitlement is a governed access value represented through the application schema and usually as a ManagedAttribute in the Entitlement Catalog. Creating or maintaining that entitlement definition is different from granting an existing entitlement to identities.

For the described regional cleanup, Add Entitlement can repair missing access and Remove Entitlement can revoke excessive access. Therefore, “Create Entitlement” does not represent the appropriate supported batch request type and the proposed solution is false.

References/topics: IdentityIQ Engineer — Lifecycle Manager Batch Requests, AddEntitlement, RemoveEntitlement, ManagedAttribute versus entitlement assignment, bulk remediation.

=======

Yes. A ManagedAttribute represents managed access originating from an IdentityIQ application—for example an entitlement value, account group, or permission. Consequently, its definition includes an association with the Application object that supplies or owns that managed access.

The Entitlement Catalog makes this relationship explicit. For each managed attribute, IdentityIQ displays an Application property identifying the application associated with the attribute. The remaining ManagedAttribute metadata—such as Type, Attribute or Target, Value, owner, requestability, classifications, and associated roles—is interpreted within that application ' s schema and governance context.

This relationship is important because identical entitlement values can exist on different systems but represent completely different access. IdentityIQ therefore requires application context to uniquely and correctly interpret the entitlement. For example, a value called Administrators on one Active Directory application is not inherently the same governed entitlement as Administrators on another target.

A ManagedAttribute can participate in roles, certifications, requests, classifications, and policy evaluation, but those governance relationships do not remove its underlying application association.

References/topics: IdentityIQ Engineer — ManagedAttribute object, Application object, Entitlement Catalog, managed entitlements, application schemas.

=======

This statement is incorrect. In SailPoint IdentityIQ email templates, entire blocks of text, including whole paragraphs, can indeed be conditionally included or omitted using the appropriate templating syntax such as #if, #else, and #end. The templating engine in IdentityIQ, which typically uses Apache Velocity, supports complex conditional logic that can control large sections of the email content, not just individual lines.

Yes. The IdentityIQ version is essential information when setting up a new sandbox environment. Version affects installation steps, supported Java versions, supported application servers, database compatibility, connector behavior, patch requirements, schema scripts, upgrade paths, and available product features. A sandbox is usually intended to mirror or safely test changes for another environment, so the engineer must know which IdentityIQ version the sandbox should run. Without the version, the engineer could deploy the wrong WAR file, apply incompatible patches, use the wrong schema scripts, or test behavior that does not match production. Version also matters for customizations such as rules, workflows, Quicklinks, UI branding, extended attributes, and connector configuration because APIs and supported patterns can differ between releases. Therefore, IdentityIQ version is not optional background information; it is a core environment-planning input. References/topics: IdentityIQ Engineer — sandbox setup, installation planning, version compatibility, patching, environment parity.

This is a valid step. To create a custom audit event in IdentityIQ, the event/action must be registered so the audit framework recognizes it. Adding an AuditAction entry in the AuditConfig object XML is the correct type of configuration because it defines the audit action name, display name, and enabled state. The name value is the internal audit action identifier that code, rules, workflows, or tasks can use when writing audit records. The displayName provides the readable label, and enabled= " true " allows the event to be captured. This step alone is not the entire solution because the engineer must also write logic to create the audit record and configure a report to query and display it. However, the question asks whether this is one of the required steps, and it is. References/topics: IdentityIQ Engineer — AuditConfig, AuditAction XML, custom audit actions, audit event enablement, audit report setup.

Syslog cannot be used to launch a certification using the search results. Launching a certification in IdentityIQ is a process that involves interacting with the application’s certification module, where you define parameters, select users or roles, and initiate the certification campaign. This process requires using the IdentityIQ user interface or APIs, not the Syslog, which is purely for logging purposes.

SailPoint IdentityIQ Certification Guide

SailPoint IdentityIQ API and UI Guide