Relativity RCA Practice Test Questions Answers

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. NOT magazine AND apple . Relativity’s dtSearch syntax documentation confirms that dtSearch supports the Boolean operators AND, OR, and NOT and uses them to connect multiple terms in a single search expression. To return only documents that contain apple while excluding those that contain magazine , the query must require the presence of apple and exclude magazine in the same Boolean expression. Option A does exactly that.

Option B is not correct because Apple NOT magazine is missing the required Boolean connector before NOT . Relativity’s dtSearch guidance and related syntax behavior show that NOT is used as part of a Boolean expression, not as a standalone middle operator without AND or OR. Option C is incorrect because Apple OR NOT magazine would broaden the result set too much, potentially returning documents that do not contain apple at all. Option D is also incorrect because it excludes apple instead of requiring it. Therefore, the valid dtSearch string that successfully returns documents containing apple but not magazine is NOT magazine AND apple .

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