RCA Exam Dumps - Relativity Admin Questions and Answers

The correct answer is A. Relativity Compare . Relativity’s official documentation on using near duplicate analysis in review states that the Relativity Compare function can compare two documents to assess their similarities and differences . This is the exact activity described in the question and is directly relevant to working within a textual near duplicate group, where reviewers often need to determine how one member differs from the principal document or from another near duplicate in the set.

The other options do not match that purpose. Image QC is used for image quality control workflows, not for textual comparison of document content. Document View Overlay is not the standard Relativity tool documented for assessing textual differences between near duplicates. Similar Documents View helps surface conceptually or textually related material, but it is not the dedicated side-by-side comparison tool Relativity identifies for evaluating differences. From a Structured Analytics perspective, this distinction matters because near duplicate analysis groups similar records together, but the actual determination of differences between two specific documents is handled through the comparison function. Therefore, when assessing differences within a textual near duplicate group, the correct tool is Relativity Compare .

The correct answer is C. The name of the file. Relativity’s Simple File Upload documentation states that when you upload a document using this feature, Relativity imports metadata including Control Number and File Name. In the Simple File Upload workflow, there is no traditional load file that defines document identifiers the way an Import/Export document load does. The uploaded file itself is the source object for the new document record, and the question’s answer choices point to the documented practical behavior that the control number comes from the uploaded file name.

The other options do not align with the Simple File Upload model. ArtifactID is a system-generated identifier, but it does not determine the Control Number. There is no document load file in this workflow, so option B is incorrect. Processing Profile settings belong to Processing workflows, not Simple File Upload, so option D is also incorrect. Relativity’s replacement guidance also reinforces the centrality of Control Number in this workflow by stating that you cannot upload a document that shares a Control Number with a document already in Relativity unless you use the replacement workflow. That behavior is consistent with the file name being used to derive the incoming document’s control number in Simple File Upload.

The correct answer is B. dog not cat. Relativity’s dtSearch syntax guidance explains that the NOT operator can be used by itself at the beginning of an expression, or in the middle of an expression only when combined with either AND or OR. Relativity gives examples such as apple OR NOT pear and applesauce and NOT pear as valid syntax. That means expressions like dog OR NOT cat and dog AND NOT cat are valid, while dog NOT cat is missing the required connector and therefore causes a syntax problem.

Relativity’s Search Terms Report error documentation further explains that STRs surface syntax errors when the search index cannot process the term because of invalid syntax. In this case, dog not cat violates the dtSearch operator rule, so it is the option most clearly expected to fail with a syntax error in a search terms report. Option A is a standard Boolean expression and is valid. Options C and D both include the required connector before NOT, which matches Relativity’s documented dtSearch usage. Therefore, among the listed queries, dog not cat is the one that would cause a syntax error on an STR.

The correct answer is B. Run the Set native file size field script. In Relativity, the purpose of the Set native file size field script is to populate a decimal field with the size of each document’s native file. This is the most efficient and direct administrative method when a workspace already contains produced native files and the case team wants a usable field showing file size. Relativity’s documentation states that the script stores the native file size for each document in the workspace in a decimal field, making it specifically aligned to this requirement. It is intended for administrators who need to backfill or populate this metadata after files have already been loaded, rather than relying on manual calculations or unrelated operations.

The other options are not correct. A tally/sum/average mass operation works on values that already exist in fields; it does not inspect native files and write their file sizes into a document field. The Set extracted text size field script applies to extracted text size, not native file size, so it addresses a different metadata requirement. The statement that native file size is automatically populated for documents is also incorrect in this context, because Relativity provides a dedicated script precisely for populating that field when needed. Therefore, from a Relativity Certified Administrator perspective under Data loading , the correct and most efficient administrative action is to run the Set native file size field script.