SailPoint IdentityIQ-Associate Exam Dumps

No. In SailPoint IdentityIQ, the provisioning plan is not necessarily static after it is initially created. A provisioning plan represents the requested account and access changes to be fulfilled, such as creating an account, modifying attributes, adding or removing entitlements, disabling an account, or deleting an account. During provisioning processing, IdentityIQ may update, expand, enrich, or transform the plan before fulfillment.

For example, provisioning policies may require additional data before a requested operation can be completed. Workflow logic, rules, approval outcomes, role expansion, dependency processing, and application-specific provisioning configuration can also affect the final provisioning instructions. IdentityIQ may compile the plan into executable provisioning activity, split requests by application, route items to connectors, or generate manual work items when direct connector provisioning is not available. These processing steps can alter what is ultimately sent to the target system or assigned for fulfillment.

Therefore, the statement that the provisioning plan will never be changed or updated is incorrect. Reference topics: Provisioning, provisioning plans, provisioning policies, plan compilation, workflows, connector provisioning, manual fulfillment, and application-specific provisioning behavior.

Yes. In SailPoint IdentityIQ, birthright roles represent access that is automatically granted based on identity context, such as job function, department, location, lifecycle state, or organizational assignment. A mover lifecycle event occurs when an identity undergoes a material change, such as transfer to a new department, change in manager, change in location, or change in business role eligibility. Because these changes can alter what baseline access the identity should have, birthright role assignment may be processed as part of the mover event.

The mover event can launch a configured business process that evaluates the identity's updated attributes and initiates access changes, including assignment of new birthright roles or removal of access no longer appropriate. This differs from requestable roles, where a user or manager explicitly asks for access through Lifecycle Manager. Birthright access is driven by identity state and business rules.

Therefore, the statement is accurate. Mover lifecycle processing can be used to keep baseline role-based access aligned with the user's changed business position. Reference topics: Access Modeling, birthright roles, role assignment, Identity Refresh, Lifecycle Events, mover processes, and Provisioning.

Marking an account schema attribute as managed does not mean the attribute can be edited in IdentityIQ. In IdentityIQ application schema configuration, a managed attribute is one whose values are promoted into IdentityIQ as governable access objects, commonly represented in the entitlement catalog. This allows IdentityIQ to attach governance metadata to the discovered values, such as display name, description, owner, requestability, classification, and review-related context.

Editability is controlled through different mechanisms, including provisioning policies, forms, workflows, connector capabilities, and provisioning plan operations. An attribute may be managed for governance purposes without being directly editable by a user in IdentityIQ. Conversely, an attribute may be populated during provisioning if the application connector and provisioning policy support it, but that is separate from the schema's managed designation.

The managed setting is therefore about governance, cataloging, and access modeling, not direct modification. It enables IdentityIQ to treat values of that schema attribute as objects that can be reviewed, requested, certified, described, and owned.

Reference topics: Applications --- account schema attributes and their functions; Access Modeling --- entitlement catalog; Governance --- certifications; Provisioning --- provisioning policies and attribute handling.

The statement is false. In SailPoint IdentityIQ, groups and populations are used to classify, filter, and organize identities for governance, reporting, certifications, and targeted user experiences. A population is a defined collection of identities, and group factories can dynamically create identity groups based on configured identity attributes. These constructs are useful for segmentation, analysis, and campaign targeting, but they are not the standard objects assigned as owners of IdentityIQ objects.

Ownership in IdentityIQ is normally assigned to an identity or to a workgroup. A workgroup is used when ownership or responsibility must be shared by multiple users, such as application owners, certification owners, entitlement owners, or approval groups. This distinction matters because ownership drives accountability, work item assignment, approvals, escalations, and administrative responsibility. Populations and generated groups do not function as accountable owners in the same way workgroups do.

Therefore, while groups and populations can influence governance scope and visibility, they are not assigned as object owners. Reference topics: Identity Modeling --- groups and populations; Foundational Concepts --- common objects and usage; Governance --- ownership, certifications, and work item responsibility.

No. In SailPoint IdentityIQ, tasks are execution mechanisms used to perform system operations such as aggregation, identity refresh, certification generation support, report execution, maintenance processing, and other repeatable administrative jobs. A task can collect data, refresh calculated identity information, process objects, or execute configured logic, but it does not itself provide the business review function of confirming whether an account group provides the correct access.

Confirming that an account group provides appropriate access is a governance activity. That type of validation is performed through access reviews or certifications, where a designated reviewer evaluates group membership, permissions, ownership, or entitlement meaning and decides whether the access remains appropriate. This requires human or configured governance judgment, not simply execution of a background task.

A task may support the process indirectly by aggregating current account group data or preparing certification data, but the actual confirmation of correctness belongs to certification and governance review functionality.

Reference topics: Foundational Concepts, tasks versus workflows, Governance, certifications, account group reviews, access reviews, and Access Modeling.