RCA Relativity Certified Administrator Questions and Answers

The correct answer is C. The blank values will replace the existing field values. Relativity’s Import/Export document load file import documentation states that for Append/Overlay and Overlay Only , if a blank metadata field exists in the load file, the blank value will overlay remove any existing value in the corresponding mapped field. That means the blank value does not preserve the original value; it clears it.

This rules out the other options. The import does not preserve the old value in the mapped field, so option A is incorrect. The workflow does not error merely because blank values are present, so option B is also incorrect. Option D is wrong because the behavior is not limited to fixed-length text fields; it is described generally for mapped metadata fields in overlay mode. Therefore, the correct answer is that blank values replace existing field values during overlay import.

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. RelativityOne Staging Explorer ROSE . Relativity’s official documentation states that Staging Explorer enables you to rapidly transfer large amounts of data to and from RelativityOne . It is specifically intended for high-volume transfer workflows and can be used to download files from your RelativityOne storage location to a local computer . That wording directly matches the question, making ROSE the exact documented tool for this scenario.

This is why the other options are incorrect. Simple File Download is not the primary enterprise-scale utility Relativity documents for rapid bulk transfer from RelativityOne storage. File Transfer Protocol is a generic technology term, not the RelativityOne tool identified by Relativity documentation for this workflow. Relativity Integration Points RIP is used for moving and integrating data across systems and workspaces, but it is not the official RelativityOne utility described as the mechanism to rapidly move large data volumes between RelativityOne storage and a local machine. Relativity also reinforces ROSE’s suitability for large datasets in its best practices and certification materials, which describe it as the tool for high-volume uploads and downloads in RelativityOne environments. From an RCA perspective, this is an important operational distinction because ROSE is purpose-built for staging and large-scale data movement, making it the correct answer.

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 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 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. Build dtSearch Index . In Relativity, Automated Workflows consists of two major components: triggers and actions . Triggers determine when a workflow starts, while actions determine what task the workflow performs once it begins. Relativity’s official Automated Workflows documentation lists Build dtSearch index as one of the available actions that can be added to a workflow. When selected, this action allows the workflow to automatically build a dtSearch index, either as a full build or incrementally depending on the configuration.

The other options are not actions. Scheduled Run and Manual Start are both documented by Relativity as trigger types , not actions. Scheduled Run starts a workflow on a defined daily, weekly, or hourly cadence, while Manual Start allows a user to launch the workflow by clicking the Manual Run button. Build a cluster is also not listed by Relativity as an Automated Workflows action. From an RCA perspective, it is important to distinguish triggers from actions because workflow design depends on choosing the correct combination of each. Administrators may configure a trigger such as Scheduled Run or Manual Start, and then assign one or more actions such as Run OCR Set, Run Imaging Set, Build Elasticsearch index, or Build dtSearch index . Therefore, among the options provided, the only valid available action is Build dtSearch Index .

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 .

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 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 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. 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 D. MM/DD/YYYY and HH:MM:SS AM/PM. Relativity’s Import/Export documentation states that the Regional Settings (Date and Time) value for document load file import reverts to the US date and time by default when browser cache is cleared. The documentation does not spell out the example string on that exact import page, but across Relativity documentation, the default U.S. date convention is month/day/year , and related Relativity guidance commonly shows U.S.-style date-time strings using AM/PM with seconds for import-oriented parsing examples. This makes MM/DD/YYYY and HH:MM:SS AM/PM the best-supported answer from the available choices.

Options A and B are not U.S. default ordering, so they do not fit the documented “US date and time” default. Option C has the correct U.S. month/day/year structure but omits seconds. Based on Relativity’s broader documentation examples for imported date-time strings and supported parsing formats, the version including seconds is the stronger match among the provided options. This answer involves a small inference from the documented U.S. default plus the product’s date-time examples, because the exact multiple-choice wording is more specific than the import page itself.

The correct answer is D. Replace produced images with a placeholder. Relativity’s official Re-production documentation lists supported and unsupported re-production types. Among the supported types, Relativity explicitly includes Replace produced images with placeholder (I-P) .

The same documentation also explicitly lists several unsupported types that correspond to the incorrect options in this question. Relativity states that replacing a document that was produced as native only with produced images or a placeholder is unsupported, which rules out option B. It also states that replacing a document that was produced as a placeholder with another placeholder is unsupported, which rules out option C. Option A is likewise unsupported because “replace produced images with a native” is not identified as a supported re-production type. Instead, Relativity supports image-to-placeholder, placeholder-to-images, and re-producing documents with the same number of pages.

This distinction matters because re-production is tightly controlled to preserve numbering integrity and production consistency. For example, when replacing produced images with placeholders, Relativity preserves the original Bates numbering while substituting placeholder pages. From an RCA production-administration perspective, the supported operation among the listed choices is clearly Replace produced images with a placeholder . Therefore, the correct answer is D .

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 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 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 C . Relativity’s official Name Normalization documentation explains that the process parses the email headers —specifically From, To, Cc, and Bcc —to identify aliases. It does not create aliases from every casual name reference appearing in the email body. Relativity further states that when an alias appears in the format "Doe, John" john.doe@example.com , Name Normalization stores three aliases: the full alias , the description/name portion , and the email address portion . Applying that exact documented rule here means the From value "Lin, David" David.Lin@example.com yields three aliases: "Lin, David" David.Lin@example.com , "Lin, David" , and David.Lin@example.com . The To header contributes Ali.Devi@example.com .

Relativity also explicitly notes that generic aliases such as simple first names are not created in order to avoid over-merging. In addition, the alias-identification process is driven by the parsed header sections , not by every name or email string appearing in the message body. That means items such as Ali , Skylar , Rush Jones , rjones@domain.com , and Dave Lin are not the correct header-derived aliases for this example. The body text may help Relativity with segment matching in some contexts, but the direct alias list in this question comes from the email headers. Therefore, the correct identified aliases are the four listed in option C .

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.