SAILPOINT-CERTIFIED-IDENTITYNOW-ENGINEER · Question #20
Does the following use case accurately describe provisioning on a source that has provisioning disabled? Solution: Provisioning is initialed by a process (e.g. Access Request Role Assignments)…
The correct answer is A. Yes. In this use case, provisioning is initiated, but the source has provisioning disabled, meaning automated provisioning cannot proceed. The process described is accurate: when provisioning is assigned to a source where provisioning is disabled, IdentityNow does not execute the…
Question
Does the following use case accurately describe provisioning on a source that has provisioning disabled? Solution: Provisioning is initialed by a process (e.g. Access Request Role Assignments). Provisioning instructions are calculated based on current access, and go through filtering and expansion processes. Provisioning is then assigned to a source for provisioning. Since provisioning is disabled on the source a manual task is opened in IdentityNow A person carries out the provisioning manually.
Options
- AYes
- BNo
How the community answered
(26 responses)- A85% (22)
- B15% (4)
Explanation
In this use case, provisioning is initiated, but the source has provisioning disabled, meaning automated provisioning cannot proceed. The process described is accurate: when provisioning is assigned to a source where provisioning is disabled, IdentityNow does not execute the provisioning through its automated system. Instead, a manual task is generated for a human to complete the provisioning process. This manual intervention ensures that the necessary access changes can still occur, albeit through human oversight rather than an automated connector. This scenario aligns with how IdentityNow handles sources that are flagged as non-provisionable. The provisioning logic is still calculated within the system, but actual implementation requires manual steps when the source is configured in this way.
Topics
Community Discussion
No community discussion yet for this question.