In Qlik Replicate, the options to read the log files are located in the following places:
In Diagnostic package (B): The diagnostic package in Qlik Replicate includes various log files that can be used for troubleshooting and analysis purposes1.
In Data directory of Installation (D): The log files are written to the log directory within the data directory.This is the primary location where Qlik Replicate writes its log files, and it is not possible to change this location2.
In Monitor of Qlik Replicate (E): The Monitor feature of Qlik Replicate allows users to view and manage log files.Users can access the Log Viewer from the Server Logging Levels or File Transfer Service Logging Level sub-tabs1.
The other options provided do not align with the locations where log files can be read in Qlik Replicate:
A: In Windows Event log: This is not a location where Qlik Replicate log files are stored.
C: In External monitoring tool: While external monitoring tools can be used to read log files, they are not a direct feature of Qlik Replicate for reading log files.
F: In Enterprise Manager: The Enterprise Manager is a separate component that may manage and monitor multiple Qlik Replicate instances, but it is not where log files are directly read.
Therefore, the verified answers areB,D, andE, as they represent the locations within Qlik Replicate where log files can be accessed and read21.

In the Qlik Enterprise Manager Analytics GUI, users can view messages related to both server and task trends. This includes:
Server-specific trends: These are metrics and trends related to the performance and usage of the servers, such as memory consumption and disk usage1.
Task-specific trends: These include metrics and trends specific to individual tasks, such as the number of tables and records processed, throughput, and the number of changes applied1.
Therefore, the correct answer isD. Server and task trends, as the Analytics tab in Qlik Enterprise Manager allows users to review trends over a specific time period for both servers and tasks.Users can filter the data to show information for a particular timeframe and for particular tasks, Replicate servers, source databases, and target databases2.
For more detailed information on the types of messages and trends that can be viewed in the Qlik Enterprise Manager Analytics GUI, you can refer to the official Qlik documentation onAnalytics dashboardsandAnalytics.

For stream endpoint types like Kafka or Azure Event Hubs in Qlik Replicate, there are specific limitations that apply to the replication options and target table preparation options:
D: The Store Changes replication option is not supported: This limitation is explicitly mentioned for Kafka1and Azure Event Hubs23. The Store Changes mode is not supported when using these stream endpoints, meaning that changes cannot be stored for later retrieval or reporting.
E: The DROP and CREATE table target table preparation option is not supported: This is also a known limitation for Kafka as a target endpoint1. The Drop and Create table Target Table Preparation option is not supported, which affects how tables are prepared on the target side during replication.
The other options are not correct because:
A: The Apply Changes replication option is not supported: This is not listed as a limitation for Kafka or Azure Event Hubs.
B: The Full Load replication option is not supported: Full Load is supported for Kafka1.
C: Associated tasks filling those endpoint types cannot be stopped: This is not mentioned as a limitation, and tasks can typically be stopped unless otherwise specified.
For more detailed information on the limitations of using Kafka or Azure Event Hubs as target endpoints in Qlik Replicate, you can refer to the official Qlik documentation123.