最も有効な ANC-301 試験参考書

Universal Containers (UC) recently activated data sync in the CRM Analytics data manager. After running the sync, UC notices that the aggregate sum of a field within the company's dataset is different than what they manually calculated by summing the same data in the Salesforce object.
What is causing the issue with the newly synced data?

• A. Differences involving flow-updated fields
• B. Differences involving formula fields
• C. Differences involving trigger-updated fields

AW Computing will start using Tableau Online to report on some of its Salesforce data to users who do NOT have an SFDC license.
What is the first step the CRM Analytics consultant should take?

• A. Use MuleSoft to generate an API ta connect and push data from SFDC to Tableau.
• B. Select the output connection in the "write to" option of the recipe.
• C. Enable the Tableau output connection in the Analytics settings.

A dashboard designer at Cloud Kicks creates a dashboard in CRM Analytics. The designer notices fields display on the dashboard with their API labels, such as "AccountId.Industry", and wants to change this behavior.
The designer also notices that the fields and their order appear to randomly change when a values table is created.
What should the CRM Analytics consultant explain to help the designer?

• A. The field labels can only be changed in the widget properties in the dashboard edit mode.
• B. The default fields In a values table and the field labels can be modified in the dataset explorer.
• C. The default fields in a values table can be changed by reordering how fields appear in the JSON of the value table.

Universal Containers has a well-defined role hierarchy in Salesforce where everyone is assigned to an appropriate node. The accounts within their instance are categorized by their demography.
An individual sales rep should be able to view all accounts that they own. In addition, sales reps should be able to see any accounts where the value of the account demography matches the demography defined on their user record. A user could have more than one demography defined on their user record.
To meet this requirement, the CRM Analytics consultant has set up a security predicate of the existing 'Account' dataset as follows:

This, however, does not seem to be working as expected.
What is causing the issue?

• A. The Sales Rep is not provided access permission on custom field Demographic__c on the User object.
• B. The security predicate needs to be updated as 'Ownerld' == "sUser.id" || 'Demography' = "$User.Demographic__c'.
• C. The Analytics Security User is not provided access permission on custom field Demographic_c on the User object.

Universal Containers has a single dataset that contains the attainment and commission fields for all sales reps. Each sales rep should be able view the attainment data for each rep in their division. Each rep should only be able to see their own commission dat a.
Which option should a CRM Analytics consultant use to enforce this requirement?

• A. Add the sales organization to the attainment dataset access list to be able to view commission data.
• B. Create separate datasets for attainment and commission, and apply security Predicates and/or sharing inheritance.
• C. Utilize a single dataset and apply security predicates and/or sharing inheritance.