A code is a clue, not a parts list
Modern vehicles use an onboard diagnostic system to watch engine and emissions-related functions. Sensors report conditions such as oxygen in the exhaust, airflow into the engine, and the temperature of the coolant. The engine computer compares those readings with expected ranges. When a reading or pattern stays outside a limit long enough, it can turn on the check-engine light and store a diagnostic trouble code.
That code usually identifies the system or condition the computer noticed—not the failed component. A code related to an oxygen-sensor circuit, for example, might result from a faulty sensor, damaged wiring, an exhaust leak, or a problem elsewhere that is making the sensor report unusual exhaust. Replacing the first part named in a code can therefore leave the underlying cause untouched.
How diagnosis narrows the possibilities
A scanner retrieves the stored code and, on many vehicles, related details about when the fault appeared. A technician uses that information to choose the next checks: inspect wiring and connections, compare live sensor readings, test a component, or look for leaks. The code makes the search more focused, but the measurements and physical checks establish what is actually wrong.
Sometimes the light comes on after a loose fuel cap disrupts the sealed fuel-vapor system. In other cases, the same broad warning can point to a fault that affects how the engine runs or how much pollution it produces. The computer is reporting what it can detect through its sensors and rules; it cannot directly inspect every part.
That distinction matters when estimating repairs. The code is the beginning of a diagnosis, not an automatic instruction to buy a particular part.
