Question: 1 / 60

When a record in a file is modified, what is an appropriate way to identify the modified contents?

Keeping a copy of a file and comparing it to the modified one later

When a record in a file is modified, keeping a copy of the original file and comparing it to the modified one later is an effective way to identify the changes. This method allows for a clear comparison that highlights exactly what was altered in the content. It provides a straightforward way to track modifications by visually or programmatically examining the differences between the two versions, making it easier to understand the specific changes that have occurred. This approach also supports situations where you may need to revert to an earlier version of the file or audit changes for compliance or review purposes. By retaining the original file, you not only preserve data integrity but also create a reference point that can be invaluable for future analysis or troubleshooting. In contrast, while using a backup service that stores changes can also be useful, it may not provide immediate visibility into what has changed from the original state. Documenting changes in a separate log file can help maintain a record of alterations but may not capture the exact nature of the changes as effectively as a direct file comparison. Deleting the original file after modification leads to potential risks of data loss and does not facilitate any subsequent review of what has been changed.

Deleting the original file after modification

Using a backup service that stores changes

Documenting changes in a separate log file

Next

Report this question