A team is using static analysis to detect memory leaks in a C++ codebase. Which findings are likely to be reported by a static analysis tool? (Select all that apply.)

A potential double-free of a pointer

A missing delete for a memory allocation in a function

The exact amount of memory leaked at runtime

A possible use-after-free scenario

A Valgrind memcheck report for a C program shows 'definitely lost: 100 bytes in 1 blocks' at a specific source line. What is the most appropriate interpretation?

The program is using uninitialized memory

The program has a buffer overflow

The program is reading freed memory

The program allocated memory that was never freed, and the leak is confirmed

In a garbage-collected environment, how can garbage collection monitoring help detect memory leaks?

By forcing the garbage collector to run more frequently to prevent leaks.

By measuring the time taken for each garbage collection to determine if the GC is efficient.

By counting the number of garbage collections performed, which directly indicates the number of leaks.

By observing that the heap size continues to grow after garbage collections, indicating that objects are being retained unnecessarily.

A test analyst is evaluating tools for memory leak detection in a mixed-language environment: a C++ backend and a Java frontend. The team wants a single tool that can handle both. Which tool is most appropriate?

Use a static analysis tool like Clang for both

Use VisualVM for both languages

Use separate tools: Valgrind for C++ and a Java profiler like VisualVM

Use Valgrind for both languages

In a reference-counting environment (e.g., Objective-C with ARC or Python's reference counting), which of the following is a common cause of memory leaks?

Using a global variable to store a temporary value that is overwritten frequently.

Allocating an object on the heap without ever storing a reference to it.

Circular references where two objects hold strong references to each other, so their reference counts never reach zero.

Using a weak reference to an object that is still needed, causing it to be deallocated prematurely.

Certified Tester Advanced Level Technical Test Analyst

Domain 3Objective 6

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

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 1–5

1expert · hard · select all that apply
A team is using static analysis to detect memory leaks in a C++ codebase. Which findings are likely to be reported by a static analysis tool? (Select all that apply.)
Select an answer first
2application · medium
A Valgrind memcheck report for a C program shows 'definitely lost: 100 bytes in 1 blocks' at a specific source line. What is the most appropriate interpretation?
Select an answer first
3foundation · easy
In a garbage-collected environment, how can garbage collection monitoring help detect memory leaks?
Select an answer first
4expert · hard
A test analyst is evaluating tools for memory leak detection in a mixed-language environment: a C++ backend and a Java frontend. The team wants a single tool that can handle both. Which tool is most appropriate?
Select an answer first
5foundation · easy
In a reference-counting environment (e.g., Objective-C with ARC or Python's reference counting), which of the following is a common cause of memory leaks?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back 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.