Explanation:

To allow users to view data but prevent them from exporting it, the consultant must ensure the user does NOT have the "Download CRM Analytics data" permission.
This specific system permission controls the user's ability to download the underlying data (as a CSV file) from a CRM Analytics lens or dashboard widget.
By withholding this permission, users can still access and interact with the dashboards (i.e., view the data), but the download and export options will be disabled, meeting the security requirement.

Incorrect Answers Explanation (A & C)

A. Export CRM Analytics data
While this permission sounds correct, the official and specific permission for downloading the underlying row-level data from a dashboard or lens is "Download CRM Analytics data" (Option B). "Export CRM Analytics data" is not the standard or primary permission used to govern this capability on dashboards and lenses.
C. View CRM Analytics Assets
This permission is a prerequisite for the users to be able to see the dashboards, lenses, and datasets in the first place. If the consultant were to exclude this permission, the users would not be able to view the data at all, which contradicts the requirement that they should be able to view the data.

References
Salesforce Help: Enable Downloading Data from CRM Analytics: This documentation specifies that the ability to "Download CRM Analytics Images and Export Filtered Data" is controlled by the "Download CRM Analytics data" user permission.
Salesforce Help: Learn about CRM Analytics Permission Set Licenses and User Permissions: This resource confirms that users need permissions like "View CRM Analytics Assets" to access and interact with the content.

Explanation:

CRM Analytics (formerly Tableau CRM) supports custom maps using GeoJSON files to visualize geographic data. While uploading GeoJSON files is supported via the UI, this functionality is restricted by permissions.

To enable GeoJSON uploads through the UI, the user must have the “Manage Analytics Custom Maps” system permission assigned via a permission set.

Without this permission, the upload option will not be visible or accessible—even if the user has other CRM Analytics permissions.

❌ Why the other options are incorrect:
Option B: There is no separate toggle in Analytics Settings labeled “Enable Custom maps with GeoJSON.” The feature is permission-gated, not setting-gated.
Option C: Uploading via API is possible, but not required. The UI supports GeoJSON uploads if the correct permission is granted.

🔗 References:
Trailhead: Enhance Data Visualization with Custom GeoJSON Maps
Salesforce Help: CRM Analytics Permissions Overview

Explanation:

✅ Correct Option: B
An SAQL query with a timeseries statement specifying Account Name as the partition and Y-M-W as the Date Cols ensures forecasts are generated at the weekly level for each customer. Partitioning by Account groups the data properly per customer, and the weekly (Y-M-W) date granularity aligns with CK’s need for weekly-level forecasting. This approach leverages SAQL’s built-in timeseries functions to produce accurate weekly forecasts.

❌ Option A
Partitioning by Opportunity Name may seem logical, but it will generate forecasts at the opportunity level, not at the customer level. This does not align with CK’s requirement for forecasts per customer. Using Opportunity Name as the partition would result in fragmented and overly granular forecasts that fail to summarize results at the customer level.

❌ Option C
Using Y-M-D (daily) as the Date Cols would generate forecasts at a daily granularity, which is not what CK requires. Additionally, while partitioning by Account Name is correct, combining it with daily granularity introduces excessive detail and could reduce forecast clarity, making it harder for users to track customer trends on a weekly basis.

Summary:
To create a weekly forecast per customer, CK should partition the timeseries by Account Name (customer) and set the date columns to Y-M-W for weekly granularity. This setup aligns perfectly with the business requirement of weekly-level forecasts per customer, avoiding unnecessary detail at the opportunity or daily level.

Reference:
Salesforce Help: SAQL timeseries function

Explanation:

To ensure a dashboard is truly usable on mobile devices, the consultant must actively design for it, not just assume automatic resizing will suffice. The key step is to use the Dashboard Editor's layout preview feature, specifically setting a target phone width to simulate real devices. This allows for deliberate widget arrangement, ensuring critical metrics are visible and accessible without scrolling for account managers on the go.

✅ Correct Option: A. Set the optimal Dashboard width for the Phone layout to get a more accurate preview.
This is the correct action. CRM Analytics allows a dashboard designer to explicitly set a custom width (in pixels) for the phone layout preview. This is crucial because simply relying on automatic optimization may not account for all device sizes. Manually setting a specific phone width (e.g., 375px for an iPhone) allows the consultant to precisely arrange widgets for that form factor and get a true-to-life preview during the design process.

❌ Incorrect Option: B. Make sure the dashboard automatically is optimized for mobile viewing.
This is partially true but incomplete and passive. While CRM Analytics dashboards are responsive by default, meaning they automatically adjust to screen size, this automatic process can often lead to a suboptimal user experience on small screens if the dashboard isn't actively designed for it. Relying solely on automatic optimization without proactively using the layout preview tools often results in horizontal scrolling or poorly arranged widgets on mobile devices.

❌ Incorrect Option: C. Enable mobile optimization in the analytics settings under Setup.
This is incorrect because there is no global "mobile optimization" switch to enable in Setup. Mobile functionality is inherent to the platform. The responsibility for ensuring a good mobile experience lies with the dashboard author, who must use the built-in phone and tablet layout preview modes in the Dashboard Editor to manually configure and test how widgets reflow for different screen sizes.

🔖 Reference:
Salesforce Help: Reports and Dashboards

Explanation:

“Tablet” or “Phone” layout—where only minWidth and maxWidth have been set—may be displayed on a desktop if the dashboard is embedded in a small frame, or if the browser window is small.

Why:
CRM Analytics selects a layout based on the rendered viewport/iframe size. When a dashboard is embedded in a narrow iframe or the browser window is reduced, device-specific layouts (like Phone/Tablet) can be triggered—even on a desktop. Salesforce notes that embedded views can default to a mobile/device layout depending on dimensions, and dashboard layouts use width constraints (minWidth/maxWidth) in their JSON.

Why not A:
There isn’t a special “dashboard” vs. “phone” property parity to make mobile behave “like desktop.” In CRM Analytics you define layouts (e.g., Default/Mobile) with properties such as minWidth/maxWidth—not a “dashboard” property for desktop and a “phone” property for mobile.
Why not B:
If no mobile-eligible layout matches, the dashboard doesn’t throw a mobile error; it falls back to another layout based on size. The issue is layout selection, not an error condition on mobile while staying fine on desktop.

References:
Salesforce Help: Embedded view defaults to Mobile layout in Browser (layout chosen by embed size).
Salesforce Dev Docs: gridLayouts Properties (use of maxWidth/minWidth in layout selection/arrangement).
Salesforce Dev Docs: Dashboard JSON Overview (how layouts are defined in dashboard JSON).