When is a single identity profile preferred in lifecycle design?

• A. When identities are completely unique
• B. When data sources are consistent and roles overlap
• C. When identities vary in attributes
• D. When there are multiple data integrations

Answer: (B)

In lifecycle design, a single identity profile is preferred when data sources are consistent and roles overlap. This approach enhances the efficiency and accuracy of identity management by consolidating information from various sources into one cohesive profile.

When the data from different systems is aligned and there is significant overlap in user roles across those sources, it allows for a unified view of the identity. This means that the identity can be managed more easily as it aggregates multiple aspects from various systems, making it simpler to maintain compliance, streamline access processes, and ensure that identity attributes are consistent across the organization.

In scenarios where identities are completely unique or where there are multiple data integrations, managing a single profile may become complex or unmanageable, as it might not effectively represent the unique characteristics and relationships of the identities involved. Similarly, when identities vary significantly in attributes, a single identity profile might fail to capture the necessary diversity needed for effective lifecycle management. Therefore, having consistent data sources with overlapping roles is crucial for the effective use of a single identity profile in lifecycle design.