Pass the Relativity Admin RCA Questions and answers with Dumpstech

The correct answer is D. Entity . Relativity’s official documentation explicitly states that the Entity object functions as the central location for people, companies, organizational groups, and their metadata . This wording appears directly in the Entity object documentation and is the exact phrasing reflected in the question.

The other options are incorrect because they serve different purposes in Relativity. A Field stores data elements, a Layout controls display and editing arrangements, and a Document represents reviewable content. None of these objects serves as the centralized person/company/group metadata object described in the official documentation. Therefore, the correct answer is Entity .

The correct answer is D. Use Mass Replace to update the long text field with the fixed-length text field values. Relativity’s mass operations documentation explains that Mass Replace can be used not only to replace text with static content, but also for field-to-field operations. Specifically, the official examples include copying the contents of one text field to another and merging the values of a source field with the values of a target field . That directly fits this scenario, where the administrator needs to populate a newly created long text field with the existing values stored in a fixed-length text field across many documents.

The other options are less efficient or not aligned with standard Relativity functionality. Manual updates would be extremely slow and error-prone in an active review. Exporting and then overlaying values would create unnecessary extra steps and administrative overhead. Option B refers to Mass Merge , but in Relativity documentation the Merge mass operation is associated with Analytics entity handling, not with copying document text values between fields. For document field content migration, Mass Replace is the documented bulk-update tool. Because this question focuses on the fastest and most efficient administrative correction after review has started, the best practice is to create the correct long text field and then use Mass Replace to populate it from the original fixed-length text field.

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 A . Relativity’s official aiR for Review permissions documentation states that to create and run an aiR for Review project, a user needs object permissions for aiR for Review Project and aiR for Review Prompt Criteria , tab visibility for aiR for Review Projects , and the Run aiR for Review Job permission under Other Settings. The documentation also explicitly states that a user can run the job without permissions for the analysis types, but will not be able to see the results . The analysis-type objects listed by Relativity are aiR Relevance Analysis , aiR Issue Analysis , aiR Key Analysis , and aiR Summaries .

That is exactly the problem in this scenario: the reviewer has enough permissions to create the project shell and prompt criteria, but no permissions were granted for the analysis result objects themselves. As a result, they can initiate work but will not be able to see the analysis results. Option B is incorrect because Viewer highlighting also depends on having analysis-type view permissions. Option C is incorrect because instance-level jobs visibility is a separate permission model. Option D is also incorrect because the provided permissions already include the aiR for Review Projects tab, and the missing issue is not dashboard tab access but the lack of object security for the individual analysis result types . Therefore, the reviewer’s main issue is that they will not be able to view any aiR for Review results without the required analysis-type object permissions .

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 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 A. Use a mass operation to update the Disable On Date field. Relativity’s Users documentation explicitly states that you can use a mass-operation to set the Disable On Date (UTC) field for multiple users . This is the exact documented method for updating that field across multiple user accounts at once.

The other options are not the documented answer for this workflow. Disabling a group is not the same thing as updating the Disable On Date field on user records. Overlay via Import/Export is not the method Relativity identifies for this task in the Users documentation. Setting the field individually works for a single user, but the question asks specifically about multiple users . Therefore, the correct answer is to use a mass operation to update the Disable On Date 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 .

The correct answer is C. The email and other parent emails in the thread are coded differently. Relativity’s Email thread visualization documentation explains the meaning of the visual warning icons used in the thread display. The red exclamation point is associated with a coding mismatch condition in the thread. In practice, this means related parent emails in the thread have been coded inconsistently, which is exactly the kind of review inconsistency ETV is designed to expose.

This is different from missing attachments, duplicate spare comparison, or a generic “Needs Review” state. ETV is focused on surfacing thread relationships, inclusiveness, missing emails, and coding consistency across the email conversation. From a Structured Analytics standpoint, the red exclamation point is a QC indicator that reviewers should inspect the thread because coding decisions across parent emails do not align. Therefore, the correct answer is C .

The correct answer is A. Document - Update . Relativity’s official Audit documentation states that system admins can revert coding decisions from the Audit list, and that this action applies to the latest Document Update , Mass Update , or Propagate action on the Document object. That makes Document - Update the correct revertable action among the choices provided.

The other options are not listed by Relativity as revertable audit actions in this context. A Field - Update concerns the field object itself rather than a document coding decision. Entity - Merge may create audit records, but Relativity does not list it as an action that can be reverted through the Audit revert feature. Redaction - Update is also not one of the documented revertable audit actions under the Audit tab’s revert capability. From an RCA perspective, this distinction matters because Audit revert is narrowly scoped to specific document-level update actions and certain supported field types. Therefore, the correct answer is Document - Update .