Which Loyalty Management Key Component should be used to quickly aggregate a high volume of data spread across many Loyalty Management objects?

The Data Processing Engine (DPE) is the correct component for this task. It is specifically designed to query large volumes of data from multiple standard and custom Salesforce objects, perform complex transformations and aggregations, and write the results back to other objects. In Loyalty Management, DPE is the standard tool used for computationally intensive processes like calculating qualifying points for tier upgrades, aggregating member behavior for promotions, and processing transaction journals. Its ability to handle high data volumes efficiently makes it the ideal choice for the described scenario.

A. Batch Management: This is a general administration feature for monitoring jobs. While DPE jobs run in batches, "Batch Management" itself is not the tool that performs the data aggregation.
B. Decision Table: Decision Tables are used to define and execute business rules based on a set of inputs (e.g., determining promotion eligibility), not for aggregating high volumes of data.
C. Quick Actions: Quick Actions are user interface components designed for users to perform simple, record-specific tasks, not for complex, back-end processing of large datasets.

1. Salesforce Help, Data Processing Engine: "Use Data Processing Engine to transform data that's available in your Salesforce org and write back the transformation results as new or updated records. Data Processing Engine gives you a user-friendly, declarative interface to query, filter, join, and aggregate data from various objects." (See "Get Started with Data Processing Engine" section).

2. Salesforce Help, Loyalty Management Tier Processing: "Loyalty Management uses a Data Processing Engine definition to run the tier assessment process... The Data Processing Engine job aggregates the member’s total qualifying points..." (See "How Does Tier Processing Work?" section).

3. Salesforce Help, Decision Tables: "Decision tables automate decisions by using a set of rules. A decision table contains a set of conditions and a corresponding set of results." (See "Decision Tables" section). This highlights its function as a rule engine, not a data aggregator.