What is a typical result of changing user needs in a flat-file database environment?

What is a typical result of changing user needs in a flat-file database environment?

• A. Additional data must be gathered or recreated
• B. Data automatically expands to accommodate
• C. Data is unaffected
• D. Data becomes inconsistent

Answer: (A)

In a flat-file setup, the data structure is fixed and not easily extended. When user needs change, there isn’t an automated way for the system to accommodate new data types or new fields. You typically end up gathering more information that wasn’t captured before or reconstructing the file to include the new data elements and relationships. This manual change is why additional data must be gathered or recreated. The other possibilities—automatic expansion, no change, or inherent inconsistency—don’t reflect how flat-files behave: adapting to new requirements usually requires reworking the data and schema rather than happening automatically or remaining unaffected.

In a flat-file setup, the data structure is fixed and not easily extended. When user needs change, there isn’t an automated way for the system to accommodate new data types or new fields. You typically end up gathering more information that wasn’t captured before or reconstructing the file to include the new data elements and relationships. This manual change is why additional data must be gathered or recreated. The other possibilities—automatic expansion, no change, or inherent inconsistency—don’t reflect how flat-files behave: adapting to new requirements usually requires reworking the data and schema rather than happening automatically or remaining unaffected.