PSM II Professional Scrum Master II Free Practice Test — 30 Questions
This practice bank exercises advanced Scrum Master competencies beyond basic framework knowledge. It focuses on real-world scenarios requiring the Scrum Master to coach self-managing teams, navigate organizational impediments, facilitate stakeholder collaboration, and uphold Scrum values under pressure. Key topics include managing external dependencies, handling Product Owner missteps, addressing team resistance to change, and fostering continuous improvement. The questions test ability to apply servant leadership, facilitation, and coaching skills to maintain team autonomy while delivering value in complex environments. Mastery of these scenarios is essential for PSM II certification.
What this PSM II Professional Scrum Master II 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.
Understanding Scrum Roles and Self-Management
This section explores the Scrum Master's role in protecting the Development Team's self-management and ensuring the Product Owner and stakeholders respect Scrum boundaries. Scenarios involve the Product Owner directly assigning tasks, stakeholders bypassing the Product Owner, or senior management mandating task assignment. The correct responses consistently emphasize facilitation and coaching rather than direct intervention. The Scrum Master must foster an environment where the team takes ownership of their work and the Product Owner manages the Product Backlog collaboratively. Key is to reorient stakeholders and the Product Owner to Scrum events and artifacts through dialogue, not dictation.
- When the Product Owner assigns tasks to individual Developers, facilitate a discussion to clarify roles and the importance of self-management.
- When stakeholders bypass the Product Owner, coach them on proper interaction channels and empower the team to redirect requests.
- When external governance boards impose rigid processes, educate them on the impact of such practices on agility and value delivery.
Facilitating Stakeholder Collaboration and Managing External Pressures
This section emphasizes the Scrum Master's role in coaching stakeholders and navigating external pressures that threaten Scrum principles. Scenarios include senior leaders demanding detailed upfront plans, stakeholders requesting granular daily reports, and clients pressuring for feature prioritization outside the Product Goal. The correct actions involve facilitating workshops to educate stakeholders on empirical process control, transparency, and the value of iterative delivery. The Scrum Master must help stakeholders understand how their requests create impediments and guide them to work within the Scrum framework to achieve their desired outcomes.
- When stakeholders request fixed delivery dates and scope, educate them on empirical process and iterative development benefits.
- When a client stakeholder demands daily task reports, facilitate a discussion using existing Scrum artifacts to provide visibility.
- When a senior executive pushes for features misaligned with the Product Goal, coach the Product Owner to communicate prioritization rationale.
Navigating Organizational Impediments and External Dependencies
This section addresses how the Scrum Master handles systemic impediments and dependencies outside the team's control, such as unreliable third-party APIs, slow infrastructure teams, or organizational restructuring. The practice bank emphasizes that the Scrum Master must escalate such issues appropriately, often to senior management, after the team has attempted mitigation. The correct responses involve facilitating collaboration with management to establish service level agreements or resolve contractual issues. The Scrum Master does not directly fix the dependency but creates visibility and advocates for organizational change.
- When a critical third-party API is unreliable, coach the team on proactive strategies (monitoring, defensive coding) and consider escalation if needed.
- When a centralized Infrastructure Team causes delays, facilitate discussions to establish service level agreements or alternative solutions.
- When organizational restructuring creates unstable priorities, facilitate a workshop to re-evaluate the Product Goal and backlog alignment.
Fostering Continuous Improvement and Adaptive Planning
This section covers situations where the team is comfortable with current practices but needs to adapt to new regulations, market shifts, or technical debt. The Scrum Master's role is to facilitate inspection and adaptation without imposing solutions. Scenarios include teams resistant to new processes (e.g., CI/CD) or failing to meet Sprint Goals due to poor forecasting. The correct responses involve facilitating retrospectives focused on root cause analysis, encouraging experimentation, and empowering the team to adjust their own practices. The Scrum Master uses coaching and facilitation to enable the team to grow.
- When a team resists adopting a new CI/CD pipeline, facilitate a workshop exploring its impact on overall value delivery and customer satisfaction.
- When a team consistently misses Sprint Goals, facilitate a retrospective to dissect root causes and experiment with new forecasting techniques.
- When a team faces technical debt and shifting priorities, facilitate a joint workshop with the Product Owner to refine the backlog and incorporate debt reduction.
Practice PSM II Professional Scrum Master II 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.
A multinational technology firm, \"Innovatech Solutions,\" has recently adopted Scrum across several of its product development units. However, one team, working on a critical customer-facing application, finds itself consistently hampered by a newly established \"Process Governance Board.\" This board, composed of senior managers from various departments, mandates that all task assignments must be explicitly approved and assigned by them, bypassing the Development Team\'s self-organization and the Product Owner\'s backlog refinement. This rigidity leads to significant delays, a lack of team autonomy, and frustration among team members who feel their ability to adapt to emerging requirements is severely curtailed. As the Professional Scrum Master for this team, what is the most effective initial course of action to address this systemic impediment while respecting organizational structure?
Study workflow
Turn one PSM II Professional Scrum Master II attempt into a study plan
- 1
Facilitate Collaborative Workshops
When encountering misunderstandings about Scrum roles or resistance to change, organize a workshop with all relevant parties. Use the space to educate stakeholders on Scrum principles, explore impacts of their requests, and jointly develop solutions. Focus on open dialogue and shared understanding rather than imposing rules.
- 2
Coach the Product Owner on the Product Goal
If the Product Owner struggles with prioritization or external pressure, coach them on articulating the Product Goal and backlog rationale. Role-play conversations with difficult stakeholders. Reinforce their authority to say no and the importance of aligning all work with the strategic objective.
- 3
Escalate Systemic Impediments with Data
When an external dependency blocks the team repeatedly, gather data on its impact (e.g., missed Sprint Goals, delayed increments). Present this to senior management and relevant stakeholders. Collaborate to identify structural solutions like service level agreements or alternative providers.
- 4
Facilitate Root-Cause Retrospectives
For recurring issues like missed Sprint Goals or low morale, dedicate a retrospective to root cause analysis. Use techniques like fishbone diagrams or the Five Whys. Let the team generate and test one improvement experiment per Sprint. Follow up in the next retrospective.
- 5
Empower Team Self-Organization
When team members ask for prescriptive guidance, resist the urge to provide direct answers. Instead, ask reflective questions like 'What options have you considered?' or 'How can you leverage the team's expertise?' Encourage them to take ownership of technical decisions and problem-solving.
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 role when a senior stakeholder demands detailed daily task reports from the Development Team?+
The Scrum Master should facilitate a discussion between the stakeholder, Product Owner, and team to show how existing Scrum artifacts (Sprint Backlog, Review) provide transparency. Coach the stakeholder to inspect progress at the Sprint Review rather than through daily reports, preserving team self-management.
How should a Scrum Master handle a Product Owner who directly assigns tasks to Developers mid-Sprint?+
Facilitate a private conversation between the Product Owner and the team to clarify roles and the value of self-management. Highlight that Sprint Planning and Backlog Refinement are the proper channels. Coach the Product Owner to trust the team's ability to self-organize around the Sprint Goal.
What is the best approach when a team resists adopting a new CI/CD pipeline that the Product Owner believes is critical?+
Facilitate a workshop with the team, Product Owner, and operations stakeholders to collaboratively explore the pipeline's impact on product value, deployment risk, and customer feedback. Let the team propose experiments to integrate the pipeline incrementally, addressing their concerns while moving toward the organizational goal.
How does a Scrum Master address a situation where the Development Team consistently fails to meet Sprint Goals?+
Facilitate a dedicated Sprint Retrospective focused on root cause analysis of missed goals. The team may identify issues like poor forecasting, incomplete understanding of work, or external disruptions. Encourage them to experiment with new estimation techniques or Definition of Ready items to improve predictability.
What should a Scrum Master do when a critical third-party API is unstable and delaying the team's progress?+
First, coach the team on proactive strategies such as enhanced monitoring, defensive coding, and communication with the API provider. If the issue persists and blocks value delivery, escalate to senior management with data on business impact, advocating for contractual renegotiation or alternative data sources.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.