RCA Certification Exam Guide + Practice Questions Updated 2026

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

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.

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.

Explanation:
The correct answer is C. Files must be generated using the RSMF specifications before they are imported into Relativity. Relativity’s official Short Message Format documentation explains that to use the Short Message Viewer, you first need to create an RSMF file, and the example/specification pages describe the required structure and header information that must be present before ingestion using Processing. Relativity also states that Processing is the recommended method of importing RSMF files into Relativity, which means the RSMF file already exists when Processing begins.
This rules out the other options. Relativity does not say that it automatically creates RSMF on-the-fly for all non-document data. It also does not describe a processing-profile feature that converts arbitrary XML from chat platforms into RSMF during import. Nor is there a document-list mass operation that converts conversations into RSMF. Instead, RSMF is a defined external format that must be constructed according to Relativity’s published specifications, then imported and processed to preserve message metadata, attachments, and near-native review behavior .
Therefore, the correct answer is C.

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.