What must be done before deleting native files in the repository workspace?

Before deleting native files in the repository workspace, it is essential to promote the physical files to the review workspace. This process ensures that the files are preserved in a location where they can be accessed for review, analysis, or potential litigation purposes. Promoting the files allows for a proper examination of the contents to occur without the risk of losing crucial data.

Deleting native files directly from the repository workspace without promoting them first could lead to irretrievable loss of data, making it impossible to review or reference that information in the future. This practice aligns with data governance and compliance protocols, ensuring that any information relevant to legal proceedings or internal investigations can be accessed as needed.

Other options do not specifically address the necessity of maintaining a copy of vital files for review once they are deleted from the original workspace. For instance, restoring the workspace can help recover lost files but does not represent a proactive step prior to deletions. Notifying users, while a courteous practice, does not mitigate the potential data loss. Archiving files might seem like a viable alternative, but it is not a requirement specifically tied to the deletion of native files in the context of this question. Hence, promoting to the review workspace stands out as the correct and most responsible action to take before proceeding