Question: Using the self-driving car scenario as an example, explain why manually substituting a 'perfect' output for one component (such as detect cars) and re-running the rest of the pipeline helps determine whether that component is responsible for a pipeline error.

Sample answer: By manually perfecting component A's output (e.g., manually specifying where other cars are) and letting the downstream components B and C run as before, you create a controlled comparison: the only thing that changed is A's output quality. If the final path planning output improves substantially when A is perfect, this proves that A's original, imperfect output was the bottleneck causing the poor path decision, because everything else in the pipeline was held constant. If the output does not improve, A's errors are not the main cause, and the fault likely lies with a downstream component like B or C. This isolates the source of error without needing to retrain or redesign the whole pipeline.

Key points:

• Only one component's output is changed at a time
• Downstream components run as before to keep the comparison controlled
• A large improvement in the final output implicates the perfected component
• No improvement means the fault lies with a downstream component
• This avoids retraining the whole pipeline to find the error source

Rubric: Full credit explains that holding other components constant while perfecting one isolates its causal contribution to the final error; also credits noting that no improvement rules out A and points to later components.