RCA Exam Dumps : Relativity Certified Administrator

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