FC0-U71 Software Development Concepts Practice Question
A developer is trying to find why a program is producing incorrect output. The developer runs the program with a debugging tool, sets a breakpoint at a specific line, and examines the values of variables at that point. Which debugging technique is being used?
⚠ Common exam trap
Candidates often confuse breakpoint inspection with step-through execution, but step-through involves actively moving through code line by line, whereas breakpoint inspection pauses at a single point for variable examination without stepping.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Breakpoint inspection
The developer is using breakpoint inspection, a debugging technique where execution is paused at a specific line of code (the breakpoint) to examine variable values at that exact moment. This allows the developer to inspect the program's state without stepping through each subsequent line, directly identifying why incorrect output occurs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Code review
Why it's wrong here
Code review is the manual, static inspection of source by a person, so it never runs the program or halts at a breakpoint to read variable state. It is tempting because review genuinely finds defects, and would be correct when the fault is a logic or style error visible in the source before execution.
- ✗
Step-through execution
Why it's wrong here
Step-through execution advances line by line from the start or a breakpoint, but the stem describes stopping at one breakpoint and inspecting variables, which is breakpoint debugging. Step-through is tempting because it also uses a debugger, and would be correct if the developer were tracing each statement's effect sequentially.
- ✗
Logging
Why it's wrong here
Logging records runtime events to files or consoles for later inspection; it cannot pause execution at a chosen line or expose live variable values. It is tempting because logs are a genuine debugging aid, and would be the right choice when breakpoints are impossible, such as in production or embedded systems.
- ✓
Breakpoint inspection
Why this is correct
Breakpoint inspection pauses execution at a chosen line so the developer can read live variable values at that exact moment. This directly matches the stem's described technique, unlike logging, stepping or static code review, which do not halt and examine state.
About these practice questions
Courseiva writes every FC0-U71 question from scratch — 988 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This FC0-U71 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-U71 exam.