RCA Relativity Certified Administrator Questions and Answers

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

The correct answer is C. Extracted text, FileExtension, and FileName. Relativity’s official Simple File Upload documentation includes a Replacing documents section that explicitly lists the metadata fields overwritten when a document is replaced with another document sharing the same control number. The overwritten fields include FileName , FileSize , FileExtension , Extracted Text , Supported By Viewer , Relativity Native Type , Has Native , and certain last-modified system fields.

Among the answer choices, option C is the only one composed entirely of fields that Relativity explicitly says are overwritten in this workflow. Option A is incorrect because Sort Date is not one of the documented overwritten fields. Option B is incorrect because Group Identifier is not listed as being overwritten. Option D is incorrect because Page Count is not listed in the documented overwritten fields for replacing a document via this workflow.

This is an important Data loading administration detail because document replacement changes core file metadata tied to the uploaded replacement native, including its filename and extension, while preserving the document identity through the shared control number. Therefore, the correct option is C. Extracted text, FileExtension, and FileName .

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 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 C. Change the job’s priority to the lowest value in the queue. Relativity’s Branding queue documentation states that only one job runs at a time and the lower numbered job runs first while the higher numbered job runs last. It also explains that you can move jobs by using Change Priority and entering a new integer value. Since lower numbers represent higher queue priority, moving a job to the front means assigning it the lowest priority number among the queued jobs.

This rules out option D, which reverses the queue logic. Changing submitted date/time is not the documented control for moving a branding job forward, and canceling/restarting is unnecessary when Relativity already provides a queue-priority control. Therefore, to move a job to the front of the Branding queue, you change its priority to the lowest value in the queue.

The correct answer is 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 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. #pear . Relativity’s Using dtSearch syntax options documentation states that phonic searching uses the pound sign (#) in front of a word. The documentation gives the exact example that a phonic search for pear also finds pair and pare , which directly matches the question.

The other choices represent different or invalid syntax. pear* is a wildcard-based pattern, not a phonic search. The apostrophe form is not the documented phonic operator, and $pear is not the phonic syntax in Relativity dtSearch. Therefore, the correct syntax for a phonic search returning pair and pare is #pear .

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 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 D. Install the Repository application to the workspace. Relativity’s official repository workspace documentation states that when installed to an existing workspace, the RelativityOne repository workspace application converts the workspace into a streamlined repository workspace for early case assessment and lower-cost storage of data not actively under review. The documentation also provides a dedicated section called Converting a review workspace to a repository workspace , where the conversion steps are simply to access the RelativityOne Repository Workspace application from the Application Library and install the application to the desired workspace .

This makes option D the exact documented conversion method. Option A describes moving data to another repository workspace, which is a different workflow and does not convert the existing workspace itself. Option B involving ARM restore is used in some repository-related workflows, especially around templates or archived workspaces, but it is not the primary documented method for converting an existing workspace. Option C is incorrect because repository mode is not enabled by editing a status field. Relativity also notes that if you convert an existing review workspace by installing the Repository application, the workspace remains classified for billing as a review workspace until the beginning of the next calendar month, which further confirms that application installation is the actual conversion mechanism.

The correct answer is C. Use Integration Points with the Links Only option for natives. Relativity’s repository workspace documentation explicitly says that to take advantage of reduced repository data costs, they strongly recommend promoting sets of documents via links only to standard review workspaces instead of storing duplicates of the files in the review workspace . The repository workflow page describes using Integration Points to move selected documents to the review workspace, and the billing guidance explains that if you promote actual files instead of links only, you incur both repository and review storage charges.

That makes option C the documented best practice. Uninstalling the repository application is actually listed as a condition that can affect repository billing adversely, so option A is incorrect. Exporting and re-importing with Import/Export duplicates the files and defeats the reduced-cost repository workflow. ARM restore is also not the recommended method for promoting data into active review while preserving the repository cost advantages. Therefore, the correct answer is use Integration Points with Links Only for natives .

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 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 D. Add them to an instance-level group with permissions to create groups, manage users, and assign permissions. Relativity’s instance security model allows administrators to assign instance-level permissions to groups through the Admin Security dialog. The documentation explains that permissions can be managed granularly through object security, tab visibility, and admin operations, which means a user can be given specific administrative rights without being made a full system administrator.

This matters because the System Administrators group grants broad access to admin-level permissions and tabs, including queue management. Relativity’s documentation specifically notes that system admins have access to all admin-level capabilities such as queue management, users, and groups tabs . If you do not want the user reviewing Processing or Production queues, giving full System Admin membership is broader than necessary. A workspace admin group is also insufficient for this requirement because creating groups, managing users, and assigning instance-level permissions are administrative functions controlled at the instance level. Therefore, the correct configuration is to place the user in an instance-level group with only the permissions they need.

The correct answer is A. By removing that user's security group from the workspace. In Relativity, workspace access is granted through groups , not by attaching workspace rights directly to individual users. Relativity’s official security documentation explains that you set permissions by adding groups to a workspace and configuring those group permissions there. Users then inherit access through their group memberships. As a result, the standard way to secure a workspace from a user is to remove the group that gives that user access, or remove the user from the relevant group.

The other options do not reflect how Relativity security is structured. User profile settings do not control workspace visibility in the manner described. IP-based security is not the mechanism for ordinary workspace access control in this scenario. Instance-level view security is also too narrow and does not remove the user’s overall workspace access; even if certain views were restricted, the user could still potentially access the workspace through other permitted objects or tabs. From an RCA perspective, this question tests a foundational principle: workspace security is group-based . Administrators grant or revoke access by managing the relationship between groups and workspaces, then managing which users belong to those groups. Therefore, to secure a workspace from a user, the correct action is to remove the user’s access-granting security group from that workspace.

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 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 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. It is the tab that has been set as the default tab. Relativity’s Tabs documentation states that a tab has a Set as Default Tab toggle, and when this is turned on, that tab serves as the workspace’s default tab. Reviewers logging into the workspace are taken to that default tab. Relativity also notes that if a reviewer does not have access to that default tab, the user is directed to the Documents tab instead.

This means the default tab is not determined merely by tab order. The lowest order number affects where a tab appears in the sidebar, but not which tab is designated as the workspace default. The Admin tab and Documents tab are not always the default either; Documents only acts as the fallback if the user lacks access to the selected default tab. Therefore, the correct answer is that the default tab is the one explicitly set as the default tab .