Salesforce ANC-301 Exam Practice Test Instant Access

Question 1

A CRM Analytics consultant has been tasked with providing access to CRM Analytics for a few users. They should be able to view the data but unable to export it.

Which permission should the consultant make sure to NOT include?

AExport CRM Analytics data

BDownload CRM Analytics data

CView CRM Analytics Assets

Answer : B

Question 2

A CRM Analytics consultant is reviewing results from an Einstein Discovery story with a business user. They agree with the findings but notice that none of the fields used in the story have a correlation value greater than 4%. The client is now concerned that the model

may not be good enough to deploy.

Which action should the consultant take?

AA Identify additional data that may have a stronger relationship with the outcome variable.

BEdit the model accuracy settings and rerun it to evaluate the correlation.

CUse the appropriate algorithm and update the model.

Answer : A

Question 3

Universal Containers (UC) is rolling out CRM Analytics to its field sales that include dashboards withorder data from an external source.

UC has a well-defined role hierarchy where everyone is assigned to an appropriate node on the hierarchy. In addition, the order data has a reference to a Salesforce opportunity.

An individual sales rep should be able to view all orders that they own or as part of the account team or opportunity team. The sales manager should be able to view all orders for the entire sales team. Similarly, the VP of sales should be able to view orders for everyone who rolls up in that hierarchy.

The dataset has a field called Ownerld which represents the order owner.

Given this information, how should a CRM Analytics consultant implement the above requirements?

AAs part of the recipe, use a formula on the Roleid fild to create an attribute called 'ParentRolelDs' on the dataset, and apply the following security predicate: 'ParentRolelDs' == ''$UserRoleId'' || Owned\ == '$User,id\\,

BAs part of the recipe, use the flatten operation on the role hierarchy, create a multi-value attribute called 'ParentRoleIDs' on the dataset, and apply the following security predicate: 'ParentRoleIDs' == '$User.UserRoleld' || 'TeamMember.Id' '$User, Id' || 'Ownerld' == '$User.Id'.

CAs part of the recipe, use a multi row formula on the Roleld field to create an attribute called 'ParentRoleIDs' on the dataset, and apply the following security predicate: ''$User.UserRoleld'' || 'Ownerld' == ''$User.Id'.

Answer : B

In addressing the requirements of Universal Containers to ensure proper visibility of order data across different levels of the sales hierarchy, the use of a security predicate based on role hierarchies is paramount. Here's why Option B is the ideal approach:

Flatten Operation on Role Hierarchy: This operation is essential as it allows for the creation of a simplified or 'flattened' view of the hierarchical relationships within the organization. This flattened view enables the dataset to understand and respect the hierarchical structure in security implementations.

Creating a Multi-value Attribute ('ParentRoleIDs'): By creating this attribute, the recipe can hold multiple role IDs that a particular user has visibility permissions for. This is crucial in a hierarchical organization like UC where data visibility needs to cascade down the hierarchy.

Security Predicate: The predicate ('ParentRoleIDs' == '$User.UserRoleld' || 'TeamMember.Id' == '$User.Id' || 'Ownerld' == '$User.Id') effectively enforces that:

A user can see all orders where their role matches any of the role IDs in the 'ParentRoleIDs' list (hierarchical visibility).

A user can see all orders where they are specifically listed as a team member.

A user can see all orders where they are the owner.

This approach aligns with best practices for implementing row-level security in CRM Analytics, ensuring data visibility is managed correctly according to the defined organizational hierarchy and individual data ownership.

Question 4

Cloud Kicks has informed CRM Analytics developers that they have two scenarios with restricted row-level security.

The parameters being:

1. Non-CXOs and VPs working in EMEA can have access to EMEA records only.

2. CXOs and VPs should have access to all data irrespective of the region (APAC, EMEA, etc.).

Which sharing method works for this scenario?

ACreate two sets of dashboards; one for EMEA, and one for CXOs and VPs while filtering the dashboard on the region.

BUse a field on the user record like Department/Region, and apply row-level security based on that field.

CCreate two separate datasets; one for EMEA, and one for CXOs and VPs.

Answer : B

For Cloud Kicks' requirements regarding access to data based on roles and geographic regions, the most efficient and scalable approach is to implement row-level security using fields on the user record, like Department or Region. Here's the rationale for choosing this approach:

Scalability and Maintenance: By applying security rules based on user record fields, Cloud Kicks can manage access dynamically without needing to maintain multiple dashboards or datasets. This reduces administrative overhead and simplifies updates as roles or regional structures change.

Flexibility: Using a field on the user record to control access allows for easy expansion or modification of security policies as new regions or roles are added.

Simplicity: This method ensures a clear and straightforward security model that can be easily audited and understood by administrators and compliance teams.

Question 5

A CRM Analytics consultant has been asked to bring data from an external database as well as five external Salesforce environments into CRM Analytics. Twenty-five objects have been enabled from the local Salesforce connector.

The requirements are:

* 10 objects should be enabled from an external database

* 12 objects each from three of the external Salesforce environments

* 15 objects each from the remaining two external Salesforce environments

The consultant estimates each connector will, per object, bring between 1,000 and 1 million rows of data.

Which limit will be exceeded?

ATotal number of enabled objects

BSalesforce external connector number of synced rows

CStorage rows of data

Answer : A

In evaluating the scenario presented where multiple external sources and objects are being integrated into CRM Analytics, we need to consider the total number of enabled objects across all connections. Here's a breakdown:

10 objects from an external database

12 objects each from three external Salesforce environments, totaling 36 objects

15 objects each from two external Salesforce environments, totaling 30 objects

25 objects already enabled from the local Salesforce connector

This brings us to a total of 101 objects enabled, which may exceed typical limits on the number of objects that can be enabled in a CRM Analytics environment, depending on the specific Salesforce licensing and platform limits.

Question 6

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?

AThe Sales Rep is not provided access permission on custom field Demographic__c on the User object.

BThe security predicate needs to be updated as 'Ownerld' == 'sUser.id'' || 'Demography' = '$User.Demographic__c'.

CThe Analytics Security User is not provided access permission on custom field Demographic_c on the User object.

Answer : A

The issue with the security predicate not functioning as expected likely stems from a permissions issue related to the custom field Demographic__c on the User object. Here's a detailed explanation:

Field-Level Security: If the sales reps do not have access to the Demographic__c field, the security predicate which references this field cannot execute properly as the system cannot evaluate the predicate without accessing the field.

Permission Settings: Ensuring that the sales reps have the necessary permissions to view and use the Demographic__c field is crucial for the security predicate to function correctly.

Data Visibility: The security model in CRM Analytics relies heavily on the underlying data permissions in Salesforce. If these permissions are not correctly configured, the expected data visibility through CRM Analytics will not be achieved.

Question 7

A model created with a GLM algorithm produced unsatisfactory results.

When re-running the model, which type of algorithm should the consultant use to improve the results?

AK-Nearest Neighbors

BSupport Vector Machines

CXGBoost

Answer : C

Salesforce Implement and Manage CRM Analytics ANC-301 Exam Practice Test