FC0-U71 Software Development Concepts Practice Question
A development team is using an agile methodology. Which TWO of the following are typical practices in agile development?
⚠ Common exam trap
FC0-U71 often tests the contrast between agile and waterfall terminology — candidates pick options like 'fixed scope' or 'detailed design phase' because those sound like good project management, but they are actually waterfall hallmarks.
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
✓
Iterative development with short cycles
Option C is correct because agile development is built on iterative, incremental delivery through short cycles (sprints or iterations, typically 1–4 weeks) that produce a potentially shippable increment and allow frequent reprioritization based on feedback. Option D is correct because the daily standup (a short, time-boxed Scrum ceremony, usually 15 minutes) is a hallmark agile practice for synchronizing the team, surfacing impediments, and maintaining transparency. Options A and E are incorrect because waterfall phase transitions and a detailed design phase completed before coding reflect sequential, plan-driven lifecycle models rather than agile's continuous, cross-functional delivery. Option B is incorrect because agile embraces emergent, reprioritized scope (e.g., a groomed product backlog) rather than a fixed scope locked at project start.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Waterfall phase transitions
Why it's wrong here
Agile runs continuous, overlapping iterations rather than sequential phase gates with formal handoffs. Tempting because waterfall's discrete phases look orderly, but that model would be correct for a fixed-requirement project where design, build and test complete before the next begins.
- ✗
Fixed scope defined at project start
Why it's wrong here
Agile welcomes changing requirements throughout delivery, so scope is refined each iteration rather than frozen at kickoff. Tempting because fixed scope suits plan-driven contracts, but it would be correct only under a predictive waterfall engagement with signed-off baseline requirements.
- ✓
Iterative development with short cycles
Why this is correct
Agile delivers work in short, fixed-length iterations (typically one to four weeks), each producing a potentially shippable increment. This iterative cadence directly satisfies the stem's agile methodology constraint, enabling frequent inspection and adaptation rather than a single sequential delivery phase.
- ✓
Daily standup meetings
Why this is correct
The daily standup is a short, timeboxed sync where the team surfaces progress, plans the day and flags blockers. This ceremony satisfies the agile methodology constraint by sustaining continuous communication and rapid impediment removal throughout each iteration.
- ✗
Detailed design phase before coding
Why it's wrong here
Agile teams code iteratively, so a detailed design phase completed before coding contradicts the incremental delivery the stem describes. It is tempting because waterfall projects do front-load design; in a predictive, plan-driven lifecycle with fixed requirements, that phase would be the expected practice.
Visual reference
Go deeper
Related to this question
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 →
Same concept, more angles
2 more ways this is tested on FC0-U71
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO of the following are characteristics of the Agile software development methodology?
medium- A.Emphasis on detailed upfront planning
- B.Heavy documentation
- C.Rigid change control
- ✓ D.Customer collaboration
- ✓ E.Iterative development cycles
Why D: Option D (Customer collaboration) is correct because Agile methodology, as codified in the Agile Manifesto, explicitly values customer collaboration over contract negotiation, keeping the customer actively involved throughout development to provide continuous feedback. Option E (Iterative development cycles) is correct because Agile delivers software in short, repeated iterations (typically 1–4 week sprints) that produce working increments, enabling frequent inspection and adaptation. Options A, B, and C do not belong: detailed upfront planning, heavy documentation, and rigid change control are hallmarks of plan-driven or waterfall methodologies, whereas Agile favors just-in-time planning, working software over comprehensive documentation, and embracing changing requirements even late in development.
Variation 2. A software development team is adopting agile practices. Which TWO of the following are common characteristics of agile methodologies? (Select TWO.)
medium- A.Sequential phases (requirements→design→implementation)
- ✓ B.Iterative development with short cycles
- ✓ C.Responding to change over following a plan
- D.Fixed scope defined at the start
- E.Comprehensive documentation at each phase
Why B: Option B is correct because agile methodologies, such as Scrum and Extreme Programming, deliver work in short, repeating iterations (typically 1–4 week sprints) that produce a potentially shippable increment each cycle, rather than progressing through one long sequential pass. Option C is correct because it reflects one of the four values in the Agile Manifesto, which explicitly states a preference for 'responding to change over following a plan,' allowing teams to adapt scope and priorities as requirements evolve. Option A is incorrect because sequential phases (requirements→design→implementation) describe the waterfall model, which agile explicitly contrasts with its iterative and incremental approach. Option D is incorrect because agile embraces emergent and evolving scope rather than fixing the full scope at the start, which is characteristic of plan-driven/waterfall contracts. Option E is incorrect because agile values 'working software over comprehensive documentation,' favoring lightweight, just-enough documentation over exhaustive artifacts at each phase.
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.