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

Free QREP Exam Braindumps (page: 2)

Page 2 of 16
PDF with 60 Questions

Which is the path to add a new column to a single table in a task?

  1. Table Selection -> Schemas -> Add Column
  2. New Transformation -> Column -> Add Column
  3. Select Table -> Transform -> Add New
  4. Table Settings -> General -> Add New Column

Answer(s): 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 transformation.



Using Qlik Replicate, how can the timestamp shown be converted to unlx time (unix epoch - number of seconds since January 1st 1970)?

  1. SELECT datetime<1092941466, 'unixepoch*, 'localtime');
  2. SELECT datetime(482340664, 'localtime', 'unixepoch');
  3. strftime('%s*,SAR_H_COMMIT_TIMESTAMP) - <code>datetime.datetime</code>('%s','1970-01-01
    00:00:00')
  4. strftime*'%s,,SAR_H_COMMIT_TIMESTAMP) - strftime('%s','1970-01-01 00:00:00')
  5. Time.now.strftime(%s','1970-01-01 00:00:00')

Answer(s): 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 operation.
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 SQL. Option E uses Time.now.strftime, which appears to be Ruby code and is not applicable in the context of Qlik Replicate.
Therefore, the verified answer is D, as it correctly uses the strftime function to convert a timestamp to Unix time in Qlik Replicate.



Which information in Qlik Replicate can be retrieved from the server logs?

  1. Network and performance issues
  2. Load status and performance of task
  3. Specific task information
  4. Qlik Replicate Server status

Answer(s): D

Explanation:

The server logs in Qlik Replicate provide information about the Qlik Replicate Server instance, rather than individual tasks. The logs can include various levels of information, such as errors, warnings, info, trace, and verbose details. Specifically, the server logs can provide insights into:
Network and performance issues: These might be indicated by error or warning messages related to connectivity or performance bottlenecks.
Load status and performance of task: While the server logs focus on the server instance, they may contain information about the overall load status and performance, especially if there are server- level issues affecting tasks.
Specific task information: The server logs can include information about tasks, particularly if there are errors or warnings that pertain to task execution at the server level. Qlik Replicate Server status: This includes general information about the server's health, status, and any significant events that affect the server's operation. Therefore, while the server logs can potentially contain a range of information, the primary purpose is to provide details on the Qlik Replicate Server status (D), including any issues that may impact the server's ability to function properly and manage tasks.



Which two components are responsible for reading data from the source endpoint and writing it to the target endpoint in Full Load replication? (Select two.)

  1. SOURCE_UNLOAD
  2. TARGET_APPLY
  3. TARGET_UNLOAD
  4. SOURCE_CAPTURE
  5. TARGET_LOAD

Answer(s): A,E

Explanation:

The SOURCE_UNLOAD component is responsible for reading data from the source endpoint. The TARGET_LOAD component is responsible for writing the data to the target endpoint. These components work in tandem during the Full Load replication process to move data from the source to the target. According to Qlik Replicate documentation, these two components are crucial in handling the extraction and loading phases of Full Load replication.

In the context of Full Load replication with Qlik Replicate, the components responsible for reading data from the source and writing it to the target are:
SOURCE_UNLOAD: This component is responsible for unloading data from the source endpoint. It extracts the data that needs to be replicated to the target system. TARGET_LOAD: This component is in charge of loading the data into the target endpoint. After the data is extracted by the SOURCE_UNLOAD, the TARGET_LOAD component ensures that the data is properly inserted into the target system.
The other options provided do not align with the Full Load replication process:
B) TARGET_APPLY and D. SOURCE_CAPTURE are typically associated with the Change Data Capture (CDC) process, not the Full Load process.
C) TARGET_UNLOAD is not a recognized component in the context of Qlik Replicate's Full Load replication.
Therefore, the correct answers are A. SOURCE_UNLOAD and E. TARGET_LOAD, as they are the components that handle the reading and writing of data during the Full Load replication process.






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