Pass the Relativity Admin RCA Questions and answers with ExamsMirror

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 .

The correct answer is A. At the User level, use the Disable on Date settings. Relativity’s Users documentation states that Disable on Date (UTC) is the field used to auto-disable users on a specific future date. It also explains that you can set this field when creating or editing an individual user, and that users will be automatically logged out and disabled on the specified date and time.

The other options are not the documented built-in mechanism for this feature. User Activity in Security Center allows admins to inspect and disable users, but it is not the setting used to preconfigure automatic disablement on a future date. Likewise, the question’s instance-level settings in options B and D are not the Relativity feature described in the official Users documentation for automatic disablement. Therefore, the correct answer is Disable on Date at the user level .

The correct answer is A. The Family Group relational view is no longer selected. In Relativity, family relationships for emails and attachments are displayed through a relational view tied to the Group Identifier field. Relativity’s documentation explains that family groups are shown in a document list when a view is configured to display those relationships, and that the Group Identifier is the field used to associate an email with its attachments. When a relational family view is active, users can see the family grouped together in the list rather than seeing only the individual records that directly meet the filter criteria.

Once the attorney adds a filter, the list may appear to “lose” attachments if the view is no longer leveraging the Family Group relational context. This is because Relativity filters act on the records in the active view, and related items such as attachments are included through family grouping behavior rather than because every attachment independently satisfies the filter. The Group Identifier field itself is generally what defines the family relationship, and if it were not populated, the issue would be broader and structural, not just something that appears after adding a filter. The Document Extension field being indexed is unrelated to whether attachments display as family members in the document list. Therefore, the most plausible and Relativity-aligned explanation is that the Family Group relational view is no longer selected , which prevents all related email attachments from continuing to display together in the filtered Hot Documents view.

The correct answer is C. Branding queue . Relativity’s official Production queue documentation states that during a production job, Relativity sends a job to the branding queue for stamping redactions, headers, or other image modifications, and any change to the priority of a job in the production queue changes its priority in the branding queue . This is a direct match to the question.

This linkage exists because branding is a dependent production-stage activity. When administrators reprioritize a production job, Relativity keeps the related branding work aligned so that downstream stamping and production preparation happen in the proper order. The other queues listed in the answers are separate queue systems and are not documented as automatically inheriting production queue priority changes. Therefore, from a Productions administration perspective, the queue whose priority is also changed is the Branding queue .

The correct answer is C. Your selection becomes a condition added to the search panel. Relativity’s Pivot and dashboard documentation explains that pie charts support multi-select, typically using Ctrl + Click , and that selecting values from charts filters the document list. Relativity’s Analytics guide further states that when you select values from a chart, a filter condition is set in the Search panel corresponding to your choice . That matches option C most directly.

Option A is not the best answer because the effect is more than a temporary highlight; Relativity applies a filter condition to the active search context. Option B is unsupported by the documentation. Option D is also incorrect because dashboard configurations are not automatically saved as new dashboards merely by interacting with chart segments; dashboards must be explicitly saved by the user. Therefore, when you select multiple pieces of a pie chart, Relativity adds that selection as a condition in the search panel , which then drives the filtered results shown in the document list and related widgets.

The correct answer is B. Run the Set native file size field script. In Relativity, the purpose of the Set native file size field script is to populate a decimal field with the size of each document’s native file. This is the most efficient and direct administrative method when a workspace already contains produced native files and the case team wants a usable field showing file size. Relativity’s documentation states that the script stores the native file size for each document in the workspace in a decimal field, making it specifically aligned to this requirement. It is intended for administrators who need to backfill or populate this metadata after files have already been loaded, rather than relying on manual calculations or unrelated operations.

The other options are not correct. A tally/sum/average mass operation works on values that already exist in fields; it does not inspect native files and write their file sizes into a document field. The Set extracted text size field script applies to extracted text size, not native file size, so it addresses a different metadata requirement. The statement that native file size is automatically populated for documents is also incorrect in this context, because Relativity provides a dedicated script precisely for populating that field when needed. Therefore, from a Relativity Certified Administrator perspective under Data loading , the correct and most efficient administrative action is to run the Set native file size field script.

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

The correct answer is B. Add the OCR text field as the first field in the Text Precedence window. Relativity’s OCR-on-redacted-production guidance explains that to produce only non-redacted text, you must use Text Precedence during export, and it specifically warns not to add the Extracted Text field to the exported field list because doing so can result in producing redacted text. It also explains that production export can use ordered text fields so Relativity pulls text from the highest-priority populated field.

In this workflow, the OCR text generated from the redacted production images is the field that reflects the redacted-visible text appropriately for export. By placing the OCR text field first in Text Precedence, Relativity uses that OCR-derived text before falling back to other long-text fields. Option A is incorrect because prioritizing Extracted Text risks exporting the original underlying text rather than the intended redacted-visible text. Options C and D are also incorrect because the guidance is to control output through Text Precedence , not by simply adding those fields to the exported field list; in fact, Relativity explicitly warns against adding Extracted Text to the exported list for this use case. Therefore, the correct step is to put the OCR text field first in Text Precedence .