Free Relativity RCA Practice Exam with Questions & Answers | Set: 2

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 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 C. Your selection becomes a condition added to the search panel. Relativity’s Pivot and dashboard documentation explains that pie charts support multi-select, typically using Ctrl + Click , and that selecting values from charts filters the document list. Relativity’s Analytics guide further states that when you select values from a chart, a filter condition is set in the Search panel corresponding to your choice . That matches option C most directly.

Option A is not the best answer because the effect is more than a temporary highlight; Relativity applies a filter condition to the active search context. Option B is unsupported by the documentation. Option D is also incorrect because dashboard configurations are not automatically saved as new dashboards merely by interacting with chart segments; dashboards must be explicitly saved by the user. Therefore, when you select multiple pieces of a pie chart, Relativity adds that selection as a condition in the search panel , which then drives the filtered results shown in the document list and related widgets.

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 D. Remove key terms from the dtSearch index noise words. Relativity’s dtSearch documentation explains that if a word in the search phrase is part of the noise words list, and that word is important to the search, you must remove it from the dtSearch noise words list and then rebuild the index. The documentation gives this exact type of guidance for terms like “and” when the term must be treated as part of the actual phrase instead of being ignored.

This makes options B and C incorrect because changing or deleting the attorney’s search terms would alter the intended search logic rather than making the index capable of respecting the requested phrase. Option A is also incorrect because the alphabet file is for searchable characters and tokenization behavior, not for managing ignored noise words. Therefore, before running the Search Terms Report, the correct step is to remove those key terms from the dtSearch index noise words list and rebuild the index if needed.

The correct answer is B. Production type. Relativity’s official Production Data Source documentation states that when adding a production data source, one of the fields you configure is Production Type , where you select whether the data source will produce images, natives, or both . This is explicitly part of the production data source setup dialog.

This makes sense because production data sources are used to attach saved searches to a production set and can define how those specific subsets of documents should be produced. Relativity also documents that placeholders can be assigned at the production data source level so that different saved searches in the same production can use different placeholder behavior. However, Production Numbering is defined at the production set level rather than as a field you set when creating the individual production data source. Likewise, Branding text size and Placeholder image format are production-level settings, not the core field identified in the data source setup described by Relativity.

From an RCA standpoint, this distinction matters because administrators configure overall production behavior in the production set, while more granular document-source behavior is controlled on each production data source. Therefore, the correct answer is B. Production type .

The correct answer is C. Unlock the application. Relativity’s application uninstall documentation states that before deleting or uninstalling an application, you must unlock the application if necessary , and specifically notes that you can't delete a locked application . That makes unlocking the required prerequisite among the options given.

The other options are not listed as required prerequisites. There is no documented requirement to run an uninstall script from the Scripts tab, delete associated tabs first, or unlink all saved searches before uninstalling. Relativity separately documents locking and unlocking applications and states that unlocking allows editing and changes to the application. Therefore, prior to uninstalling an application from a workspace, the required step is to unlock the application .

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