Practice Free RCA Relativity Certified Administrator Exam Questions Answers With Explanation

The correct answer is D. Existing production numbering . Relativity’s official production set documentation states that Existing production numbering should be selected when you want to re-use the Bates numbering fields from a previously run production set . This is the exact numbering option designed for scenarios where documents are being reproduced but must retain the same Bates values from an earlier production. Relativity further explains that this option is appropriate when you need to change the produced images, produce only a subset of documents from the existing production, or otherwise reissue the same produced documents while preserving the prior numbering.

This aligns directly with re-production workflows. Relativity’s re-production documentation also notes that re-production jobs reuse the numbering format and Bates numbers from the original productions , reinforcing that the platform supports maintaining the original numbering scheme instead of assigning new Bates values. That is critical in litigation workflows where Bates continuity must be preserved for references in correspondence, court filings, and prior productions. The other options do not fit this requirement. Page level numbering and document field numbering generate or rely on other numbering methods, while original image numbering is not the production numbering choice used for preserving prior Bates values in a re-production. Therefore, when reproducing documents and keeping the same Bates numbering, the correct production numbering method is Existing production numbering .

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. Copy from Previous on the layout. Relativity’s Copy from Previous documentation explains that you enable this behavior on specific layout fields by setting Enable Copy from Previous to Yes . During review, after saving one document and moving to the next, users can copy the prior document’s coding values into the current document for those enabled fields. That directly matches the scenario of carrying Responsiveness tagging from one document to the next.

The other options do not provide that reviewer-interface behavior. Mass Copy is a separate bulk operation and not the per-document review workflow described here. Propagation is a different concept and is not the setting used to let reviewers carry coding values forward document by document. Document Local Access controls access-related actions, not coding carry-forward. Therefore, to let reviewers apply Responsiveness tagging from one document to the next, you enable Copy from Previous on the layout field.

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 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 A. Everyone . Relativity’s official instance security documentation states that all users in any instance of Relativity are members of the Everyone group . This means that when a user account is created, that user is automatically part of the built-in Everyone group, even before any additional group assignments are made.

This is an important distinction because Relativity also documents that users are then manually added to other groups for operational permissions and workspace access. The Users documentation explains that you create users and then add them to groups, which are associated with workspaces. That confirms that while administrators normally assign users to functional groups after creation, the system-wide Everyone group already applies automatically.

The other options are incorrect. All Users is not the Relativity built-in group name documented by Relativity. Users are not automatically added to a group is false because the Everyone group membership exists by default. Domain Users is a Windows or directory-services style concept, not the Relativity group referenced in the platform’s own security model. For RCA purposes, this matters because the Everyone group has baseline, environment-level significance and certain permissions are managed with that universal membership in mind. Therefore, the correct answer is Everyone .

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

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 C. You cannot use Audit to revert coding decisions on required fields back to a null state. Relativity’s official Audit documentation states that certain field types, including single choice , can be reverted. However, it also explicitly states that you cannot revert a required field if doing so would return that field to a blank null value . That is exactly what this scenario describes: the field was changed from null to Responsive, and reverting would restore it to null. If the field is required, Relativity blocks that revert because required fields cannot be blank.

This means option A is incorrect because single-choice fields can be reverted in Audit. Option B is also incorrect because Relativity supports both individual and mass revert workflows depending on the situation. Option D is not the documented reason for the failure. The controlling issue is the required-field constraint. From an RCA perspective, this is a subtle but important administrative behavior: the Audit system can revert field changes, but only where the resulting value remains valid under Relativity’s field rules. If the revert would violate a field’s required setting, the system will not allow it. Therefore, the most accurate reason is that Audit cannot revert the value because the revert would place a required field back into a null state .

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. Artifact ID. Relativity’s official Production Sets documentation states that in the Sorting section of a production, if no custom sort criteria are selected, the default sort order is Artifact ID , which Relativity describes as the load order of the documents. This is the platform’s documented default for productions.

