LMP-C01 common mistakes
LMP-C01 · Understand the traps and how to avoid them.
Memorizing the names of item types (e.g., multiple choice, multiple response, matching, hot spot) without learning what each type can and cannot measure, so the candidate picks an item type based on its label rather than on the construct it must assess.
Item-type terminology is easy to drill as a vocabulary list, so candidates over-invest in flashcards and under-invest in linking item formats to cognitive demand and content constraints.
What to do instead
For each item format, write a one-line statement of what it measures well and one construct it measures poorly, then practice mapping a given learning objective to an appropriate format before checking the answer.
Treating an exam blueprint as a list of topics to read about rather than as a weighting scheme, and therefore allocating study time evenly across domains instead of in proportion to the published percentage weights.
Candidates study what feels unfamiliar or interesting, and domain titles look equally important when the percentages are not explicitly tracked.
What to do instead
Convert the published domain percentages into a study-hour budget and log actual hours per domain; rebalance whenever a domain's logged hours drift from its weighted share.
Answering item-writing questions by choosing the option that sounds most rigorous (e.g., always preferring the longest, most technical distractor) rather than applying the specific flaw being tested, such as implausible distractors or grammatical cueing.
Item-writing flaws are subtle and candidates substitute a general impression of 'serious-sounding' for the actual rule about distractor plausibility, option length parity, or avoiding 'all of the above'.
What to do instead
Before answering, name the specific flaw category in the stem or options (cueing, convergence, implausible distractor, negative wording, ambiguous key) and evaluate only against that rule.
Confusing reliability with validity when interpreting a scenario, for example concluding that a high internal-consistency coefficient proves the exam measures the intended construct.
Both terms appear together in psychometric content, and high reliability intuitively feels like proof of quality, so candidates collapse the two concepts.
What to do instead
Apply a fixed test: reliability concerns consistency and precision of scores; validity concerns whether interpretations and uses are supported by evidence. For each scenario, ask whether the claim is about score consistency or about meaning and use.
Assuming a fixed passing standard is derived from the score distribution (for example, passing the top percentage of candidates or setting the cut score at the mean) when the scenario describes a criterion-referenced, content-based standard-setting method.
Candidates import norm-referenced intuitions from school grading and misattribute distribution-based logic to methods such as modified Angoff or bookmark procedures.
What to do instead
Classify the described method first as criterion-referenced (judgments about content required for competence) or norm-referenced (relative standing), then evaluate whether the stated cut score logic matches that classification.
Treating a reported standard error of measurement as a fixed property of the candidate rather than of the scores, and failing to apply it when interpreting a score band or a pass/fail decision near the cut score.
The concept is abstract, and candidates default to treating a reported score as exact rather than as an estimate with a confidence interval.
What to do instead
Practice constructing and interpreting a confidence band around a score using the reported SEM, and state explicitly how a score within that band of the cut score should be described.
Responding to a security incident scenario by proposing the most punitive action (immediate score cancellation, public disclosure) rather than the sequence of evidence preservation, documentation, and review prescribed by test-security practice.
Incident scenarios provoke a strong reaction, and candidates equate severity of response with correctness rather than following procedural order.
What to do instead
For any security scenario, order the response as secure the evidence, document the facts, notify according to policy, then adjudicate; select the option that preserves due process at the correct step.
Confusing test accommodations with test modifications, and answering fairness questions by endorsing changes to the construct or the cut score in the name of accessibility.
Both terms concern fairness and accessibility, and the distinction between removing a barrier to measurement and altering what is measured is easy to blur under time pressure.
What to do instead
Apply the rule that accommodations change access without changing the construct or standard, while modifications change what is measured or required; classify the described change before judging whether it is appropriate.
Drafting candidate communication that omits the actionable specifics (what the candidate must do, by when, through which channel, and what happens next) in favor of general reassurance about the program's commitment to quality.
Candidates write the tone they would want to receive and mistake a warm, vague message for a complete one.
What to do instead
Check every drafted communication against a four-part template: required action, deadline, channel or contact, and consequence or next step; revise until all four are explicit.
Skipping the review of eligibility, registration, and score-reporting logistics because they seem administrative, then missing scenario details about deadlines, retake rules, or score-report validity that determine the correct answer.
Logistics content feels low-status compared with psychometrics, so candidates skim it and rely on assumptions about how programs typically operate.
What to do instead
Build a one-page reference of program rules as stated in the source material (registration windows, retake policy, score-report lifespan, appeal timelines) and rehearse scenarios against that sheet rather than against assumptions.