Important Qlik QREP Exam Questions

Answer: D

Explanation:

To add a new column to a single table in a Qlik Replicate task, the correct path is through Table Settings. Here's the process you would typically follow:

Navigate to the Table Settings of the table you wish to modify within your task.

Go to the General section.

Use the option to Add New Column.

This process allows you to add a column directly to the table's schema as part of the task configuration. It's important to note that this action is part of the task's design phase, where you can specify the schema changes that should be applied to the data as it is replicated.

The other options listed, such as New Transformation or Select Table -> Transform, are not the direct paths for adding a new column to a table's schema within a task. They are related to different aspects of task configuration and transformation1.

Answer: D

Explanation:

When using LogStream staging for replication in Qlik Replicate, the Staging folder is compressed and stored on the Qlik Replicate server itself. Here's the process:

A Log Stream Staging task is defined to replicate changes from the source endpoint to the Log Stream Staging folder1.

This task creates a ''Staging'' file in the Log Stream Staging folder, which contains the changes from the source database transaction log as a compressed binary file1.

The storage path for the streamed data, which includes the Staging folder, must be specified in the Log Stream target endpoint settings, and it is explicitly stated that this path should be located on the Replicate Server machine2.

Therefore, the correct answer is D. On the Qlik Replicate server, as the staging folder is located on the machine where Qlik Replicate server is running, and it is where the compressed staging files are stored12.

Answer: D

Explanation:

In Qlik Replicate, when multiple schema rename rules are applied, the final schema name is determined by the last applied setting that affects the schema name directly. Here's how the process works:

Global Transformation to rename schema to 'USER1': This rule will initially rename the schema from 'HR' to 'USER1'. However, this is not the final schema name as further changes are applied later in the task settings1.

Task Settings -> Target Metadata to enter the Target table schema as 'USER2': This setting overrides the previous global transformation rule and sets the target schema name to 'USER2'. This is because the Target Metadata settings are applied after the Global Transformations and directly affect the target schema name1.

Global Transformation to add a new column named 'SCHEMA' with expression as 'USER3': While this rule adds a new column with a value of 'USER3', it does not change the schema name itself. It only affects the content of a column within the tables1.

Therefore, the final target schema name, after considering all the applied settings, is D. USER2. This is because the Target Metadata setting in the task settings has the final say on the target schema name, and it is set to 'USER2'1.

Answer: D

Explanation:

The goal is to convert a timestamp to Unix time (seconds since January 1, 1970).

The strftime function is used to format date and time values.

To get the Unix epoch time, you can use the command: strftime('%s',SAR_H_COMMIT_TIMESTAMP) - strftime('%s','1970-01-01 00:00:00').

This command extracts the Unix time from the timestamp and subtracts the Unix epoch start time to get the number of seconds since January 1, 1970. This is consistent with the Qlik Replicate documentation and SQL standard functions for handling date and time conversions.

To convert a timestamp to Unix time (also known as Unix epoch time), which is the number of seconds since January 1st, 1970, you can use the strftime function with the %s format specifier in Qlik Replicate. The correct syntax for this conversion is:

strftime('%s', SAR_H_COMMIT_TIMESTAMP) - strftime('%s','1970-01-01 00:00:00')

This function will return the number of seconds between the SAR_H_COMMIT_TIMESTAMP and the Unix epoch start date. Here's a breakdown of the function:

strftime('%s', SAR_H_COMMIT_TIMESTAMP) converts the SAR_H_COMMIT_TIMESTAMP to Unix time.

strftime('%s','1970-01-01 00:00:00') gives the Unix time for the epoch start date, which is 0.

Subtracting the second part from the first part is not necessary in this case because the Unix epoch time is defined as the time since 1970-01-01 00:00:00. However, if the timestamp is in a different time zone or format, adjustments may be needed.

The other options provided do not correctly represent the conversion to Unix time:

Options A and B use datetime instead of strftime, which is not the correct function for this operation1.

Option C incorrectly includes <code>datetime.datetime</code>, which is not a valid function in Qlik Replicate and seems to be a mix of Python code and SQL1.

Option E uses Time.now.strftime, which appears to be Ruby code and is not applicable in the context of Qlik Replicate1.

Therefore, the verified answer is D, as it correctly uses the strftime function to convert a timestamp to Unix time in Qlik Replicate1.

Answer: B, E

Explanation:

When performing a Full Load to a target endpoint in Qlik Replicate, the task logging components that are associated with this process are TARGET_LOAD and SOURCE_UNLOAD.

TARGET_LOAD: This component is responsible for loading the data into the target endpoint. It represents the process where Qlik Replicate reads all columns/rows from the Source database and creates the exact same copy on the Target database1.

SOURCE_UNLOAD: This component is involved in unloading the data from the source endpoint. It is part of the Full Load process where the data is read from the source and prepared for transfer to the target2.

The other options provided are not directly associated with the Full Load process to a target endpoint:

TARGET_APPLY is related to the Change Data Capture (CDC) phase where changes from the source are applied to the target2.

FILE_TRANSFER is not a term directly associated with Qlik Replicate's logging components.

STREAM refers to the Log Stream tasks, which is a different type of task configuration used for saving data changes from the transaction log of a single source database and applying them to multiple targets2.

For a comprehensive understanding of the task types and options in Qlik Replicate, you can refer to the official Qlik community articles on Qlik Replicate Task Configuration Options and An Introduction to Qlik Replicate Tasks: Full Load vs CDC.