Which of the following will a company do to update a customer's address while using a flat file database?

While a flat file might duplicate address information per order, the question asks what a company 'will do,' implying the direct action on the data field, and updating 'each order' is a consequence of the flat-file structure, not the most direct description of the update action itself as compared to C.

Flat file databases typically do not use separate, normalized 'customer address tables'; they embed data, so this choice describes a relational database approach.

A flat file database typically stores all related information, including customer details like addresses, directly within each record or file, often without normalization. Therefore, to update a customer's address, the change must be applied to the specific address field wherever it appears within the customer order table or associated file that contains that customer's order records. This differs from relational databases where a separate customer address table would exist.

The primary key uniquely identifies a record and should not be updated to reflect a customer's address, as addresses are typically attributes, not identifiers.