When a Data Definition Language (DDL) change, such as adding a new column, is executed on a source table, Qlik Replicate captures this event. To correctly apply this structural change to the target table, the task must be stopped and then resumed. This process forces Qlik Replicate to re-cache the table's metadata from the source endpoint. Upon resuming, Replicate will apply the pending DDL change (e.g., ALTER TABLE ... ADD COLUMN) to the target and then continue with the Change Data Capture (CDC) process from where it left off.

B. Stop task, enableCT tables, and resume: Change Tables (CT) are used for specific CDC processing modes like Batch Optimized Apply and are not relevant to propagating DDL changes.

C. Change the DDL Handling Policy to accommodate this change: This is a one-time configuration setting that defines how DDL is handled (e.g., replicate, ignore). It is not the operational step taken to apply a specific DDL change that has already occurred.

D. Stop and reload the task: A full reload is an inefficient and unnecessary action for this scenario. It involves truncating the target table and re-copying all data, whereas a simple resume operation applies only the structural change.

1. Qlik Replicate User Guide (May 2023), Section: DDL and CDC > DDL change handling. The documentation states, "When a DDL change is made to a source table, Replicate applies the change to the target table. In some cases, you may need to stop and then resume the task for the DDL change to be applied." This confirms that a stop/resume cycle is a standard procedure for certain DDL operations.

2. Qlik Replicate User Guide (May 2023), Section: Task Settings > DDL. This section describes the DDL handling policies. It clarifies that setting the policy is a configuration step, distinct from the operational step of applying a captured DDL change. The default policy is typically to replicate DDL changes, which would necessitate the stop/resume action described in option A.