Free PSM I mock exams

The pass mark is unusually high, so a mock score that would pass most certification exams is a fail here. You can afford only a handful of misses in the whole paper, which means the usual habit of banking a comfortable margin on strong topics and accepting losses elsewhere does not work. Treat every domain as one you must nearly clear.

The test is the Scrum Guide, read exactly. Most wrong answers are not absurd; they are things many real teams do — a Scrum Master who assigns tasks, a hardening Sprint, mandatory story points, a manager collecting status at the Daily Scrum, or wording from the older 2017 Guide. Experience with a company's own flavour of Scrum is the most common reason a confident candidate scores lower than expected. When an option sounds like your workplace, check it against the Guide before choosing it.

Accountability questions decide a lot of marks: who orders the Product Backlog, who owns the Sprint Backlog, who sizes items, who may cancel a Sprint, who must attend which event. The trap is an option that hands a decision to someone who could plausibly help but does not own it. Name the owner before you read the options.

The clock is tight for the number of questions, but the items are short, so pace is rarely the problem on its own. Misses come from reading too fast: a "not", a "must" against a "may", or "choose the best two" read as one. Sit mocks strictly to time and use the spare minutes to re-read the multiple-answer items, where one wrong pick loses the whole question.

Scrum.org reports the real result by competency rather than by question, and our per-domain breakdown works the same way. If the people-and-teams or product-management domains trail while the framework domain is strong, the gap is usually in what the Scrum Master and Product Owner do between the events, not in the rules of the events themselves.