Relativity RCA Relativity Certified Administrator Exam Practice Test

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 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 B. After the current task completes. Relativity’s Automated Workflows documentation states that when you click Cancel Workflow , the workflow is canceled once the currently running task is completed . The documentation is explicit that canceling the workflow does not cancel an action that is currently in progress . If you want to stop the active action itself, you must navigate to that specific object and cancel it there.

This means the cancellation is neither immediate nor delayed until the whole workflow finishes. It also means option A is false because workflows can be canceled. From an RCA administration perspective, this is important because workflow cancellation is staged: pending downstream actions are stopped, but the in-flight task is allowed to finish unless separately canceled at its own object level. Therefore, the correct answer is after the current task completes .

The correct answer is C . Relativity’s official production staging documentation states that a staging error occurs when the same document is found in multiple data sources within the same production set. When this happens, Relativity generates an error message identifying the data sources that pulled back the same document and which specific document is duplicated. The documented resolution is to modify the saved searches used as data sources so they no longer return the same document.

This means staging does not simply ignore the duplicate, nor does it produce the document twice or proceed using the first data source’s settings. The duplicate condition is treated as a production-stopping issue that must be corrected before the production can successfully continue. From an RCA perspective, this is a core Productions concept because it affects production QC and data-source design. Administrators should ensure that saved searches used as production data sources are mutually exclusive when necessary, especially if different branding, numbering, or production settings apply. During staging, Relativity is validating the integrity of the production inputs, and duplicate documents across data sources are explicitly flagged as errors. Therefore, the correct interpretation is that an error message appears during staging and the production cannot proceed until the duplicate documents are removed from overlapping data sources .

The correct answer is B. Replace entire field . Relativity’s Mass Replace documentation lists the available Action options for Mass Replace. These include Replace Entire Field , Append to End , Insert at Beginning , and Search For . Since Replace Entire Field is explicitly named by Relativity as one of the supported Mass Replace actions, it is the correct answer.

The other options are not valid as written. Relativity uses Append to End and Insert at Beginning , not “Insert after.” “Rename field” is a field-administration task, not a Mass Replace action. “Search for sentiment” is unrelated to Mass Replace and not part of the operation’s feature set. This question tests familiarity with the exact Mass Replace UI choices. Therefore, the correct available option is Replace entire field .

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. 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. Regular expression filter. Relativity’s Structured Analytics documentation states that a Regular expression filter can be linked to a structured analytics set as an optional setting, and that it is used to clean up extracted text before analysis . The documentation further explains that this setting is implemented through a repeated content filter whose type must be Regular Expression . This directly matches the question’s wording about excluding document text before analytics processing begins.

This capability is especially useful when documents contain extraneous content such as dates, URLs, page numbers, Bates numbers, standard disclaimers, or other repeated text that can interfere with email threading or textual near duplicate results. Relativity notes that the filter applies only to the field being analyzed, which is usually Extracted Text unless another field is selected. By removing this noise before the algorithm runs, administrators can improve the quality of structured analytics outcomes.

The other options are not the correct named filter for this function in Relativity’s structured analytics workflow. The official setting is specifically the Regular expression filter . Therefore, the correct answer is D .

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 . Relativity’s official production console documentation explains that Stage Production and Stage and Run Production both take a snapshot of the data sources for the production. The staging step captures the current contents of those data sources so the production job runs against a fixed set of documents. Relativity also documents that staging errors occur if the same document is found in multiple data sources , which means duplicate-document checking is part of what administrators must evaluate during the staging phase.

The other options describe different production activities. Showing a sample image of branding is associated with Preview Production , not staging. Bates numbers are assigned later as part of the production run, not during the initial staging snapshot. The option about conflict checking against a Production Restriction saved search is not the best description of the staging step itself according to the official documentation. For RCA exam purposes, the key concept is that staging freezes the production inputs and surfaces structural issues, especially duplicate documents across data sources, before the full production run proceeds. This is an important quality-control checkpoint because it helps administrators verify that the right documents and data-source configuration are in place before branding, numbering, and export occur. Therefore, the best answer is that during staging, Relativity takes a snapshot of the data sources and checks for duplicate documents between data sources .

