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

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.

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.

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. 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.

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.

The statement is false. In SailPoint IdentityIQ, while message files may indeed be added to support additional languages, the out-of-the-box supplied message files can also be modified. Administrators can customize these message files to adapt the text in the user interface to better suit the organization’s needs. This includes modifying existing translations or adding custom messages to meet specific requirements.

SailPoint IdentityIQ Localization Guide

SailPoint IdentityIQ Configuration Guide (Customization of Message Files)

Running the command iiq extendedSchema in the IIQ_Home/WEB-INF/bin directory is correct and one of the standard procedures for generating database scripts to extend Application attributes in the IdentityIQ database. This command processes the schema definitions (including any new attributes) and generates the appropriate SQL scripts to update the database schema. These scripts can then be executed against the database to apply the changes.

SailPoint IdentityIQ Administration Guide (Schema Extension and Database Management Sections)

SailPoint IdentityIQ Configuration Guide (Extended Schema Management)

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.

Yes. Domain information is a fundamental connection element when configuring IdentityIQ to interact with Active Directory. Active Directory is organized around forests and domains, and the connector must know the domain context in which user, group, membership, authentication, aggregation, and provisioning operations will occur.

In the IdentityIQ Active Directory connector ' s Domain Settings, the engineer configures the relevant forest and enters the Domain along with the required service-account information and authentication settings. The connector then uses this information to bind to the appropriate Active Directory domain controller environment and manage directory objects in the configured scope.

Specific connector releases also provide conveniences such as forest-level domain discovery or “Manage All Domains,” but these mechanisms do not eliminate the underlying Active Directory domain context. The connector still needs to know which domains it manages, whether they are explicitly configured or discovered under a forest configuration.

For the DOMC proposition as stated, Domain is therefore a required core Active Directory configuration concept, rather than an optional role-modeling or cosmetic application property.

References/topics: IdentityIQ Engineer — Active Directory connector, Domain Settings, forests and domains, service account configuration, connector authentication.

=======

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.

=======