Is this a true statement about the provisioning process in IdentityIQ? IdentityIQ determines if the account needs to be created before modification.

The statement is true. The IdentityIQ provisioning engine is designed to handle dependencies logically. When a provisioning plan is created to modify a user's account on a target application (e.g., add an entitlement), the system first checks for the existence of that account. If the account does not exist, the provisioning plan is automatically updated to include a "create account" operation before the modification operation. This ensures that provisioning actions are executed in the correct sequence, preventing errors that would occur from attempting to modify a non-existent object. This is a fundamental aspect of the Provisioning Broker's logic.

B. No: This is incorrect. Attempting to modify a non-existent account would cause a provisioning failure. IdentityIQ's architecture is built to prevent this by ensuring account creation precedes modification.

1. SailPoint IdentityIQ 8.2, Technical Manual for Provisioning, Section 3.1: "The Provisioning Plan." The manual describes how the Provisioning Broker compiles requests and resolves dependencies, including the implicit creation of accounts before modifications are applied.

2. SailPoint IdentityIQ Connector and Integration Guide, Version 8.1, Chapter 2: "Provisioning Concepts," Paragraph: "Provisioning Plan Compilation." This section details that the plan is an ordered set of actions, and the system ensures prerequisites, like account existence, are met.