Which batch request types must be placed in a separate file in SailPoint IdentityIQ?

In SailPoint IdentityIQ, certain batch request types have specific requirements regarding how they are processed, particularly when it comes to creating new identities and changing passwords. When handling batch requests, it's important to recognize that the creation of an identity and a password change are operations that have distinct implications for the system and the identities involved.

The operation of creating an identity, being a foundational task, often requires additional processing and synchronization steps. Similarly, changing a password involves security checks and communications with external systems or directories. Combining these request types into a single file could potentially lead to processing complications or errors due to the differing nature and urgency of these requests.

By placing the create identity and change password requests in a separate file, it ensures that each request type is managed appropriately. This separation helps the IdentityIQ system maintain its integrity, ensures adherence to relevant security protocols, and allows for proper logging and error handling specific to each batch type.

In contrast, other combinations provided in the options correspond to operations that can be managed together without significant risk or complexity in processing. Understanding these distinctions is crucial for managing batch operations effectively in IdentityIQ.