Online RCA Questions Video

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.