The correct answer is B. Name conflicts: Rename or map Fields. Relativity’s Troubleshooting application installation errors documentation explains that for Name conflicts , the available resolution options include Rename and Map Field . The page specifically instructs admins to use the Resolve Errors drop-down and choose either Rename or Map Field to address the conflicting artifact during application installation.

The other choices are inconsistent with the documentation. For locking conflicts , Relativity says you can resolve them by selecting the Unlock checkbox, so option A is incorrect. For restricted file types , the documented resolution is to remove the external resource from the application and re-install , not simply “run a re-install,” so option D is incomplete and inaccurate. Option C is also too vague and not one of the documented named error-resolution pairings. Therefore, the correct expected application installation error and solution is Name conflicts: Rename or map Fields

The correct answer is D. The same document is found in multiple data sources. Relativity’s official production documentation identifies this as a staging error . When the same document appears in more than one production data source within a single production set, Relativity generates an error message identifying the overlapping data sources and the duplicate document. This must be corrected before the production can proceed successfully.

This behavior exists because Relativity production data sources are intended to define a clear, non-conflicting set of documents and related production settings. If the same document is pulled from multiple data sources, the system cannot reliably determine which source configuration should govern that document for the production. As a result, Relativity stops the process and requires the administrator to resolve the overlap by adjusting the saved searches used as data sources.

The other options are not the documented production error in this context. Relativity does not identify “too many redactions” as the standard production error described here. Producing the image version of an unresponsive document is a review judgment issue, not a system production error. Producing a native file for a redacted document may raise workflow concerns, but it is not the specific documented staging error addressed by the production help pages. Therefore, the correct answer is D .

The correct answer is A. Relativity. Relativity’s Processing throughput guidance states that internal performance testing has shown the Relativity text extraction method to be at least two times faster than the native method on Excel, Word, and PowerPoint file types, and also less error-prone than native extraction. Since the question asks for the best method to get a large Excel-only data set to review as quickly as possible, the documented speed advantage makes Relativity the best answer.

The native-based methods are slower according to that same documentation, even though they may have other use cases. The processing profile documentation also shows that native/failover combinations are available configurations, but the performance guidance specifically favors the Relativity extraction method for speed on Excel files. “Extract and place inline” is not the documented Excel text extraction method choice for this question. Therefore, the fastest and most review-efficient choice for large Excel files is Relativity.

The correct answer is D. Add them to an instance-level group with permissions to create groups, manage users, and assign permissions. Relativity’s instance security model allows administrators to assign instance-level permissions to groups through the Admin Security dialog. The documentation explains that permissions can be managed granularly through object security, tab visibility, and admin operations, which means a user can be given specific administrative rights without being made a full system administrator.

This matters because the System Administrators group grants broad access to admin-level permissions and tabs, including queue management. Relativity’s documentation specifically notes that system admins have access to all admin-level capabilities such as queue management, users, and groups tabs . If you do not want the user reviewing Processing or Production queues, giving full System Admin membership is broader than necessary. A workspace admin group is also insufficient for this requirement because creating groups, managing users, and assigning instance-level permissions are administrative functions controlled at the instance level. Therefore, the correct configuration is to place the user in an instance-level group with only the permissions they need.

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 B. Save as PDF. Relativity’s imaging documentation states that the Password Bank is used to decrypt certain password-protected files during processing and imaging workflows. It also explicitly states that Save as PDF does not integrate with the Password Bank and that if you select Save as PDF when imaging a password-protected native document, an error occurs .

