Qlik QREP Exam Dumps

To run daily reports about the changes that have occurred within the past 24 hours using Qlik Replicate, the option that must be set is Store Changes. This feature enables Qlik Replicate to keep a record of the changes that have occurred over a specified period, which in this case is the past 24 hours.

B . Store Changes: This setting allows Qlik Replicate to capture and store the changes made to the data in the source system. These stored changes can then be used to generate reports that reflect the data modifications within the desired timeframe1.

The other options are not specifically designed for the purpose of running daily change reports:

A . Apply Changes: This option is related to applying the captured changes to the target system, which is a different stage of the replication process.

C . Stage Changes: Staging changes involves temporarily storing the changes before they are applied to the target, which is not the same as storing changes for reporting purposes.

Questions no: 38 Verified Answer: = B. Admin

Explanation: Step by Step Comprehensive and Detailed Explanation with all Reference: = In Qlik Replicate, different user roles are assigned specific permissions that dictate what tasks they can perform within the system. To import tasks into Qlik Replicate, a user must have the Admin role. Here's the breakdown of permissions for each role related to task management:

Admin: This role has the highest level of permissions, including the ability to import tasks. Users with the Admin role can perform all operations within Qlik Replicate, such as creating, designing, deleting, exporting, and importing tasks1.

Designer: Users with this role can create and design tasks but do not have permission to import tasks.

Operator: This role allows users to perform runtime operations like start, stop, or reload targets but does not include permissions to import tasks.

Viewer: Users with the Viewer role can view task history and other details but cannot perform task management operations like importing tasks.

Therefore, the correct answer is B. Admin, as only users with the Admin role are granted the permission to import tasks into Qlik Replicate1.

When a new column is added to one of the tables in a Qlik Replicate task, the administrator should stop and then resume the task to replicate this change. This process allows Qlik Replicate to recognize the structural change and apply it accordingly.

The steps involved in this process are:

Stop the task: This ensures that no data changes are missed during the schema change.

Resume the task: Once the task is resumed, Qlik Replicate will pick up the DDL change and apply the new column to the target system.

This procedure is supported by the Qlik Replicate's DDL handling policy, which can be set to perform an ''alter target table'' when the source table is altered. This means that when the task is resumed, the new columns from the source tables will be added to the Replicate target1.

It's important to note that while stopping and resuming the task is generally the recommended approach, the exact steps may vary depending on the specific configuration and version of Qlik Replicate being used. Therefore, it's always best to consult the latest official documentation or support resources to ensure the correct procedure for your environment.

The attrep_apply_exceptions table in Qlik Replicate is used for troubleshooting specific issues that occur during the data replication process. Based on the documentation and community discussions, the two situations where this table can be particularly useful are:

Apply conflicts (B): This table records errors related to conflicts that occur when applying changes to the target system. For instance, if there is a primary key violation or a constraint failure, the details of the conflict are logged in this table1.

Data errors (E): The table also captures errors related to the data itself, such as missing data or data type mismatches. If a record cannot be applied due to data-related issues, the error message and the statement that caused the error are stored in the attrep_apply_exceptions table2.

The attrep_apply_exceptions table is not typically used for abnormal termination (A), table errors , or environment errors (D) as these issues are generally logged elsewhere within the system or require different troubleshooting approaches. For example, abnormal terminations might be logged in system event logs, while environment errors could be related to infrastructure issues outside the scope of Qlik Replicate's control tables.

In Qlik Replicate, tasks can be exported and imported for various purposes such as remote backup, migration, troubleshooting, and configuration updates. The format used for these operations is the JSON file format. Here's how the process works:

To export tasks, you can use the repctl exportrepository command, which generates a JSON file containing all task definitions and endpoint information (except passwords)1.

The generated JSON file can then be imported to a new server or instance of Qlik Replicate using the repctl importrepository command, allowing for easy migration or restoration of tasks2.

This JSON file contains everything required to reconstruct the data replication project, making it an essential tool for administrators managing Qlik Replicate tasks3.

Therefore, the correct answer is D. Task JSON files, as they are the files that can be exported and imported in Qlik Replicate for the mentioned purposes123.