Which quality describes ease of changing software?
A Portability
B Availability
C Scalability
D Maintainability
Answer: D. Maintainability. Maintainability is the ease with which software can be analyzed, modified, and tested.
Typically, what does a user story express?
A Role, need, benefit
B Class, method, variable
C Budget, risk, schedule
D Branch, commit, tag
Answer: A. Role, need, benefit. A common user-story form identifies a user role, a need, and its benefit.
How do acceptance criteria help a team?
A Set the project budget
B Choose programming languages
C Define acceptance conditions
D Replace product goals
Answer: C. Define acceptance conditions. Acceptance criteria make the conditions for accepting a story or feature explicit.
Which process gathers stakeholder needs?
A Software deployment
B Requirements elicitation
C Code refactoring
D Release monitoring
Answer: B. Requirements elicitation. Elicitation obtains requirements from stakeholders and other relevant sources.
Traceability links a requirement to what?
A Unrelated meeting notes
B Only source files
C Only team members
D Related project artifacts
Answer: D. Related project artifacts. Traceability connects requirements with sources, design, implementation, and tests.
Once approved, a baseline provides what?
A Automatic quality guarantee
B A new project estimate
C Controlled reference version
D An untested release
Answer: C. Controlled reference version. A baseline is an approved reference point that changes through controlled procedures.
Why create a version-control branch?
A Isolate parallel changes
B Erase the release history
C Replace automated tests
D Change stakeholder needs
Answer: A. Isolate parallel changes. Branches let work proceed separately before changes are integrated.
Version-control merging combines what?
A Requirements and budgets
B Branch changes
C Test plans and risks
D Users and permissions
Answer: B. Branch changes. A merge integrates changes from different branches into a target branch.
At a Sprint Review, participants mainly do what?
A Inspect the product increment
B Estimate every future task
C Approve individual timesheets
D Replace the Sprint Goal
Answer: A. Inspect the product increment. The Scrum Team and stakeholders inspect outcomes and discuss future adaptations.
During a retrospective, the team considers what?
A Which users to remove
B How to skip testing
C Which backlog to delete
D How to improve its work
Answer: D. How to improve its work. The retrospective focuses on improving quality and effectiveness.
What does the Definition of Done describe?
A A release calendar
B Shared completion criteria
C A user role
D A coding language
Answer: B. Shared completion criteria. It is a shared description of the state of work that meets the product's quality measures.
In continuous integration, teams integrate code how often?
A Only at project end
B Once per year
C Frequently
D After release only
Answer: C. Frequently. Frequent integration helps reveal integration problems earlier.
Automated builds mainly improve what?
A Repeatable packaging
B Stakeholder interviews
C User acceptance
D Risk ownership
Answer: A. Repeatable packaging. Build automation makes compiling and packaging more consistent and repeatable.
Static analysis examines source code how?
A Only after deployment
B Only through interviews
C By deleting test data
D Without running it
Answer: D. Without running it. Static analysis evaluates code or other artifacts without executing the program.
Which activity reviews requirements for ambiguity before approval?
A Load test
B Sprint Review
C Requirements review
D Mutation test
Answer: C. Requirements review. A requirements review helps find omissions, ambiguity, and inconsistency before implementation.
Smoke testing checks whether what?
A Every requirement is complete
B Key build functions work
C All edge cases pass
D The budget is accurate
Answer: B. Key build functions work. Smoke tests make a broad, shallow check that important functions of a build work.
Boundary-value analysis targets which inputs?
A Random source lines
B Unrelated data types
C Only middle values
D Input range edges
Answer: D. Input range edges. Boundary-value tests focus on values at and near the edges of input partitions.
Equivalence partitioning groups inputs with what?
A Similar expected behavior
B Identical source code
C Equal project cost
D The same developer
Answer: A. Similar expected behavior. Values in an equivalence partition are expected to be handled similarly.
In a test case, which details are essential?
A Budget and staffing
B Backlog and roadmap
C Inputs and expected results
D Build and release dates
Answer: C. Inputs and expected results. A test case specifies conditions or inputs and the expected outcome.
Why record expected results in a test case?
A Assign a product owner
B Compare actual behavior
C Estimate project duration
D Choose an architecture
Answer: B. Compare actual behavior. Expected results provide the basis for judging observed behavior.
When software must adapt to a new environment, use?
A Corrective maintenance
B Perfective maintenance
C Preventive maintenance
D Adaptive maintenance
Answer: D. Adaptive maintenance. Adaptive maintenance changes software to keep it usable in a changed environment.
Corrective maintenance addresses what?
A Discovered faults
B New operating environments
C New user capabilities
D Future code risks
Answer: A. Discovered faults. Corrective maintenance modifies software to correct faults found after delivery.
Which maintenance improves performance or usability?
A Adaptive maintenance
B Corrective maintenance
C Perfective maintenance
D Emergency maintenance
Answer: C. Perfective maintenance. Perfective maintenance enhances software to meet user needs or improve quality.
Reliability describes the likelihood of what?
A Fastest possible coding
B Failure-free operation
C Lowest project cost
D Complete user agreement
Answer: B. Failure-free operation. Reliability concerns failure-free operation under stated conditions for a stated time.
Teams build a minimum viable product to do what?
A Test core value
B Avoid all feedback
C Finish every feature
D Replace the product backlog
Answer: A. Test core value. An MVP provides enough value to test key assumptions with users and learn.