FC0-U71 Software Development Concepts Practice Question
In which phase of the Software Development Life Cycle (SDLC) are the system requirements gathered and analyzed?
⚠ Common exam trap
FC0-U71 often tests the distinction between the Planning and Analysis phases, as candidates may confuse high-level project planning (feasibility, scope) with the detailed requirements gathering and analysis that occurs in the Analysis phase.
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
✓
Analysis
The Analysis phase (also called Requirements Analysis or Requirements Gathering) is specifically dedicated to eliciting, documenting, and validating stakeholder needs and system requirements. During this phase, business analysts and developers work with stakeholders to define functional and non-functional requirements, often producing artifacts like a Software Requirements Specification (SRS). This is distinct from planning, which focuses on feasibility and project scope, and design, which translates requirements into technical blueprints.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Implementation
Why it's wrong here
Implementation writes and tests code from an approved design, so requirements have already been gathered and baselined. It is tempting because developers often clarify details while coding, but that is rework, not the SDLC phase whose purpose is eliciting and analysing system requirements.
- ✓
Analysis
Why this is correct
Requirements gathering and analysis occur during the Analysis phase, where stakeholder needs are elicited, documented and validated before design begins. This phase produces the functional and non-functional specifications that later phases depend on, satisfying the stem's constraint of identifying where requirements are gathered and analysed.
- ✗
Design
Why it's wrong here
Design translates gathered requirements into architecture, interfaces and data models; it consumes requirements rather than eliciting them. It is tempting because design documents often restate requirements, but the gathering and analysis activity belongs to the requirements phase, which precedes design in the SDLC.
- ✗
Planning
Why it's wrong here
Planning defines scope, feasibility, schedule and resources; it produces the project charter rather than eliciting and analysing detailed system requirements. It is tempting because planning sounds like early information gathering, but the formal requirements phase, not planning, is where stakeholder needs are captured and analysed.
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.