Salesforce Certified Data 360 Consultant free question 2 / 10 · Domain 2: Data 360 Setup and Administration
You want to ingest quick text and macro usage records (QuickTextUsage and MacroUsage) from a Service Cloud org into Data 360. Before creating the data stream, which preparation does the Help article give for these two objects?
- These two objects default to Public sharing for the org, so leave the sharing settings alone and add read on the objects to the Data 360 connector's permission set
- Even if read access is granted in a permission set, these two objects default to Private sharing, so change the default internal access to Public Read Only
- Leave the default internal access as Private, and use a sharing rule to share the records of the two objects with all users as read-only
- Even though both default to Private, granting View All Records on the connector's permission set lets you ingest them without changing the sharing settings
Show the answer and explanation
Answer: B
Why this is correct
The article says some objects, such as QuickTextUsage and MacroUsage, have their sharing access set to Private by default. To ingest them into Data 360, you change the object's default internal access to Public Read Only in the organization-wide defaults. The steps are to open Sharing Settings in Setup and change it from Edit on the organization-wide defaults. A System Administrator profile or the Data Cloud Architect permission set can make this change.
Why the other options are wrong
"Leave the default internal access as Private, and use a sharing rule to share the records of the two objects with all users as read-only" … The measure the article gives is not a sharing rule. It changes the default internal access itself to Public Read Only; leaving it Private and adding a sharing rule is not a procedure in the article.
"These two objects default to Public sharing for the org, so leave the sharing settings alone and add read on the objects to the Data 360 connector's permission set" … These two objects are Private by default, so the premise of a public default is wrong. Adding read access on a permission set without changing the sharing settings is not the preparation the article gives.
"Even though both default to Private, granting View All Records on the connector's permission set lets you ingest them without changing the sharing settings" … The article does not offer View All Records on a permission set as a way to compensate for a Private default. To ingest them, you change the org's default internal access to Public.
How this differs from object permissions
The permissions that let Data 360 read CRM objects and fields are explained on a separate page (Enable Permissions for Salesforce CRM Objects and Fields). QuickTextUsage and MacroUsage need, in addition to that, the preparation of changing the org's sharing default to public.