Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Qlik Exam QV12SA Topic 3 Question 64 Discussion

Actual exam question for Qlik's QV12SA exam
Question #: 64
Topic #: 3
[All QV12SA Questions]

A system administrator looks in the QMC > Status > QVS Statistics No documents are open in the QlikView Server but the memory usage of the QlikView Server (QVS) process is still above 10 GB.

Which is the cause of this behavior?

Show Suggested Answer Hide Answer
Suggested Answer: B, E

Contribute your Thoughts:

Thaddeus
1 months ago
I bet the system admin is scratching their head, wondering 'Where did all my memory go?' Time to do some serious QlikView troubleshooting!
upvoted 0 times
...
Keneth
1 months ago
Haha, the QlikView Server must be really hungry, eating up 10 GB of memory! I wonder if it's going on a document binge.
upvoted 0 times
Vicki
4 days ago
C) The Document Timeout setting is too high, which causes documents to never time out and unload
upvoted 0 times
...
Stephane
23 days ago
B) A reload is currently running that uses memory in the QlikView Server until it is finished
upvoted 0 times
...
Asuncion
1 months ago
A) Cached data for unloaded documents remains in memory to decrease calculation time
upvoted 0 times
...
...
Caprice
2 months ago
Hmm, I'm not sure. C and D both sound plausible too. This is a tricky one!
upvoted 0 times
Dean
4 days ago
C) The Document Timeout setting is too high, which causes documents to never time out and unload
upvoted 0 times
...
Vilma
16 days ago
B) A reload is currently running that uses memory in the QlikView Server until it is finished
upvoted 0 times
...
Alexis
1 months ago
A) Cached data for unloaded documents remains in memory to decrease calculation time
upvoted 0 times
...
...
Noelia
2 months ago
B seems like the correct answer. If a reload is running, it would definitely use a lot of memory on the QlikView Server.
upvoted 0 times
Polly
14 days ago
It's possible, but I still think B is the most likely cause in this scenario.
upvoted 0 times
...
Willis
1 months ago
But could it also be A) Cached data for unloaded documents remains in memory to decrease calculation time?
upvoted 0 times
...
Moira
1 months ago
That makes sense, a reload would definitely use up a lot of memory.
upvoted 0 times
...
Valentine
1 months ago
I think it's B) A reload is currently running that uses memory in the QlikView Server until it is finished.
upvoted 0 times
...
...
Walton
2 months ago
I think the answer is A. Cached data for unloaded documents remains in memory to decrease calculation time. That makes the most sense to me.
upvoted 0 times
Hildred
1 months ago
User 2: That makes sense. It's important to optimize memory usage in the QlikView Server.
upvoted 0 times
...
Pamella
2 months ago
User 1: I think the answer is A. Cached data for unloaded documents remains in memory to decrease calculation time.
upvoted 0 times
...
...
Denny
2 months ago
I'm not sure, but I think it could also be B) A reload is currently running that uses memory in the QlikView Server until it is finished.
upvoted 0 times
...
Gerald
2 months ago
I agree with Lavelle. It makes sense that cached data would still be in memory even if no documents are open.
upvoted 0 times
...
Lavelle
2 months ago
I think the cause might be A) Cached data for unloaded documents remains in memory to decrease calculation time.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77