Quick Answer
The answer is profiling, as it is the standard development practice for identifying a memory leak by analyzing an application’s runtime memory usage. Profiling works by monitoring object allocation and garbage collection in real time, allowing you to see which objects are retained unnecessarily and are not being freed, which directly reveals the source of the leak. On the CompTIA ITF+ FC0-U61 exam, this concept tests your understanding of how developers debug performance issues—profiling is the correct choice over debugging or logging because it provides a dynamic view of memory behavior. A common trap is confusing profiling with simple debugging, but remember that profiling specifically tracks resource consumption over time. To recall this easily, think: “Profiling pinpoints the pile-up” of uncollected objects.
This FC0-U61 practice question tests your understanding of software development concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A software application is experiencing performance degradation. The team suspects a memory leak. Which development practice should be used to identify the source of the leak?
Unit testing
Why wrong: Unit tests check functionality, not memory allocation over time.
Debugging
Why wrong: Debugging helps with logic errors but is not designed for memory leak detection.
Profiling
Profiling tools track resource usage, including memory allocation, to identify leaks.
Code review
Why wrong: Code review is manual and may not catch runtime memory leaks.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Profiling
Profiling is the correct practice because it involves monitoring the application's runtime behavior, including memory allocation and garbage collection. A memory profiler can track object creation and retention, pinpointing which objects are not being released and causing the leak. This is the standard approach for diagnosing memory leaks in languages like Java or C#.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Unit testing
Why it's wrong here
Unit tests check functionality, not memory allocation over time.
Debugging
Why it's wrong here
Debugging helps with logic errors but is not designed for memory leak detection.
Profiling
Why this is correct
Profiling tools track resource usage, including memory allocation, to identify leaks.
Related concept
Read the scenario before looking for a memorised answer.
Code review
Why it's wrong here
Code review is manual and may not catch runtime memory leaks.
Common exam traps
The trap here is that candidates confuse debugging (step-by-step logic inspection) with profiling (runtime performance and memory analysis), assuming any performance issue can be solved by stepping through code, but memory leaks require heap analysis tools.
Detailed technical explanation
Memory profilers work by hooking into the runtime's memory manager (e.g., JVM's heap dump analysis or .NET's GC roots) to track object references and identify 'leaked' objects that are still reachable but no longer needed. In Java, tools like VisualVM or YourKit can take heap dumps and analyze the 'retained heap' to find the exact allocation site. A real-world scenario is a web application that caches user sessions in a static HashMap without eviction, causing OutOfMemoryError after many users.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the FC0-U61 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Software Development Concepts — study guide chapter
Learn the concepts, then practise the questions
Software Development Concepts practice questions
Targeted practice on this topic area only
All FC0-U61 questions
512 questions across all exam domains
CompTIA ITF+ FC0-U61 study guide
Full concept coverage aligned to exam objectives
FC0-U61 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise FC0-U61 questions linked to IT Concepts and Terminology.
Practise FC0-U61 questions linked to Infrastructure.
Practise FC0-U61 questions linked to Applications and Software.
Practise FC0-U61 questions linked to Software Development Concepts.
Practise FC0-U61 questions linked to Security.
Practise FC0-U61 questions linked to Database Fundamentals.
Practise FC0-U61 questions linked to FC0-U61 fundamentals.
Practise FC0-U61 questions linked to FC0-U61 scenario.
Practise FC0-U61 questions linked to FC0-U61 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Software Development Concepts — This question tests Software Development Concepts — Read the scenario before looking for a memorised answer..
The correct answer is: Profiling — Profiling is the correct practice because it involves monitoring the application's runtime behavior, including memory allocation and garbage collection. A memory profiler can track object creation and retention, pinpointing which objects are not being released and causing the leak. This is the standard approach for diagnosing memory leaks in languages like Java or C#.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
Last reviewed: Jun 11, 2026
This FC0-U61 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the FC0-U61 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.