In Qlik Replicate's CDC (Change Data Capture) mode, the "Batch optimized apply" method is designed to enhance performance by grouping multiple individual changes into a single transaction before applying them to the target. The task can be configured to apply these batches based on two primary triggers that work in tandem: a time interval and data volume. The batch is applied whenever the specified time limit is reached OR the accumulated size of the change data reaches the defined volume threshold, whichever occurs first. This provides a flexible way to balance throughput and latency.

A. Source connection processes are configured at the source endpoint level, not within the change processing apply mode settings.

B. While you can limit the maximum number of records in a batch, the primary triggers for applying the batch are time and total data volume.

D. This option is incomplete as it only mentions the time-based trigger and omits the equally important volume-based trigger.

1. Qlik Replicate User Guide: In the section "Setting advanced run options," under the "Change Processing Tuning" tab, the configuration for "Batch optimized apply" mode explicitly lists the options: "Apply changes every seconds" (Time) and "Apply changes when accumulated changes exceed MB" (Volume). This directly confirms that batching is controlled by time and/or volume.

2. Qlik Community Knowledge Base: Article 000038693, "Qlik Replicate batch optimized apply mode and transaction apply mode," explains that in Batch Optimized Apply, "Replicate accumulates the changes and applies them to the target in batches. The batch is applied when either the configured time or size is reached." This corroborates the dual trigger mechanism.