This is an important administrative detail because production sort order affects how documents are sequenced when a production is generated. Relativity also notes that when you apply a custom sort order, family groups are not kept together automatically , so administrators need to design sort strategies carefully if they want a specific production sequence. But absent any special configuration, Relativity defaults to Artifact ID.

The other options are not the documented default. Family group may be relevant in review workflows, but not as the production default sort order. Control number is also not the starting sort value because control numbers may be assigned independently of the production sort configuration. Custodian is a common field for review and QC, but again not the production default. Therefore, the correct answer is A. Artifact ID .

The correct answer is D. Saved Search import. Relativity’s official Import/Export workflow overview states that Import/Export supports unprocessed raw native files , document load files , image load files , production load files , and Relativity Dynamic Objects for import. On the export side, it supports folders , production sets , saved searches , and RDO files . In other words, saved searches are export workflows, not import workflows .

That distinction is important for RCA-level administration because Import/Export is organized around specific import and export pathways. A Saved Search import is not listed as a supported workflow because a saved search is a Relativity object used to define document criteria inside a workspace, not a standard external load-file-based content import. By contrast, document load file import and image load file import are explicitly supported workflows, and Relativity also supports unstructured data import for processing.

Therefore, among the options given, the unsupported Import/Export workflow is Saved Search import . This is consistent with Relativity’s current documentation, which shows Saved Search only under export workflows.

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 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 A. Relativity. Relativity’s Processing throughput guidance states that internal performance testing has shown the Relativity text extraction method to be at least two times faster than the native method on Excel, Word, and PowerPoint file types, and also less error-prone than native extraction. Since the question asks for the best method to get a large Excel-only data set to review as quickly as possible, the documented speed advantage makes Relativity the best answer.

The native-based methods are slower according to that same documentation, even though they may have other use cases. The processing profile documentation also shows that native/failover combinations are available configurations, but the performance guidance specifically favors the Relativity extraction method for speed on Excel files. “Extract and place inline” is not the documented Excel text extraction method choice for this question. Therefore, the fastest and most review-efficient choice for large Excel files is Relativity.

The correct answer is B. dog not cat. Relativity’s dtSearch syntax guidance explains that the NOT operator can be used by itself at the beginning of an expression, or in the middle of an expression only when combined with either AND or OR. Relativity gives examples such as apple OR NOT pear and applesauce and NOT pear as valid syntax. That means expressions like dog OR NOT cat and dog AND NOT cat are valid, while dog NOT cat is missing the required connector and therefore causes a syntax problem.

Relativity’s Search Terms Report error documentation further explains that STRs surface syntax errors when the search index cannot process the term because of invalid syntax. In this case, dog not cat violates the dtSearch operator rule, so it is the option most clearly expected to fail with a syntax error in a search terms report. Option A is a standard Boolean expression and is valid. Options C and D both include the required connector before NOT, which matches Relativity’s documented dtSearch usage. Therefore, among the listed queries, dog not cat is the one that would cause a syntax error on an STR.

The correct answer is C. Speaker . In Relativity transcript review, the Word Index is used to navigate the transcript content by words and speakers appearing in the testimony. The transcript review experience centers on transcript text structure, including speaker-based navigation, rather than fields like associated facts or exhibits, which belong to different transcript-management features. Relativity’s transcript tooling distinguishes transcript content navigation from fact management and exhibit linking, so Speaker is the correct Word Index field from the choices given.

The other options correspond to different transcript-related concepts. Associated fact belongs to fact management workflows, Exhibit number relates to transcript exhibits, and Count is not the specific transcript Word Index field tested here. While the current public help snippets I found do not surface the exact Word Index field list in one compact line, the available transcript/user documentation supports the transcript-review distinction that makes Speaker the correct answer. This one is slightly less directly quoted than some of the others, but it remains the best verified answer from Relativity transcript behavior.