Pass the Relativity Admin RCA Questions and answers with Dumpstech

The correct answer is C. Export the production set as PDFs using Import/Export. Relativity’s official Import/Export documentation states that Import/Export is the recommended method for importing and exporting data for RelativityOne , and the production export workflow specifically supports exporting a production set load file with production files. The production export workflow is the documented method for exporting production sets and their associated deliverables in a structured, transferable form.

This makes it the best fit for the question’s requirement: produced PDFs with a corresponding load file . The PDF mass action is a separate document-level utility for creating PDFs from documents, natives, images, or produced documents, but it is not the standard production export workflow for packaging a production with its corresponding load file. Downloading PDFs from the Viewer is a manual review action, not a formal production export workflow. ROSE is used for large-scale data transfer to and from RelativityOne storage, but the product documentation positions Import/Export as the recommended export mechanism for production sets and related load files.

So, from a Productions and RCA workflow perspective, the recommended method is to export the production set as PDFs using Import/Export .

The correct answer is D. Replace produced images with a placeholder. Relativity’s official Re-production documentation lists supported and unsupported re-production types. Among the supported types, Relativity explicitly includes Replace produced images with placeholder (I-P) .

The same documentation also explicitly lists several unsupported types that correspond to the incorrect options in this question. Relativity states that replacing a document that was produced as native only with produced images or a placeholder is unsupported, which rules out option B. It also states that replacing a document that was produced as a placeholder with another placeholder is unsupported, which rules out option C. Option A is likewise unsupported because “replace produced images with a native” is not identified as a supported re-production type. Instead, Relativity supports image-to-placeholder, placeholder-to-images, and re-producing documents with the same number of pages.

This distinction matters because re-production is tightly controlled to preserve numbering integrity and production consistency. For example, when replacing produced images with placeholders, Relativity preserves the original Bates numbering while substituting placeholder pages. From an RCA production-administration perspective, the supported operation among the listed choices is clearly Replace produced images with a placeholder . Therefore, the correct answer is D .

The correct answer is A. After updating fields in the searchable set. Relativity’s dtSearch index documentation states that you must perform a full build when you add an additional field to the index, change any index settings, change fields of the searchable set, or overlay text on existing fields . That directly matches option A.

By contrast, Relativity documents that an incremental build is used after adding or removing documents . That makes options B and D incorrect. “After using Swap Index” is not listed as a required trigger for a full build in the dtSearch console documentation. Therefore, the correct answer is that a full build is required after updating fields in the searchable set .

The correct answer is A. After a production is exported. Relativity’s official documentation on OCR for redacted production documents explains that you create an OCR set and then point the OCR set to the completed Production . The workflow explicitly states that OCR is performed against the completed production , and once the OCR job is complete, the resulting text becomes ready to export. This means the production must already exist before OCR is run against it. In practical terms, OCR is performed after the production has been run/exported as a completed production set , not before the production exists.

The reason for this is that Relativity OCR in this workflow can operate on production images containing burned-in redactions . That allows the exported text to reflect the redacted version rather than unredacted underlying extracted text. Running OCR before the production is run would not achieve this production-specific result, because the final production images would not yet exist. Option D is too broad and incomplete because a document being redacted does not itself define the OCR timing; the documented process is tied to a completed production . Therefore, under the Productions topic, the correct answer is that you run OCR after the production is exported/completed , because that is when the production images are available for OCR processing.

The correct answer is A. The field to use for production numbering. Relativity’s documentation distinguishes between production set settings and production data source settings . The production set defines overarching settings such as document numbering , appearance of numbering, and related production-wide behaviors. By contrast, the production data source page includes settings such as production type , placeholder image format , burn redactions , burn native redactions , burn PDF redactions , and markup set .

This means the field used for production numbering is not configured at the individual data source level; it belongs to the production set itself. The other options are all part of production data source configuration. The documentation explicitly shows Burn Redactions and Markup Set , and placeholder behavior is also configured within the production data source settings.

Therefore, the option that cannot be configured when creating a new production data source is the field to use for production numbering , because that is a production-set-level setting rather than a data-source-level one.

The correct answer is B. Production type. Relativity’s official Production Data Source documentation states that when adding a production data source, one of the fields you configure is Production Type , where you select whether the data source will produce images, natives, or both . This is explicitly part of the production data source setup dialog.

This makes sense because production data sources are used to attach saved searches to a production set and can define how those specific subsets of documents should be produced. Relativity also documents that placeholders can be assigned at the production data source level so that different saved searches in the same production can use different placeholder behavior. However, Production Numbering is defined at the production set level rather than as a field you set when creating the individual production data source. Likewise, Branding text size and Placeholder image format are production-level settings, not the core field identified in the data source setup described by Relativity.

From an RCA standpoint, this distinction matters because administrators configure overall production behavior in the production set, while more granular document-source behavior is controlled on each production data source. Therefore, the correct answer is B. Production type .

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.

The correct answer is C. #pear . Relativity’s Using dtSearch syntax options documentation states that phonic searching uses the pound sign (#) in front of a word. The documentation gives the exact example that a phonic search for pear also finds pair and pare , which directly matches the question.

The other choices represent different or invalid syntax. pear* is a wildcard-based pattern, not a phonic search. The apostrophe form is not the documented phonic operator, and $pear is not the phonic syntax in Relativity dtSearch. Therefore, the correct syntax for a phonic search returning pair and pare is #pear .

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. 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 .