Qlik Replicate Certification QREP Exam Questions

Answer : C

The error message 'Failed adding supplemental logging for table' indicates that supplemental logging is not enabled on the Oracle source.

Supplemental logging must be enabled to capture the necessary changes for replication.

To fix this error, you should enable supplemental logging on the Oracle database for the specific table or tables.

This can usually be done by executing the following SQL command on the Oracle source:

ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;

Verify that the logging is enabled and then retry the replication task. This solution aligns with the troubleshooting steps provided in the Qlik Replicate documentation for dealing with supplemental logging errors.

The error message ''Failed adding supplemental logging for table 'Table name''' indicates that supplemental logging has not been enabled for the table in the Oracle source database. Supplemental logging is necessary for Qlik Replicate to capture the changes in the Oracle database accurately, especially for Change Data Capture (CDC) operations.

To resolve this error, you should:

Enable supplemental logging at the database level by executing the following SQL command in the Oracle database:

ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;

This command enables minimal supplemental logging, which is required for Qlik Replicate to function correctly1.

If you need to enable supplemental logging for all columns, you can use the following SQL command:

ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;

This ensures that all necessary column data is logged for replication purposes1.

After enabling supplemental logging, verify that it is active by querying the v$database view:

SELECT supplemental_log_data_min FROM v$database;

The correct return value should be 'YES', indicating that supplemental logging is enabled1.

The other options provided are not directly related to the issue of supplemental logging:

A . Contact the Oracle DBA: While contacting the DBA might be helpful, the specific action needed is to enable supplemental logging.

B . Check the permission on the target endpoint: Permissions on the target endpoint are not related to the supplemental logging requirement on the source database.

D . Check the permission of the source endpoint: Permissions on the source endpoint are important, but the error message specifically refers to the need for supplemental logging.

Therefore, the verified answer is C. Enable supplemental logging, as it directly addresses the requirement to fix the error related to supplemental logging in Qlik Replicate21.

Answer : A

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.

Answer : C

To add a new source endpoint in Qlik Replicate, in addition to the connection string, username/password, and permission to the database, the presence of transactional logs is essential. Transactional logs are crucial because they record all changes made to the database, which Qlik Replicate uses to capture the data changes that need to be replicated.

Here's the process of adding a new source endpoint:

Access to the system: You must have access to the system where the endpoint resides.

Connection information: Provide the connection string, which includes the network address and other parameters needed to connect to the source database.

User credentials: Supply the username and password that have the necessary permissions to access the database.

Transactional logs: Ensure that transactional logs are available and accessible because Qlik Replicate uses these logs to track changes in the source database for replication purposes.

The requirement for transactional logs is consistent with the nature of Qlik Replicate's operation, which relies on change data capture (CDC) technology to detect and replicate database changes12.

It's important to note that while the database client (option A) and access to the database server (option D) are also important components in the overall setup, they are not specifically required to add a new source endpoint in the context of this question. File access (option B) is not directly related to the addition of a source endpoint in Qlik Replicate.

Answer : C

In Qlik Enterprise Manager, permissions can be managed in a granular way, and one of the key features is the ability to inherit permissions. Here's how it works:

Inherited permissions for all functions : By default, inheritance is enabled for all objects, including users and groups. This means that permissions are automatically carried over from the parent object, ensuring consistency and ease of management across different levels of the organizational structure1.

Using the same permissions as in Qlik Replicate (A) and Using the same permissions as in Qlik Replicate and Qlik Compose (D): While Qlik Enterprise Manager may integrate with Qlik Replicate and Qlik Compose, the permissions are not directly transferred or used in the same way. Each tool has its own set of permissions and roles that need to be configured separately.

Transfer rights from Qlik Replicate (B): There is no direct option to transfer rights from Qlik Replicate to Qlik Enterprise Manager. Permissions need to be set within the Enterprise Manager itself, although it may be guided by the roles and permissions defined in Qlik Replicate.

Therefore, the verified answer is C. Inherited permissions for all functions, as it reflects the capability of Qlik Enterprise Manager to set permissions based on inheritance, which simplifies the management of user permissions across the system1.

Answer : D

To address the issue of column names in a source endpoint being too long for the target endpoint's character limit, the Qlik Replicate administrator should:

D . Define a new Global Transformation rule of the Column type: This allows the administrator to create a rule that applies to all affected columns across all tables. By defining a global transformation rule, the administrator can systematically rename all columns that exceed the character limit1.

The process involves:

Going to the Global Transformations section in Qlik Replicate.

Selecting the option to create a new transformation rule of the Column type.

Using the transformation rule to specify the criteria for renaming the columns (e.g., replacing a prefix or suffix or using a pattern).

Applying the rule to ensure that all affected columns are renamed according to the defined criteria.

The other options are not as efficient or appropriate for solving the issue:

A . Open the Windows command line terminal and run the renamecolumn command: This is not a standard method for renaming columns in Qlik Replicate and could lead to errors if not executed correctly.

B . Visit the Table Settings for each table in a task and select the Transform tab: While this could work, it is not as efficient as defining a global transformation rule, especially if there are many tables and columns to update.

C . Visit the Table Settings for each table and select the Filter tab: The Filter tab is used for record selection conditions and not for renaming columns.

For more detailed instructions on how to define and apply global transformation rules in Qlik Replicate, you can refer to the official Qlik documentation on Global Transformations.

Answer : A

When a Qlik Replicate developer encounters errors about a duplicate key when applying INSERT, the first step to identify and resolve the issue is to:

A . Check the error message in the Apply Exceptions control table: This control table contains detailed information about any exceptions that occur during the apply process, including duplicate key errors. By examining the error messages, the developer can understand the cause of the issue and take appropriate action to resolve it1.

The process involves:

Accessing the Qlik Replicate Console.

Navigating to the task that is experiencing the issue.

Opening the Apply Exceptions control table to review the error messages related to the duplicate key issue.

Analyzing the error details to determine the cause, such as whether it's due to a source data problem or a target schema constraint.

The other options are not the correct initial steps for identifying the issue:

B . Stop and reload the task: This action might temporarily bypass the error but does not address the root cause of the duplicate key issue.

C . Stop task and enable the Apply Exceptions control table: The Apply Exceptions control table should already be enabled and checked for errors as the first step.

D . Stop and resume the task: Resuming the task without identifying the cause of the error will likely result in the error reoccurring.

For more information on how to troubleshoot and handle duplicate key errors in Qlik Replicate, you can refer to the official Qlik community articles and support resources that provide guidance on error handling and the use of the Apply Exceptions control table2.

Answer : C

When the ''Apply batched changes to multiple tables concurrently'' option is enabled in a Qlik Replicate task, the attrep_apply_exception control table stores specific information related to change processing errors. The details stored in this table include:

TASK_NAME: The name of the Qlik Replicate task.

TABLE_NAME: The name of the table.

ERROR_TIME (in UTC): The time the exception (error) occurred.

STATEMENT: The statement that was being executed when the error occurred.

ERROR: The actual error message1.

This information is crucial for troubleshooting and resolving issues that may arise during the replication process. The data in the attrep_apply_exception table is never deleted, ensuring a persistent record of all exceptions1.

The other options do not accurately reflect the information stored in the attrep_apply_exception control table:

A and B mention ''Warning_Time,'' which is not a column in the table.

D is incorrect because the table does store information about errors.

For more detailed information on the attrep_apply_exception control table and its role in handling change processing errors, you can refer to the official Qlik Replicate documentation1.