Free and Premium Relativity RCA Dumps Questions Answers

The correct answer is A. At the User level, use the Disable on Date settings. Relativity’s Users documentation states that Disable on Date (UTC) is the field used to auto-disable users on a specific future date. It also explains that you can set this field when creating or editing an individual user, and that users will be automatically logged out and disabled on the specified date and time.

The other options are not the documented built-in mechanism for this feature. User Activity in Security Center allows admins to inspect and disable users, but it is not the setting used to preconfigure automatic disablement on a future date. Likewise, the question’s instance-level settings in options B and D are not the Relativity feature described in the official Users documentation for automatic disablement. Therefore, the correct answer is Disable on Date at the user level .

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 .

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 .

The correct answer is B. :Name: . Relativity’s RSMF-supported emoji documentation states that emojis in RSMF files display as text strings surrounded by colons , giving the example :smile: . That directly establishes the emoji short-name format used by Relativity for named emoji representations.

The Short Message Viewer documentation also confirms that users can search for emojis in conversations. Since Relativity’s own emoji naming convention is colon-delimited short names, the correct format for searching by name is :Name:. The other options use bracket, angle-bracket, or quoted forms that Relativity does not identify as the short-name syntax for emoji. Therefore, the correct answer is :Name: .

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

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 B . Relativity’s official production console documentation explains that Stage Production and Stage and Run Production both take a snapshot of the data sources for the production. The staging step captures the current contents of those data sources so the production job runs against a fixed set of documents. Relativity also documents that staging errors occur if the same document is found in multiple data sources , which means duplicate-document checking is part of what administrators must evaluate during the staging phase.

The other options describe different production activities. Showing a sample image of branding is associated with Preview Production , not staging. Bates numbers are assigned later as part of the production run, not during the initial staging snapshot. The option about conflict checking against a Production Restriction saved search is not the best description of the staging step itself according to the official documentation. For RCA exam purposes, the key concept is that staging freezes the production inputs and surfaces structural issues, especially duplicate documents across data sources, before the full production run proceeds. This is an important quality-control checkpoint because it helps administrators verify that the right documents and data-source configuration are in place before branding, numbering, and export occur. Therefore, the best answer is that during staging, Relativity takes a snapshot of the data sources and checks for duplicate documents between data sources .

The correct answer is A. Ignore Numbers. Relativity’s near duplicate documentation explains that when Ignore Numbers is set to true, the similarity calculation considers only tokens beginning with letters, which means numbers are excluded from the similarity percentage calculation. That is directly relevant for invoice populations, because many invoices share nearly identical wording while differing mainly by dates, invoice numbers, quantities, or amounts. In a set like the one described, toggling Ignore Numbers is the setting most likely to change how those documents are grouped and help you assess whether the current near duplicate results can be improved.

The other options do not fit this use case. MD5Hash Verifier is related to hash-based duplicate validation rather than textual near duplicate tuning. Relativity Compare is a review tool for examining differences after grouping, not a setting that changes how the grouping is calculated. Auto-recognize Dates is not the structured analytics tuning option documented for this scenario. Therefore, for invoice-heavy data where numerical differences are driving questionable textual near duplicate results, the correct setting to toggle is Ignore Numbers.

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. After a production is exported. Relativity’s official documentation on OCR for redacted production documents explains that you create an OCR set and then point the OCR set to the completed Production . The workflow explicitly states that OCR is performed against the completed production , and once the OCR job is complete, the resulting text becomes ready to export. This means the production must already exist before OCR is run against it. In practical terms, OCR is performed after the production has been run/exported as a completed production set , not before the production exists.

The reason for this is that Relativity OCR in this workflow can operate on production images containing burned-in redactions . That allows the exported text to reflect the redacted version rather than unredacted underlying extracted text. Running OCR before the production is run would not achieve this production-specific result, because the final production images would not yet exist. Option D is too broad and incomplete because a document being redacted does not itself define the OCR timing; the documented process is tied to a completed production . Therefore, under the Productions topic, the correct answer is that you run OCR after the production is exported/completed , because that is when the production images are available for OCR processing.

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. You cannot use Audit to revert coding decisions on required fields back to a null state. Relativity’s official Audit documentation states that certain field types, including single choice , can be reverted. However, it also explicitly states that you cannot revert a required field if doing so would return that field to a blank null value . That is exactly what this scenario describes: the field was changed from null to Responsive, and reverting would restore it to null. If the field is required, Relativity blocks that revert because required fields cannot be blank.

This means option A is incorrect because single-choice fields can be reverted in Audit. Option B is also incorrect because Relativity supports both individual and mass revert workflows depending on the situation. Option D is not the documented reason for the failure. The controlling issue is the required-field constraint. From an RCA perspective, this is a subtle but important administrative behavior: the Audit system can revert field changes, but only where the resulting value remains valid under Relativity’s field rules. If the revert would violate a field’s required setting, the system will not allow it. Therefore, the most accurate reason is that Audit cannot revert the value because the revert would place a required field back into a null state .

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.

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 .

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

The correct answer is B. Add the OCR text field as the first field in the Text Precedence window. Relativity’s OCR-on-redacted-production guidance explains that to produce only non-redacted text, you must use Text Precedence during export, and it specifically warns not to add the Extracted Text field to the exported field list because doing so can result in producing redacted text. It also explains that production export can use ordered text fields so Relativity pulls text from the highest-priority populated field.

In this workflow, the OCR text generated from the redacted production images is the field that reflects the redacted-visible text appropriately for export. By placing the OCR text field first in Text Precedence, Relativity uses that OCR-derived text before falling back to other long-text fields. Option A is incorrect because prioritizing Extracted Text risks exporting the original underlying text rather than the intended redacted-visible text. Options C and D are also incorrect because the guidance is to control output through Text Precedence , not by simply adding those fields to the exported field list; in fact, Relativity explicitly warns against adding Extracted Text to the exported list for this use case. Therefore, the correct step is to put the OCR text field first in Text Precedence .

The correct answer is C. Speaker . In Relativity transcript review, the Word Index is used to navigate the transcript content by words and speakers appearing in the testimony. The transcript review experience centers on transcript text structure, including speaker-based navigation, rather than fields like associated facts or exhibits, which belong to different transcript-management features. Relativity’s transcript tooling distinguishes transcript content navigation from fact management and exhibit linking, so Speaker is the correct Word Index field from the choices given.

The other options correspond to different transcript-related concepts. Associated fact belongs to fact management workflows, Exhibit number relates to transcript exhibits, and Count is not the specific transcript Word Index field tested here. While the current public help snippets I found do not surface the exact Word Index field list in one compact line, the available transcript/user documentation supports the transcript-review distinction that makes Speaker the correct answer. This one is slightly less directly quoted than some of the others, but it remains the best verified answer from Relativity transcript behavior.