RCA Relativity Certified Administrator Free Practice Exam Questions (2026 Updated)

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 A. Simple File Upload. Relativity’s Simple File Upload documentation states that the Viewer supports the ability to replace natives and images from the Document Actions menu. The same documentation ties this replacement workflow to Simple File Upload , explaining that if you want to replace a document rather than upload a new one, you use the Replace document native function in the Review Interface. Relativity’s review interface guide also shows that reviewers can replace the native file of the current document and replace the images for the current document from the Viewer.

The other tools do not match this Viewer-based replacement workflow. Mass Replace updates field values, not the native or image file itself. Relativity Processing is for ingestion and extraction workflows, not replacing a currently loaded document in the Reviewer Interface. Native Imaging Sets image groups of documents but are not the tool identified for replacing a native or image from within the Viewer. Therefore, the correct answer is Simple File Upload .

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 C. Change the job’s priority to the lowest value in the queue. Relativity’s Branding queue documentation states that only one job runs at a time and the lower numbered job runs first while the higher numbered job runs last. It also explains that you can move jobs by using Change Priority and entering a new integer value. Since lower numbers represent higher queue priority, moving a job to the front means assigning it the lowest priority number among the queued jobs.

This rules out option D, which reverses the queue logic. Changing submitted date/time is not the documented control for moving a branding job forward, and canceling/restarting is unnecessary when Relativity already provides a queue-priority control. Therefore, to move a job to the front of the Branding queue, you change its priority to the lowest value in the queue.

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 D. RAP . Relativity’s official application export documentation states that when you export an application, Relativity produces a RAP file . The documentation explicitly says that after the export completes, you can find the RAP file in the selected folder and then upload that file to the target workspace or Relativity instance for deployment. This is the standard application package format used by Relativity for moving custom or configured applications between environments.

This matters in case administration because administrators frequently manage applications across workspaces and instances, including exporting custom objects, views, layouts, scripts, event handlers, and other application components. Knowing that the package format is .rap is essential when promoting configurations between development, test, and production environments. The other options are generic archive formats that may be familiar in general computing, but they are not the official Relativity application package type. Relativity also refers throughout its application installation and export documentation to installing or uploading .rap files , which reinforces that this is the correct and platform-specific answer. Therefore, from an RCA perspective, the correct answer is RAP , because that is the documented file type generated when a Relativity application is exported.

The correct answer is B. Turn on Date Recognition before building the dtSearch index. Relativity’s Searching Guide explains that date recognition must be activated before it can be used in the workspace. It also states that dtSearch recognizes valid date formats common in both the US and UK , including DD/MM/YY and DD/MM/YYYY formats. That means UK dates are supported, but the index must be configured with Date Recognition enabled in order to take advantage of date searching behavior.

This rules out option D because UK date formats are explicitly supported. Option C is incorrect because adding the slash character to the alphabet file is not the documented preparation step for date searching. Option A is unrelated to dtSearch date-recognition configuration. From an RCA perspective, the important point is that dtSearch can recognize UK-style numeric dates, but only if Date Recognition is enabled before the relevant index build. Therefore, the correct answer is B .

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. 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. Speaker . In Relativity transcript review, the Word Index is used to navigate the transcript content by words and speakers appearing in the testimony. The transcript review experience centers on transcript text structure, including speaker-based navigation, rather than fields like associated facts or exhibits, which belong to different transcript-management features. Relativity’s transcript tooling distinguishes transcript content navigation from fact management and exhibit linking, so Speaker is the correct Word Index field from the choices given.

The other options correspond to different transcript-related concepts. Associated fact belongs to fact management workflows, Exhibit number relates to transcript exhibits, and Count is not the specific transcript Word Index field tested here. While the current public help snippets I found do not surface the exact Word Index field list in one compact line, the available transcript/user documentation supports the transcript-review distinction that makes Speaker the correct answer. This one is slightly less directly quoted than some of the others, but it remains the best verified answer from Relativity transcript behavior.

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 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. 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. The fields returned by the Searchable Set saved search are all empty for this document. Relativity documents that dtSearch indexes are built against a Searchable Set, and administrators must manually update those indexes when the underlying document search sets change. Relativity also describes dtSearch as indexing the content made available through the configured search/index setup rather than magically finding text that is not present in the indexed fields. If the document is part of the saved search but the fields being indexed for that document are empty, there is effectively no searchable text for dtSearch to return for that record.

Option B is not the best answer because an incremental build is a maintenance activity for adding new documents, not the documented reason a single already-known document cannot be found. Relativity notes that incremental builds look for new documents in the searchable set and do not re-index previously indexed records with changed content, which is a different issue. Option D is unrelated because Review Center queue assignment does not control whether a document is searchable through a dtSearch index. Option A is also not the best explanation for this question; dtSearch availability is driven by index/searchable-set configuration and accessible indexed text, not by parent-email folder access in the way the option suggests. So the best RCA-aligned answer is that the document has no indexed searchable content in the fields returned by the searchable set.

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. 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 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. 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 C. Unlock the application. Relativity’s application uninstall documentation states that before deleting or uninstalling an application, you must unlock the application if necessary , and specifically notes that you can't delete a locked application . That makes unlocking the required prerequisite among the options given.

The other options are not listed as required prerequisites. There is no documented requirement to run an uninstall script from the Scripts tab, delete associated tabs first, or unlink all saved searches before uninstalling. Relativity separately documents locking and unlocking applications and states that unlocking allows editing and changes to the application. Therefore, prior to uninstalling an application from a workspace, the required step is to unlock the application .