A heap dump analysis shows that a Java application retains many instances of a custom class, but the dominator tree shows they are reachable from multiple threads' stack traces. What is the most likely cause?

The objects are being created faster than they are collected

The garbage collector is not running

The objects are intentionally kept alive by the threads' local variables

The objects are part of a circular reference

Certified Tester Advanced Level Technical Test Analyst

Domain 3Objective 6

Detecting Memory Leaks CTAL-TTA Practice Questions (Page 7)

Part of the Domain 3: Static and Dynamic Analysis domain, which makes up ~21% of our current practice bank. ISTQB does not publish an official question count, but from its 120-minute exam (~50–80 total, ~11–17 in this domain), expect 1–2 from this objective — we provide 31 practice questions to prepare you well beyond it. (estimate)

31questions here

7free pages

7concepts

Questions 31–31

31expert · hard
A heap dump analysis shows that a Java application retains many instances of a custom class, but the dominator tree shows they are reachable from multiple threads' stack traces. What is the most likely cause?
Select an answer first

Finished these 1 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to CTAL-TTA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CTAL-TTA” is a trademark of its owner, used for identification only.

Detecting Memory Leaks CTAL-TTA Practice Questions (Page 7)

Questions 31–31

A heap dump analysis shows that a Java application retains many instances of a custom class, but the dominator tree shows they are reachable from multiple threads' stack traces. What is the most likely cause?

Keep studying — Domain 3: Static and Dynamic Analysis