Should Identity Profiles be configured after aggregation?

• A. Yes, they should be configured post-aggregation
• B. No, they should be configured before aggregation
• C. Only for certain sources
• D. Only if required by the client

Answer: (B)

Configuring Identity Profiles before aggregation is essential because Identity Profiles define the attributes that are pulled into the identity system for each identity. When an aggregation occurs, the system collects data from various sources and constructs identities using the defined profiles.

If the profiles are set up post-aggregation, it would not allow for the proper construction of identities based on the desired attributes during the aggregation process. By preparing profiles ahead of time, you ensure that the aggregation pulls in all relevant data that aligns with the organizational needs for identity management. This proactive configuration helps maintain data integrity and relevance, avoids redundant processing, and allows identity governance capabilities to function optimally from the start.

This practice is foundational in identity security, as it aligns the data ingestion process with organizational policies and ensures that the collected identities are accurate and complete from the outset.