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

The statement " The rule type must be IdentityAttribute " is correct. In SailPoint IdentityIQ, when writing a rule that is intended to map or manipulate identity attributes during the aggregation process, the rule type should be set to " IdentityAttribute " . This ensures that the rule is recognized and executed in the appropriate context for managing identity attributes.

Therefore, the correct answer is A. Yes.

Yes. LCM provisioning workflows contain control behavior for handling provisioning operations that are not completed synchronously. A queued result is materially different from a failed result: IdentityIQ has successfully submitted the request into a provisioning path, but the downstream operation has not necessarily completed yet.

LCM processing can therefore be configured so that asynchronous/queued provisioning does not cause the overall request workflow to be treated as an immediate provisioning failure. This is important for connectors and integrations where target operations are queued, brokered, or fulfilled asynchronously. Otherwise, the workflow could incorrectly follow failure handling merely because the target-system change was not completed during the same execution thread.

The engineer must still distinguish this from claiming that the target access has definitely been provisioned. “Successful” at this workflow stage means the request was accepted into the expected provisioning process. Subsequent transaction processing, retries, aggregation, or request maintenance can establish the final state.

This is precisely why provisioning status management is a workflow concern, whereas whether an application supports a particular account operation is an application/connector concern.

References/topics: IdentityIQ Engineer — LCM provisioning workflows, asynchronous provisioning, queued provisioning status, ProvisioningProject, provisioning transaction status, request maintenance.

=======

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, this statement is incorrect. When a wait step is encountered in a foreground workflow, it does not cause the user’s screen to freeze for the specified number of seconds. Instead, the wait step simply pauses the workflow execution for the specified duration, but this is managed in the background. The user interface remains responsive, and the end-user typically won’t notice any freezing or delays caused by the wait step itself.

SailPoint IdentityIQ Workflow Guide (Section on Workflow Step Types)

SailPoint IdentityIQ Scripting and Workflow Best Practices

Yes. IdentityIQ reports are closely tied to the platform’s task framework. Out-of-the-box report templates are represented as task/report definitions, and these definitions describe how the report is executed, what arguments or filters it accepts, and how the resulting report instance is generated. In IdentityIQ, scheduled and executable background operations commonly use TaskDefinition objects, and reporting is implemented through this same general task infrastructure. A report definition is not the same thing as a generated report result. The TaskDefinition defines the report template or executable report behavior, while a run of that report creates task/report result data. This distinction matters because an engineer may inspect, export, import, customize, or troubleshoot report definitions through IdentityIQ objects. The proposed statement is therefore valid for out-of-the-box reports as report definitions/templates. References/topics: IdentityIQ Engineer — reporting framework, TaskDefinition objects, report templates, task execution, generated report results.

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.

The solution provided is incomplete. To create a custom audit event and set up an associated report, the process involves several steps, including defining the custom audit event in the Audit Configuration object, updating or creating relevant audit triggers in the system, and defining the custom report using XML or the IdentityIQ report editor. The steps mentioned in the solution do not cover the necessary configuration and implementation details required for this task. For a complete process, consult the SailPoint IdentityIQ Reporting Guide and the Audit Framework documentation.

Syslog is primarily used for logging system events and not for performing complex searches or queries on hierarchical or organizational data like identifying the number of employees that report to a specific person. Such a query would typically require access to the organizational hierarchy or identity data, which is better achieved through IdentityIQ’s reporting or search capabilities within the application rather than using Syslog. Syslog captures log events related to system operations, errors, and other activity logs but isn ' t designed for the type of structured query described in the question.

SailPoint IdentityIQ Logging and Monitoring Guide

SailPoint IdentityIQ Administration Guide (Sections on Reporting and Search)

Based on the goals and scheduling parameters provided, the tasks should be scheduled in the following order to achieve efficient processing for a 24-hour period:

1st Check Expired Work Items (12:00 AM)

This task runs at midnight to check for expired work items. It’s important to run this first to clean up any pending tasks from the previous day.

1st Perform Identity Request Maintenance (2:00 AM)

This maintenance task is scheduled at 2:00 AM, a time when the system is least likely to be under load.

1st Aggregate Employee Authoritative Application (5:00 AM)

The aggregation for the Employee Authoritative application starts early in the day, at 5:00 AM.

1st Aggregate Contractor Authoritative Application (5:10 AM)

The Contractor Authoritative application aggregation is scheduled 10 minutes after the Employee aggregation, as per the goals.

1st Identity Refresh (5:20 AM)

Active Directory aggregation runs next at 5:20 AM.

2nd Aggregate Employee Authoritative Application (12:00 PM)

The second run for the Employee Authoritative application happens at noon.

2nd Aggregate Contractor Authoritative Application (12:10 PM)

At 12:10 PM, the Contractor Authoritative application runs again for its second aggregation.

2nd Identity Refresh (12:20 PM)

The second aggregation for Active Directory happens at 12:20 PM.

1st Aggregate Finance Authoritative Application (8:00 PM)

The Finance application aggregation is scheduled for 8:00 PM, which aligns with the goal of processing it in the evening.

Comprehensive Detailed Explanation with All IdentityIQ Engineer References

Check Expired Work Items (12:00 AM)

This task is run first to ensure any expired or pending work items from the previous day are cleared out and do not interfere with the new day’s tasks. Running it at midnight ensures that any workflows or approvals with expirations are processed efficiently.

Identity Request Maintenance (2:00 AM)

This is a maintenance task that keeps the system running smoothly by managing identity requests. Scheduling it at 2:00 AM minimizes interference with other key business tasks since it ' s an off-peak hour.

Authoritative Application Aggregations (Employee/Contractor/Active Directory)

The authoritative applications (Employee, Contractor, Active Directory) need to be processed twice a day: once early in the morning and once at noon. Each aggregation must follow the specified order, as it ensures that the data flow is properly managed from the more critical Employee applications to the less frequent Contractor and Active Directory ones.

Finance Application (8:00 PM)

The Finance application is aggregated once a day, in the evening, after other high-priority applications have been processed. This ensures that financial data is up to date for reporting and compliance purposes, without overlapping with the core workday processes.

SailPoint IdentityIQ Scheduler Documentation (section on task scheduling and run-time configuration).

The statement is true. In the SailPoint IdentityIQ Reporting user interface, report templates are located on the " Reports " tab. These templates define the structure and parameters of reports but do not contain actual report data. Instances of reports, which are the actual generated reports containing data based on the templates, are located on the " My Reports " tab. The " My Reports " tab is used for viewing and managing reports that have been generated for a specific user.

SailPoint IdentityIQ Reporting Guide

SailPoint IdentityIQ Administration Guide (Section on Reporting Interface)