What is a consequence of the task-data dependency of a flat-file approach?

• A. As users' needs change, additional data need to be gathered or recreated.
• B. As users' needs change, additional data are readily available.
• C. As users' needs change, additional data need to be filtered.
• D. As users' needs change, additional data are properly disseminated.

Answer: (A)

Task-data dependency in a flat-file system means the data are created and stored for a specific task and aren’t easily reused for other tasks. Because the data are tied to that particular use and aren’t organized for flexible sharing, changing user needs usually requires gathering new data or reconstructing data structures to support the new requirements. That’s why the consequence is that additional data must be gathered or recreated. The other possibilities imply easy reuse, automatic availability, or seamless dissemination, which don’t align with the inflexibility of flat-file designs.