RCA Exam Dumps - Relativity Admin Questions and Answers

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 .

The correct answer is A. "Queue Refresh" must be set to "On". Relativity’s Review Center admin documentation states that Queue Refresh controls whether the queue automatically refreshes after coding activity . For prioritized review queues, that refresh includes re-running the saved search, checking for outside-coded documents, retraining the classifier, and re-ranking documents based on the latest coding. That makes Queue Refresh the setting required for automatic queue refreshing.

Relativity also documents that prioritized review queues auto-refresh when there has been a 20% change in total coded documents, and additionally after 8 hours if there has been coding activity. Those are auto-refresh conditions, but they do not replace the need for the Queue Refresh setting itself. Option B therefore describes a trigger condition, not the required setting. Options C and D are not documented as the needed configuration for automatic refresh. Therefore, the correct answer is that Queue Refresh must be turned on .

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. 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 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 . 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: . Relativity’s RSMF-supported emoji documentation states that emojis in RSMF files display as text strings surrounded by colons , giving the example :smile: . That directly establishes the emoji short-name format used by Relativity for named emoji representations.

The Short Message Viewer documentation also confirms that users can search for emojis in conversations. Since Relativity’s own emoji naming convention is colon-delimited short names, the correct format for searching by name is :Name:. The other options use bracket, angle-bracket, or quoted forms that Relativity does not identify as the short-name syntax for emoji. Therefore, the correct answer is :Name: .

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 D. Use the Tally/Sum/Average mass operation on the Relativity Image Count field. Relativity’s Tally/sum/average documentation says this mass operation is commonly used to determine the number of pages in a print job or production. Relativity also specifically documents, in related guidance, that to estimate project size you can use Tally/sum/average on the Relativity Image Count field.

This makes it the fastest and most direct built-in method for obtaining an image count estimate. The other options are less efficient or are not the documented workflow for quickly producing a total image count. Therefore, the correct answer is to use Tally/Sum/Average on the Relativity Image Count field.

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 .