QUESTIONS AND ANSWERS | 2026/2027
PRACTICE EDITION
Exam coverage: Capstone project definition and planning; requirements engineering; stakeholders;
Agile/Scrum/Kanban; scheduling; risk and quality management; software testing; architecture; databases;
networks; cybersecurity; privacy and ethics; research and evidence; UX/accessibility; cloud and
deployment; data/AI concepts; documentation; communication; project evaluation and closure.
Subject area: Information Technology / IT Project and Capstone Practice Course context: TECH8000 IT
Capstone
School: Kaplan Business School (KBS), Australia. KBS currently lists TECH8000 IT Capstone as a core subject
in its Master of Information Technology and states that it can be completed in the final or penultimate
trimester. This paper is independently written practice material and does not reproduce confidential or
copyrighted assessment questions.
Format: A, B, C, D answer choices. The correct answer and rationale appear immediately after each question. Questions
are blue, choices are black, and correct answers are green.
1. What is the primary purpose of an IT capstone project?
A. To demonstrate the integrated application of IT knowledge to a substantial problem
B. To replace every previous unit with one final exam
C. To eliminate the need for project documentation
D. To guarantee that a proposed system will be commercially successful
✓ Correct answer: A. To demonstrate the integrated application of IT knowledge to a
substantial problem
Rationale: A capstone integrates previously learned technical, analytical, project, and professional skills into a
substantial applied project.
2. Which project characteristic most clearly distinguishes a capstone from a small
programming exercise?
A. It requires integration of multiple skills and evidence of a complete project lifecycle
B. It must always use artificial intelligence
C. It can only be completed individually
D. It cannot involve stakeholders
✓ Correct answer: A. It requires integration of multiple skills and evidence of a complete
project lifecycle
Rationale: A capstone normally demonstrates end-to-end project capability rather than a single isolated
technical task.
3. A strong capstone problem statement should primarily describe what?
A. The problem, affected context, and why the problem matters
B. Every line of code that will be written
C. The final grade expected
D. Only the software brand to be used
✓ Correct answer: A. The problem, affected context, and why the problem matters
Rationale: A problem statement establishes the real-world issue and its significance before detailed solution
design.
Original practice material — not an official Kaplan Business School examination paper Page 1
, 4. Which is the best example of a measurable project objective?
A. Reduce average manual data-entry time from 10 minutes to 6 minutes during pilot testing
B. Build a modern system
C. Make users happy
D. Use the newest technology
✓ Correct answer: A. Reduce average manual data-entry time from 10 minutes to 6 minutes
during pilot testing
Rationale: A measurable objective contains a clear outcome and a metric that can be evaluated.
5. What should normally happen before selecting a detailed technical solution?
A. Clarify requirements, stakeholders, constraints, and project objectives
B. Purchase production servers immediately
C. Write the final presentation first
D. Delete alternative solutions
✓ Correct answer: A. Clarify requirements, stakeholders, constraints, and project objectives
Rationale: Solution selection should follow understanding of the problem, requirements, constraints, and
stakeholders.
6. Who is a stakeholder?
A. A person or group affected by, interested in, or able to influence the project
B. Only the person writing the code
C. Only the project sponsor
D. Any person who has used a computer
✓ Correct answer: A. A person or group affected by, interested in, or able to influence the
project
Rationale: Stakeholders can include users, sponsors, managers, technical staff, regulators, and other affected
groups.
7. What is a project constraint?
A. A limitation such as time, budget, scope, technology, or resources
B. A feature that must always be added
C. A project success celebration
D. A type of database query
✓ Correct answer: A. A limitation such as time, budget, scope, technology, or resources
Rationale: Constraints limit the conditions under which the project can be delivered.
8. What is scope creep?
A. Uncontrolled expansion of project requirements after the scope has been established
B. Planned testing before release
C. A method of encrypting data
D. A formal project closure process
✓ Correct answer: A. Uncontrolled expansion of project requirements after the scope has
been established
Rationale: Scope creep occurs when additional work is introduced without appropriate evaluation and control.
9. Which artifact best records what is inside and outside a project's agreed boundaries?
A. Scope statement
B. Password policy
C. Unit test report
D. Network packet capture
✓ Correct answer: A. Scope statement
Rationale: The scope statement defines project boundaries, deliverables, assumptions, and exclusions.
Original practice material — not an official Kaplan Business School examination paper Page 2
, 10. What is a project deliverable?
A. A tangible or verifiable output produced by the project
B. A personal opinion about the project
C. An unapproved feature request
D. A random technical task
✓ Correct answer: A. A tangible or verifiable output produced by the project
Rationale: A deliverable is an output that can be reviewed or accepted, such as a prototype, report, or tested
system.
11. Which technique is especially useful for identifying stakeholder expectations early?
A. Stakeholder interviews and workshops
B. Deleting requirements
C. Skipping user contact
D. Changing the project title
✓ Correct answer: A. Stakeholder interviews and workshops
Rationale: Direct engagement helps reveal needs, priorities, constraints, and acceptance expectations.
12. What is a functional requirement?
A. A behavior or capability the system must provide
B. A statement about project budget only
C. A color preference with no system implication
D. A staff holiday schedule
✓ Correct answer: A. A behavior or capability the system must provide
Rationale: Functional requirements describe what the system should do.
13. Which is a non-functional requirement?
A. The system must respond to a standard request within two seconds
B. The user can create an account
C. The system can generate an invoice
D. The administrator can reset a password
✓ Correct answer: A. The system must respond to a standard request within two seconds
Rationale: Performance is a quality attribute and therefore a non-functional requirement.
14. What is a requirements traceability matrix used for?
A. Linking requirements to design, implementation, and verification evidence
B. Replacing all project meetings
C. Tracking employee salaries
D. Choosing a programming language automatically
✓ Correct answer: A. Linking requirements to design, implementation, and verification
evidence
Rationale: Traceability demonstrates that requirements are addressed and tested throughout the lifecycle.
15. Which requirement is most testable?
A. The application shall lock an account after five failed login attempts
B. The application shall be very secure
C. The interface shall look professional
D. Users should like the system
✓ Correct answer: A. The application shall lock an account after five failed login attempts
Rationale: A testable requirement has an observable condition and measurable outcome.
Original practice material — not an official Kaplan Business School examination paper Page 3
, 16. What is requirements validation intended to determine?
A. Whether documented requirements reflect stakeholder needs and are sufficiently clear
B. Whether the database has enough storage
C. Whether the final poster is attractive
D. Whether the developer prefers the design
✓ Correct answer: A. Whether documented requirements reflect stakeholder needs and are
sufficiently clear
Rationale: Validation checks that requirements represent the right problem and are understandable and
consistent.
17. What is a user story commonly used to express?
A. A user-centered need and its expected value
B. A server's physical dimensions
C. A list of programming errors
D. A project's financial audit
✓ Correct answer: A. A user-centered need and its expected value
Rationale: User stories express functionality from the perspective of a user or role and emphasize value.
18. Which is a common user-story structure?
A. As a [role], I want [capability], so that [benefit]
B. If server then database equals user
C. When code, therefore budget
D. Project has system because technology
✓ Correct answer: A. As a [role], I want [capability], so that [benefit]
Rationale: This structure identifies the user, desired capability, and reason or value.
19. What is an acceptance criterion?
A. A condition that must be satisfied for a requirement or story to be accepted
B. A list of team members
C. A programming comment
D. A backup file
✓ Correct answer: A. A condition that must be satisfied for a requirement or story to be
accepted
Rationale: Acceptance criteria make completion conditions explicit and verifiable.
20. Which activity best reduces ambiguity in requirements?
A. Ask clarifying questions and confirm interpretations with stakeholders
B. Assume the most convenient meaning
C. Avoid documenting decisions
D. Wait until deployment
✓ Correct answer: A. Ask clarifying questions and confirm interpretations with stakeholders
Rationale: Clarification and confirmation reduce misunderstandings before they become expensive changes.
21. What is a work breakdown structure (WBS)?
A. A hierarchical decomposition of project work into manageable components
B. A database schema
C. A security firewall
D. A user-interface color guide
✓ Correct answer: A. A hierarchical decomposition of project work into manageable
components
Rationale: A WBS breaks scope into progressively smaller work packages for planning and control.
Original practice material — not an official Kaplan Business School examination paper Page 4