What must be included in the JDBC source configuration for entitlement aggregation?

• A. User Roles
• B. Entitlement Schema
• C. Service Level Agreements
• D. Audit Logs

Answer: (B)

The inclusion of an entitlement schema in the JDBC source configuration for entitlement aggregation is essential because it defines the structure and organization of entitlement data within the database. An entitlement schema outlines how the entitlements are represented, including the tables, columns, and relationships among the data entities. This structure allows identity governance solutions to accurately retrieve, interpret, and aggregate entitlement information from the data source.

When the entitlement schema is correctly configured, it facilitates the seamless integration of the entitlement data into the identity management system. This process is crucial for effective access certification, compliance reporting, and ensuring that users have the appropriate access to resources based on their roles and responsibilities. Without a well-defined entitlement schema, the system may struggle to correctly identify and aggregate the entitlements, leading to incomplete or inaccurate identity information.

Other options, while potentially relevant in broader contexts of identity management, do not directly pertain to the specifics of configuring entitlements for aggregation within a JDBC source. For instance, user roles are significant but are typically part of the access control framework rather than the schema setup. Service Level Agreements relate to expectations and commitments regarding service delivery rather than data structure. Audit logs provide tracking and accountability but do not define how entitlements are stored or retrieved. Thus, the emphasis on the entitlement