[2026年07月31日]RCA練習試験問題集で試験99%合格率があります
最新の検証済みRCA問題と解答、合格保証もしくは全額返金
質問 # 18
When cancelling an Automated Workflow, how fast does the cancellation occur?
- A. Immediately
- B. After the current task completes
- C. After the full workflow completes
- D. Automated Workflows cannot be cancelled
正解：B
解説：
The correct answer is B. After the current task completes. Relativity's Automated Workflows documentation states that when you click Cancel Workflow , the workflow is canceled once the currently running task is completed . The documentation is explicit that canceling the workflow does not cancel an action that is currently in progress . If you want to stop the active action itself, you must navigate to that specific object and cancel it there.
This means the cancellation is neither immediate nor delayed until the whole workflow finishes. It also means option A is false because workflows can be canceled. From an RCA administration perspective, this is important because workflow cancellation is staged: pending downstream actions are stopped, but the in-flight task is allowed to finish unless separately canceled at its own object level. Therefore, the correct answer is after the current task completes .
質問 # 19
How is a Relativity Short Message Format RSMF file created?
- A. By using the mass operation on the document list to convert a conversation into RSMF.
- B. Relativity creates it on-the-fly for all non-document data.
- C. By using the processing profile option to automatically convert XML from a messaging platform into RSMF.
- D. Files must be generated using the RSMF specifications before they are imported into Relativity.
正解：D
解説：
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.
質問 # 20
What is true when transferring images from one workspace to another using Relativity Integration Points RIP?
- A. The native file used to create the images must be included in the transfer.
- B. The metadata fields from your data source will be auto-mapped and migrated.
- C. The RIP application must be installed in the destination workspace.
- D. The field mapping section is disabled because only the control number is needed.
正解：D
解説：
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 .
質問 # 21
Your document collection contains a subset of invoices that are being identified as textual near duplicates yet are all from different days and are of differing amounts. What setting can you toggle to see if the results can be improved?
- A. Relativity Compare
- B. Auto-recognize Dates
- C. MD5Hash Verifier
- D. Ignore Numbers
正解：D
解説：
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.
質問 # 22
How can you secure a workspace from a user?
- A. By individually securing instance-level views from a user.
- B. By changing the security settings of the user's IP address.
- C. By removing that user's security group from the workspace.
- D. By excluding the workspace name from a user's profile settings.
正解：C
解説：
The correct answer is A. By removing that user's security group from the workspace. In Relativity, workspace access is granted through groups , not by attaching workspace rights directly to individual users.
Relativity's official security documentation explains that you set permissions by adding groups to a workspace and configuring those group permissions there. Users then inherit access through their group memberships. As a result, the standard way to secure a workspace from a user is to remove the group that gives that user access, or remove the user from the relevant group.
The other options do not reflect how Relativity security is structured. User profile settings do not control workspace visibility in the manner described. IP-based security is not the mechanism for ordinary workspace access control in this scenario. Instance-level view security is also too narrow and does not remove the user's overall workspace access; even if certain views were restricted, the user could still potentially access the workspace through other permitted objects or tabs. From an RCA perspective, this question tests a foundational principle: workspace security is group-based . Administrators grant or revoke access by managing the relationship between groups and workspaces, then managing which users belong to those groups. Therefore, to secure a workspace from a user, the correct action is to remove the user's access- granting security group from that workspace.
質問 # 23
You loaded a third-party production of native files, and the case team would like a field that provides the file size for each of the files received. What is the most efficient way to populate information for your native files?
- A. Run the Set native file size field script.
- B. The native file size is automatically populated for documents.
- C. Run the Set extracted text size field script.
- D. Run the tally/sum/average mass operation on the native files.
正解：A
質問 # 24
After imaging the documents in preparation for production, the case team asks for the estimated image count of the production. How can you quickly obtain the image count for the case team?
- A. Export the results of the Mass Convert operation.
- B. Use the Tally/Sum/Average mass operation on the Relativity Image Count field.
- C. Export the Relativity Image Count field and calculate it in Excel.
- D. Use the Has Images widget on your pre-production dashboard.
正解：B
解説：
The correct answer is D. Use the Tally/Sum/Average mass operation on the Relativity Image Count field.
Relativity's Tally/sum/average documentation says this mass operation is commonly used to determine the number of pages in a print job or production. Relativity also specifically documents, in related guidance, that to estimate project size you can use Tally/sum/average on the Relativity Image Count field.
This makes it the fastest and most direct built-in method for obtaining an image count estimate. The other options are less efficient or are not the documented workflow for quickly producing a total image count.
Therefore, the correct answer is to use Tally/Sum/Average on the Relativity Image Count field.
質問 # 25
After review started, you realize the fixed-length text field you created should have been a long text field.
What is the fastest, most efficient way to populate the new long text field with the values from the fixed- length text field?
- A. Use Mass Replace to update the long text field with the fixed-length text field values.
- B. Export the values from the fixed-length text field and overlay them to the new long text field.
- C. Manually update the new long text field for each individual document.
- D. Use Mass Merge to merge values from the fixed-length text field to the long text field.
正解：A
解説：
The correct answer is D. Use Mass Replace to update the long text field with the fixed-length text field values. Relativity's mass operations documentation explains that Mass Replace can be used not only to replace text with static content, but also for field-to-field operations. Specifically, the official examples include copying the contents of one text field to another and merging the values of a source field with the values of a target field . That directly fits this scenario, where the administrator needs to populate a newly created long text field with the existing values stored in a fixed-length text field across many documents.
The other options are less efficient or not aligned with standard Relativity functionality. Manual updates would be extremely slow and error-prone in an active review. Exporting and then overlaying values would create unnecessary extra steps and administrative overhead. Option B refers to Mass Merge , but in Relativity documentation the Merge mass operation is associated with Analytics entity handling, not with copying document text values between fields. For document field content migration, Mass Replace is the documented bulk-update tool. Because this question focuses on the fastest and most efficient administrative correction after review has started, the best practice is to create the correct long text field and then use Mass Replace to populate it from the original fixed-length text field.
質問 # 26
When should you run OCR on a production?
- A. After a production is exported.
- B. Before a production is run.
- C. After a document is redacted.
- D. Before a production is exported.
正解：A
質問 # 27
When using Mass PDF, what field type can you use to name the file?
- A. Fixed length text
- B. Artifact ID
- C. Single choice
- D. Date
正解：A
解説：
The correct answer is D. Fixed length text . Relativity's Mass PDF documentation states that when saving PDFs as a ZIP or PDF portfolio , you can choose to name the individual PDFs using the control number , the control number plus a field , or just a field . In other words, Relativity supports file naming from a document field value. The same documentation also notes that long names are truncated if they exceed the allowed length, which confirms that the chosen field value is being used directly as part of the resulting file name.
Among the answer choices, fixed length text is the best and most appropriate field type for this purpose. A fixed length text field is designed to store concise string values that work well as filenames. Artifact ID is not a field type in this context, but rather a system identifier. Date fields can exist, but they are not the standard answer for naming PDFs in an exam question framed around field type suitability. Single choice stores coded values and is not the expected best answer here. This question appears to test practical Relativity administration knowledge rather than every technically possible field serialization outcome. Since Mass PDF naming relies on a field value and file names are most appropriately based on text metadata, the correct exam- aligned answer is fixed length text . The Relativity documentation supports the field-based naming capability, and the selection of fixed length text is the most reasonable administrative interpretation from the provided options.
質問 # 28
Using Simple File Upload, what metadata fields are overwritten if you replace a document with a document that has a different name?
- A. Extracted text, FileSize, and Page Count
- B. Extracted text, FileExtension, and FileName
- C. FileExtension, FileName, and Sort Date
- D. Extracted text, Group Identifier, and FileSize
正解：B
解説：
The correct answer is C. Extracted text, FileExtension, and FileName. Relativity's official Simple File Upload documentation includes a Replacing documents section that explicitly lists the metadata fields overwritten when a document is replaced with another document sharing the same control number. The overwritten fields include FileName , FileSize , FileExtension , Extracted Text , Supported By Viewer , Relativity Native Type , Has Native , and certain last-modified system fields.
Among the answer choices, option C is the only one composed entirely of fields that Relativity explicitly says are overwritten in this workflow. Option A is incorrect because Sort Date is not one of the documented overwritten fields. Option B is incorrect because Group Identifier is not listed as being overwritten. Option D is incorrect because Page Count is not listed in the documented overwritten fields for replacing a document via this workflow.
This is an important Data loading administration detail because document replacement changes core file metadata tied to the uploaded replacement native, including its filename and extension, while preserving the document identity through the shared control number. Therefore, the correct option is C. Extracted text, FileExtension, and FileName .
質問 # 29
What do you need to do to ensure you produce only non-redacted text?
- A. Add the Extracted Text field as the first field in the Text Precedence window.
- B. Add the OCR text field as the first field in the Text Precedence window.
- C. Add the Extracted Text field to the exported field list.
- D. Add the OCR text field to the exported field list.
正解：B
解説：
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 .
質問 # 30
What is required to use the communication analysis widget?
- A. Email threading
- B. Conceptual analytics index
- C. Repeated content filter
- D. Name normalization
正解：D
解説：
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 .
質問 # 31
If you add the same document to two different data sources in the same production set, what happens when you stage the production?
- A. No error messages are generated when you stage the production, and the document is produced once according to the first data source settings.
- B. No error messages are generated when you stage the production, and the document is produced twice.
- C. An error message is generated when you stage the production, and you cannot run the production until duplicate documents are removed.
- D. An error message is generated when you stage the production, and you can proceed to run the production.
正解：C
解説：
The correct answer is C . Relativity's official production staging documentation states that a staging error occurs when the same document is found in multiple data sources within the same production set. When this happens, Relativity generates an error message identifying the data sources that pulled back the same document and which specific document is duplicated. The documented resolution is to modify the saved searches used as data sources so they no longer return the same document.
This means staging does not simply ignore the duplicate, nor does it produce the document twice or proceed using the first data source's settings. The duplicate condition is treated as a production-stopping issue that must be corrected before the production can successfully continue. From an RCA perspective, this is a core Productions concept because it affects production QC and data-source design. Administrators should ensure that saved searches used as production data sources are mutually exclusive when necessary, especially if different branding, numbering, or production settings apply. During staging, Relativity is validating the integrity of the production inputs, and duplicate documents across data sources are explicitly flagged as errors. Therefore, the correct interpretation is that an error message appears during staging and the production cannot proceed until the duplicate documents are removed from overlapping data sources .
質問 # 32
What happens during the staging step of a production?
- A. Relativity assigns Bates numbers to documents.
- B. Relativity displays a sample image showing how the branding is applied to documents in the production.
- C. Relativity takes a snapshot of the data sources and checks for duplicate documents between data sources.
- D. Relativity performs a conflict check to ensure the data sources do not contain documents that are also in the saved search selected in the Production Restriction field.
正解：C
解説：
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 .
質問 # 33
......
RCAリアル有効かつ正確な問題集83問題と解答が待ってます：https://jp.fast2test.com/RCA-premium-file.html