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 project team member uploads a CSV file to CRM Analytics, and they notice a few records failed during the upload. The manager wants to view the error log generated so this can be fixed and uploaded again. The manager has the CRM Analytics administrator permission but is unable to download the error log details.
Why is the manager unable to download the log details?
In CRM Analytics, when a CSV file is uploaded and errors occur during the upload process, an error log is generated. However, only the user who uploaded the external data file can download the error log, even if other users have administrative permissions. This restriction ensures that only the user responsible for the data upload can access the details to resolve the issues.
In a dataset, there are multiple boolean fields. When displayed on any dashboard, the boolean fields should all be displayed in the same way: a value of true should result in the display of the word "Yes" in
green; a value of false should result in the display of the word "No" in red.
How should the consultant accomplish this?
A consultant is tasked with creating a dataset and a dashboard for a sales team. During the requirements gathering, it was highlighted that security of the data is important.
It was noted that the Opportunity object has organization-wide defaults set to Private with access via the role hierarchy. Sales wants to keep this security in place for the dashboard. Looking at the Opportunity data, the consultant sees that the VP of sales can have access to up to 20,000 records and is unsure if sharing inheritance can be used.
Which approach ensures data security for the new Opportunity dataset?
For ensuring that the security settings on the Opportunity object are appropriately replicated in the CRM Analytics environment, running the Sharing Inheritance Coverage Assessment is an effective strategy. Here's why:
Assessment of Inheritance Feasibility: This tool assesses whether sharing rules on the Opportunity object can be effectively inherited in the analytics environment, ensuring that the organization-wide defaults and role hierarchy are maintained.
Identification of Limitations: The assessment will identify any potential issues or limitations with inheriting sharing settings due to the large number of records (up to 20,000 for the VP of Sales), providing clear insights on how to proceed.
Guided Decision Making: Based on the outcome of the assessment, the consultant can make informed decisions about whether to directly inherit sharing or consider alternative strategies like flattening the role hierarchy or using security predicates.
A consultant has been asked to build and embed a dashboard in a Lightning page. Users should only be able to change the dashboard contrast and open Analytics Studio from the header of
the dashboard.
How should the consultant achieve this?
CRM Analytics users at Cloud Kicks are granted access to an app with specific dashboards. When trying to download a specific widget, they are unable to do so.
What is causing the issue?
As in the previous question, the issue is related to permissions. Users can be granted access to dashboards and apps, but if their permission set does not explicitly allow the 'Download Data' action, they will not be able to download the widget data. This is a common issue encountered when users have restricted permissions, especially in environments where security and data access are tightly controlled.
consultant is reviewing a model that is set to maximize the daily sales quantity of consumer products in stores, and they see this recommendation.
Which action should the consultant take?
Upon reviewing the data model and noticing the high correlation alert between 'Store' and daily sales quantity, the appropriate action is to verify with the client their expectations regarding the influence of the Store field on daily sales. Here's the rationale:
Understanding the Role of 'Store' in the Model: Before making any changes to the model, it's crucial to understand whether the 'Store' field is expected to be a strong predictor based on the business context. If the client expects that different stores inherently have different sales volumes due to factors like location, size, or customer base, this correlation may be both meaningful and desired.
Potential Data Leakage: High correlation warnings can sometimes indicate data leakage, where a predictor (like 'Store') might inadvertently include information about the outcome variable (daily sales quantity). It's essential to verify whether this correlation makes sense logically or if it's skewing the model predictions.
Client Consultation: Consulting with the client helps ensure that any modeling decisions align with their business knowledge and expectations. It's about validating the model against real-world expectations and ensuring it remains a useful tool for decision-making.
By taking these steps, the consultant not only adheres to best practices in data science by validating model inputs and their implications but also ensures that the model aligns with the client's business strategies and operational realities.
Universal Containers builds a new sales dashboard and wants to make sure account managers can access the dashboard while traveling.
What should the consultant consider doing in this process?
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?
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.
What is the purpose of the CRM Analytics Dashboard Inspector?
The CRM Analytics Dashboard Inspector is a powerful tool used to troubleshoot and optimize dashboards. Its primary function is to display the underlying SAQL (Salesforce Analytics Query Language) query executed for each widget. It helps users see the final query that is run and the corresponding results. This feature allows CRM Analytics consultants and developers to diagnose issues, optimize performance, and understand how data is being processed in the dashboard.
While the Inspector helps view execution times and identify bottlenecks, it does not automatically resolve performance issues (which is why option B is incorrect). It simply provides visibility into query performance and execution details, allowing the user to make manual optimizations.
