QREP Practice Questions

To manage the load on a source database during an initial load, Qlik Replicate provides a specific setting to control concurrency. The "Maximum number of tables to load in parallel" option, located within the task's "Full Load Settings" (specifically on the Tuning tab), dictates how many concurrent processes, or "engines," Replicate will use. By default, this is set to five. To comply with the operative database's limitation of two concurrent engines, this setting must be modified to '2'. This ensures that Replicate does not overwhelm the source system, allowing the initial load to proceed without causing performance degradation or connection failures on the source.

A. "Apply Change Processing Tuning" settings relate to the ongoing Change Data Capture (CDC) phase, not the initial Full Load phase specified in the question.

B. This statement is factually incorrect. By default, Qlik Replicate loads multiple tables (typically five) in parallel to optimize the speed of the Full Load.

D. While the setting is in a "Tuning" sub-section, the primary configuration area is "Full Load Settings". Option C provides a more accurate high-level description of the required action.

1. Qlik Replicate User Guide (May 2023), Section: Task settings > Full Load settings > Tuning tab. The documentation states: "Maximum number of tables to load in parallel: The maximum number of tables that Qlik Replicate can load in parallel from the source database. The default is 5... You may want to decrease this value... if the source system is overloaded." This directly confirms that limiting the number of parallel table loads is the correct method to manage source system constraints. (Accessed via Qlik Help Portal).

Qlik Replicate provides a comprehensive notification system that allows administrators to monitor the health and status of the replication environment at three distinct levels. These are:

1. Server Events: Pertain to the overall Qlik Replicate server, such as license expiration, high memory usage, or disk space issues.

2. Task Events: Relate to the status of individual replication tasks, including events like a task starting, stopping, or encountering an error.

3. Endpoint Events: Concern the connectivity and status of source and target endpoints, such as connection failures.

Configuring alerts for all three categories is crucial for proactive monitoring and management.

A. This option is incomplete as it omits Server Events, which are critical for monitoring the overall health of the Replicate server itself.

B. This option is incomplete as it omits Task Events, which are essential for tracking the status and potential failures of individual replication jobs.

D. This option is incomplete as it omits Endpoint Events, which are necessary for monitoring the connectivity status of data sources and targets.

1. Qlik Replicate User Guide (May 2023). Chapter: "Managing and Monitoring Replicate", Section: "Setting up notifications", Page 101. The document explicitly states: "You can set up notifications for the following types of events: Server events, Task events, Endpoint events."

2. Qlik Help Portal, Qlik Replicate Documentation. Page: "Setting up notifications". The online documentation confirms the three categories of events for which notifications can be configured: Server, Task, and Endpoint. It provides detailed lists of specific events under each category.

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 are B, D, and E, as they represent the locations within Qlik Replicate

where log files can be accessed and read21.

PDFs are binary files, not text. The appropriate data type for storing large binary data, such as documents, images, or multimedia files, is a BLOB (Binary Large Object). Qlik Replicate is designed to handle LOB data types to efficiently replicate large, unstructured data. Using a BLOB column ensures that the binary integrity of the PDF file is maintained during replication from the source to the target system. Character-based data types like NCLOB or NVARCHAR would lead to data corruption as they are designed to handle text, not binary streams.

A. DLOB: This is not a standard or recognized Large Object (LOB) data type within Qlik Replicate or major database systems.

B. NCLOB: This data type is for National Character Large Objects (Unicode text) and is unsuitable for binary files like PDFs.

C. NVARCHAR(1000): This is a variable-length character string with a limited size, making it inappropriate for large binary files.

1. Qlik Replicate Documentation, "Working with LOBs": The official documentation distinguishes between different LOB types. It clarifies that BLOBs are used for binary data streams like images or sound files, while CLOBs and NCLOBs are for character data. This directly supports the choice of BLOB for binary PDF files. (Source: Qlik Replicate for Windows User Guide, section "Working with LOBs").

2. Qlik Replicate Documentation, "Data type support" for Oracle Source: The documentation for using Oracle as a source endpoint explicitly lists BLOB as a supported LOB data type. This confirms Replicate's capability to handle this specific data type for binary content. (Source: Qlik Replicate Help, "Using Oracle as a source" -> "Data type support").

