CSM001 Certified Scrum Master Free Practice Test — 30 Questions
This practice bank of 30 questions exercises core Scrum Master competencies: facilitating team adaptation to external changes, guiding self-managing teams through technical and interpersonal impediments, and upholding Scrum principles under pressure. Questions explore scenarios like market pivots, regulatory changes, vendor dependencies, team conflict, and Product Owner overreach. Deciding factors often involve empowering the Development Team, fostering transparency, and coaching rather than dictating. The bank emphasizes behavioral competencies such as adaptability, conflict resolution, leadership potential, and problem-solving. Mastering these questions helps internalize the Scrum Master's servant-leader role in real-world agile environments.
What this CSM001 Certified Scrum Master practice set measures
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Facilitating Adaptation to External Changes
This section examines scenarios where market shifts, regulatory mandates, or competitive pressures require rapid re-prioritization. The Scrum Master's role is to facilitate collaborative sessions involving Product Owner and Development Team to inspect and adapt the Product Backlog and Sprint Goal. The practice bank consistently shows that direct intervention or imposing solutions is less effective than enabling team self-organization and transparency.
- Market or regulatory changes are best addressed through facilitated backlog refinement workshops.
- The Scrum Master coaches the team to evaluate impact and adjust Sprint commitments collaboratively.
- Bypassing the Product Owner or assigning tasks directly undermines team autonomy.
- Adaptability is demonstrated by guiding teams to explore alternatives rather than forcing a predetermined path.
Navigating Team Dysfunction and Conflict
Several questions involve interpersonal friction, dominating personalities, or communication breakdowns. The correct approach is to facilitate team discussions during retrospectives or dedicated workshops to build psychological safety and address root causes. The Scrum Master acts as a mediator, not a judge, encouraging open dialogue and collaborative problem-solving. The practice bank emphasizes that addressing underlying team dynamics is more effective than imposing rules or singling out individuals.
- Use retrospectives to collaboratively examine disruptive behaviors and agree on improvements.
- Facilitate private conversations with involved parties to de-escalate tension.
- Teach active listening and conflict resolution techniques.
- Avoid direct management; instead coach the team to self-manage interpersonal issues.
Upholding Scrum Principles with Stakeholder Pressure
Scenarios where executives, clients, or Product Owners attempt to bypass Scrum events or assign tasks directly test the Scrum Master's commitment to Scrum values. The correct response involves facilitating a discussion to explain the impact on the Sprint Goal and team self-organization, then collaboratively deciding a path forward. The Scrum Master protects the team without alienating stakeholders.
- Never allow mid-sprint changes to be dictated; facilitate a conversation between stakeholder and team.
- Remind the Product Owner of their responsibility for backlog prioritization and value maximization.
- Coach stakeholders on the value of Sprint cadence and team commitment.
- Use transparency to show trade-offs, not to block requests outright.
Impediment Removal and Process Improvement
This section covers recurring technical or organizational impediments like unstable environments, external dependencies, or integration delays. The Scrum Master facilitates team identification of root causes and co-creation of solutions, such as automation, cross-team communication, or backlog reordering. The bank highlights that the Scrum Master does not solve the impediment alone but empowers the team to mitigate its impact.
- Conduct root cause analysis with the team during retrospectives.
- Encourage automation and process improvements to reduce manual delays.
- Escalate organizational impediments with management when beyond team influence.
- Visualize dependencies and risks to promote transparency and collaborative mitigation.
Practice CSM001 Certified Scrum Master with real flashcards
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 30-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
During a Sprint, a critical software component, developed by an external vendor with no prior engagement with the team, fails to integrate as expected, jeopardizing the Sprint Goal. The Development Team is unsure how to proceed given the lack of direct control over the vendor\'s codebase and release cycle. What is the most effective approach for the Scrum Master to facilitate the team\'s response to this unexpected impediment?
Study workflow
Turn one CSM001 Certified Scrum Master attempt into a study plan
- 1
Analyze Impediment Patterns
Review the practice bank to identify recurring impediment types: external dependencies, regulatory changes, team conflict, and stakeholder pressure. For each, understand the Scrum Master's role: facilitator and coach, not solver. Note the pattern of empowering the team to act.
- 2
Apply the Three Pillars: Transparency, Inspection, Adaptation
In every scenario, first make the issue transparent (e.g., raise in Daily Scrum or retrospective). Then inspect the impact on the Sprint Goal. Finally, adapt the plan through collaborative decision-making. Avoid unilateral actions.
- 3
Use Retrospectives for Conflict and Process Issues
When team dysfunction or repeated process failures appear, schedule a dedicated retrospective. Use facilitated exercises to surface underlying causes and collectively design experiments for improvement. The Scrum Master should model openness and vulnerability.
- 4
Handle Urgent External Changes with a Quick Facilitated Discussion
When a market shift or executive request arises mid-Sprint, call a brief meeting with Product Owner and Development Team. Discuss the impact, explore options (e.g., renegotiate Sprint Goal), and decide transparently. Document decisions and communicate to stakeholders.
- 5
Build Psychological Safety for Open Feedback
If team members avoid giving honest feedback, run trust-building activities. Establish ground rules for retrospectives (e.g., "no blame"). Encourage anonymous inputs initially. The Scrum Master continuously models constructive feedback and active listening.
FAQ
Questions about this exam practice page
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
What is the Scrum Master’s primary responsibility when a Product Owner frequently changes priorities mid-Sprint?+
Facilitate a discussion between the Product Owner and Development Team to review the impact on the Sprint Goal. Coach the Product Owner on the importance of stable commitments and transparent backlog refinement to reduce the need for mid-Sprint changes.
How should a Scrum Master handle a team member who dominates technical decisions?+
Facilitate a retrospective focused on communication and psychological safety. Encourage the team to establish norms for inclusive decision-making. Coach the dominant member on active listening and valuing diverse viewpoints. Avoid direct confrontation.
What is the best initial step when an external dependency consistently delays Sprint Goals?+
Facilitate a team workshop to identify the root cause and explore mitigation strategies, such as breaking dependencies, early integration, or escalation. Empower the team to own the solution; the Scrum Master does not solve it alone.
Can a Scrum Master ever assign tasks to team members?+
No. The Development Team is self-managing and decides how to accomplish work. The Scrum Master facilitates self-organization and removes impediments, but never dictates task assignments.
What competencies are most critical for a Scrum Master facing a sudden market pivot?+
Adaptability and flexibility, combined with strong facilitation and coaching skills. The Scrum Master must guide the team through ambiguity, foster transparent discussion with the Product Owner, and help re-prioritize without team autonomy.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.