CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Salesforce
  5. ANC301

Free ANC301 Exam Braindumps (page: 9)

Page 8 of 30
PDF with 242 Questions

Which statement best describes how to ensure CRM Analytics dashboards are easily used across both desktop and mobile devices?

  1. Create multiple layouts and reorder all the widgets so that they fit nicely within the new default width
  2. Create multiple layouts and allow CRM Analytics to automatically select and organize dashboard contents to be optimal for the device type.
  3. Create multiple layouts, ensure the layout selectors match the device, and resize/hide widgets to ensure the content is appropriate for the device screen size.

Answer(s): C

Explanation:

To ensure that CRM Analytics dashboards are optimally usable on both desktop and mobile devices, creating multiple layouts tailored to each device type is crucial. Here's why Option C is the best approach:
Device-Specific Layouts: By creating specific layouts for each device type, you ensure that the dashboard contents are presented in a manner best suited to the screen size and interaction model of the device.

Layout Selectors: These are used to automatically display the appropriate layout based on the device accessing the dashboard, enhancing user experience without manual intervention. Widget Customization: Resizing or hiding certain widgets for specific device layouts ensures that the dashboard remains clean, uncluttered, and easy to navigate, regardless of the device used.



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?

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

Answer(s): A

Explanation:

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.



Universal Containers uses CRM Analytics to build dashboards for different departments: Sales, Service, and Marketing. Users in the same department have the same role and need to have access to the same dashboards. Dashboards for different departments use some common datasets with the same row-level security.

How should a CRM Analytics consultant address this need?

  1. Create one app for each department, put common datasets in the shared app, and use roles to share apps.
  2. Create one app for each department, put common datasets in the shared app, and use profiles to share apps.
  3. Create one app for each department, put common datasets in the shared app, and use permission sets to share apps.

Answer(s): C

Explanation:

For managing access to department-specific dashboards while leveraging common datasets, the best approach involves the use of apps and permission sets. Here's why:
App Segregation: Creating a separate app for each department (Sales, Service, Marketing) allows for tailored dashboards and datasets to be grouped by department, facilitating easier management and navigation.
Shared Common Datasets: Placing common datasets in a shared app ensures that all departments can access necessary data without duplication, maintaining consistency and reducing storage requirements.
Use of Permission Sets: Leveraging permission sets to control access to these apps is a flexible and scalable approach. Permission sets can be finely tuned to grant or restrict access based on user roles within the organization, and they can be easily adjusted as roles or organizational structures change. This structure not only ensures data security and appropriate access but also enhances the efficiency of managing CRM Analytics resources across different departments.



A CRM Analytics consultant is building a dashboard for Cloud Kicks that is embedded in a separate Lightning page called "Management Dashboard" using a CRM Analytics Dashboard Component. The system administrator and the contract manager should both have access. The system administrator is able to see the dashboard and the data, but the contract manager sees a blank Lightning page.
What is causing the issue?

  1. The consultant has set up component visibility for the dashboard for system administrators only.
  2. The consultant has set up a dashboard filter condition for data to be visible to system administrators only.
  3. The consultant has set up/enabled a `Hide on Error' feature for the dashboard while embedding it.

Answer(s): A

Explanation:

When embedding a CRM Analytics dashboard in a Lightning page using a CRM Analytics Dashboard Component, you must configure the component's visibility settings correctly to ensure that all relevant users have access. In this case, the issue arises because the system administrator can see the dashboard, but the contract manager cannot. The most likely cause is that the consultant has set the component visibility to display only for system administrators, which would prevent the contract manager from seeing the content. To resolve this issue, the consultant must modify the component visibility settings to include both the system administrator and contract manager profiles.


Reference:

CRM Analytics and Lightning Components






Post your Comments and Discuss Salesforce ANC301 exam with other Community members: