Pass the Relativity Relativity Admin RCA Questions and answers with CertsForce

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

The correct answer is B. Copy from Previous on the layout. Relativity’s Copy from Previous documentation explains that you enable this behavior on specific layout fields by setting Enable Copy from Previous to Yes . During review, after saving one document and moving to the next, users can copy the prior document’s coding values into the current document for those enabled fields. That directly matches the scenario of carrying Responsiveness tagging from one document to the next.

The other options do not provide that reviewer-interface behavior. Mass Copy is a separate bulk operation and not the per-document review workflow described here. Propagation is a different concept and is not the setting used to let reviewers carry coding values forward document by document. Document Local Access controls access-related actions, not coding carry-forward. Therefore, to let reviewers apply Responsiveness tagging from one document to the next, you enable Copy from Previous on the layout field.

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 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 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. The email and other parent emails in the thread are coded differently. Relativity’s Email thread visualization documentation explains the meaning of the visual warning icons used in the thread display. The red exclamation point is associated with a coding mismatch condition in the thread. In practice, this means related parent emails in the thread have been coded inconsistently, which is exactly the kind of review inconsistency ETV is designed to expose.

This is different from missing attachments, duplicate spare comparison, or a generic “Needs Review” state. ETV is focused on surfacing thread relationships, inclusiveness, missing emails, and coding consistency across the email conversation. From a Structured Analytics standpoint, the red exclamation point is a QC indicator that reviewers should inspect the thread because coding decisions across parent emails do not align. Therefore, the correct answer is C .

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.