This directly differentiates Save as PDF from the other options. Processing supports password decryption through the Password Bank. Mass Image and Imaging Sets also work with the Password Bank, allowing protected files to be imaged if the correct password is available in the bank. Because Save as PDF does not use that mechanism, it fails where the other imaging-related workflows can succeed.

From a case administration perspective, this is a practical operational detail. Password-protected content often needs special handling, and administrators need to know which tools integrate with Relativity’s decryption workflow. The one that does not work for this purpose is Save as PDF .

The correct answer is B. Runs the saved search and trains the classifier. Relativity’s Review Center documentation states that during the Preparing state, the queue is refreshing the saved search for the first time , and for a prioritized review queue , this also trains the classifier . The Review Center admin quick reference guide further states that Prepare Only re-runs the saved search for all queues and retrains the AI classifier for prioritized review queues , and it does not start the queue.

That makes option B the direct documented effect of Prepare Only. It does not grant reviewer access by itself, it does not release checked-out documents, and it is not a statistical sampling action. From a case administration perspective, Prepare Only is used to get the queue ready and refresh the machine-learning state before reviewers begin or resume work. Therefore, the correct answer is B .

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. Fixed length text . Relativity’s Mass PDF documentation states that when saving PDFs as a ZIP or PDF portfolio , you can choose to name the individual PDFs using the control number , the control number plus a field , or just a field . In other words, Relativity supports file naming from a document field value. The same documentation also notes that long names are truncated if they exceed the allowed length, which confirms that the chosen field value is being used directly as part of the resulting file name.

Among the answer choices, fixed length text is the best and most appropriate field type for this purpose. A fixed length text field is designed to store concise string values that work well as filenames. Artifact ID is not a field type in this context, but rather a system identifier. Date fields can exist, but they are not the standard answer for naming PDFs in an exam question framed around field type suitability. Single choice stores coded values and is not the expected best answer here. This question appears to test practical Relativity administration knowledge rather than every technically possible field serialization outcome. Since Mass PDF naming relies on a field value and file names are most appropriately based on text metadata, the correct exam-aligned answer is fixed length text . The Relativity documentation supports the field-based naming capability, and the selection of fixed length text is the most reasonable administrative interpretation from the provided options.

The correct answer is A. Configure the index to be accent sensitive. Relativity’s official dtSearch index documentation lists Create accent sensitive as a configurable Yes/No setting on a dtSearch index. When enabled, the index becomes sensitive to accents and other language-specific characters. This is an example of a valid dtSearch index modification that an administrator can configure.

The other options are incorrect. Relativity does not document a dtSearch feature that translates search terms into multiple languages, so option B is not a valid dtSearch index modification. A repeated content filter is associated with Analytics workflows, not dtSearch index configuration, so option C is also wrong. Option D is clearly incorrect because dtSearch indexes are not simply automatic and fixed upon import; Relativity provides a dedicated dtSearch object with editable settings such as searchable set, sub-index sizing behavior, skip malicious files, and accent sensitivity.

From an RCA perspective, this matters because dtSearch is a configurable search technology in Relativity, and administrators are responsible for tuning it for the needs of a workspace. Accent sensitivity can materially affect search precision in multilingual or language-specific datasets. Therefore, the correct answer is A .

The correct answer is B. Copy from Previous on the layout. Relativity’s Copy from Previous documentation explains that you enable this behavior on specific layout fields by setting Enable Copy from Previous to Yes . During review, after saving one document and moving to the next, users can copy the prior document’s coding values into the current document for those enabled fields. That directly matches the scenario of carrying Responsiveness tagging from one document to the next.

The other options do not provide that reviewer-interface behavior. Mass Copy is a separate bulk operation and not the per-document review workflow described here. Propagation is a different concept and is not the setting used to let reviewers carry coding values forward document by document. Document Local Access controls access-related actions, not coding carry-forward. Therefore, to let reviewers apply Responsiveness tagging from one document to the next, you enable Copy from Previous on the layout field.

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

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 .