Free Practice Questions for Relativity RCA Exam

The correct answer is D. Name normalization. Relativity’s official Communication Analysis documentation states that you can add the Communication Analysis widget to a dashboard after running name normalization . The widget visualizes communication frequencies, patterns, and networks between entities linked to the documents in the view, and those entities come from the results of name normalization.

This requirement is fundamental because the widget depends on entity and alias relationships generated by structured analytics name normalization. Without those normalized entities, the system does not have the participant relationship structure needed to render communication maps. Relativity also repeats this requirement in its dashboard documentation, again stating that Communication Analysis is available after running the name normalization operation within structured analytics .

The other options are not the prerequisite named by Relativity. A repeated content filter is optional and only used to improve text cleanup. A conceptual analytics index is a different analytics technology entirely. Email threading is a separate structured analytics operation and is not the stated prerequisite for this widget. Therefore, the correct answer is D. Name normalization .

The correct answer is B. Production type. Relativity’s official Production Data Source documentation states that when adding a production data source, one of the fields you configure is Production Type , where you select whether the data source will produce images, natives, or both . This is explicitly part of the production data source setup dialog.

This makes sense because production data sources are used to attach saved searches to a production set and can define how those specific subsets of documents should be produced. Relativity also documents that placeholders can be assigned at the production data source level so that different saved searches in the same production can use different placeholder behavior. However, Production Numbering is defined at the production set level rather than as a field you set when creating the individual production data source. Likewise, Branding text size and Placeholder image format are production-level settings, not the core field identified in the data source setup described by Relativity.

From an RCA standpoint, this distinction matters because administrators configure overall production behavior in the production set, while more granular document-source behavior is controlled on each production data source. Therefore, the correct answer is B. Production type .

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