# Guiding Lot Operations

Use these questions to prepare for the Kanoa Trace certification exam.

<details>
<summary>Do asset and item links on a lot operation stop a script from running it somewhere else?</summary>

No. They narrow the choices in Lot Manager and custom screens, but aren't database rules. See [Adding Rules to Lot Operations](../03-guiding-lot-operations/1-operation-rules.md).

</details>

<details>
<summary>Why leave `Transfer` and `Scrap` unlinked?</summary>

They happen almost anywhere, to almost anything, so restricting them would block valid work. See [Adding Rules to Lot Operations](../03-guiding-lot-operations/1-operation-rules.md).

</details>

<details>
<summary>What's the difference between a lot operation and a lot state?</summary>

The operation records what happened. The state records the resulting condition of the material on that lot event. See [Lot States](../03-guiding-lot-operations/2-lot-states.md).

</details>

<details>
<summary>Does a route stop an operator from running steps out of order?</summary>

Not by itself. It describes the expected path; screens and scripts that read it decide how strictly to enforce it. See [Routes](../03-guiding-lot-operations/3-routes.md).

</details>

<details>
<summary>Why model an LGV as a transport asset rather than a location?</summary>

Its position changes. As a transport, you can ask both what's on it and where it is, without moving every lot each time it moves. See [Transports and Trucks](../03-guiding-lot-operations/4-transports.md).

</details>