Yes. Aggregation partitioning in SailPoint IdentityIQ is a performance and scalability option used to divide a large aggregation workload into smaller units of work. Instead of processing the entire aggregation as one continuous task on a single execution thread, IdentityIQ can partition the work so multiple task executors can process different portions of the aggregation workload concurrently.
This is especially useful in large environments where applications contain many accounts, groups, or entitlement records. Partitioning can improve throughput by distributing processing across multiple hosts in an IdentityIQ deployment and by allowing multiple threads per host to participate in the aggregation workload. The goal is to reduce total aggregation runtime while maintaining controlled processing of account and entitlement data.
Partitioning is not the same as connector-based delta processing. Delta processing depends on connector support for identifying changed records, while partitioning concerns how the aggregation workload is divided and executed. Therefore, the statement is accurate.
Reference topics: Applications, aggregation task options, aggregation partitioning, account aggregation, performance optimization, task execution, and multi-host processing.

Yes. In SailPoint IdentityIQ, some application connectors include predefined schema information because the structure of accounts and groups on those target systems is well known to the connector. When an application is created and a specific connector type is selected, IdentityIQ may automatically populate schema elements such as the account schema, native identity attribute, display attribute, common account attributes, and sometimes group or entitlement schema definitions. This is common for standard connectors where the managed system has a predictable object model.
However, predefined does not mean final or immutable. The application administrator must still review and adjust the schema to ensure it accurately represents the implementation, including which attributes are aggregated, which attributes are searchable, which attributes are entitlements, and which attributes are used for identity correlation. Other connector types, such as generic JDBC, delimited file, or custom connectors, may require more manual schema definition.
This statement is therefore accurate because connector selection can provide default schema structure. Reference topics: Applications, connector selection, account schema, group schema, schema attributes, aggregation configuration, and application definition.

Yes. In SailPoint IdentityIQ, marking an application account schema attribute as managed designates that the values discovered for that attribute are treated as managed entitlement values and promoted into the Entitlement Catalog. This is typically used for attributes that represent access, such as groups, roles, permissions, profiles, or other application-specific entitlement assignments. During aggregation, IdentityIQ reads account data from the application. When a schema attribute is marked as managed, the distinct values of that attribute can become ManagedAttribute objects, allowing IdentityIQ to govern them as cataloged access items.
This catalog promotion is important because raw technical values often need business context before they can be reviewed, requested, approved, certified, or reported on. The Entitlement Catalog can store metadata such as display name, description, owner, requestability, classification, and other governance attributes. These values then become usable in access certifications, access requests, reports, policy evaluation, and role modeling.
Therefore, the statement accurately describes the managed attribute function. Reference topics: Applications - account schema attribute properties; Access Modeling - entitlement catalog; Governance - certification content and entitlement review.

Yes. In SailPoint IdentityIQ, preventive policy checking evaluates proposed access changes before the request is completed or provisioned. When a user submits an access request, IdentityIQ can analyze the requested roles, entitlements, or account changes against configured policies, including separation-of-duty and other access-control policies. If the requested access would create a policy violation, IdentityIQ can present a notification or warning to the requester during the request process.
This notification allows the requester to understand that the requested access conflicts with defined governance rules before the request proceeds further. Depending on configuration, IdentityIQ may allow the request to continue with warning, require additional approval or mitigation, or prevent the request from being submitted. The behavior is controlled by policy configuration, request workflow, and preventive checking settings.
Therefore, the statement is accurate: IdentityIQ can notify the requester when an access request will cause a policy violation. Reference topics: Governance, policy detection, preventive policy checking, access request evaluation, policy violations, and User-Driven Requests.

No. Defining access conditions that violate business policies is not provisioning. In SailPoint IdentityIQ, this activity belongs to governance and policy configuration. Policies define conditions that IdentityIQ should detect as violations, such as separation-of-duty conflicts, prohibited combinations of access, excessive privilege, or access that conflicts with organizational rules. These policies are evaluated against identities, roles, accounts, and entitlements to identify existing or potential violations.
Provisioning is the execution or fulfillment of access changes. Examples of provisioning include creating an account, modifying account attributes, adding or removing entitlements, disabling an account, deleting an account, or generating manual fulfillment work items. A policy violation may influence provisioning by blocking a request, warning the requester, requiring approval, or triggering remediation, but defining the violation condition itself is not a provisioning action.
Therefore, the described action is governance policy definition, not provisioning. Reference topics:
Governance, policy configuration, policy detection, preventive policy checking, Provisioning, provisioning plans, remediation, and access-change fulfillment.