FC0-U71 Software Development Concepts Practice Question
A testing team is verifying a new version of an e-commerce website. They run a set of pre-existing test cases to ensure that recent changes have not broken any previously working functionality. What type of testing is this?
⚠ Common exam trap
FC0-U71 often tests the distinction between regression testing (re-verifying existing functionality after changes) and retesting (verifying a specific fix) — candidates frequently pick 'system testing' because it sounds comprehensive.
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
✓
Regression testing
Regression testing re-runs previously passing test cases after code changes to confirm that new modifications have not broken existing functionality. The scenario describes exactly this: pre-existing test cases are executed to verify that recent changes did not introduce defects in working features. It is a core part of continuous integration pipelines.
Answer analysis
Option-by-option breakdown
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 testing exercises one isolated function or method, so it cannot confirm that previously working end-to-end functionality still passes. It tempts because unit tests are the fastest, most granular checks developers rerun constantly, yet the scenario requires re-running existing tests after changes.
- ✗
System testing
Why it's wrong here
System testing validates the complete integrated application against requirements, typically on a fresh build rather than replaying an existing regression suite. It tempts because it covers the whole e-commerce site end to end, but the stem's purpose of detecting broken prior functionality defines regression testing.
- ✓
Regression testing
Why this is correct
Regression testing re-executes existing test cases after code changes to confirm previously working functionality still behaves correctly. It directly targets the stem's goal of detecting unintended breakage introduced by the new website version, rather than validating new features or performance.
- ✗
Integration testing
Why it's wrong here
Integration testing verifies interactions between combined modules or services, not re-execution of existing cases after changes. It tempts because integration testing does exercise multiple components together, which suits validating data flow across an e-commerce checkout, but the stem describes regression testing.
About these practice questions
One of 988 original FC0-U71 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.