PK0-005 Tools and Documentation Practice Question
In an agile project, the team is using user stories to capture requirements. Which of the following is the correct format for a user story?
⚠ Common exam trap
CompTIA often tests the distinction between user stories and traditional requirements by embedding a correct user story among system-imperative statements or mixed-format options, tricking candidates who memorize only the 'As a... I want...' part without requiring the 'so that' clause.
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
✓
As a customer, I want to view my order history, so that I can track my purchases.
Follows the standard user story format: 'As a [user role], I want [goal], so that [benefit].' This structure is prescribed by agile methodologies like Scrum and XP to ensure requirements are user-centric, testable, and value-driven. The 'so that' clause provides the business rationale, which is critical for prioritization and acceptance criteria definition.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
As a customer, I want to view my order history, so that I can track my purchases.
Why this is correct
"As a [role], I want [goal], so that [benefit]" is the canonical user story template, and this option instantiates all three clauses correctly: customer, viewing order history, and the tracking benefit. It satisfies the stem's agile requirement by capturing the requirement from the user's perspective rather than as a technical specification.
- ✗
The system shall allow users to login.
Why it's wrong here
This is a traditional requirements-specification sentence, stating system behaviour with no user role or benefit, so it cannot be estimated or prioritised as a story. It is tempting because it is clear and testable, and would be correct in a waterfall requirements document rather than an agile backlog.
- ✗
Login functionality must be implemented.
Why it's wrong here
This states a system requirement in imperative form, omitting the role, the goal and the benefit that a user story must express. It is tempting because it reads like a clear, testable backlog item, and would be acceptable as a functional requirement or acceptance criterion rather than a user story.
- ✗
As a user, I want to login, and the system must be secure.
Why it's wrong here
Appending a security constraint after the benefit breaks the role–goal–benefit template, mixing a non-functional requirement into the story. It is tempting because it captures user intent plus a quality attribute, and would be acceptable as a separate acceptance criterion or non-functional requirement rather than the story statement itself.
Go deeper
Related to this question
About these practice questions
This PK0-005 question is part of Courseiva's 954-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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PK0-005 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 PK0-005 exam.