The correct answer is C. The blank values will replace the existing field values. Relativity's Import/Export document load file import documentation states that for Append/Overlay and Overlay Only , if a blank metadata field exists in the load file, the blank value will overlay remove any existing value in the corresponding mapped field. That means the blank value does not preserve the original value; it clears it.
This rules out the other options. The import does not preserve the old value in the mapped field, so option A is incorrect. The workflow does not error merely because blank values are present, so option B is also incorrect.
Option D is wrong because the behavior is not limited to fixed-length text fields; it is described generally for mapped metadata fields in overlay mode. Therefore, the correct answer is that blank values replace existing field values during overlay import.

The correct answer is C. RIP must be installed in the source workspace. Relativity's Integration Points documentation states that to use Integration Points successfully, you must install the application to at least one workspace . In the specific context of promoting data between workspaces, Relativity also states that you are not required to have Integration Points installed on the destination workspace . That means the practical prerequisite is installation in the source workspace , not both source and destination.
This rules out the other choices. Integration Points is not described as an instance-level-only install requirement, so option A is incorrect. Option B is too broad because the destination workspace installation is explicitly not required. Option D is also incorrect because Integration Points is an application that must be installed in a workspace to be used. Therefore, for migrating documents from one workspace to another with RIP, the required prerequisite is that Integration Points be installed in the source workspace .

The correct answer is C. Extracted text, FileExtension, and FileName. Relativity's official Simple File Upload documentation includes a Replacing documents section that explicitly lists the metadata fields overwritten when a document is replaced with another document sharing the same control number. The overwritten fields include FileName , FileSize , FileExtension , Extracted Text , Supported By Viewer , Relativity Native Type , Has Native , and certain last-modified system fields.
Among the answer choices, option C is the only one composed entirely of fields that Relativity explicitly says are overwritten in this workflow. Option A is incorrect because Sort Date is not one of the documented overwritten fields. Option B is incorrect because Group Identifier is not listed as being overwritten. Option D is incorrect because Page Count is not listed in the documented overwritten fields for replacing a document via this workflow.
This is an important Data loading administration detail because document replacement changes core file metadata tied to the uploaded replacement native, including its filename and extension, while preserving the document identity through the shared control number. Therefore, the correct option is C. Extracted text, FileExtension, and FileName .

The correct answer is C. Files must be generated using the RSMF specifications before they are imported into Relativity. Relativity's official Short Message Format documentation explains that to use the Short Message Viewer, you first need to create an RSMF file, and the example/specification pages describe the required structure and header information that must be present before ingestion using Processing. Relativity also states that Processing is the recommended method of importing RSMF files into Relativity, which means the RSMF file already exists when Processing begins.
This rules out the other options. Relativity does not say that it automatically creates RSMF on-the-fly for all non-document data. It also does not describe a processing-profile feature that converts arbitrary XML from chat platforms into RSMF during import. Nor is there a document-list mass operation that converts conversations into RSMF. Instead, RSMF is a defined external format that must be constructed according to Relativity's published specifications, then imported and processed to preserve message metadata, attachments, and near-native review behavior. Therefore, the correct answer is C.

The correct answer is D. Install the Repository application to the workspace. Relativity's official repository workspace documentation states that when installed to an existing workspace, the RelativityOne repository workspace application converts the workspace into a streamlined repository workspace for early case assessment and lower-cost storage of data not actively under review. The documentation also provides a dedicated section called Converting a review workspace to a repository workspace , where the conversion steps are simply to access the RelativityOne Repository Workspace application from the Application Library and install the application to the desired workspace .
This makes option D the exact documented conversion method. Option A describes moving data to another repository workspace, which is a different workflow and does not convert the existing workspace itself.
Option B involving ARM restore is used in some repository-related workflows, especially around templates or archived workspaces, but it is not the primary documented method for converting an existing workspace.
Option C is incorrect because repository mode is not enabled by editing a status field. Relativity also notes that if you convert an existing review workspace by installing the Repository application, the workspace remains classified for billing as a review workspace until the beginning of the next calendar month, which further confirms that application installation is the actual conversion mechanism.