[Jul 27, 2026] Pass Relativity Admin RCA Exam With 83 Questions
Ultimate Guide to Prepare Free Relativity RCA Exam Questions and Answer
NEW QUESTION # 47
When exporting a saved search using Import/Export, how can you maintain the hierarchy of multiple-choice lists?
- A. There is not a way to maintain the information.
- B. Check the box to export multiple-choice fields as nested.
- C. Export as CSV only so Excel recognizes the order.
- D. Sort the saved search on the Multiple Choice field.
Answer: B
Explanation:
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 .
NEW QUESTION # 48
What is an available action in Automated Workflows?
- A. Build a cluster
- B. Manual Start
- C. Build dtSearch Index
- D. Scheduled Run
Answer: C
Explanation:
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 .
NEW QUESTION # 49
When must you run a full build of a dtSearch index?
- A. After adding new documents.
- B. After updating fields in the searchable set.
- C. After removing documents from the search.
- D. After using Swap Index.
Answer: B
Explanation:
The correct answer is A. After updating fields in the searchable set. Relativity's dtSearch index documentation states that you must perform a full build when you add an additional field to the index, change any index settings, change fields of the searchable set, or overlay text on existing fields . That directly matches option A.
By contrast, Relativity documents that an incremental build is used after adding or removing documents .
That makes options B and D incorrect. "After using Swap Index" is not listed as a required trigger for a full build in the dtSearch console documentation. Therefore, the correct answer is that a full build is required after updating fields in the searchable set .
NEW QUESTION # 50
What dtSearch syntax properly creates a phonic search for the word pear to return pair and pare?
- A. #pear
- B. pear*
- C. $pear
- D. 'pear
Answer: A
Explanation:
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 .
NEW QUESTION # 51
A reviewer cannot find a specific document using dtSearch. Why might this be?
- A. The document's parent email is in a secured folder that the reviewer's group does not have access to.
- B. The document is in a Review Center queue the reviewer's group is not assigned to.
- C. An incremental build of the dtSearch index is in progress.
- D. The fields returned by the Searchable Set saved search are all empty for this document.
Answer: D
Explanation:
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.
NEW QUESTION # 52
When using Simple File Upload to import new documents, what determines the Control Number?
- A. The next available Document ArtifactID value.
- B. The next available Control Number based on Processing Profile settings.
- C. The name of the file.
- D. The Filename field of the document's load file.
Answer: C
Explanation:
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.
NEW QUESTION # 53
After adding a pie chart to a dashboard, what is one resulting action when you select multiple pieces of the pie?
- A. The document list will highlight the documents that meet the condition.
- B. No other pivot charts can be changed.
- C. The new configuration is automatically saved as a new dashboard.
- D. Your selection becomes a condition added to the search panel.
Answer: D
Explanation:
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.
NEW QUESTION # 54
You grant the permissions below so that a reviewer on your team can begin creating and running aiR for Review projects. What problem will this reviewer encounter when attempting to analyze documents using aiR for Review?
Object Security:
* aiR for Review Project: View, Edit, Add
* aiR for Review Prompt Criteria: View, Edit, Add
Tab Visibility:
* aiR for Review Projects
- A. They will only be able to view aiR for Review results highlighted in the Viewer.
- B. Without the tab visibility permission granted for the aiR for Review dashboard, the reviewer will not be able to start the analysis.
- C. Without individual Object Security permissions granted for each analysis type's object, they will not be able to view any results.
- D. They will only be able to view aiR for Review projects at the instance-level instead of the workspace level.
Answer: C
Explanation:
The correct answer is A . Relativity's official aiR for Review permissions documentation states that to create and run an aiR for Review project, a user needs object permissions for aiR for Review Project and aiR for Review Prompt Criteria , tab visibility for aiR for Review Projects , and the Run aiR for Review Job permission under Other Settings. The documentation also explicitly states that a user can run the job without permissions for the analysis types, but will not be able to see the results . The analysis-type objects listed by Relativity are aiR Relevance Analysis , aiR Issue Analysis , aiR Key Analysis , and aiR Summaries .
That is exactly the problem in this scenario: the reviewer has enough permissions to create the project shell and prompt criteria, but no permissions were granted for the analysis result objects themselves. As a result, they can initiate work but will not be able to see the analysis results. Option B is incorrect because Viewer highlighting also depends on having analysis-type view permissions. Option C is incorrect because instance- level jobs visibility is a separate permission model. Option D is also incorrect because the provided permissions already include the aiR for Review Projects tab, and the missing issue is not dashboard tab access but the lack of object security for the individual analysis result types . Therefore, the reviewer's main issue is that they will not be able to view any aiR for Review results without the required analysis- type object permissions .
NEW QUESTION # 55
What is true when importing a LEF or .XMEF bundled transcript file from the Document object?
- A. Bundled transcript files are not supported in Relativity.
- B. Exhibits are uploaded, but need to be linked manually.
- C. Existing links to exhibits in the transcript are visible once completed.
- D. Exhibits need to be parsed out and uploaded separately.
Answer: C
Explanation:
The correct answer is D. Existing links to exhibits in the transcript are visible once completed. Relativity' s official Transcripts documentation states that supported bundle file types include .lef and .xmef . When a bundle is uploaded, Relativity extracts the transcript file and displays the extra files as exhibits. The documentation further states that existing links to exhibits in transcript files will be visible in the Viewer once they are uploaded to Relativity . That is a direct match to option D.
This makes the other options incorrect. Bundled transcript files are explicitly supported, so option A is wrong.
Exhibits do not need to be manually linked in the way described by option B when the transcript already contains those links; Relativity preserves and displays existing links. Option C is also incorrect because the documentation explains that the bundle upload process extracts the transcript and surfaces the additional files as exhibits, rather than requiring administrators to parse and upload them separately. From a case administration standpoint, this is useful because it streamlines transcript management and preserves exhibit relationships during import. Therefore, when importing LEF or XMEF bundled transcript files from the Document object, the true statement is that existing links to exhibits are visible once the upload is completed .
NEW QUESTION # 56
You need to create a saved search of all documents containing the term apple that do not contain the term magazine. What dtSearch string would successfully return these documents?
- A. NOT apple and magazine
- B. Apple NOT magazine
- C. Apple OR NOT magazine
- D. NOT magazine AND apple
Answer: D
Explanation:
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 .
NEW QUESTION # 57
When using Import/Export, what happens to existing metadata fields when you select the option to overlay metadata while importing a document load file that contains several blank metadata values?
- A. The existing values will remain in the corresponding mapped fields.
- B. The blank values will replace the existing field values.
- C. The overlay will error for each document with blank values.
- D. Only fixed-length text fields will be overlaid with the blank values.
Answer: B
Explanation:
The correct answer is C. The blank values will replace the existing field values. Relativity's Import/Export document load file import documentation states that for Append/Overlay and Overlay Only , if a blank metadata field exists in the load file, the blank value will overlay remove any existing value in the corresponding mapped field. That means the blank value does not preserve the original value; it clears it.
This rules out the other options. The import does not preserve the old value in the mapped field, so option A is incorrect. The workflow does not error merely because blank values are present, so option B is also incorrect.
Option D is wrong because the behavior is not limited to fixed-length text fields; it is described generally for mapped metadata fields in overlay mode. Therefore, the correct answer is that blank values replace existing field values during overlay import.
NEW QUESTION # 58
What operator is invalid in a text box filter?
- A. > =
- B. IS SET
- C. NOT
- D. AND
Answer: C
Explanation:
The correct answer is D. NOT . Relativity's Filters documentation for text box filters lists the valid operators as AND, OR, IS SET, IS NOT SET, BETWEEN, =, > =, and < = . Since NOT does not appear in that valid operator list, it is the invalid choice among the options provided.
This is a useful distinction because Relativity supports NOT in some other search contexts, such as dtSearch or advanced filtering patterns, but the question asks specifically about a text box filter operator. In that exact context, AND , IS SET , and > = are valid, while NOT is not. Therefore, the invalid operator for a text box filter is NOT .
NEW QUESTION # 59
What is true when transferring images from one workspace to another using Relativity Integration Points RIP?
- A. The RIP application must be installed in the destination workspace.
- B. The field mapping section is disabled because only the control number is needed.
- C. The native file used to create the images must be included in the transfer.
- D. The metadata fields from your data source will be auto-mapped and migrated.
Answer: B
Explanation:
The correct answer is A. The field mapping section is disabled because only the control number is needed.
Relativity's official Integration Points documentation for promoting data between workspaces states that when you select Copy Images , the field mapping section is disabled because only the control number is required and available in this scenario . It further notes that if you want to transfer other field metadata, you must create a separate integration point without choosing to copy images.
That directly rules out the other options. Relativity does not state that the native file must be included to transfer images in this scenario. It also specifically notes that you are not required to have Integration Points installed on the destination workspace , so option C is incorrect. Option D is wrong because metadata is not automatically mapped and migrated in the Copy Images path; in fact, field mapping is disabled in that configuration.
From an RCA and data-movement perspective, this is a common distinction: image promotion through Integration Points is streamlined and relies on control number matching , not standard metadata field mapping. Therefore, the true statement is A .
NEW QUESTION # 60
A client sends you a data set they want processed that is comprised entirely of large Excel files. What is the best Excel Text Extraction Method to get the data to review as quickly as possible?
- A. Native failover to dtSearch
- B. Native
- C. Relativity
- D. Extract and place inline
Answer: C
Explanation:
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.
NEW QUESTION # 61
When should you run OCR on a production?
- A. After a production is exported.
- B. After a document is redacted.
- C. Before a production is run.
- D. Before a production is exported.
Answer: A
NEW QUESTION # 62
What object in Relativity functions as the central location for people, companies, organizational groups, and their metadata?
- A. Entity
- B. Field
- C. Layout
- D. Document
Answer: A
Explanation:
The correct answer is D. Entity . Relativity's official documentation explicitly states that the Entity object functions as the central location for people, companies, organizational groups, and their metadata . This wording appears directly in the Entity object documentation and is the exact phrasing reflected in the question.
The other options are incorrect because they serve different purposes in Relativity. A Field stores data elements, a Layout controls display and editing arrangements, and a Document represents reviewable content. None of these objects serves as the centralized person/company/group metadata object described in the official documentation. Therefore, the correct answer is Entity .
NEW QUESTION # 63
What operation does not work when trying to analyze documents that are password protected?
- A. Mass Image
- B. Save as PDF
- C. Processing
- D. Imaging Sets
Answer: B
Explanation:
The correct answer is B. Save as PDF. Relativity's imaging documentation states that the Password Bank is used to decrypt certain password-protected files during processing and imaging workflows. It also explicitly states that Save as PDF does not integrate with the Password Bank and that if you select Save as PDF when imaging a password-protected native document, an error occurs .
This directly differentiates Save as PDF from the other options. Processing supports password decryption through the Password Bank. Mass Image and Imaging Sets also work with the Password Bank, allowing protected files to be imaged if the correct password is available in the bank. Because Save as PDF does not use that mechanism, it fails where the other imaging-related workflows can succeed.
From a case administration perspective, this is a practical operational detail. Password-protected content often needs special handling, and administrators need to know which tools integrate with Relativity's decryption workflow. The one that does not work for this purpose is Save as PDF .
NEW QUESTION # 64
To what group does Relativity automatically add users that you create?
- A. All Users
- B. Users are not automatically added to a group
- C. Domain Users
- D. Everyone
Answer: D
Explanation:
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 .
NEW QUESTION # 65
What option cannot be configured when you create a new production data source?
- A. The field to use for production numbering.
- B. The placeholder to apply.
- C. The markup set to apply.
- D. Whether or not to burn redactions on the documents.
Answer: A
Explanation:
The correct answer is A. The field to use for production numbering. Relativity's documentation distinguishes between production set settings and production data source settings . The production set defines overarching settings such as document numbering , appearance of numbering, and related production-wide behaviors. By contrast, the production data source page includes settings such as production type , placeholder image format , burn redactions , burn native redactions , burn PDF redactions , and markup set .
This means the field used for production numbering is not configured at the individual data source level; it belongs to the production set itself. The other options are all part of production data source configuration.
The documentation explicitly shows Burn Redactions and Markup Set , and placeholder behavior is also configured within the production data source settings.
Therefore, the option that cannot be configured when creating a new production data source is the field to use for production numbering , because that is a production-set-level setting rather than a data-source-level one.
NEW QUESTION # 66
What situation can lead to a production error?
- A. Producing the image version of an unresponsive document.
- B. The same document is found in multiple data sources.
- C. Producing a document that exceeds the maximum number of allowed redactions.
- D. Producing the native file of a document that has redactions.
Answer: B
Explanation:
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 .
NEW QUESTION # 67
What aliases will Name Normalization identify from the email below?
From: "Lin, David" [email protected]
To: [email protected]
CC:
BCC:
Date: 1/25/2020 11:15 AM
Subject: Report Request for Skylar
Hi Ali,
Skylar is looking into the issue involving Rush Jones ([email protected]). Can you please provide a copy of the analytics report to her?
Best,
Dave Lin
- A. * "Lin, David" [email protected]
* [email protected]
* [email protected]
* Dave Lin - B. * "Lin, David" [email protected]
* [email protected]
* [email protected]
* "Lin, David"
* [email protected]
* [email protected]
* Skylar - C. * "Lin, David" [email protected]
* [email protected]
* [email protected]
* Ali
* Skylar
* Rush Jones
* Dave Lin - D. * "Lin, David" [email protected]
* "Lin, David"
* [email protected]
* [email protected]
Answer: D
Explanation:
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" [email protected] , 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" [email protected] yields three aliases:
"Lin, David" [email protected] , "Lin, David" , and [email protected] . The To header contributes [email protected] .
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 , [email protected] , 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 .
NEW QUESTION # 68
What is required to use the communication analysis widget?
- A. Conceptual analytics index
- B. Name normalization
- C. Repeated content filter
- D. Email threading
Answer: B
Explanation:
The correct answer is D. Name normalization. Relativity's official Communication Analysis documentation states that you can add the Communication Analysis widget to a dashboard after running name normalization . The widget visualizes communication frequencies, patterns, and networks between entities linked to the documents in the view, and those entities come from the results of name normalization.
This requirement is fundamental because the widget depends on entity and alias relationships generated by structured analytics name normalization. Without those normalized entities, the system does not have the participant relationship structure needed to render communication maps. Relativity also repeats this requirement in its dashboard documentation, again stating that Communication Analysis is available after running the name normalization operation within structured analytics .
The other options are not the prerequisite named by Relativity. A repeated content filter is optional and only used to improve text cleanup. A conceptual analytics index is a different analytics technology entirely. Email threading is a separate structured analytics operation and is not the stated prerequisite for this widget.
Therefore, the correct answer is D. Name normalization .
NEW QUESTION # 69
What tool replaces a native or image within the Reviewer Interface?
- A. Relativity Processing
- B. Simple File Upload
- C. Native Imaging Sets
- D. Mass Replace
Answer: B
Explanation:
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 .
NEW QUESTION # 70
......
Pass RCA Tests Engine pdf - All Free Dumps: https://www.passtorrent.com/RCA-latest-torrent.html