Pass Your RCA Exam Easily - Real RCA Practice Dump Updated Sep 22, 2026
2026 Realistic Verified Free Relativity RCA Exam Questions
NEW QUESTION # 38
With what tool can you rapidly transfer large amounts of data from your RelativityOne storage location to a local computer?
- A. Simple File Download
- B. Relativity Integration Points RIP
- C. RelativityOne Staging Explorer ROSE
- D. File Transfer Protocol
Answer: C
Explanation:
The correct answer is D. RelativityOne Staging Explorer ROSE . Relativity's official documentation states that Staging Explorer enables you to rapidly transfer large amounts of data to and from RelativityOne .
It is specifically intended for high-volume transfer workflows and can be used to download files from your RelativityOne storage location to a local computer . That wording directly matches the question, making ROSE the exact documented tool for this scenario.
This is why the other options are incorrect. Simple File Download is not the primary enterprise-scale utility Relativity documents for rapid bulk transfer from RelativityOne storage. File Transfer Protocol is a generic technology term, not the RelativityOne tool identified by Relativity documentation for this workflow.
Relativity Integration Points RIP is used for moving and integrating data across systems and workspaces, but it is not the official RelativityOne utility described as the mechanism to rapidly move large data volumes between RelativityOne storage and a local machine. Relativity also reinforces ROSE's suitability for large datasets in its best practices and certification materials, which describe it as the tool for high-volume uploads and downloads in RelativityOne environments. From an RCA perspective, this is an important operational distinction because ROSE is purpose-built for staging and large-scale data movement, making it the correct answer.
NEW QUESTION # 39
What operator is invalid in a text box filter?
- A. AND
- B. > =
- C. IS SET
- D. NOT
Answer: D
Explanation:
The correct answer is D. NOT . Relativity's Filters documentation for text box filters lists the valid operators as AND, OR, IS SET, IS NOT SET, BETWEEN, =, > =, and < = . Since NOT does not appear in that valid operator list, it is the invalid choice among the options provided.
This is a useful distinction because Relativity supports NOT in some other search contexts, such as dtSearch or advanced filtering patterns, but the question asks specifically about a text box filter operator. In that exact context, AND , IS SET , and > = are valid, while NOT is not. Therefore, the invalid operator for a text box filter is NOT .
NEW QUESTION # 40
You're provided a list of key terms that include noise words by the supervising attorney. What step should you take before running a Search Terms Report?
- A. Replace noise words in the key terms with asterisk *.
- B. Remove key terms from the dtSearch index noise words.
- C. Add key terms to the dtSearch index alphabet file.
- D. Remove noise words from the key terms.
Answer: B
Explanation:
The correct answer is D. Remove key terms from the dtSearch index noise words. Relativity's dtSearch documentation explains that if a word in the search phrase is part of the noise words list, and that word is important to the search, you must remove it from the dtSearch noise words list and then rebuild the index. The documentation gives this exact type of guidance for terms like "and" when the term must be treated as part of the actual phrase instead of being ignored.
This makes options B and C incorrect because changing or deleting the attorney's search terms would alter the intended search logic rather than making the index capable of respecting the requested phrase. Option A is also incorrect because the alphabet file is for searchable characters and tokenization behavior, not for managing ignored noise words. Therefore, before running the Search Terms Report, the correct step is to remove those key terms from the dtSearch index noise words list and rebuild the index if needed.
NEW QUESTION # 41
How is the default tab in a workspace determined?
- A. The Documents tab is always the default tab in a workspace.
- B. It is the tab that has been set as the default tab.
- C. It is the tab with the lowest order number.
- D. The Admin tab is always the default tab in a workspace.
Answer: B
Explanation:
The correct answer is A. It is the tab that has been set as the default tab. Relativity's Tabs documentation states that a tab has a Set as Default Tab toggle, and when this is turned on, that tab serves as the workspace' s default tab. Reviewers logging into the workspace are taken to that default tab. Relativity also notes that if a reviewer does not have access to that default tab, the user is directed to the Documents tab instead.
This means the default tab is not determined merely by tab order. The lowest order number affects where a tab appears in the sidebar, but not which tab is designated as the workspace default. The Admin tab and Documents tab are not always the default either; Documents only acts as the fallback if the user lacks access to the selected default tab. Therefore, the correct answer is that the default tab is the one explicitly set as the default tab .
NEW QUESTION # 42
What is an available action in Automated Workflows?
- A. Scheduled Run
- B. Build dtSearch Index
- C. Manual Start
- D. Build a cluster
Answer: B
Explanation:
The correct answer is C. Build dtSearch Index . In Relativity, Automated Workflows consists of two major components: triggers and actions . Triggers determine when a workflow starts, while actions determine what task the workflow performs once it begins. Relativity's official Automated Workflows documentation lists Build dtSearch index as one of the available actions that can be added to a workflow. When selected, this action allows the workflow to automatically build a dtSearch index, either as a full build or incrementally depending on the configuration.
The other options are not actions. Scheduled Run and Manual Start are both documented by Relativity as trigger types , not actions. Scheduled Run starts a workflow on a defined daily, weekly, or hourly cadence, while Manual Start allows a user to launch the workflow by clicking the Manual Run button. Build a cluster is also not listed by Relativity as an Automated Workflows action. From an RCA perspective, it is important to distinguish triggers from actions because workflow design depends on choosing the correct combination of each. Administrators may configure a trigger such as Scheduled Run or Manual Start, and then assign one or more actions such as Run OCR Set, Run Imaging Set, Build Elasticsearch index, or Build dtSearch index .
Therefore, among the options provided, the only valid available action is Build dtSearch Index .
NEW QUESTION # 43
How can you ensure a video will be synced to a transcript?
- A. The video and text files must be uploaded separately and synced through a mass action.
- B. Import the video file as part of the larger .pst.
- C. The video must be synced to one .MP4 video and uploaded at the same time.
- D. Videos cannot be synced to a transcript.
Answer: C
Explanation:
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 .
NEW QUESTION # 44
What happens during the staging step of a production?
- A. Relativity assigns Bates numbers to documents.
- B. Relativity takes a snapshot of the data sources and checks for duplicate documents between data sources.
- C. Relativity displays a sample image showing how the branding is applied to documents in the production.
- 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.
Answer: B
Explanation:
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 .
NEW QUESTION # 45
You need a user to perform some admin operations, including creating groups, managing users, and assigning permissions. However, you do not want them to review the Processing or Production queues. How should you configure the user's permissions?
- A. Add the user to the System Admin group.
- B. Add the user to the Workspace Admin group.
- C. Add the user to the System Admin group and configure the System Admin group to restrict permissions to access Process and Production queues.
- D. Add them to an instance-level group with permissions to create groups, manage users, and assign permissions.
Answer: D
NEW QUESTION # 46
What is the default production sort order?
- A. Custodian
- B. Control number
- C. Family group
- D. Artifact ID
Answer: D
Explanation:
The correct answer is A. Artifact ID. Relativity's official Production Sets documentation states that in the Sorting section of a production, if no custom sort criteria are selected, the default sort order is Artifact ID , which Relativity describes as the load order of the documents. This is the platform's documented default for productions.
This is an important administrative detail because production sort order affects how documents are sequenced when a production is generated. Relativity also notes that when you apply a custom sort order, family groups are not kept together automatically , so administrators need to design sort strategies carefully if they want a specific production sequence. But absent any special configuration, Relativity defaults to Artifact ID.
The other options are not the documented default. Family group may be relevant in review workflows, but not as the production default sort order. Control number is also not the starting sort value because control numbers may be assigned independently of the production sort configuration. Custodian is a common field for review and QC, but again not the production default. Therefore, the correct answer is A. Artifact ID .
NEW QUESTION # 47
What is the recommended workflow for exporting produced PDFs with a corresponding load file?
- A. Run a PDF production export from the RelativityOne Staging Explorer ROSE.
- B. Export the production set as PDFs using Import/Export.
- C. Use the PDF mass action.
- D. Download PDFs from the Viewer.
Answer: B
Explanation:
The correct answer is C. Export the production set as PDFs using Import/Export. Relativity's official Import/Export documentation states that Import/Export is the recommended method for importing and exporting data for RelativityOne , and the production export workflow specifically supports exporting a production set load file with production files. The production export workflow is the documented method for exporting production sets and their associated deliverables in a structured, transferable form.
This makes it the best fit for the question's requirement: produced PDFs with a corresponding load file .
The PDF mass action is a separate document-level utility for creating PDFs from documents, natives, images, or produced documents, but it is not the standard production export workflow for packaging a production with its corresponding load file. Downloading PDFs from the Viewer is a manual review action, not a formal production export workflow. ROSE is used for large-scale data transfer to and from RelativityOne storage, but the product documentation positions Import/Export as the recommended export mechanism for production sets and related load files.
So, from a Productions and RCA workflow perspective, the recommended method is to export the production set as PDFs using Import/Export .
NEW QUESTION # 48
When using Simple File Upload to import new documents, what determines the Control Number?
- A. The name of the file.
- B. The Filename field of the document's load file.
- C. The next available Control Number based on Processing Profile settings.
- D. The next available Document ArtifactID value.
Answer: A
Explanation:
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.
NEW QUESTION # 49
When should you run OCR on a production?
- A. After a document is redacted.
- B. Before a production is exported.
- C. Before a production is run.
- D. After a production is exported.
Answer: D
Explanation:
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.
NEW QUESTION # 50
After adding a pie chart to a dashboard, what is one resulting action when you select multiple pieces of the pie?
- A. The document list will highlight the documents that meet the condition.
- B. The new configuration is automatically saved as a new dashboard.
- C. No other pivot charts can be changed.
- D. Your selection becomes a condition added to the search panel.
Answer: D
Explanation:
The correct answer is C. Your selection becomes a condition added to the search panel. Relativity's Pivot and dashboard documentation explains that pie charts support multi-select, typically using Ctrl + Click , and that selecting values from charts filters the document list. Relativity's Analytics guide further states that when you select values from a chart, a filter condition is set in the Search panel corresponding to your choice .
That matches option C most directly.
Option A is not the best answer because the effect is more than a temporary highlight; Relativity applies a filter condition to the active search context. Option B is unsupported by the documentation. Option D is also incorrect because dashboard configurations are not automatically saved as new dashboards merely by interacting with chart segments; dashboards must be explicitly saved by the user. Therefore, when you select multiple pieces of a pie chart, Relativity adds that selection as a condition in the search panel , which then drives the filtered results shown in the document list and related widgets.
NEW QUESTION # 51
What operation does the document re-production feature support?
- A. Replace a document that was produced as a placeholder with another placeholder.
- B. Replace produced images with a placeholder.
- C. Replace a document that was produced as native only with produced images.
- D. Replace produced images with a native.
Answer: B
Explanation:
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 .
NEW QUESTION # 52
What problem could you identify using the Imaging Warnings tab after imaging a set of documents?
- A. Possible cut-off content on imaged MSG or EML files.
- B. Native contains content that cannot be imaged.
- C. Native was not imaged because it is password protected.
- D. System was not able to image embedded images.
Answer: A
Explanation:
The correct answer is C. Possible cut-off content on imaged MSG or EML files. Relativity's official Imaging Warnings documentation states that the Imaging Warnings object identifies possible cut-off content on imaged MSG or EML files and stores that information. It further explains that users can review these items on the Imaging Warnings tab after imaging completes.
The other choices describe imaging failures or limitations, but they are not what the Imaging Warnings tab is specifically designed to identify. Password-protected failures and general non-imageable content are handled through other imaging or processing error mechanisms. The Imaging Warnings feature is much narrower and is specifically meant to flag the risk that content in imaged MSG or EML items may have been cut off in the rendered output. Therefore, the correct answer is C .
NEW QUESTION # 53
Any change to the priority of a job in the production queue also changes its priority in which other queue?
- A. OCR queue
- B. Branding queue
- C. Import/Export queue
- D. Processing and Imaging queue
Answer: B
Explanation:
The correct answer is C. Branding queue . Relativity's official Production queue documentation states that during a production job, Relativity sends a job to the branding queue for stamping redactions, headers, or other image modifications, and any change to the priority of a job in the production queue changes its priority in the branding queue . This is a direct match to the question.
This linkage exists because branding is a dependent production-stage activity. When administrators reprioritize a production job, Relativity keeps the related branding work aligned so that downstream stamping and production preparation happen in the proper order. The other queues listed in the answers are separate queue systems and are not documented as automatically inheriting production queue priority changes.
Therefore, from a Productions administration perspective, the queue whose priority is also changed is the Branding queue .
NEW QUESTION # 54
How do you move a job to the front of the Branding queue?
- A. Change the job's submitted date / time.
- B. Change the job's priority to the lowest value in the queue.
- C. Cancel and restart the job.
- D. Change the job's priority to the highest value in the queue.
Answer: B
Explanation:
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.
NEW QUESTION # 55
Why would Review Center charts show "Unknown User 1" for some coded documents?
- A. The project has not yet been prepared, so Review Center is not yet tracking reviewer coding decisions.
- B. There was an error encountered for that particular user and the queue must be re-prepared.
- C. A reviewer no longer has permissions to code documents in the project.
- D. A reviewer was originally part of the workspace and coded documents, but has since been removed from the workspace.
Answer: D
Explanation:
The correct answer is B. A reviewer was originally part of the workspace and coded documents, but has since been removed from the workspace. Relativity's official Review Center documentation explains that when documents were coded by reviewers who are not part of the current Relativity instance , those reviewers can appear in charts and tables as "Unknown User 1," "Unknown User 2," and so on. The documentation specifically notes that this can happen if a reviewer was removed from the workspace or if the workspace was archived and restored into a different instance. That directly supports option B.
The other options do not match Relativity's documented explanation. Losing permission to code is not the stated reason for the "Unknown User" label. Likewise, an unprepared project is a separate project-state issue and does not explain why specific prior coding activity would be attributed to an anonymous placeholder. An error requiring queue re-preparation is also not the documented cause of this naming behavior. From a case administration perspective, this is an important concept because administrators often manage workspace users, permissions, and lifecycle changes over time. If prior reviewers are removed, their historical coding may still appear in analytics or project monitoring views, but the user identity may no longer resolve normally. In that circumstance, Review Center surfaces those coding records under a label such as
"Unknown User 1."
NEW QUESTION # 56
What is true when transferring images from one workspace to another using Relativity Integration Points RIP?
- A. The RIP application must be installed in the destination workspace.
- B. The field mapping section is disabled because only the control number is needed.
- C. The metadata fields from your data source will be auto-mapped and migrated.
- D. The native file used to create the images must be included in the transfer.
Answer: B
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 .
NEW QUESTION # 57
When should you run OCR on a production?
- A. After a document is redacted.
- B. Before a production is exported.
- C. Before a production is run.
- D. After a production is exported.
Answer: D
NEW QUESTION # 58
What format should you use to search for a specific emoji by name in the Short Message Viewer?
- A. "Name"
- B. :Name:
- C. [Name]
- D. < Name >
Answer: B
Explanation:
The correct answer is B. :Name: . Relativity's RSMF-supported emoji documentation states that emojis in RSMF files display as text strings surrounded by colons , giving the example :smile: . That directly establishes the emoji short-name format used by Relativity for named emoji representations.
The Short Message Viewer documentation also confirms that users can search for emojis in conversations.
Since Relativity's own emoji naming convention is colon-delimited short names, the correct format for searching by name is :Name:. The other options use bracket, angle-bracket, or quoted forms that Relativity does not identify as the short-name syntax for emoji. Therefore, the correct answer is :Name: .
NEW QUESTION # 59
What option cannot be configured when you create a new production data source?
- A. The markup set to apply.
- B. Whether or not to burn redactions on the documents.
- C. The field to use for production numbering.
- D. The placeholder to apply.
Answer: C
Explanation:
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.
NEW QUESTION # 60
What is true when importing a LEF or .XMEF bundled transcript file from the Document object?
- A. Bundled transcript files are not supported in Relativity.
- B. Existing links to exhibits in the transcript are visible once completed.
- C. Exhibits need to be parsed out and uploaded separately.
- D. Exhibits are uploaded, but need to be linked manually.
Answer: B
Explanation:
The correct answer is D. Existing links to exhibits in the transcript are visible once completed. Relativity' s official Transcripts documentation states that supported bundle file types include .lef and .xmef . When a bundle is uploaded, Relativity extracts the transcript file and displays the extra files as exhibits. The documentation further states that existing links to exhibits in transcript files will be visible in the Viewer once they are uploaded to Relativity . That is a direct match to option D.
This makes the other options incorrect. Bundled transcript files are explicitly supported, so option A is wrong.
Exhibits do not need to be manually linked in the way described by option B when the transcript already contains those links; Relativity preserves and displays existing links. Option C is also incorrect because the documentation explains that the bundle upload process extracts the transcript and surfaces the additional files as exhibits, rather than requiring administrators to parse and upload them separately. From a case administration standpoint, this is useful because it streamlines transcript management and preserves exhibit relationships during import. Therefore, when importing LEF or XMEF bundled transcript files from the Document object, the true statement is that existing links to exhibits are visible once the upload is completed .
NEW QUESTION # 61
How can you secure a workspace from a user?
- A. By individually securing instance-level views from a user.
- B. By removing that user's security group from the workspace.
- C. By changing the security settings of the user's IP address.
- D. By excluding the workspace name from a user's profile settings.
Answer: B
Explanation:
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.
NEW QUESTION # 62
......
RCA Real Exam Questions and Answers FREE: https://examsdocs.dumpsquestion.com/RCA-exam-dumps-collection.html