FC0-U71 Software Development Concepts Practice Question
A developer is debugging a program that unexpectedly crashes. Which TWO tools or techniques are commonly used to identify the cause of the crash? (Select the two correct answers.)
⚠ Common exam trap
FC0-U71 often tests the difference between static techniques (code review, compilation) and dynamic techniques (breakpoints, logging) — candidates incorrectly include code review as a crash diagnosis tool, but it does not observe runtime behavior.
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
✓
Breakpoints
Breakpoints (C) are correct because they let a developer pause program execution at a specific line or condition, inspect variables, call stack, and memory state at the moment before the crash, which directly reveals the faulty logic or invalid value causing the failure. Logging (D) is correct because strategically placed log statements (or a logging framework) record runtime events, error messages, and stack traces leading up to the crash, allowing post-mortem analysis of the sequence of operations that triggered it. Code compilation (A) only translates source into executable code and would surface syntax or type errors at build time, not the runtime cause of a crash. Refactoring (B) restructures existing code to improve readability or design without diagnosing the crash, and code review (E) is a static, human inspection of source that may catch defects but does not observe the program's actual runtime behavior during the crash.
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 compilation
Why it's wrong here
Compilation translates source code into an executable and reports syntax errors, but it does not trace runtime state, so it cannot identify the cause of an unexpected crash. It is tempting because build failures feel like crashes, and it would be correct when resolving syntax or type errors flagged at build time.
- ✗
Refactoring
Why it's wrong here
Refactoring restructures existing code to improve readability or design without altering behaviour, so it cannot reveal the cause of a crash. It is tempting because cleaner code reduces latent defects, and it would be the right choice when improving maintainability of working code rather than diagnosing a failure.
- ✓
Breakpoints
Why this is correct
Breakpoints pause execution at a chosen line, letting the developer inspect variables, call stack and memory state immediately before the crash occurs. This satisfies the scenario by catching the fault at its source rather than inferring it afterwards from logs alone.
- ✓
Logging
Why this is correct
Logging records runtime events, variable states and error messages to a file or console, so after a crash the developer can trace the sequence of events leading up to it. This satisfies the scenario's need to identify the cause retrospectively, since the crash itself destroys in-memory state.
- ✗
Code review
Why it's wrong here
Code review inspects source for defects by human reading, which may spot suspicious logic but provides no runtime evidence about the crash. It is tempting because it is a core quality practice, and it would be correct when assessing maintainability, style or design before code is executed.
Go deeper
Related to this question
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.