A new analyst treats every control objective as if it were already an entity-specific control. Why is that incorrect?
Select an answer to reveal the explanation.
Short Explanation
A recipe is not the cake on each table. The objective is the recipe—the definition—while the control is the cake baked for a specific entity. Swap those roles and the kitchen model falls apart.
Full Explanation
Architecturally, a control objective defines the reusable requirement. A control is an instance of that requirement applied to a scoped entity, often created through generation. Entity-specific ownership, testing, and issues belong on the control instance. Reusable design and citation mapping belong on the objective, so swapping the two roles breaks the model.