BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Qlik Exam QREP Topic 2 Question 5 Discussion

Actual exam question for Qlik's QREP exam
Question #: 5
Topic #: 2
[All QREP Questions]

The connection to the source endpoint is unavailable over several days. The log files contain only 2 hours of data before being deleted. Which Is the safest way to create a consistent state in the target endpoint?

Show Suggested Answer Hide Answer
Suggested Answer: A

When the connection to the source endpoint is unavailable for an extended period, and the log files are limited to only 2 hours of data before being deleted, the safest way to ensure a consistent state in the target endpoint is to use the Reload Target Run option (A). This approach is recommended because it allows for a complete refresh of the target data, ensuring that it is in sync with the source once the connection is re-established.

The Reload Target Run option is designed to handle situations where the replication logs are not sufficient to recover the replicated state due to extended outages or log retention policies. By reloading the target, you can be confident that the data reflects the current state of the source, without relying on potentially incomplete change logs.

Starting processing from a fixed date and time (B) or recovering from a locally stored checkpoint would not be reliable if the logs do not cover the entire period of the outage. Resuming the task and ignoring warnings (D) could lead to inconsistencies due to missed changes.

Therefore, the Reload Target Run option is the safest method to create a consistent state in the target endpoint under these circumstances1.


Contribute your Thoughts:

Carry
2 months ago
I think resuming the task and ignoring warnings is the best option in this scenario.
upvoted 0 times
...
Lezlie
2 months ago
I would go with starting processing changes from a fixed date and time.
upvoted 0 times
...
Alease
2 months ago
I disagree, I believe recovering from a locally stored checkpoint is safer.
upvoted 0 times
...
Georgeanna
2 months ago
I think the safest way is to use Reload Target Run option.
upvoted 0 times
...
Angella
3 months ago
I think resuming the task and ignoring warnings is the best option in this scenario.
upvoted 0 times
...
Louis
3 months ago
Option B seems like the way to go. Who needs recent data when you can just go back in time? Time travel is the future, I tell you!
upvoted 0 times
Melita
3 months ago
I agree, going back in time to a fixed date and time seems like a reliable way to create a consistent state in the target endpoint.
upvoted 0 times
...
Helene
3 months ago
I think option B is the safest choice. It's better to start processing changes from a fixed date and time.
upvoted 0 times
...
...
Adell
3 months ago
I would go with starting processing changes from a fixed date and time.
upvoted 0 times
...
Adell
3 months ago
I disagree, I believe recovering from a locally stored checkpoint is safer.
upvoted 0 times
...
Paz
4 months ago
Eve
upvoted 0 times
Kendra
3 months ago
C) Recover from a locally stored checkpoint
upvoted 0 times
...
Teresita
3 months ago
B) Start processing changes from a fixed date and time
upvoted 0 times
...
Tesha
3 months ago
A) Use Reload Target Run option
upvoted 0 times
...
...
Catalina
4 months ago
I think the safest way is to use Reload Target Run option.
upvoted 0 times
...

Save Cancel