RCA Relativity Certified Administrator Questions and Answers

The correct answer is B. Turn on Date Recognition before building the dtSearch index. Relativity’s Searching Guide explains that date recognition must be activated before it can be used in the workspace. It also states that dtSearch recognizes valid date formats common in both the US and UK , including DD/MM/YY and DD/MM/YYYY formats. That means UK dates are supported, but the index must be configured with Date Recognition enabled in order to take advantage of date searching behavior.

This rules out option D because UK date formats are explicitly supported. Option C is incorrect because adding the slash character to the alphabet file is not the documented preparation step for date searching. Option A is unrelated to dtSearch date-recognition configuration. From an RCA perspective, the important point is that dtSearch can recognize UK-style numeric dates, but only if Date Recognition is enabled before the relevant index build. Therefore, the correct answer is B .

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 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 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 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 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 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 B . Relativity’s official production console documentation explains that Stage Production and Stage and Run Production both take a snapshot of the data sources for the production. The staging step captures the current contents of those data sources so the production job runs against a fixed set of documents. Relativity also documents that staging errors occur if the same document is found in multiple data sources , which means duplicate-document checking is part of what administrators must evaluate during the staging phase.

The other options describe different production activities. Showing a sample image of branding is associated with Preview Production , not staging. Bates numbers are assigned later as part of the production run, not during the initial staging snapshot. The option about conflict checking against a Production Restriction saved search is not the best description of the staging step itself according to the official documentation. For RCA exam purposes, the key concept is that staging freezes the production inputs and surfaces structural issues, especially duplicate documents across data sources, before the full production run proceeds. This is an important quality-control checkpoint because it helps administrators verify that the right documents and data-source configuration are in place before branding, numbering, and export occur. Therefore, the best answer is that during staging, Relativity takes a snapshot of the data sources and checks for duplicate documents between data sources .

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 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 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 B. Run the Set native file size field script. In Relativity, the purpose of the Set native file size field script is to populate a decimal field with the size of each document’s native file. This is the most efficient and direct administrative method when a workspace already contains produced native files and the case team wants a usable field showing file size. Relativity’s documentation states that the script stores the native file size for each document in the workspace in a decimal field, making it specifically aligned to this requirement. It is intended for administrators who need to backfill or populate this metadata after files have already been loaded, rather than relying on manual calculations or unrelated operations.

The other options are not correct. A tally/sum/average mass operation works on values that already exist in fields; it does not inspect native files and write their file sizes into a document field. The Set extracted text size field script applies to extracted text size, not native file size, so it addresses a different metadata requirement. The statement that native file size is automatically populated for documents is also incorrect in this context, because Relativity provides a dedicated script precisely for populating that field when needed. Therefore, from a Relativity Certified Administrator perspective under Data loading , the correct and most efficient administrative action is to run the Set native file size field script.

The correct answer is A. 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 B. Runs the saved search and trains the classifier. Relativity’s Review Center documentation states that during the Preparing state, the queue is refreshing the saved search for the first time , and for a prioritized review queue , this also trains the classifier . The Review Center admin quick reference guide further states that Prepare Only re-runs the saved search for all queues and retrains the AI classifier for prioritized review queues , and it does not start the queue.

That makes option B the direct documented effect of Prepare Only. It does not grant reviewer access by itself, it does not release checked-out documents, and it is not a statistical sampling action. From a case administration perspective, Prepare Only is used to get the queue ready and refresh the machine-learning state before reviewers begin or resume work. Therefore, the correct answer is B .

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 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. 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 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. Replace entire field . Relativity’s Mass Replace documentation lists the available Action options for Mass Replace. These include Replace Entire Field , Append to End , Insert at Beginning , and Search For . Since Replace Entire Field is explicitly named by Relativity as one of the supported Mass Replace actions, it is the correct answer.

The other options are not valid as written. Relativity uses Append to End and Insert at Beginning , not “Insert after.” “Rename field” is a field-administration task, not a Mass Replace action. “Search for sentiment” is unrelated to Mass Replace and not part of the operation’s feature set. This question tests familiarity with the exact Mass Replace UI choices. Therefore, the correct available option is Replace entire field .

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 C. The fields returned by the Searchable Set saved search are all empty for this document. Relativity documents that dtSearch indexes are built against a Searchable Set, and administrators must manually update those indexes when the underlying document search sets change. Relativity also describes dtSearch as indexing the content made available through the configured search/index setup rather than magically finding text that is not present in the indexed fields. If the document is part of the saved search but the fields being indexed for that document are empty, there is effectively no searchable text for dtSearch to return for that record.

Option B is not the best answer because an incremental build is a maintenance activity for adding new documents, not the documented reason a single already-known document cannot be found. Relativity notes that incremental builds look for new documents in the searchable set and do not re-index previously indexed records with changed content, which is a different issue. Option D is unrelated because Review Center queue assignment does not control whether a document is searchable through a dtSearch index. Option A is also not the best explanation for this question; dtSearch availability is driven by index/searchable-set configuration and accessible indexed text, not by parent-email folder access in the way the option suggests. So the best RCA-aligned answer is that the document has no indexed searchable content in the fields returned by the searchable set.