Relativity RCA Relativity Certified Administrator Exam Practice Test

The correct answer is D. When you save a group of documents to a single PDF, the documents retain the sort order in which they appear in the document list. Relativity’s Mass PDF documentation explicitly states that when you Mass Save as PDF a group of documents, the documents retain their sort order based on the order in which they appear within your document list . This is a direct match to option D.

The other options are contradicted by the same documentation. Option A is incorrect because when saving as a ZIP or PDF portfolio, Relativity gives multiple naming choices: control number , control number plus a field , or just a field . So the individual PDFs are not automatically limited to control number only. Option B is incorrect because the documentation states that the ZIP or portfolio container itself is always named result.[extension] , meaning you do not choose the ZIP file name in that workflow. Option C is also wrong because Relativity imposes a file-name length limit and states that if the file name exceeds 251 characters , the system truncates it.

From an RCA perspective, this is a practical operational detail for export preparation and downstream organization of PDFs. The documented true statement is that the resulting PDF preserves the current document-list ordering. Therefore, the correct answer is D .

The correct answer is A. The field to use for production numbering. Relativity’s documentation distinguishes between production set settings and production data source settings . The production set defines overarching settings such as document numbering , appearance of numbering, and related production-wide behaviors. By contrast, the production data source page includes settings such as production type , placeholder image format , burn redactions , burn native redactions , burn PDF redactions , and markup set .

This means the field used for production numbering is not configured at the individual data source level; it belongs to the production set itself. The other options are all part of production data source configuration. The documentation explicitly shows Burn Redactions and Markup Set , and placeholder behavior is also configured within the production data source settings.

Therefore, the option that cannot be configured when creating a new production data source is the field to use for production numbering , because that is a production-set-level setting rather than a data-source-level one.

The correct answer is A. Ignore Numbers. Relativity’s near duplicate documentation explains that when Ignore Numbers is set to true, the similarity calculation considers only tokens beginning with letters, which means numbers are excluded from the similarity percentage calculation. That is directly relevant for invoice populations, because many invoices share nearly identical wording while differing mainly by dates, invoice numbers, quantities, or amounts. In a set like the one described, toggling Ignore Numbers is the setting most likely to change how those documents are grouped and help you assess whether the current near duplicate results can be improved.

The other options do not fit this use case. MD5Hash Verifier is related to hash-based duplicate validation rather than textual near duplicate tuning. Relativity Compare is a review tool for examining differences after grouping, not a setting that changes how the grouping is calculated. Auto-recognize Dates is not the structured analytics tuning option documented for this scenario. Therefore, for invoice-heavy data where numerical differences are driving questionable textual near duplicate results, the correct setting to toggle is Ignore Numbers.

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. Regular expression filter. Relativity’s Structured Analytics documentation states that a Regular expression filter can be linked to a structured analytics set as an optional setting, and that it is used to clean up extracted text before analysis . The documentation further explains that this setting is implemented through a repeated content filter whose type must be Regular Expression . This directly matches the question’s wording about excluding document text before analytics processing begins.

This capability is especially useful when documents contain extraneous content such as dates, URLs, page numbers, Bates numbers, standard disclaimers, or other repeated text that can interfere with email threading or textual near duplicate results. Relativity notes that the filter applies only to the field being analyzed, which is usually Extracted Text unless another field is selected. By removing this noise before the algorithm runs, administrators can improve the quality of structured analytics outcomes.

The other options are not the correct named filter for this function in Relativity’s structured analytics workflow. The official setting is specifically the Regular expression filter . Therefore, the correct answer is D .

The correct answer is C . Relativity’s official production staging documentation states that a staging error occurs when the same document is found in multiple data sources within the same production set. When this happens, Relativity generates an error message identifying the data sources that pulled back the same document and which specific document is duplicated. The documented resolution is to modify the saved searches used as data sources so they no longer return the same document.

This means staging does not simply ignore the duplicate, nor does it produce the document twice or proceed using the first data source’s settings. The duplicate condition is treated as a production-stopping issue that must be corrected before the production can successfully continue. From an RCA perspective, this is a core Productions concept because it affects production QC and data-source design. Administrators should ensure that saved searches used as production data sources are mutually exclusive when necessary, especially if different branding, numbering, or production settings apply. During staging, Relativity is validating the integrity of the production inputs, and duplicate documents across data sources are explicitly flagged as errors. Therefore, the correct interpretation is that an error message appears during staging and the production cannot proceed until the duplicate documents are removed from overlapping data sources .

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 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. 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 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. 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 C. RIP must be installed in the source workspace. Relativity’s Integration Points documentation states that to use Integration Points successfully, you must install the application to at least one workspace . In the specific context of promoting data between workspaces, Relativity also states that you are not required to have Integration Points installed on the destination workspace . That means the practical prerequisite is installation in the source workspace , not both source and destination.

