RCA Relativity Certified Administrator Question and Answers

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 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. Set the image size. Relativity’s Imaging Profiles documentation distinguishes between Basic Imaging Engine Options and Native Imaging Engine Options . Under the Basic Imaging Engine Options , Relativity explicitly lists Basic Image Size as a configurable setting, with options such as Original setting, Letter, A4, Legal, and Custom. That means image size is directly configurable when using the basic imaging engine.

The other options belong to the native imaging engine rather than the basic imaging engine. Maximum pages imaged per file is listed under Native Imaging Engine Options . Presentation orientation and spreadsheet print-area settings are also documented under native-file-specific options, not the basic engine. So, among the choices provided, the feature available through the basic imaging engine options is the ability to set the image size .

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 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. 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 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 C. The video must be synced to one .MP4 video and uploaded at the same time. Relativity’s official Transcripts application documentation explicitly states that the video can be played in the Viewer in sync with the text of the transcript, and further notes: you must import videos at the same time you are uploading transcripts or the video and transcript cannot sync . The documentation also describes uploading the video as an .mp4 alongside the transcript during the transcript upload workflow.

This directly eliminates the other options. Option A is false because Relativity clearly supports synced transcript video playback. Option B is wrong because this is not a PST-based workflow. Option D is also incorrect because the documentation does not describe a later mass action that separately syncs already uploaded video and text files; instead, the sync relationship is established during the same upload process. Relativity even distinguishes that videos are not stored as normal documents in the document list, but rather as a file field within a transcript, reinforcing that the transcript upload workflow is the correct path.

From a case administration standpoint, this is important because transcript/video synchronization affects deposition and interview review usability. To ensure successful synchronization, the transcript and its associated .mp4 video must be uploaded together. Therefore, the correct answer is C .

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. Building a search terms report. Relativity’s Search Terms Report documentation requires you to define report information including a Searchable Set, which is a saved search containing the documents to be evaluated by the STR. Relativity’s guidance for using STRs also states that you should define a saved search that returns the required document population for the searchable set. That makes a saved search a required component of building a search terms report.

The other options do not inherently require a saved search. A keyword search can be run directly in the search panel. A dashboard can be created without requiring a saved search as its core prerequisite. A persistent highlight set is commonly used with STR output, but the question asks which action itself requires a saved search, and the STR workflow is the one explicitly documented to require one. Therefore, the correct answer is Building a search terms report.

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 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 D. Use the Tally/Sum/Average mass operation on the Relativity Image Count field. Relativity’s Tally/sum/average documentation says this mass operation is commonly used to determine the number of pages in a print job or production. Relativity also specifically documents, in related guidance, that to estimate project size you can use Tally/sum/average on the Relativity Image Count field.

This makes it the fastest and most direct built-in method for obtaining an image count estimate. The other options are less efficient or are not the documented workflow for quickly producing a total image count. Therefore, the correct answer is to use Tally/Sum/Average on the Relativity Image Count field.

The correct answer is A. Document - Update . Relativity’s official Audit documentation states that system admins can revert coding decisions from the Audit list, and that this action applies to the latest Document Update , Mass Update , or Propagate action on the Document object. That makes Document - Update the correct revertable action among the choices provided.

The other options are not listed by Relativity as revertable audit actions in this context. A Field - Update concerns the field object itself rather than a document coding decision. Entity - Merge may create audit records, but Relativity does not list it as an action that can be reverted through the Audit revert feature. Redaction - Update is also not one of the documented revertable audit actions under the Audit tab’s revert capability. From an RCA perspective, this distinction matters because Audit revert is narrowly scoped to specific document-level update actions and certain supported field types. Therefore, the correct answer is Document - Update .

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. 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 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 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. "Queue Refresh" must be set to "On". Relativity’s Review Center admin documentation states that Queue Refresh controls whether the queue automatically refreshes after coding activity . For prioritized review queues, that refresh includes re-running the saved search, checking for outside-coded documents, retraining the classifier, and re-ranking documents based on the latest coding. That makes Queue Refresh the setting required for automatic queue refreshing.

Relativity also documents that prioritized review queues auto-refresh when there has been a 20% change in total coded documents, and additionally after 8 hours if there has been coding activity. Those are auto-refresh conditions, but they do not replace the need for the Queue Refresh setting itself. Option B therefore describes a trigger condition, not the required setting. Options C and D are not documented as the needed configuration for automatic refresh. Therefore, the correct answer is that Queue Refresh must be turned on .

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