IdentityIQ-Engineer Exam Dumps - SailPoint Certified IdentityIQ Engineer

No. A ManagedAttribute in IdentityIQ represents a managed value of an application attribute, most commonly an entitlement or account-group value that IdentityIQ can govern, certify, request, or provision. It is not the object used to define the “type” of an account, such as service account or privileged account. Account information aggregated from an application is represented through Link objects associated with an Identity. The Application object defines the connected system, schema, connector configuration, and aggregation/provisioning behavior. A Bundle represents a role. ManagedAttribute objects are typically used when an application schema attribute is marked as managed, such as group membership, permission, role, or entitlement values. Account type classifications may be represented as attributes on a Link or through identity/account metadata, but calling that a ManagedAttribute definition is technically wrong. This question tests whether the engineer understands the IdentityIQ object model and does not confuse entitlements with account records. References/topics: IdentityIQ Engineer — Application object, Identity object, Link object, Bundle/role object, ManagedAttribute entitlement model.

Yes. When a new IdentityIQ object is created and persisted correctly through the application layer, IdentityIQ can generate the internal object ID upon save. The object ID is the persistent identifier used by the platform and database, while the object name is a separate logical or display identifier. This distinction is important when engineers create or import objects through Debug. A new object should not reuse the ID of an existing object, because that would update or conflict with the existing object rather than create a clean new record. Automatic ID generation is one reason object XML is often edited before import or creation: copied XML must have old IDs removed so IdentityIQ can assign a fresh identifier. The statement is therefore valid, but engineers must still ensure required fields, class type, name uniqueness, and object references are correct before saving. References/topics: IdentityIQ Engineer — Debug-Object page, object persistence, automatic ID generation, object name versus ID, XML import safety.

This implementation is not correct. The requirement is to return all account names for an identity on the application MagicBox, but the code retrieves only a single Link by calling service.getLink(identity, " MagicBox " ). Even worse, the while (link != null) loop never changes the link variable, so if a link is found, the loop becomes infinite and repeatedly adds the same native identity. A correct implementation must retrieve the application object, obtain all matching Link objects for the identity and application, iterate over that list, and add each link’s native identity once. There is also no visible import for ArrayList or List, although BeanShell environments may sometimes tolerate imports differently. The fatal issue remains the flawed loop and single-link retrieval. IdentityIQ account data is represented by Link objects, and multiple accounts may exist for the same identity on the same application depending on connector and policy design. References/topics: IdentityIQ Engineer — IdentityService, Link objects, native identity, BeanShell API usage, account lookup logic.

Syslog is not intended for querying or identifying specific objects, such as all Link objects from a particular application. Syslog is used to record events and log information related to system activities, errors, and operations. To identify all Link objects from a particular application, you would use IdentityIQ ' s internal search functionality or reports that allow you to filter and retrieve such objects. These tasks involve querying the database and application-specific data structures rather than examining log files.

SailPoint IdentityIQ Administration Guide (Section on Objects and Searching)

SailPoint IdentityIQ Configuration Guide (Understanding Link Objects)

No. Upgrading the IdentityIQ web application does not automatically upgrade an independently installed IQService instance. IQService is a native Windows service installed on Windows hosts to support functionality requiring Windows APIs, including certain Active Directory provisioning operations and other Windows-specific connector capabilities.

SailPoint ' s IdentityIQ documentation states that the IQService version must match the IdentityIQ server version, including patch versions, and explicitly says that when one is upgraded, the other must also be upgraded. This is an operational requirement—not evidence of an automatic upgrade mechanism. The implementation engineer must deploy the appropriate IQService binaries and follow the required service upgrade or replacement procedure on each relevant Windows host.

Failing to align the versions can cause compatibility issues between IdentityIQ and IQService, particularly for connector requests, authentication/encryption behavior, provisioning, or Windows-native operations. The service configuration, port, TLS/certificate configuration, and service account should also be validated after upgrading.

Therefore, IQService must be deliberately upgraded alongside IdentityIQ; it is not automatically replaced merely because IdentityIQ itself was upgraded.

References/topics: IdentityIQ Engineer — IQService installation, version compatibility, IdentityIQ upgrades, Windows connector services, patch alignment.

=======

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 workflow transition condition shown in the image is Transition to= " Approve " when= " identityName != null " . This condition checks whether the identityName variable is not null. In the provided scenario, the identityName variable has a value of " Catherine.Simmons, " which is clearly not null. Therefore, the condition for transitioning to the " Approve " step will evaluate as true, meaning the workflow will indeed continue to the " Approve " step.

However, it seems like the question might be worded incorrectly as it asks if the workflow will continue to the " Approve " step when it actually will. If this was an error and the intention was to determine if it should not continue, the answer would have been " No. " But based on the logic, the workflow will continue to the " Approve " step.

SailPoint IdentityIQ Workflow Documentation

SailPoint IdentityIQ Scripting Guide (Conditions and Transitions in Workflows)

Create Policy is not required for every IdentityIQ application. In IdentityIQ, provisioning policies are used when the system needs structured forms and field definitions for operations such as account creation, update, delete, enable, disable, or password actions. A Create Policy is specifically relevant when IdentityIQ is expected to create accounts on that target application and needs to collect or calculate the required values for account creation. Many applications may be onboarded initially for aggregation, correlation, governance, certifications, or visibility only, without immediate provisioning. In those cases, a Create Policy is unnecessary. Even in provisioning-enabled environments, not all applications support account creation, and some may support only entitlement changes or account disables. Therefore, Create Policy is an optional provisioning configuration, not a required field for setting up any application. References/topics: IdentityIQ Engineer — application onboarding, provisioning policies, Create Account policy, aggregation-only applications, account provisioning configuration.