MITO Light Auto L5 common mistakes
MITO Light Auto L5 · Understand the traps and how to avoid them.
Classifying a vehicle by its total gross weight (GVW) when the question actually asks for the vehicle category based on its maximum permissible mass or design type, and then applying the wrong licence/technical category to it.
Candidates memorise one weight figure from a spec sheet and assume every classification question uses that number, not realising that light automobile categories are defined by specific legal mass limits and use (passenger vs goods), and that kerb weight, GVW and train weight are different values.
What to do instead
Build a one-page comparison table of the categories tested (kerb weight, gross vehicle weight, gross train weight, passenger vs goods thresholds) and practise reading a spec plate to identify which figure answers which category question. Always restate the question's classification criterion before choosing an answer.
Diagnosing a no-start or poor-running condition by replacing parts (plugs, coils, fuel pump) before confirming whether the fault is spark, fuel or compression related.
Candidates jump to the most familiar component, often the one they have replaced before, and skip the systematic three-necessities check because it feels slower under exam time pressure.
What to do instead
Adopt a fixed diagnostic order for every engine-performance scenario: confirm battery/cranking, then check for spark, then fuel pressure and injector pulse, then compression and timing. In exam questions, eliminate options that replace a component without a stated test result first.
Confusing the roles of the ECU, sensors and actuators when interpreting a fault code, and assuming a code naming a sensor means the sensor itself has failed.
Fault-code descriptions often name the circuit or component being monitored, not the failed part, and candidates read the code label literally instead of tracing the circuit, wiring, connector and reference voltage.
What to do instead
For every code-based question, ask what the ECU actually measured (voltage, resistance, signal plausibility) and list the possible causes in order: wiring/connector, supply or ground, sensor, then ECU. Practise interpreting codes as 'circuit fault reported by the monitoring ECU', not as a parts diagnosis.
Mixing up brake hydraulic principles, such as assuming a larger master cylinder bore increases braking force at the wheels, or ignoring the effect of air in the circuit on pedal feel.
Candidates reason from everyday intuition ('bigger pump means more force') rather than from Pascal's law and the relationship between bore area, pedal travel and line pressure, and they underweight bleeding and fluid condition as causes of a spongy pedal.
What to do instead
Revise the pressure = force/area relationship and how master-cylinder and caliper piston areas trade pressure against travel. For pedal-feel questions, always consider air, fluid condition, leaks and flex before component replacement, and practise explaining each hydraulic relationship in one sentence.
Describing suspension and steering geometry faults by symptom only (for example 'pulls to one side') without linking the symptom to a measurable angle or worn component such as camber, caster, toe or a worn bush.
Candidates learn symptom lists by rote and cannot connect them to the geometry values or inspection points that would confirm the cause, so they choose a plausible-sounding but unmeasurable answer.
What to do instead
Create a symptom-to-angle-to-test map (pull to one side: camber/caster difference or brake drag; uneven tyre wear: toe or camber; wander: caster or worn bushes) and practise stating the confirming measurement for each symptom before selecting an answer.
Skipping the pre-inspection preparation steps in maintenance questions, such as not verifying fluid levels, tyre pressures, battery state or service history before deciding on a maintenance action.
Candidates treat maintenance questions as recall of service intervals and overlook that the correct procedure depends on recorded mileage, condition and manufacturer schedule, which the question supplies and expects to be used.
What to do instead
Before answering any maintenance question, extract the stated mileage, condition and history and check whether the proposed action matches the schedule and the observed condition. Practise writing a short inspection sequence for each system so preparation steps become automatic.
Ignoring the sequence and safety prerequisites of a diagnostic road test or lift procedure, for example testing brakes or steering on a public road without the required checks, or raising a vehicle without confirming jacking points and support stands.
Candidates focus on the technical fault-finding step and treat procedural safety content as filler, but exam questions deliberately test the order of operations and the required supports and checks.
What to do instead
Memorise the standard sequence for each procedure (pre-road-test checks, jacking points, axle stands, wheel chocks, second-person checks where required) and answer procedure questions by first eliminating any option that omits a safety prerequisite.
Treating waste streams as interchangeable, such as placing used oil filters, brake fluid, coolant or refrigerant in general waste, or failing to identify the correct handling route for each.
Candidates learn the general principle 'recycle waste' but not the specific segregation and handling requirements for each automotive waste type, and they underestimate how often exam questions test the specific route.
What to do instead
Make a waste-segregation table listing each waste type (waste oil, oil filters, coolant, brake fluid, refrigerant, batteries, tyres, contaminated rags) with its storage, labelling and disposal route. Revise it before the exam and apply it to every environmental scenario question.
Underestimating personal protective equipment and workshop hazard controls, for example assuming gloves alone protect against every hazard or that a running engine in a closed workshop is acceptable.
Candidates reduce safety to 'wear PPE' and do not match the specific hazard (exhaust gas, high voltage, hot surfaces, rotating parts, lifting) to the specific control, so they pick a generic safety answer that is incomplete.
What to do instead
Practise matching each hazard to its control using a hazard-control hierarchy: elimination, engineering controls (extraction, guards, insulation), administrative controls, then PPE. For each scenario, name the specific hazard and the specific control rather than a general safety statement.
Misreading the question stem, for example answering what a component does when asked why it fails, or choosing the first technically true statement without checking it answers the actual question.
Under time pressure candidates pattern-match keywords to memorised facts and stop reading at the first familiar term, and multi-part stems with a condition ('except', 'most likely', 'first action') are easily missed.
What to do instead
Underline the operative words in every stem (what, why, first, most likely, except) before looking at the options, then check each option against that exact wording. In practice, write a one-line restatement of the question before choosing an answer.