When performing an incremental import from an integration, what is the expected behavior?

When performing an incremental import from an integration, the expected behavior is that only updated users since the last import are imported. This means that the system focuses on efficiency by capturing changes that have occurred since the previous import cycle. Incremental imports are designed to minimize the load on both the source system and the receiving system, which is critical for maintaining performance and keeping data synchronized without unnecessary duplication.

This approach is especially useful in environments where user data can frequently change, as it allows administrators to update existing records without re-importing the entire user base. Consequently, only the data that has been altered will be processed, ensuring that the system is up-to-date with the latest changes while avoiding redundancies.

The other options imply behaviors that do not align with the principle of incremental imports. Importing all users and groups each time would lead to redundancy and inefficiencies, whereas importing only changes in application settings or creating new users regardless of updates does not reflect the targeted nature of an incremental update.