3. Qlik Replicate Documentation, "Data type support" for Microsoft SQL Server Source: For SQL Server, data types like image and varbinary(max) are used for binary data and are supported by Replicate. These types are the SQL Server equivalents of a BLOB, reinforcing the principle of using binary types for binary files. (Source: Qlik Replicate Help, "Using Microsoft SQL Server as a source" -> "Data type support").

Qlik Replicate uses JSON (JavaScript Object Notation) files to export and import task definitions. This feature is fundamental for administrative operations such as creating backups, migrating tasks between different Replicate servers, or sharing task configurations with Qlik Support for troubleshooting. The exported JSON file encapsulates all the necessary task settings, including source and target endpoint configurations, table selections, and transformation rules, allowing for a complete and portable representation of the task.

A. Task CFG files: Qlik Replicate does not use the .cfg extension for the export and import of task definitions; this format is not standard for this function.

B. Task XML files: While XML is a common data interchange format, Qlik Replicate has standardized on JSON for exporting and importing task configurations.

C. Task INI files: INI is a legacy configuration file format and is not used by Qlik Replicate for managing modern, complex task definitions.

---

1. Qlik Replicate User Guide, "Exporting and importing tasks" section: The official documentation explicitly states, "You can export one or more task definitions to a JSON file. You can then import the task(s) to the same or a different Replicate server." This confirms JSON as the correct file format for task migration and backup. (Accessed via Qlik Help Portal for Qlik Replicate, May 2024 version).

2. Qlik Replicate repctl Command Line Reference, "exportrepository" command: The documentation for the command-line utility repctl shows the syntax for exporting a task, which specifies a JSON file. For example: repctl exportrepository task= file=. This provides further official validation of the JSON format. (Accessed via Qlik Help Portal, repctl Command Line Utility documentation).

Questions no: 17 Verified Answer: =

A. IBM IMS &

E. HP NonStop

Explanation:

Step by Step Comprehensive and Detailed Explanation with all Reference: =

ARC (Attunity Replicate Connect) CDC agents are used for capturing changes (CDC) and can be

utilized with both relational and non-relational endpoints supported by ARC. The endpoints that

have ARC CDC agents include:

IBM IMS (A): This is a database and transaction management system, and it is listed as one of the

endpoints supported by ARC CDC agents1.

HP NonStop (E): This is a platform for high-availability servers and is also supported by ARC CDC

agents1.

The other options provided do not align with the endpoints that have ARC CDC agents:

B . IBMDB2Z/OS: While DB2 for z/OS is a common database system, it is not mentioned in the

context of ARC CDC agents.

C . Kafka Source: Kafka is a streaming platform, and while it can be an endpoint for data, it is not

listed as having ARC CDC agents.

D . SAPHANA: SAP HANA is an in-memory database, and it is not specified as having ARC CDC agents.

Therefore, the verified answers are

A. IBM IMS and

E. HP NonStop, as they are the endpoints that

utilize ARC CDC agents for capturing changes1.

The Qlik Replicate bin directory is the designated location for binary executables and required dynamic-link libraries (DLLs), which include ODBC drivers. To ensure that the Qlik Replicate server can locate and load the necessary 64-bit drivers for establishing a connection to an ODBC-based endpoint, the driver files must be placed in the \bin folder. This is a standard prerequisite for configuring many database endpoints that rely on ODBC connectivity.

A. \Replicate\data: This directory is used for storing application data, such as task definitions, logs, and transaction files, not executable drivers.

B. \Replicate\users: This is not a standard directory within the Qlik Replicate installation path for storing system-level components like drivers.

D. \Replicate\drivers: While the name seems logical, Qlik Replicate does not use a dedicated \drivers directory by default. It expects necessary libraries and drivers to be in the \bin directory.

1. Qlik Replicate Official Documentation - Setting up Teradata as a source: In the "Prerequisites" section, the instructions state: "Copy the Teradata client libraries (or the entire client installation) to the /bin directory." This confirms the bin directory is the correct location for client libraries, which include the ODBC drivers. (Qlik Replicate Help, "Data sources and targets" -> "Teradata" -> "Setting up Teradata as a source").

