ALOA CML common mistakes
ALOA CML · Understand the traps and how to avoid them.
Answering lock-component questions from generic memory instead of identifying the specific mechanism type (pin tumbler, wafer, disc, lever) named in the stem before choosing.
Candidates study a single lock family and then apply its terminology and failure logic to every mechanism, because the mechanisms look similar in diagrams and share part names like 'driver' and 'spacer'.
What to do instead
Before answering, write the mechanism family from the stem on scratch paper and list its unique components; only then evaluate options, discarding any that describe a component the named mechanism does not contain.
Choosing an answer that describes a plausible sequence of steps but omits a required safety or verification step (e.g., testing a rekeyed cylinder with the old key, confirming the plug turns freely before reinstalling).
Candidates recognize the general procedure and stop reading once they see a familiar first step, so the option that is procedurally correct but incomplete looks right.
What to do instead
Read every option to the end and check each against a mental checklist of the full job: disassembly, work, reassembly, functional test with both new and old keys, and documentation.
Misdiagnosing a mechanical lock fault by replacing parts before isolating whether the fault is in the cylinder, the cam/actuator, or the door hardware alignment.
Symptom-based thinking ('key won't turn, so replace the cylinder') is faster than systematic isolation, and candidates under exam time pressure skip the isolation step.
What to do instead
Practice a fixed diagnostic order: operate the lock detached from the door if possible, then check alignment/strike, then internal components; answer questions in that order of elimination.
Treating electronic lock failures as purely electrical or purely mechanical, and selecting answers that ignore power, credential, or firmware layers when the stem points to an access-denied condition.
Candidates with mechanical backgrounds default to mechanical causes, and those with electronics backgrounds default to board or battery causes, so they pick the answer matching their comfort zone.
What to do instead
For every electronic lock scenario, run a layered checklist in order: power source, credential validity, reader/input, controller logic/firmware, then mechanical bolt/latch; choose the option consistent with the earliest failing layer described.
Selecting a key-cutting or key-generation answer that ignores the difference between originating a key by code and duplicating an existing key, including which data source is authoritative.
Both tasks produce a working key, so candidates conflate the workflows and pick an option that mixes code-machine setup with duplication steps.
What to do instead
Classify the task in the stem first as originate-by-code, originate-by-impression/decoding, or duplicate; then require the answer to name the correct data source (code card, database, decoded bitting, original key) for that classification.
Answering automotive programming questions without accounting for vehicle-side requirements such as immobilizer state, required number of working keys, or on-board relearn procedures.
Candidates focus on the key or programmer tool and forget that the vehicle imposes preconditions, so answers that describe only the tool side seem complete.
What to do instead
For each automotive scenario, list the vehicle preconditions (existing key count, security access, relearn cycle, battery support) before evaluating options, and reject any option that skips a stated precondition.
Mixing safe-opening techniques with safe-servicing techniques, e.g., choosing a manipulation or drilling approach for a stem that describes routine maintenance or combination change.
Opening methods are the most memorable material studied, so candidates over-apply them to scenarios that call for non-destructive service procedures.
What to do instead
Label the stem's objective as open, service, or install before answering, and only consider techniques valid for that objective; discard any destructive or coercive method when the objective is service.
Ignoring the container's rating or construction class when selecting a procedure, tool, or expected outcome for a safe or vault question.
Candidates memorize techniques without attaching them to the ratings and constructions they apply to, so they select an approach that would fail or be inappropriate on the described container.
What to do instead
Extract the stated rating, lock type, and construction from the stem, then check that the chosen method is described as applicable to that class; if the stem gives no rating, prefer the answer that states its applicability condition.
Answering ethics and legal-scope questions by what is technically possible or common practice rather than by documented authorization, licensing, and record-keeping obligations.
Candidates reason from workshop habit and customer convenience, and the technically effective answer reads as the 'professional' one.
What to do instead
For every professional-practice item, first identify the ownership/authorization evidence and the record the task requires; eliminate any option that proceeds without verified authorization or omits required documentation, even if it is the fastest fix.
Choosing business-operation answers (pricing, liability, warranty, vehicle or premises access) that maximize customer satisfaction while overlooking contractual, insurance, or statutory exposure.
Candidates treat business questions as soft-skills questions and pick the most accommodating option, missing that the exam tests risk allocation and compliance.
What to do instead
Evaluate business options against three filters in order: legal/regulatory compliance, contractual and liability exposure, then customer relationship; the correct answer must survive all three, not just the last.