RCA Relativity Certified Administrator Questions and Answers

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. Check the box to export multiple-choice fields as nested. Relativity’s official export documentation states that Export Multiple Choice Fields as Nested is the option used to maintain the hierarchy of Relativity multiple-choice lists during export. It further explains that the nested value delimiter is a backslash, which preserves the parent-child structure of those choices in the exported data.

This means the hierarchy is not lost by default if the appropriate export option is selected, so option A is incorrect. Sorting on the field does not preserve the nested hierarchy, making option B wrong. Exporting as CSV for Excel recognition is also not the documented mechanism, so option C is incorrect. From an RCA and data loading standpoint, this setting matters because exported hierarchical values often need to be re-used downstream, re-imported, or validated in a way that preserves their original structure. Without the nested export option, the relationship between parent and child values may not be represented correctly. Therefore, the proper way to maintain multiple-choice hierarchy when exporting a saved search through Import/Export is to check the box to export multiple-choice fields as nested .

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 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. NOT magazine AND apple . Relativity’s dtSearch syntax documentation confirms that dtSearch supports the Boolean operators AND, OR, and NOT and uses them to connect multiple terms in a single search expression. To return only documents that contain apple while excluding those that contain magazine , the query must require the presence of apple and exclude magazine in the same Boolean expression. Option A does exactly that.

Option B is not correct because Apple NOT magazine is missing the required Boolean connector before NOT . Relativity’s dtSearch guidance and related syntax behavior show that NOT is used as part of a Boolean expression, not as a standalone middle operator without AND or OR. Option C is incorrect because Apple OR NOT magazine would broaden the result set too much, potentially returning documents that do not contain apple at all. Option D is also incorrect because it excludes apple instead of requiring it. Therefore, the valid dtSearch string that successfully returns documents containing apple but not magazine is NOT magazine AND apple .

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 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 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. Files must be generated using the RSMF specifications before they are imported into Relativity. Relativity’s official Short Message Format documentation explains that to use the Short Message Viewer, you first need to create an RSMF file, and the example/specification pages describe the required structure and header information that must be present before ingestion using Processing. Relativity also states that Processing is the recommended method of importing RSMF files into Relativity, which means the RSMF file already exists when Processing begins.

This rules out the other options. Relativity does not say that it automatically creates RSMF on-the-fly for all non-document data. It also does not describe a processing-profile feature that converts arbitrary XML from chat platforms into RSMF during import. Nor is there a document-list mass operation that converts conversations into RSMF. Instead, RSMF is a defined external format that must be constructed according to Relativity’s published specifications, then imported and processed to preserve message metadata, attachments, and near-native review behavior. Therefore, the correct answer is C.

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 B. Save as PDF. Relativity’s imaging documentation states that the Password Bank is used to decrypt certain password-protected files during processing and imaging workflows. It also explicitly states that Save as PDF does not integrate with the Password Bank and that if you select Save as PDF when imaging a password-protected native document, an error occurs .

This directly differentiates Save as PDF from the other options. Processing supports password decryption through the Password Bank. Mass Image and Imaging Sets also work with the Password Bank, allowing protected files to be imaged if the correct password is available in the bank. Because Save as PDF does not use that mechanism, it fails where the other imaging-related workflows can succeed.

From a case administration perspective, this is a practical operational detail. Password-protected content often needs special handling, and administrators need to know which tools integrate with Relativity’s decryption workflow. The one that does not work for this purpose is Save as PDF .

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

The correct answer is D. Remove key terms from the dtSearch index noise words. Relativity’s dtSearch documentation explains that if a word in the search phrase is part of the noise words list, and that word is important to the search, you must remove it from the dtSearch noise words list and then rebuild the index. The documentation gives this exact type of guidance for terms like “and” when the term must be treated as part of the actual phrase instead of being ignored.

This makes options B and C incorrect because changing or deleting the attorney’s search terms would alter the intended search logic rather than making the index capable of respecting the requested phrase. Option A is also incorrect because the alphabet file is for searchable characters and tokenization behavior, not for managing ignored noise words. Therefore, before running the Search Terms Report, the correct step is to remove those key terms from the dtSearch index noise words list and rebuild the index if needed.

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 A. The field mapping section is disabled because only the control number is needed. Relativity’s official Integration Points documentation for promoting data between workspaces states that when you select Copy Images , the field mapping section is disabled because only the control number is required and available in this scenario . It further notes that if you want to transfer other field metadata, you must create a separate integration point without choosing to copy images.

That directly rules out the other options. Relativity does not state that the native file must be included to transfer images in this scenario. It also specifically notes that you are not required to have Integration Points installed on the destination workspace , so option C is incorrect. Option D is wrong because metadata is not automatically mapped and migrated in the Copy Images path; in fact, field mapping is disabled in that configuration.

From an RCA and data-movement perspective, this is a common distinction: image promotion through Integration Points is streamlined and relies on control number matching , not standard metadata field mapping. Therefore, the true statement is A .

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. 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 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 C. Document - Edit. Relativity’s workspace security documentation explicitly states: Use the document Edit permission to tag documents with workspace coding values using layouts. Deciding whether a document is privileged is a coding decision made on the document, typically through a coding layout and fields such as Privileged or Privilege Designation. That activity requires the ability to edit document-level coding values, which is exactly what Document - Edit provides.

The other permissions serve different purposes. Layout - Edit is for editing the layout object itself, not for making coding calls on documents. Field - Edit is for editing field properties and administration, not for reviewers coding documents. Relativity even warns not to assign coding users rights to edit fields or layouts when what they really need is to code documents. Document - Local Access is tied to actions like opening natives in their native applications, downloading, or copying text, not making privilege determinations. Therefore, from an RCA permissions standpoint, the correct permission to let users decide whether a document is privileged is Document - Edit.

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 .