CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. QlikView
  5. QREP

Free QREP Exam Braindumps (page: 3)

Page 2 of 16
PDF with 60 Questions

Where are the three options in Qlik Replicate used to read the log files located? (Select three.)

  1. In Windows Event log
  2. In Diagnostic package
  3. In External monitoring tool
  4. In Data directory of Installation
  5. In Monitor of Qlik Replicate
  6. In Enterprise Manager

Answer(s): B,D,E

Explanation:

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 purposes.
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 location.
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-tabs.
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 read.



In the CDC mode of a Qlik Replicate task, which option can be set for Batch optimized apply mode?

  1. Source connection processes
  2. Number of changed records
  3. Time and/or volume
  4. Maximum time to batch transactions

Answer(s): C

Explanation:

In Change Data Capture (CDC) mode, Batch optimized apply mode can be set based on time and/or volume.
This means that the batching of transactions can be controlled by specifying time intervals or the volume of data changes to be batched together.
This optimization helps improve performance by reducing the frequency of writes to the target system and handling large volumes of changes efficiently. The Qlik Replicate documentation outlines this option as a method to enhance the efficiency of data replication in CDC mode by batching transactions based on specific criteria.

In the Change Data Capture (CDC) mode of a Qlik Replicate task, when using the Batch optimized apply mode, the system allows for tuning based on time and/or volume. This setting is designed to optimize the application of changes in batches to the target system. Here's how it works:
Time: You can set intervals at which batched changes are applied. This includes setting a minimum amount of time to wait between each application of batch changes, as well as a maximum time to wait before declaring a timeout.
Volume: The system can be configured to force apply a batch when the processing memory exceeds a certain threshold. This allows for the consolidation of operations on the same row, reducing the number of operations on the target to a single transaction. The other options provided do not align with the settings for Batch optimized apply mode in CDC tasks:
A) Source connection processes: This is not a setting related to the batch apply mode.
B) Number of changed records: While the number of changed records might affect the batch size, it is not a setting that can be directly configured in this context.
D) Maximum time to batch transactions: This option is related to the time aspect but does not fully capture the essence of the setting, which includes both time and volume considerations. Therefore, the verified answer is C. Time and/or volume, as it accurately represents the options that can be set for Batch optimized apply mode in the CDC tasks of Qlik Replicate.



How should missing metadata be added in a Qlik Replicate task after the task has been stopped?

  1. Drop tables or delete tables and data on target side, then run task from a certain timestamp
  2. Under Advanced Run option choose reload target, stop task again, and then resume processing
  3. Under Advanced Run option choose metadata only, stop task again, and then resume processing
  4. Drop tables and data on the target side, run advanced option, create metadata, and then resume task

Answer(s): C

Explanation:

If a task has missing metadata, you need to first stop the task.

Navigate to the "Advanced Run" options.
Select the option "Metadata Only."
Start the task with this setting to process the missing metadata.
Stop the task again after the metadata is added.
Resume normal task processing. This procedure ensures that only the metadata is processed without affecting the existing data on the target side. This method is recommended in Qlik Replicate documentation for handling missing metadata issues.

To add missing metadata in a Qlik Replicate task after the task has been stopped, the correct approach is to use the Advanced Run option for metadata only. Here's the process:
Select the task that requires metadata to be added.
Go to the Advanced Run options for the task.
Choose the Metadata Only option, which has two sub-options:
Recreate all tables and then stop: This will rebuild metadata for all available tables in the task. Create missing tables and then stop: This will rebuild metadata only for the missing tables or the tables that were newly added to the task.
By selecting the Metadata Only option and choosing to create missing tables, you can ensure that the metadata for the newly added tables is updated without affecting the existing tables and data. After this operation, you can stop the task again and then resume processing. The other options provided are not the recommended methods for adding missing metadata:
A and D suggest dropping tables or data, which is not necessary for simply adding metadata. B suggests reloading the target, which is not the same as updating metadata only. Therefore, the verified answer is C, as it accurately describes the process of adding missing metadata to a Qlik Replicate task using the Advanced Run options.



When running a task in Qlik Replicate (From Oracle to MS SQL), the following error message appears:
Failed adding supplemental logging for table "Table name" Which must be done to fix this error?

  1. Contact the Oracle DBA
  2. Check the permission on the target endpoint
  3. Enable supplemental logging
  4. Check the permission of the source endpoint

Answer(s): C

Explanation:

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 correctly.
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 purposes. 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 enabled. 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 Replicate.






Post your Comments and Discuss QlikView QREP exam with other Community members:

QREP Discussions & Posts