Data maintenance workflow: in a typical file or database table, the Modify (update) operation is most likely performed after which prior action to locate the target record?

Introduction / Context:
CRUD operations (Create, Read, Update, Delete) describe the life cycle of data in files and databases. Understanding the natural sequence among these operations helps analysts, developers, and end users perform consistent, error-free maintenance. The question asks which action typically precedes a Modify (update) operation when working with existing records.

Given Data / Assumptions:

• You are modifying an existing record, not creating a new one.
• Records are stored in a file or table with one or more key fields.
• A safe update requires selecting the correct record instance before changing values.

Concept / Approach:
Modify corresponds to Update in CRUD. To update precisely the intended row, the system must first find (read) it using a search criterion such as a primary key, unique key, or indexed attribute. Therefore, a Look-up (read/search) action is the immediate logical predecessor to Modify. Insert precedes Modify only in workflows where a new record is immediately edited after creation, and Delete obviously cannot precede Modify on the same record because deletion removes it from the set of updatable rows.

Step-by-Step Solution:

Verification / Alternative check:
In SQL, an UPDATE statement includes a WHERE clause that effectively performs a look-up by key or predicate. In form-based systems, users search or navigate to a record before editing fields, again confirming the dependency on look-up.

Why Other Options Are Wrong:

Common Pitfalls:
Skipping the read/validation step can cause updates to the wrong record or unintended bulk changes due to a missing WHERE clause. Always verify the identity and current state of the target row before applying updates.

Final Answer:
Look-up