Relativity Relativity Certified Administrator RCA Exam Dumps: Updated Questions & Answers (May 2026)

The correct answer is D. Regular expression filter. Relativity’s Structured Analytics documentation states that a Regular expression filter can be linked to a structured analytics set as an optional setting, and that it is used to clean up extracted text before analysis . The documentation further explains that this setting is implemented through a repeated content filter whose type must be Regular Expression . This directly matches the question’s wording about excluding document text before analytics processing begins.

This capability is especially useful when documents contain extraneous content such as dates, URLs, page numbers, Bates numbers, standard disclaimers, or other repeated text that can interfere with email threading or textual near duplicate results. Relativity notes that the filter applies only to the field being analyzed, which is usually Extracted Text unless another field is selected. By removing this noise before the algorithm runs, administrators can improve the quality of structured analytics outcomes.

The other options are not the correct named filter for this function in Relativity’s structured analytics workflow. The official setting is specifically the Regular expression filter . Therefore, the correct answer is D .

The correct answer is D. MM/DD/YYYY and HH:MM:SS AM/PM. Relativity’s Import/Export documentation states that the Regional Settings (Date and Time) value for document load file import reverts to the US date and time by default when browser cache is cleared. The documentation does not spell out the example string on that exact import page, but across Relativity documentation, the default U.S. date convention is month/day/year , and related Relativity guidance commonly shows U.S.-style date-time strings using AM/PM with seconds for import-oriented parsing examples. This makes MM/DD/YYYY and HH:MM:SS AM/PM the best-supported answer from the available choices.

Options A and B are not U.S. default ordering, so they do not fit the documented “US date and time” default. Option C has the correct U.S. month/day/year structure but omits seconds. Based on Relativity’s broader documentation examples for imported date-time strings and supported parsing formats, the version including seconds is the stronger match among the provided options. This answer involves a small inference from the documented U.S. default plus the product’s date-time examples, because the exact multiple-choice wording is more specific than the import page itself.

The correct answer is A. Use a mass operation to update the Disable On Date field. Relativity’s Users documentation explicitly states that you can use a mass-operation to set the Disable On Date (UTC) field for multiple users . This is the exact documented method for updating that field across multiple user accounts at once.

The other options are not the documented answer for this workflow. Disabling a group is not the same thing as updating the Disable On Date field on user records. Overlay via Import/Export is not the method Relativity identifies for this task in the Users documentation. Setting the field individually works for a single user, but the question asks specifically about multiple users . Therefore, the correct answer is to use a mass operation to update the Disable On Date field.

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 C . Relativity’s official Name Normalization documentation explains that the process parses the email headers —specifically From, To, Cc, and Bcc —to identify aliases. It does not create aliases from every casual name reference appearing in the email body. Relativity further states that when an alias appears in the format "Doe, John" john.doe@example.com , Name Normalization stores three aliases: the full alias , the description/name portion , and the email address portion . Applying that exact documented rule here means the From value "Lin, David" David.Lin@example.com yields three aliases: "Lin, David" David.Lin@example.com , "Lin, David" , and David.Lin@example.com . The To header contributes Ali.Devi@example.com .

Relativity also explicitly notes that generic aliases such as simple first names are not created in order to avoid over-merging. In addition, the alias-identification process is driven by the parsed header sections , not by every name or email string appearing in the message body. That means items such as Ali , Skylar , Rush Jones , rjones@domain.com , and Dave Lin are not the correct header-derived aliases for this example. The body text may help Relativity with segment matching in some contexts, but the direct alias list in this question comes from the email headers. Therefore, the correct identified aliases are the four listed in option C .

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 D. Existing production numbering . Relativity’s official production set documentation states that Existing production numbering should be selected when you want to re-use the Bates numbering fields from a previously run production set . This is the exact numbering option designed for scenarios where documents are being reproduced but must retain the same Bates values from an earlier production. Relativity further explains that this option is appropriate when you need to change the produced images, produce only a subset of documents from the existing production, or otherwise reissue the same produced documents while preserving the prior numbering.

This aligns directly with re-production workflows. Relativity’s re-production documentation also notes that re-production jobs reuse the numbering format and Bates numbers from the original productions , reinforcing that the platform supports maintaining the original numbering scheme instead of assigning new Bates values. That is critical in litigation workflows where Bates continuity must be preserved for references in correspondence, court filings, and prior productions. The other options do not fit this requirement. Page level numbering and document field numbering generate or rely on other numbering methods, while original image numbering is not the production numbering choice used for preserving prior Bates values in a re-production. Therefore, when reproducing documents and keeping the same Bates numbering, the correct production numbering method is Existing production numbering .

The correct answer is C. 100 . According to Relativity’s official Simple File Upload documentation, the SFUMaxFilesToUpload instance setting determines the maximum number of documents a user can upload at one time using Simple File Upload. Relativity states that administrators can configure this setting up to 100 files , and when the setting is at its maximum, users can upload up to 100 files at one time . If a user selects more than 100 files, Relativity uploads only the first 100 selected files and does not upload the remainder. Relativity also indicates that a warning message appears in the upload window when more than 100 files are selected.

This makes the answer operationally important for administrators because Simple File Upload is designed for lightweight, direct document uploads within a workspace, not for large-scale ingestion jobs. For more substantial data loading exercises, administrators typically use Relativity’s broader import workflows rather than relying on Simple File Upload. From an RCA perspective, knowing this limit helps with user support, upload troubleshooting, and setting expectations for workspace users who need to add small batches of documents quickly. Therefore, among the options given, 100 is the only choice that aligns with the official Relativity behavior for Simple File Upload.

The correct answer is B. Name conflicts: Rename or map Fields. Relativity’s Troubleshooting application installation errors documentation explains that for Name conflicts , the available resolution options include Rename and Map Field . The page specifically instructs admins to use the Resolve Errors drop-down and choose either Rename or Map Field to address the conflicting artifact during application installation.

The other choices are inconsistent with the documentation. For locking conflicts , Relativity says you can resolve them by selecting the Unlock checkbox, so option A is incorrect. For restricted file types , the documented resolution is to remove the external resource from the application and re-install , not simply “run a re-install,” so option D is incomplete and inaccurate. Option C is also too vague and not one of the documented named error-resolution pairings. Therefore, the correct expected application installation error and solution is Name conflicts: Rename or map Fields

The correct answer is A. Document - Update . Relativity’s official Audit documentation states that system admins can revert coding decisions from the Audit list, and that this action applies to the latest Document Update , Mass Update , or Propagate action on the Document object. That makes Document - Update the correct revertable action among the choices provided.

The other options are not listed by Relativity as revertable audit actions in this context. A Field - Update concerns the field object itself rather than a document coding decision. Entity - Merge may create audit records, but Relativity does not list it as an action that can be reverted through the Audit revert feature. Redaction - Update is also not one of the documented revertable audit actions under the Audit tab’s revert capability. From an RCA perspective, this distinction matters because Audit revert is narrowly scoped to specific document-level update actions and certain supported field types. Therefore, the correct answer is Document - Update .