RCA Exam Dumps - Relativity Admin Questions and Answers

The correct answer is D. Name normalization. Relativity’s official Communication Analysis documentation states that you can add the Communication Analysis widget to a dashboard after running name normalization . The widget visualizes communication frequencies, patterns, and networks between entities linked to the documents in the view, and those entities come from the results of name normalization.

This requirement is fundamental because the widget depends on entity and alias relationships generated by structured analytics name normalization. Without those normalized entities, the system does not have the participant relationship structure needed to render communication maps. Relativity also repeats this requirement in its dashboard documentation, again stating that Communication Analysis is available after running the name normalization operation within structured analytics .

The other options are not the prerequisite named by Relativity. A repeated content filter is optional and only used to improve text cleanup. A conceptual analytics index is a different analytics technology entirely. Email threading is a separate structured analytics operation and is not the stated prerequisite for this widget. Therefore, the correct answer is D. Name normalization .

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. 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 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. Entity . Relativity’s official documentation explicitly states that the Entity object functions as the central location for people, companies, organizational groups, and their metadata . This wording appears directly in the Entity object documentation and is the exact phrasing reflected in the question.

The other options are incorrect because they serve different purposes in Relativity. A Field stores data elements, a Layout controls display and editing arrangements, and a Document represents reviewable content. None of these objects serves as the centralized person/company/group metadata object described in the official documentation. Therefore, the correct answer is Entity .

The correct answer is A. The field mapping section is disabled because only the control number is needed. Relativity’s official Integration Points documentation for promoting data between workspaces states that when you select Copy Images , the field mapping section is disabled because only the control number is required and available in this scenario . It further notes that if you want to transfer other field metadata, you must create a separate integration point without choosing to copy images.

That directly rules out the other options. Relativity does not state that the native file must be included to transfer images in this scenario. It also specifically notes that you are not required to have Integration Points installed on the destination workspace , so option C is incorrect. Option D is wrong because metadata is not automatically mapped and migrated in the Copy Images path; in fact, field mapping is disabled in that configuration.

From an RCA and data-movement perspective, this is a common distinction: image promotion through Integration Points is streamlined and relies on control number matching , not standard metadata field mapping. Therefore, the true statement is A .

The correct answer is A. Mass Image and Document Local Access. Relativity’s official Mass Delete permissions page lists the required rights to successfully mass delete documents. In addition to the Mass Delete permission itself under mass operations, the user must have several document-related permissions, including Delete , Edit , Image , and object-security rights such as Add Image and Delete Image on the Document object. In exam-style shorthand, this corresponds to having image-related deletion capability and document-level access beyond the Mass Delete toggle alone.

The other combinations do not match the documented permission model. Mass Convert is unrelated to deletion. Mass Edit alone does not satisfy the image/file handling aspects of document deletion. The question’s wording is a little compressed compared with the full Relativity permissions matrix, but among the answer choices, the only one that aligns with the need for image-related rights plus document-level access is Mass Image and Document Local Access . In practical administration, mass deleting documents can also involve deleting associated images and natives from storage, so Relativity requires more than a single Mass Delete checkbox. That is why administrators must ensure the deleting group has the necessary image and document permissions in addition to Mass Delete. Therefore, the best answer from the provided options is A .

The correct answer is C. The video must be synced to one .MP4 video and uploaded at the same time. Relativity’s official Transcripts application documentation explicitly states that the video can be played in the Viewer in sync with the text of the transcript, and further notes: you must import videos at the same time you are uploading transcripts or the video and transcript cannot sync . The documentation also describes uploading the video as an .mp4 alongside the transcript during the transcript upload workflow.

This directly eliminates the other options. Option A is false because Relativity clearly supports synced transcript video playback. Option B is wrong because this is not a PST-based workflow. Option D is also incorrect because the documentation does not describe a later mass action that separately syncs already uploaded video and text files; instead, the sync relationship is established during the same upload process. Relativity even distinguishes that videos are not stored as normal documents in the document list, but rather as a file field within a transcript, reinforcing that the transcript upload workflow is the correct path.

From a case administration standpoint, this is important because transcript/video synchronization affects deposition and interview review usability. To ensure successful synchronization, the transcript and its associated .mp4 video must be uploaded together. Therefore, the correct answer is C .

The correct answer is A. It is the tab that has been set as the default tab. Relativity’s Tabs documentation states that a tab has a Set as Default Tab toggle, and when this is turned on, that tab serves as the workspace’s default tab. Reviewers logging into the workspace are taken to that default tab. Relativity also notes that if a reviewer does not have access to that default tab, the user is directed to the Documents tab instead.

This means the default tab is not determined merely by tab order. The lowest order number affects where a tab appears in the sidebar, but not which tab is designated as the workspace default. The Admin tab and Documents tab are not always the default either; Documents only acts as the fallback if the user lacks access to the selected default tab. Therefore, the correct answer is that the default tab is the one explicitly set as the default tab .

The correct answer is A. NOT magazine AND apple . Relativity’s dtSearch syntax documentation confirms that dtSearch supports the Boolean operators AND, OR, and NOT and uses them to connect multiple terms in a single search expression. To return only documents that contain apple while excluding those that contain magazine , the query must require the presence of apple and exclude magazine in the same Boolean expression. Option A does exactly that.

Option B is not correct because Apple NOT magazine is missing the required Boolean connector before NOT . Relativity’s dtSearch guidance and related syntax behavior show that NOT is used as part of a Boolean expression, not as a standalone middle operator without AND or OR. Option C is incorrect because Apple OR NOT magazine would broaden the result set too much, potentially returning documents that do not contain apple at all. Option D is also incorrect because it excludes apple instead of requiring it. Therefore, the valid dtSearch string that successfully returns documents containing apple but not magazine is NOT magazine AND apple .