The correct answer is D. MM/DD/YYYY and HH:MM:SS AM/PM. Relativity’s Import/Export documentation states that the Regional Settings (Date and Time) value for document load file import reverts to the US date and time by default when browser cache is cleared. The documentation does not spell out the example string on that exact import page, but across Relativity documentation, the default U.S. date convention is month/day/year , and related Relativity guidance commonly shows U.S.-style date-time strings using AM/PM with seconds for import-oriented parsing examples. This makes MM/DD/YYYY and HH:MM:SS AM/PM the best-supported answer from the available choices.

Options A and B are not U.S. default ordering, so they do not fit the documented “US date and time” default. Option C has the correct U.S. month/day/year structure but omits seconds. Based on Relativity’s broader documentation examples for imported date-time strings and supported parsing formats, the version including seconds is the stronger match among the provided options. This answer involves a small inference from the documented U.S. default plus the product’s date-time examples, because the exact multiple-choice wording is more specific than the import page itself.

The correct answer is C. RIP must be installed in the source workspace. Relativity’s Integration Points documentation states that to use Integration Points successfully, you must install the application to at least one workspace . In the specific context of promoting data between workspaces, Relativity also states that you are not required to have Integration Points installed on the destination workspace . That means the practical prerequisite is installation in the source workspace , not both source and destination.

This rules out the other choices. Integration Points is not described as an instance-level-only install requirement, so option A is incorrect. Option B is too broad because the destination workspace installation is explicitly not required. Option D is also incorrect because Integration Points is an application that must be installed in a workspace to be used. Therefore, for migrating documents from one workspace to another with RIP, the required prerequisite is that Integration Points be installed in the source workspace .

The correct answer is D. Add them to an instance-level group with permissions to create groups, manage users, and assign permissions. Relativity’s instance security model allows administrators to assign instance-level permissions to groups through the Admin Security dialog. The documentation explains that permissions can be managed granularly through object security, tab visibility, and admin operations, which means a user can be given specific administrative rights without being made a full system administrator.

This matters because the System Administrators group grants broad access to admin-level permissions and tabs, including queue management. Relativity’s documentation specifically notes that system admins have access to all admin-level capabilities such as queue management, users, and groups tabs . If you do not want the user reviewing Processing or Production queues, giving full System Admin membership is broader than necessary. A workspace admin group is also insufficient for this requirement because creating groups, managing users, and assigning instance-level permissions are administrative functions controlled at the instance level. Therefore, the correct configuration is to place the user in an instance-level group with only the permissions they need.

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.

The correct answer is D. Replace produced images with a placeholder. Relativity’s official Re-production documentation lists supported and unsupported re-production types. Among the supported types, Relativity explicitly includes Replace produced images with placeholder (I-P) .

The same documentation also explicitly lists several unsupported types that correspond to the incorrect options in this question. Relativity states that replacing a document that was produced as native only with produced images or a placeholder is unsupported, which rules out option B. It also states that replacing a document that was produced as a placeholder with another placeholder is unsupported, which rules out option C. Option A is likewise unsupported because “replace produced images with a native” is not identified as a supported re-production type. Instead, Relativity supports image-to-placeholder, placeholder-to-images, and re-producing documents with the same number of pages.

This distinction matters because re-production is tightly controlled to preserve numbering integrity and production consistency. For example, when replacing produced images with placeholders, Relativity preserves the original Bates numbering while substituting placeholder pages. From an RCA production-administration perspective, the supported operation among the listed choices is clearly Replace produced images with a placeholder . Therefore, the correct answer is D .

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 .

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

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.

The correct answer is C. The video must be synced to one .MP4 video and uploaded at the same time. Relativity’s official Transcripts application documentation explicitly states that the video can be played in the Viewer in sync with the text of the transcript, and further notes: you must import videos at the same time you are uploading transcripts or the video and transcript cannot sync . The documentation also describes uploading the video as an .mp4 alongside the transcript during the transcript upload workflow.

This directly eliminates the other options. Option A is false because Relativity clearly supports synced transcript video playback. Option B is wrong because this is not a PST-based workflow. Option D is also incorrect because the documentation does not describe a later mass action that separately syncs already uploaded video and text files; instead, the sync relationship is established during the same upload process. Relativity even distinguishes that videos are not stored as normal documents in the document list, but rather as a file field within a transcript, reinforcing that the transcript upload workflow is the correct path.

From a case administration standpoint, this is important because transcript/video synchronization affects deposition and interview review usability. To ensure successful synchronization, the transcript and its associated .mp4 video must be uploaded together. Therefore, the correct answer is C .