Cloud Kicks needs to purge detailed transactional records from Salesforce. The data should be aggregated at a summary level and available in…

The goal is to automate a process that aggregates detailed records into a summary, stores the summary in Salesforce, and purges the original details. A third-party ETL (Extract, Transform, Load) tool is designed for such data operations and can be scheduled to run automatically. It can extract data, perform the aggregation transformation, load the summary back, and then delete the source records. Schedulable Batch Apex is a native Salesforce solution for processing large data sets asynchronously. It can be coded to query records, calculate summaries, create summary records, and delete the detailed transactional records on a recurring schedule.

C. Third-party Business Intelligence system: BI systems are primarily for data analysis and visualization, not for data transformation and purging within the source system (Salesforce).

D. Apex Triggers: Triggers are not designed for large-scale, scheduled data processing. They execute on DML events and would be inefficient and likely hit governor limits.

1. Salesforce Developer Documentation, "Batch Apex". Batch Apex is designed for processing large numbers of records and can be scheduled. (See "Using Batch Apex" section).

2. Salesforce Developer Documentation, "Schedulable Interface". This interface allows developers to schedule Apex classes, such as a Batch Apex class, to run at a specific time.

3. Salesforce Architects, "Architect's Guide to Data Management". This guide discusses various data management strategies, including using ETL tools for data integration and archival processes (See "Data Archiving Strategies").