MENU
An operative database can only commit two engines to Qlik Replicate (or initial loads at any given time. How should the task settings be modified?
In a scenario where an operative database can commit only two engines to Qlik Replicate for initial loads, the task settings should be modified to ensure that no more than two tables are loaded at any given time. This can be achieved by:
C . Apply Full Load Settings to limit the number of engines to two: This setting allows you to specify the maximum number of concurrent table loads during the Full Load operation. By limiting this number to two, you ensure that the operative database's capacity is not exceeded1.
The other options are not suitable because:
A . Apply Change Processing Tuning: This option is related to the CDC (Change Data Capture) phase and not the initial Full Load phase. Increasing the apply batched changes interval would not limit the number of engines used during the Full Load.
B . Qlik Replicate tasks only load one table at a time by default: This statement is not accurate as Qlik Replicate can be configured to load multiple tables concurrently, depending on the task settings.
D . Apply Full Load Tuning to read a maximum number of tables not greater than two: While this option seems similar to the correct answer, it is not a recognized setting in Qlik Replicate's configuration options.
For detailed guidance on configuring task settings in Qlik Replicate, particularly for managing the number of concurrent loads, you can refer to the official Qlik community articles on Qlik Replicate Task Configuration Options.