ADAS Fundamentals and System Architecture
ADAS is best understood as a layered chain: perception (sensors), fusion (combining sensor data into a world model), decision (feature logic and thresholds), and actuation (steering, braking, throttle, alerting). A candidate must be able to describe each layer and map a named system to it. Know the SAE driving-automation levels 0-5 and the difference between active safety (intervenes, e.g., AEB, ACC) and passive safety (protects after a crash). Understand the distinction between the feature (what the driver experiences) and the underlying subsystem (e.g., ACC depends on radar, camera, and the brake/engine controllers).
Traps in questions: confusing a system that only warns (LDW) with one that intervenes (LKA); assuming a feature works without a specific sensor; treating driver-assist as autonomous. Another trap is the role of the domain controller or ECU network-questions often test that features are distributed across modules communicating over CAN, not contained in one box.
Worked example / rule of thumb: For any feature named in a question, ask three things-what senses it, what decides it, and what actuates it. If any link is missing or disabled (sensor fault, network fault, actuation fault), the feature is inoperative. Use this "sense-decide-act" triad to reason through architecture questions.