Pass the Relativity Admin RCA Questions and answers with ExamsMirror

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 D. NOT . Relativity’s Filters documentation for text box filters lists the valid operators as AND, OR, IS SET, IS NOT SET, BETWEEN, =, > =, and < = . Since NOT does not appear in that valid operator list, it is the invalid choice among the options provided.

This is a useful distinction because Relativity supports NOT in some other search contexts, such as dtSearch or advanced filtering patterns, but the question asks specifically about a text box filter operator. In that exact context, AND , IS SET , and > = are valid, while NOT is not. Therefore, the invalid operator for a text box filter is NOT .

The correct answer is D. Existing production numbering . Relativity’s official production set documentation states that Existing production numbering should be selected when you want to re-use the Bates numbering fields from a previously run production set . This is the exact numbering option designed for scenarios where documents are being reproduced but must retain the same Bates values from an earlier production. Relativity further explains that this option is appropriate when you need to change the produced images, produce only a subset of documents from the existing production, or otherwise reissue the same produced documents while preserving the prior numbering.

This aligns directly with re-production workflows. Relativity’s re-production documentation also notes that re-production jobs reuse the numbering format and Bates numbers from the original productions , reinforcing that the platform supports maintaining the original numbering scheme instead of assigning new Bates values. That is critical in litigation workflows where Bates continuity must be preserved for references in correspondence, court filings, and prior productions. The other options do not fit this requirement. Page level numbering and document field numbering generate or rely on other numbering methods, while original image numbering is not the production numbering choice used for preserving prior Bates values in a re-production. Therefore, when reproducing documents and keeping the same Bates numbering, the correct production numbering method is Existing production numbering .

The correct answer is C. Build dtSearch Index . In Relativity, Automated Workflows consists of two major components: triggers and actions . Triggers determine when a workflow starts, while actions determine what task the workflow performs once it begins. Relativity’s official Automated Workflows documentation lists Build dtSearch index as one of the available actions that can be added to a workflow. When selected, this action allows the workflow to automatically build a dtSearch index, either as a full build or incrementally depending on the configuration.

The other options are not actions. Scheduled Run and Manual Start are both documented by Relativity as trigger types , not actions. Scheduled Run starts a workflow on a defined daily, weekly, or hourly cadence, while Manual Start allows a user to launch the workflow by clicking the Manual Run button. Build a cluster is also not listed by Relativity as an Automated Workflows action. From an RCA perspective, it is important to distinguish triggers from actions because workflow design depends on choosing the correct combination of each. Administrators may configure a trigger such as Scheduled Run or Manual Start, and then assign one or more actions such as Run OCR Set, Run Imaging Set, Build Elasticsearch index, or Build dtSearch index . Therefore, among the options provided, the only valid available action is Build dtSearch Index .