New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Qlik QREP Exam - 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:

0/2000 characters
Margarett
3 months ago
Not sure about C, what if the checkpoint is outdated?
upvoted 0 times
...
Fannie
3 months ago
I’m leaning towards B, starting from a fixed date could work too.
upvoted 0 times
...
Lorrine
3 months ago
Wait, can we really ignore warnings? Sounds risky!
upvoted 0 times
...
Cecil
4 months ago
Definitely agree with C, makes the most sense!
upvoted 0 times
...
Cristina
4 months ago
I think option C is the best choice here.
upvoted 0 times
...
Virgie
4 months ago
I definitely recall that resuming and ignoring warnings is risky. We should avoid that option for sure.
upvoted 0 times
...
Kimberlie
4 months ago
I feel like starting from a fixed date could work, but what if there are changes that happened after the log files were deleted?
upvoted 0 times
...
Shantay
4 months ago
I think the "Recover from a locally stored checkpoint" option might be the best choice, but I need to double-check the implications of that.
upvoted 0 times
...
Walton
5 months ago
I remember we discussed the importance of consistency in the target endpoint, but I'm not sure which option is the safest.
upvoted 0 times
...
Sherill
5 months ago
I'm a bit confused by the options. I'll need to review the details more closely to decide which one is the best approach.
upvoted 0 times
...
Gerald
5 months ago
I'm leaning towards option B - starting processing changes from a fixed date and time. That seems like the safest approach to ensure consistency.
upvoted 0 times
...
Alex
5 months ago
Okay, let's see. The key seems to be finding a way to create a consistent state in the target endpoint given the limited data in the log files.
upvoted 0 times
...
Adelaide
5 months ago
Hmm, this is a tricky one. I'll need to think carefully about the options and the potential risks involved.
upvoted 0 times
...
Ronnie
5 months ago
Option C, recovering from a locally stored checkpoint, could be a good solution if we have a recent and reliable checkpoint available.
upvoted 0 times
...
Blossom
5 months ago
B for sure. The manifest file is where you declare all the activities, services, and other components that make up your Android app. Gotta know that one!
upvoted 0 times
...
Carry
1 year ago
I think resuming the task and ignoring warnings is the best option in this scenario.
upvoted 0 times
...
Lezlie
1 year ago
I would go with starting processing changes from a fixed date and time.
upvoted 0 times
...
Alease
1 year ago
I disagree, I believe recovering from a locally stored checkpoint is safer.
upvoted 0 times
...
Georgeanna
1 year ago
I think the safest way is to use Reload Target Run option.
upvoted 0 times
...
Angella
2 years ago
I think resuming the task and ignoring warnings is the best option in this scenario.
upvoted 0 times
...
Louis
2 years 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
2 years 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
2 years 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
2 years ago
I would go with starting processing changes from a fixed date and time.
upvoted 0 times
...
Adell
2 years ago
I disagree, I believe recovering from a locally stored checkpoint is safer.
upvoted 0 times
...
Paz
2 years ago
Eve
upvoted 0 times
Kendra
2 years ago
C) Recover from a locally stored checkpoint
upvoted 0 times
...
Teresita
2 years ago
B) Start processing changes from a fixed date and time
upvoted 0 times
...
Tesha
2 years ago
A) Use Reload Target Run option
upvoted 0 times
...
...
Catalina
2 years ago
I think the safest way is to use Reload Target Run option.
upvoted 0 times
...

Save Cancel