What is a common mistake with First, Single, and OrDefault variants in LINQ?

Using Single without an enforced uniqueness rule can cause runtime exceptions, while First can hide duplicate data. In practice, the value of this concept comes from understanding where it belongs in the architecture, what problem it solves, and what constraints or tradeoffs it introduces.