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: 6)

Page 5 of 16
PDF with 60 Questions

Which two endpomts have ARC (Attunity Replicate Connect) CDC (Change Data Capture) agents? (Select two )

  1. IBM IMS
  2. IBMDB2Z/OS
  3. Kafka Source
  4. SAPHANA
  5. HP NonStop

Answer(s): A,E

Explanation:

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 agents.
HP NonStop (E): This is a platform for high-availability servers and is also supported by ARC CDC agents.
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 changes.



AQlik Replicate administrator requires data from a CRM application that can be accessed through different methods. How should this be done?

  1. Connect directly to the application
  2. Export tables to CSVs in a shared folder and connect to that
  3. Connect to the REST API provided by the application
  4. Connect to the underlying RDBMS

Answer(s): C

Explanation:

When a Qlik Replicate administrator needs to access data from a CRM application, the most efficient and direct method is often through the application's REST API. Here's why:
Connect to the REST API provided by the application ©: Many modern CRM applications provide a REST API for programmatic access to their data. This method is typically supported by data integration tools like Qlik Replicate and allows for a more seamless and real-time data extraction process. The REST API can provide a direct and efficient way to access the required data without the need for intermediate steps.
Connect directly to the application (A): While this option might seem straightforward, it is not always possible or recommended due to potential limitations in direct application connections or the lack of a suitable interface for data extraction.
Export tables to CSVs in a shared folder and connect to that (B): This method involves additional steps and can be less efficient. It requires manual intervention to export the data and does not support real-time data access.
Connect to the underlying RDBMS (D): Accessing the underlying relational database management system (RDBMS) can be an option, but it may bypass the business logic implemented in the CRM application and could lead to incomplete or inconsistent data extraction. Given these considerations, the REST API method © is generally the preferred approach for accessing CRM application data in a structured and programmable manner, which aligns with the capabilities of Qlik Replicate.



A customer needs to run daily reports about the changes that have occurred within the past 24 hours When setting up a new Qlik Replicate task, which option must be set to see these changes?

  1. Apply Changes
  2. Store Changes
  3. Stage Changes
  4. Full Load

Answer(s): B

Explanation:

To run daily reports about the changes that have occurred within the past 24 hours using Qlik Replicate, the option that must be set is Store Changes. This feature enables Qlik Replicate to keep a record of the changes that have occurred over a specified period, which in this case is the past 24 hours.

B) Store Changes: This setting allows Qlik Replicate to capture and store the changes made to the data in the source system. These stored changes can then be used to generate reports that reflect the data modifications within the desired timeframe.
The other options are not specifically designed for the purpose of running daily change reports:

A) Apply Changes: This option is related to applying the captured changes to the target system, which is a different stage of the replication process.
C) Stage Changes: Staging changes involves temporarily storing the changes before they are applied to the target, which is not the same as storing changes for reporting purposes. D. Full Load: The Full Load option is used to replicate the entire dataset from the source to the target, which is not necessary for generating reports based on changes within a specific timeframe. For more information on how to configure the Store Changes option and generate reports based on the stored changes, you can refer to the official Qlik documentation and community discussions that provide insights into best practices for setting up replication tasks and managing change data.



During the process of handling data errors, the Qlik Replicate administrator recognizes that data might be truncated Which process should be used to maintain full table integrity?

  1. Stop Task
  2. Suspend Table
  3. Ignore Record
  4. Log record to the exceptions table

Answer(s): D

Explanation:

When handling data errors in Qlik Replicate, especially when data might be truncated, maintaining full table integrity is crucial. The best approach to handle this situation is to log the record to the exceptions table. Here's why:
Log record to the exceptions table (D): This option allows the task to continue processing while ensuring that any records that could not be applied due to errors, such as truncation, are captured for review and resolution. The exceptions table serves as a repository for such records, allowing administrators to address the issues without losing the integrity of the full dataset. Stop Task (A): While stopping the task will prevent further data processing, it does not provide a mechanism to handle the specific records that caused the error. Suspend Table (B): Suspending the table will halt processing for that specific table, but again, it does not address the individual records that may be causing truncation issues. Ignore Record ©: Ignoring the record would mean that the truncated data is not processed, potentially leading to data loss and compromising table integrity. Therefore, the verified answer is D. Log record to the exceptions table, as it allows for the identification and resolution of specific data errors while preserving the integrity of the overall table data.






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

QREP Discussions & Posts