IdentityIQ-Engineer Exam Dumps - SailPoint Certified IdentityIQ Engineer

An Account Group Membership Certification is designed to certify group memberships within accounts, typically focusing on the validation of access within specific account groups (e.g., Active Directory groups).

This type of certification does not directly address the accuracy of role composition or the correctness of entitlements assigned within roles. Since the bank ' s goal is to ensure that all roles include the correct entitlements, an Account Group Membership Certification is not suitable for this purpose.

Thus, the correct answer is B. No.

Yes. Reviewing provisioning transactions and their processing states is a principal purpose of the Provisioning tab in the IdentityIQ Administrator Console. The engineer can use this administrative view to inspect provisioning activity and distinguish transactions according to states such as pending, failed, or completed/successful.

This visibility is particularly important for troubleshooting asynchronous provisioning. A failed transaction may require investigation into connector errors, target-system responses, invalid attribute values, authentication failures, or workflow/provisioning-plan problems. A pending transaction may indicate queued processing or an operation awaiting further execution. Successful transactions provide confirmation and historical visibility into completed processing.

The Provisioning tab is therefore an operational troubleshooting interface for provisioning transactions; it is not merely a configuration page.

This should also be distinguished from another proposition already present in the Word bank: the bank explicitly states that the Provisioning tab can be used to manually retry the provisioning attempt for pending transactions . The video proposition here tests a different capability—viewing transactions across their various states—so it remains a separate DOMC item.

References/topics: IdentityIQ Engineer — Administrator Console, provisioning transactions, failed provisioning, pending transactions, transaction history, provisioning troubleshooting.

=======

Yes. IdentityIQ Identity Provisioning Policies define the fields and validation behavior used when identities are created or updated through supported identity-management flows. When an explicit Update Identity Provisioning Policy is not configured, IdentityIQ can fall back to the Create Identity Provisioning Policy for Edit Identity operations. This fallback allows environments to avoid duplicating identity-field configuration when the create and update forms require the same data model or validation logic. The engineer still needs to design this carefully: create and update operations are not always identical. Create flows may require fields that should not be editable later, while update flows may expose fields that are irrelevant at creation. If the organization needs separate behavior for editing identities, an Update Identity Provisioning Policy should be defined. But the proposed statement is true as a product behavior: the Create Identity policy can be used when no Update Identity policy exists. References/topics: IdentityIQ Engineer — Identity Provisioning Policies, Create Identity, Edit Identity, Update Identity policy, field validation and allowed values.

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.

=======

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)

No, the " Email Protocol " is not a setting that an engineer must set up to ensure successful communication with the SMTP server. Instead, the essential settings include the mail server address, port, authentication details (like username and password if required), and possibly the security settings (such as SSL/TLS). While the email protocol (e.g., SMTP) is implicitly involved, it is not a specific setting that needs to be configured separately within IdentityIQ. The critical setup revolves around configuring the mail server connection parameters.

SailPoint IdentityIQ Configuration Guide (Email and Notification Settings)

SailPoint IdentityIQ Administration Guide (SMTP Configuration for Email Notifications)

In SailPoint IdentityIQ, the configuration in IdentityExtended.hbm.xml file as shown in the image indeed outlines the use of extended identity attributes. These attributes (extended1, extended2, etc.) are custom attributes that are appended to the standard identity object model to store additional identity-related data.

According to the official SailPoint IdentityIQ documentation, when defining identity mappings under Global Settings > Identity Attributes, only up to 12 additional attributes can be made searchable within the IdentityIQ system. This limitation is crucial because it directly impacts the efficiency of search operations in large environments, where making too many attributes searchable can significantly slow down performance.

Once you define these 12 searchable attributes, any additional attributes can still be added, but they will not be indexed for search operations. This means that while the data in these attributes can be used in workflows, reports, and other operations, they cannot be used in search filters in the IdentityIQ user interface.

This limitation is particularly important when planning the design of the identity schema, as it affects both performance and usability. Therefore, the statement in question is correct and accurately reflects the constraints imposed by SailPoint IdentityIQ in terms of searchable identity attributes.

In SailPoint IdentityIQ, the concept of a " role " is fundamental to the identity governance framework. The platform supports several default role types that are pre-configured to help organizations manage access effectively. The default role types include:

Business Role: Represents a collection of entitlements necessary for a specific job function within the organization.

IT Role: Aggregates technical entitlements that are typically assigned together, often linked to specific applications or systems.

Application Role: Tied to a specific application, representing roles within that application ' s context.

Composite Role: A combination of other roles, either business or IT, to form a higher-level role.

The term " Entitlement Role " is not recognized as a default role type in SailPoint IdentityIQ. While entitlements can be components of roles, " Entitlement Role " itself is not a predefined role type in the platform. Therefore, the correct answer is B. No.