IdentityIQ-Engineer Exam Dumps - SailPoint Certified IdentityIQ Engineer

Yes. An account attribute must have an Attribute Name because the name provides the logical identifier IdentityIQ uses to reference that attribute throughout the application configuration and subsequent processing. In this scenario, the engineer needs an attribute representing whether an account is privileged. That attribute must be identifiable when its value is populated from source data, calculated by rule logic, exposed to Advanced Analytics, referenced from BeanShell, or evaluated in policies.

The Attribute Name is distinct from the source mapping and datatype. The name establishes what attribute is being defined ; the source mapping determines where or how its value is obtained; and the datatype specifies what kind of value IdentityIQ expects.

The existing Word bank tests this same scenario with Source Mappings: Application Rule, which it marks as required, and separately with Edit Mode: Read Only. Those do not duplicate this proposition because DOMC treats each configuration option independently.

Therefore, Attribute Name is necessary for the account-attribute definition.

References/topics: IdentityIQ Engineer — application schema, account attributes, attribute naming, source mappings, Advanced Analytics, policy attributes.

=======

Yes. IdentityIQ Debug pages provide administrative access to persisted objects and can support object deletion, including deletion of individual objects and, depending on the view and selection mechanism, bulk deletion of selected objects. This capability is powerful and risky. Engineers must not treat Debug deletion like ordinary UI cleanup because IdentityIQ objects often have dependencies. Deleting a rule, workflow, application, form, task definition, policy, identity, or certification-related object can break references and cause runtime failures. Bulk deletion is especially dangerous because it can remove many objects without the safeguards provided by normal functional pages. The statement is valid from a usability/control perspective, but it should be understood as an administrative capability, not a recommended routine practice. Proper change control, export backups, dependency analysis, and non-production validation are mandatory before deleting objects through Debug. References/topics: IdentityIQ Engineer — Debug-Object page, object deletion, bulk object actions, object dependencies, administrative safeguards.

No. QuickLink population membership is not an exclusive one-population relationship. IdentityIQ can evaluate an identity against multiple QuickLink population definitions, and the same identity can satisfy the membership criteria for multiple populations.

QuickLink populations are used to govern which QuickLinks users can access and, for “For Others” use cases, which target identities they may act upon. Populations can be based on identity attributes, capabilities, workgroups, individual identities, or other configured membership logic. Because those criteria can overlap, there is no general requirement that an identity belong to only one population.

For example, the same employee could satisfy a Managers population, a particular geographic population, and another population associated with access-request functionality. IdentityIQ evaluates the applicable configuration rather than forcing those groups to be mutually exclusive.

The Word bank itself contains examples where QuickLink population configuration controls access to manager-only QuickLinks, reinforcing that populations represent authorization groupings rather than a single-valued classification.

Therefore, “at most one QuickLink population” is false.

References/topics: IdentityIQ Engineer — QuickLink populations, authentication and authorization, population membership, capabilities, workgroups, QuickLink visibility.

=======

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)

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

SailPoint IdentityIQ Logging and Auditing Guide

SailPoint IdentityIQ Performance Tuning Guide

Yes. IdentityIQ uses message-catalog properties to supply a large amount of user-interface text rather than hard-coding every label directly into individual pages. In traditional IdentityIQ deployments, the iiqMessages resource files contain message keys and their displayed text. Changing or overriding the relevant message key is therefore a standard mechanism for customizing labels, prompts, descriptions, placeholders, and other localized UI strings.

A safer customization pattern is generally to place customer-specific overrides into the appropriate custom message properties file rather than directly altering the SailPoint-delivered base resource, because base files can be replaced during an upgrade. This also supports internationalization because locale-specific message catalogs can provide different values for the same key.

For example, IdentityIQ certification screens, access-request pages, login-related messages, and general interface labels frequently resolve displayed strings through message keys. SailPoint ' s internationalization and templating mechanisms likewise retrieve translated values from message catalogs.

Therefore, the statement that iiQMessages files can be used to change text labels is valid.

References/topics: IdentityIQ Engineer — message catalogs, iiqMessages.properties, iiqCustom.properties, localization, UI labels and branding.

=======

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. Identity Provisioning Policies provide the field definitions and associated behavior used for identity-management operations such as Create Identity and Edit Identity . They can control which identity attributes are presented, which are required, what defaults or calculations are performed, and what validation or allowed-values logic applies.

For identity creation, the Create Identity Provisioning Policy defines the information collected when an authorized user creates an identity through IdentityIQ. Update/Edit behavior can similarly be governed through the appropriate identity provisioning policy. This allows implementations to expose controlled identity-management functionality without relying on arbitrary direct editing of Identity objects.

This proposition is different from two related items already in the Word bank. The bank contains a proposition stating that a Create Identity policy is applied during authoritative-source aggregation, and another covering allowed-values/validation logic when using Create Identity. Neither is the same DOMC proposition as defining policies for create/edit operations through the IdentityIQ UI.

Therefore, this is a separate unique question and the answer is Yes.

References/topics: IdentityIQ Engineer — Identity Provisioning Policies, Create Identity, Edit Identity, form fields, validation, identity lifecycle management.

=======