FC0-U71 Software Development Concepts Practice Question
During debugging, a developer sets a breakpoint and steps through the code line by line. Which debugging tool feature is being used to execute one line of code at a time?
⚠ Common exam trap
FC0-U71 often tests the distinction between breakpoints (pause at a line) and step execution (execute one line at a time), so candidates must focus on the 'one line at a time' phrasing.
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
✓
Step execution
Step execution (or stepping) is the debugging feature that executes one line of code at a time, allowing the developer to observe the program's state after each statement. This is typically done using 'Step Over', 'Step Into', or 'Step Out' commands in a debugger. The question describes exactly this line-by-line execution, which is step execution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Step execution
Why this is correct
Step execution runs one line of code at a time, pausing after each statement so the developer can inspect variable values and control flow. This matches the scenario of stepping through code line by line during debugging.
- ✗
Breakpoint
Why it's wrong here
A breakpoint pauses execution at a chosen line; it does not itself execute one line at a time. Stepping, not breaking, advances a single statement per action. Breakpoints are the correct tool for halting at a specific location before inspecting state, which is a different debugging task from line-by-line execution.
- ✗
Variable inspection
Why it's wrong here
Variable inspection displays current values of variables at a paused breakpoint; it does not itself execute the next line. It is tempting because inspecting state accompanies stepping, and would be correct when the developer needs to examine a variable's value rather than advance execution line by line.
- ✗
Logging
Why it's wrong here
Logging records runtime events to files or streams after execution; it cannot pause execution or advance one line at a time. It is tempting because logs are widely used to trace program behaviour, and would be correct for post-mortem diagnosis where interactive control of execution is not required.
About these practice questions
This FC0-U71 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
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.