SailPoint Updated IdentityIQ-Engineer Exam Questions and Answers by alan

No. IdentityIQ report execution is based on task/report scheduling behavior, and the platform is not limited to running reports only once per day. Reports can be executed manually or scheduled according to supported scheduling options, depending on task configuration and administrative requirements. A daily schedule is only one possible cadence. IdentityIQ reporting is built on task infrastructure, and report templates can generate report instances based on selected parameters, filters, and schedules. In real deployments, organizations may schedule reports daily, weekly, monthly, or at other configured intervals depending on governance, compliance, and operational needs. The proposed solution is too restrictive because it says “at most once per day,” which incorrectly imposes a limitation that is not inherent to IdentityIQ reporting. The accurate concept is that reports can be scheduled, but the frequency depends on the task scheduler configuration and the report’s business purpose. References/topics: IdentityIQ Engineer — reporting, report templates, scheduled reports, task execution, report instances.

No. The key phrase is “inherited from an assigned Business Role.” IdentityIQ distinguishes between roles that are directly requestable and technical access that an identity receives because another role requires or contains it.

An IT Role can certainly be part of the IdentityIQ role model and can provide technical entitlement access. A Business Role can also be related to lower-level roles through required or permitted role relationships. However, when an IT Role is inherited automatically because an assigned Business Role requires it, that inherited access is not independently presented as a new role for the manager to request—the Business Role assignment is what drives the inherited role relationship.

Permitted roles are different because they can define additional role access that becomes eligible or meaningful in the context of another role. That distinction between automatic inheritance and requestability is important in access-model design.

The Word bank already contains the same manager-request stem with Business Role, which it marks valid, and another with HR Role, which it marks invalid. This inherited-IT-role proposition is separate.

References/topics: IdentityIQ Engineer — Business Roles, IT Roles, required roles, permitted roles, inherited role access, access requests.

=======

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.

The Rapid Setup user interface in SailPoint IdentityIQ is designed to simplify and streamline common configuration tasks, particularly during the initial setup of IdentityIQ environments. However, it has certain limitations in terms of granularity and customization.

In this case, the requirement is to disable an account on a particular application for one set of users and delete the account for another set of users during administrative terminations. The Rapid Setup interface does not provide options to differentiate between user groups for different actions (disable vs. delete) within the same termination event.

This level of specificity—applying different actions based on user group membership—would require a more advanced setup, possibly involving custom rules or workflows rather than using the Rapid Setup options. Therefore, the correct answer is B. No.