Open Assessment
Product management fundamentals
A short sample of general product management questions, in the same style as a PMCert certification exam.
Start the assessmentProvisional questions: this set is generic and will be replaced by the definitive PMCert bank.
Free
No account, no card, no limit on attempts.
Not the certification exam
Separate questions, never reused in the exam.
Nothing on your record
Your answers are not kept. Only the result by domain is saved, linked to you only if you are signed in, and it produces no credential.
Sample questions
Two questions from this practice test, in the same style as the certification exam. Answer before opening the explanation.
Question 1
A product manager needs to decide what the team builds next quarter. Which input should carry the most weight in that decision?
- The feature most often requested by the sales team
- Evidence about which customer problem is costing the most today
- What the closest competitor announced last month
- The item that has been sitting longest in the backlog
Show answer and explanation
Correct answer: B. Evidence about which customer problem is costing the most today
Prioritization follows the problem with the largest measurable cost, because that is what predicts the return of solving it. Sales requests, competitor moves and backlog age are all signals worth reading, but none of them establishes the size of the problem and each one, taken as the rule, leads a team to build steadily while the important thing stays broken.
Question 2
A team ships a feature and adoption is far below expectation. What is the most useful first step?
- Add the feature to the onboarding tour so more people see it
- Rebuild the interface, since low adoption points to usability
- Find out whether the problem the feature solves was real for those users
- Wait one more quarter to see whether adoption grows on its own
Show answer and explanation
Correct answer: C. Find out whether the problem the feature solves was real for those users
Low adoption has two very different causes: people cannot find or use it, or they never needed it. Discovery separates the two, and the answer changes what to do next. Promoting or redesigning first assumes the need was real; waiting assumes the same and adds delay.