This rules out the other choices. Integration Points is not described as an instance-level-only install requirement, so option A is incorrect. Option B is too broad because the destination workspace installation is explicitly not required. Option D is also incorrect because Integration Points is an application that must be installed in a workspace to be used. Therefore, for migrating documents from one workspace to another with RIP, the required prerequisite is that Integration Points be installed in the source workspace .

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 D. Fixed length text . Relativity’s Mass PDF documentation states that when saving PDFs as a ZIP or PDF portfolio , you can choose to name the individual PDFs using the control number , the control number plus a field , or just a field . In other words, Relativity supports file naming from a document field value. The same documentation also notes that long names are truncated if they exceed the allowed length, which confirms that the chosen field value is being used directly as part of the resulting file name.

Among the answer choices, fixed length text is the best and most appropriate field type for this purpose. A fixed length text field is designed to store concise string values that work well as filenames. Artifact ID is not a field type in this context, but rather a system identifier. Date fields can exist, but they are not the standard answer for naming PDFs in an exam question framed around field type suitability. Single choice stores coded values and is not the expected best answer here. This question appears to test practical Relativity administration knowledge rather than every technically possible field serialization outcome. Since Mass PDF naming relies on a field value and file names are most appropriately based on text metadata, the correct exam-aligned answer is fixed length text . The Relativity documentation supports the field-based naming capability, and the selection of fixed length text is the most reasonable administrative interpretation from the provided options.

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. 100 . According to Relativity’s official Simple File Upload documentation, the SFUMaxFilesToUpload instance setting determines the maximum number of documents a user can upload at one time using Simple File Upload. Relativity states that administrators can configure this setting up to 100 files , and when the setting is at its maximum, users can upload up to 100 files at one time . If a user selects more than 100 files, Relativity uploads only the first 100 selected files and does not upload the remainder. Relativity also indicates that a warning message appears in the upload window when more than 100 files are selected.

This makes the answer operationally important for administrators because Simple File Upload is designed for lightweight, direct document uploads within a workspace, not for large-scale ingestion jobs. For more substantial data loading exercises, administrators typically use Relativity’s broader import workflows rather than relying on Simple File Upload. From an RCA perspective, knowing this limit helps with user support, upload troubleshooting, and setting expectations for workspace users who need to add small batches of documents quickly. Therefore, among the options given, 100 is the only choice that aligns with the official Relativity behavior for Simple File Upload.

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 .

The correct answer is C. The email and other parent emails in the thread are coded differently. Relativity’s Email thread visualization documentation explains the meaning of the visual warning icons used in the thread display. The red exclamation point is associated with a coding mismatch condition in the thread. In practice, this means related parent emails in the thread have been coded inconsistently, which is exactly the kind of review inconsistency ETV is designed to expose.

This is different from missing attachments, duplicate spare comparison, or a generic “Needs Review” state. ETV is focused on surfacing thread relationships, inclusiveness, missing emails, and coding consistency across the email conversation. From a Structured Analytics standpoint, the red exclamation point is a QC indicator that reviewers should inspect the thread because coding decisions across parent emails do not align. Therefore, the correct answer is C .

The correct answer is C. The name of the file. Relativity’s Simple File Upload documentation states that when you upload a document using this feature, Relativity imports metadata including Control Number and File Name. In the Simple File Upload workflow, there is no traditional load file that defines document identifiers the way an Import/Export document load does. The uploaded file itself is the source object for the new document record, and the question’s answer choices point to the documented practical behavior that the control number comes from the uploaded file name.

The other options do not align with the Simple File Upload model. ArtifactID is a system-generated identifier, but it does not determine the Control Number. There is no document load file in this workflow, so option B is incorrect. Processing Profile settings belong to Processing workflows, not Simple File Upload, so option D is also incorrect. Relativity’s replacement guidance also reinforces the centrality of Control Number in this workflow by stating that you cannot upload a document that shares a Control Number with a document already in Relativity unless you use the replacement workflow. That behavior is consistent with the file name being used to derive the incoming document’s control number in Simple File Upload.

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 A. Relativity Compare . Relativity’s official documentation on using near duplicate analysis in review states that the Relativity Compare function can compare two documents to assess their similarities and differences . This is the exact activity described in the question and is directly relevant to working within a textual near duplicate group, where reviewers often need to determine how one member differs from the principal document or from another near duplicate in the set.

The other options do not match that purpose. Image QC is used for image quality control workflows, not for textual comparison of document content. Document View Overlay is not the standard Relativity tool documented for assessing textual differences between near duplicates. Similar Documents View helps surface conceptually or textually related material, but it is not the dedicated side-by-side comparison tool Relativity identifies for evaluating differences. From a Structured Analytics perspective, this distinction matters because near duplicate analysis groups similar records together, but the actual determination of differences between two specific documents is handled through the comparison function. Therefore, when assessing differences within a textual near duplicate group, the correct tool is Relativity Compare .

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 D. NOT . Relativity’s Filters documentation for text box filters lists the valid operators as AND, OR, IS SET, IS NOT SET, BETWEEN, =, > =, and < = . Since NOT does not appear in that valid operator list, it is the invalid choice among the options provided.

This is a useful distinction because Relativity supports NOT in some other search contexts, such as dtSearch or advanced filtering patterns, but the question asks specifically about a text box filter operator. In that exact context, AND , IS SET , and > = are valid, while NOT is not. Therefore, the invalid operator for a text box filter is NOT .

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 .