2. Qlik Replicate Official Documentation - Setting up Netezza as a source: The "Prerequisites" for configuring a Netezza source explicitly require the user to: "Copy the Netezza client libraries to the /bin directory." This reinforces the standard practice of placing necessary drivers in the bin folder. (Qlik Replicate Help, "Data sources and targets" -> "Netezza" -> "Setting up Netezza as a source").

In Qlik Replicate, the "Table Errors" handling settings allow for an escalation action to be triggered after a specified number of retries fail. The user can configure one of three possible actions: Stop task (the default action), which halts the entire replication task; Suspend table, which stops replication only for the table that encountered the error while others continue; or No action, which allows the task to continue running without stopping or suspending. All three are valid, configurable options for escalating a table error.

A. Log Record to the Exceptions Table: This action is specific to handling "Apply Conflicts" (e.g., record-not-found on UPDATE), not a general escalation option for all types of "Table Errors" like data truncation or constraint violations.

1. Qlik Replicate User Guide (May 2023): In the section "Defining and managing tasks," under "Setting task options" -> "Error Handling," the subsection "Table Error Handling settings" details the available choices for the Escalate action dropdown menu. It explicitly lists Stop task (Default), Suspend table, and No action as the three possible options. (p. 201).

The repctl utility is a command-line interface for managing Qlik Replicate. To export a repository object, such as a task, the correct command is exportrepository. This command requires specifying the object type and its name. The correct syntax to specify a task is using the argument task=. Therefore, the complete and accurate command to export the specified task is repctl exportrepository task=Oracle2SSTarget1. Note that repct1 in the options is a common typo for repctl.

B. exporttask is not a valid command within the repctl utility. The correct command for exporting any repository object is exportrepository.

C. export is an incomplete and invalid command. Additionally, the syntax task-Oracle2SSTarget1 is incorrect for specifying the task name.

D. exporttask is not a valid command in the repctl utility. The correct command is exportrepository.

1. Qlik Replicate User Guide (November 2023), "Managing Replicate using commands" -> "repctl command syntax" -> "Repository commands". The documentation explicitly lists exportrepository as the command for exporting repository objects. The syntax provided is: repctl exportrepository [jsonfile=] [collection=] [task=] [noct=] [nopasswords=]. This confirms that task= is the correct argument for specifying a task. (Reference available via the official Qlik Help portal).

To add a new column to a single table within a Qlik Replicate task, the user must first navigate to the Table Selection tab. From there, the specific table is selected, and the Transform settings for that table are opened. Inside the Transform tab, the user can then use the "Add Column" function to define the new column, its data type, and an expression to populate its value. This process ensures the transformation is applied only to the selected table.

A. Table Selection -> Schemas -> Add Column: This path is incorrect. Schema-level operations are managed differently and do not involve adding a column to a single, specific table in this manner.

B. New Transformation -> Column -> Add Column: This describes the process for creating a global transformation, which would apply the new column to all tables in the task, not a single table as specified.

D. Table Settings -> General -> Add New Column: The General tab within a table's settings is used for defining properties like the target table name and schema, not for adding or transforming columns.

1. Qlik Replicate User Guide (May 2023): In the section "Defining transformations on a single table," the procedure is outlined. It states: "In the Table Selection tab, select the table that you want to transform. The Transform button will be enabled above the list of tables. Click Transform to open the Transform tab for the selected table... To add a column to the table, click the Add Column button..." This directly supports the path of selecting a table and then using the Transform function. (See Chapter: Using Transformations, Sub-section: Defining transformations on a single table).

2. Qlik Help - Replicate (November 2023): The online documentation for "Defining transformations on a single table" confirms the same steps. It shows that after selecting a table from the Table Selection screen, the user clicks the Transform button to access the interface for adding columns. This aligns with the sequence described in option C. (See Qlik Help Portal -> Qlik Replicate -> Transforming data -> Defining transformations on a single table).