What is a common mistake with change tracking and AsNoTracking in Entity Framework Core?

Tracking large read-only result sets wastes memory and CPU and may lead to accidental updates. 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.