Relativity RCA Dumps Questions Answers

The correct answer is D. Existing links to exhibits in the transcript are visible once completed. Relativity’s official Transcripts documentation states that supported bundle file types include .lef and .xmef . When a bundle is uploaded, Relativity extracts the transcript file and displays the extra files as exhibits. The documentation further states that existing links to exhibits in transcript files will be visible in the Viewer once they are uploaded to Relativity . That is a direct match to option D.

This makes the other options incorrect. Bundled transcript files are explicitly supported, so option A is wrong. Exhibits do not need to be manually linked in the way described by option B when the transcript already contains those links; Relativity preserves and displays existing links. Option C is also incorrect because the documentation explains that the bundle upload process extracts the transcript and surfaces the additional files as exhibits, rather than requiring administrators to parse and upload them separately. From a case administration standpoint, this is useful because it streamlines transcript management and preserves exhibit relationships during import. Therefore, when importing LEF or XMEF bundled transcript files from the Document object, the true statement is that existing links to exhibits are visible once the upload is completed .

The correct answer is B. A reviewer was originally part of the workspace and coded documents, but has since been removed from the workspace. Relativity’s official Review Center documentation explains that when documents were coded by reviewers who are not part of the current Relativity instance , those reviewers can appear in charts and tables as “Unknown User 1,” “Unknown User 2,” and so on. The documentation specifically notes that this can happen if a reviewer was removed from the workspace or if the workspace was archived and restored into a different instance. That directly supports option B.

The other options do not match Relativity’s documented explanation. Losing permission to code is not the stated reason for the “Unknown User” label. Likewise, an unprepared project is a separate project-state issue and does not explain why specific prior coding activity would be attributed to an anonymous placeholder. An error requiring queue re-preparation is also not the documented cause of this naming behavior. From a case administration perspective, this is an important concept because administrators often manage workspace users, permissions, and lifecycle changes over time. If prior reviewers are removed, their historical coding may still appear in analytics or project monitoring views, but the user identity may no longer resolve normally. In that circumstance, Review Center surfaces those coding records under a label such as “Unknown User 1.”

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.