RCA Exam Dumps - Relativity Certified Administrator

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 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 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 C. Export the production set as PDFs using Import/Export. Relativity’s official Import/Export documentation states that Import/Export is the recommended method for importing and exporting data for RelativityOne , and the production export workflow specifically supports exporting a production set load file with production files. The production export workflow is the documented method for exporting production sets and their associated deliverables in a structured, transferable form.

This makes it the best fit for the question’s requirement: produced PDFs with a corresponding load file . The PDF mass action is a separate document-level utility for creating PDFs from documents, natives, images, or produced documents, but it is not the standard production export workflow for packaging a production with its corresponding load file. Downloading PDFs from the Viewer is a manual review action, not a formal production export workflow. ROSE is used for large-scale data transfer to and from RelativityOne storage, but the product documentation positions Import/Export as the recommended export mechanism for production sets and related load files.

So, from a Productions and RCA workflow perspective, the recommended method is to export the production set as PDFs using Import/Export .

The correct answer is A. 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 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 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. 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 .