Explanation:

When a Generalized Linear Model (GLM) produces unsatisfactory results, it typically indicates that the relationships in the data are non-linear, or that there are complex interactions between predictors that GLM (which assumes linearity) cannot capture. XGBoost (Extreme Gradient Boosting) is an ensemble tree-based algorithm that excels at capturing non-linear patterns, interactions, and high-dimensional relationships. It generally outperforms GLM on most structured/tabular datasets, handles missing values well, and provides better predictive accuracy through boosting and regularization. For the CRM Analytics/Einstein Discovery consultant, switching to XGBoost is the recommended next step when GLM underperforms, as it is the most powerful algorithm available in the platform for regression and classification tasks.

Why the others are wrong:

A (K-Nearest Neighbors – KNN):
KNN is a distance-based algorithm that can capture non-linearity, but it performs poorly on high-dimensional data, is sensitive to scale, and typically does not outperform XGBoost in business prediction scenarios. It is rarely used in Einstein Discovery for production models.

B (Support Vector Machines – SVM):
SVM can model non-linear relationships using kernels, but it is computationally expensive, less interpretable, and often underperforms compared to XGBoost on large, noisy business datasets. It is not a primary algorithm in Einstein Discovery's recommendation engine.

References:

Salesforce Help – "Einstein Discovery Algorithms": Lists GLM, XGBoost, and other algorithms; XGBoost is recommended for complex, non-linear patterns.

Einstein Discovery Best Practices Guide: Suggests switching to XGBoost if GLM results are unsatisfactory.

Explanation:

This question tests the understanding of how to assign CRM Analytics licenses and permissions efficiently and in accordance with Salesforce best practices.

Why C is Correct:
Permission sets are the standard and recommended way to grant granular access to features in Salesforce without modifying user profiles. In this scenario, the client has three distinct user personas:
Builders (3 users): Need CRM Analytics Data Manager and CRM Analytics Dataflow Manager permissions to build datasets and dashboards.
Dashboard Creators (15 users): Need CRM Analytics Creator permission to create dashboards but not manage datasets.
Viewers (~982 users): Need CRM Analytics Consumer permission to only view dashboards.

The consultant should recommend creating three separate permission sets, each containing the corresponding CRM Analytics permission license (Data Manager, Creator, or Consumer). These permission sets are then assigned to the respective users. This is scalable, manageable, and follows the principle of using permission sets for functional access rather than creating multiple profiles.

Why A is Incorrect:
App permissions (Viewer, Editor, Manager) control what a user can do within a specific Analytics app (e.g., view, modify, or manage the app's dashboards and datasets). However, these permissions are secondary. A user must first be assigned a CRM Analytics permission license (via a profile or permission set) to even log in to the Analytics Studio. You cannot assign app permissions to users who do not have a base license. Option A addresses the second step without solving the fundamental licensing requirement.

Why B is Incorrect:
While creating three new Salesforce profiles would technically work, it is considered a poor practice and is not scalable. Profiles are complex and control a very wide range of system permissions and settings across the entire Salesforce org. Creating multiple profiles for the sole purpose of managing CRM Analytics access is an administrative burden and can lead to unnecessary complexity in the overall user management system. Permission sets are the modern, flexible, and recommended tool for this specific purpose.

Reference
Salesforce Help: Assign CRM Analytics Permissions Licenses
This documentation outlines the process, stating: "You grant access to CRM Analytics by assigning permission sets that contain CRM Analytics permissions licenses to users." It explicitly recommends using permission sets to assign the core licenses: CRM Analytics Consumer, CRM Analytics Creator, CRM Analytics Data Manager, and CRM Analytics Dataflow Manager.

Key Concept: The process is a two-step assignment:

License Assignment: A user gets a functional license (Consumer, Creator, etc.) via a Permission Set.
App-Level Permissions: After being licensed, the user is then granted specific permissions (Viewer, Editor, Manager) within individual Analytics apps to control what they can see and do inside that app.

Explanation:

In CRM Analytics, only assets (dashboards, lenses, datasets, dataflows) that are stored in a Public App or Shared Folder can be included in a change set for deployment to another org. Assets that reside in a Private App (an app created by a user and not shared with others) are not visible in the change set component list because they are tied to the individual user's private context and lack the necessary metadata visibility for org-wide deployment. To make the dataflow and dataset available for change sets, the administrator must first move the assets to a Public App (or a shared folder) and ensure they have the appropriate metadata visibility.

Why the others are wrong:

A (Does not have system administrator permission):
If the user lacked System Administrator permissions, they wouldn't be able to create change sets at all. The issue is not permission—it's the location of the assets.

C (Does not have access to the assets):
The administrator likely has access to the assets (they can see them in CRM Analytics), but access alone does not make them available in change sets. The assets must be in a public, org-wide location.

References:

Salesforce Help – "Deploy CRM Analytics Assets with Change Sets": States that only assets in public apps or shared folders are available for change sets.

CRM Analytics Implementation Guide:
Private app assets are excluded from metadata deployment.

Explanation:

In CRM Analytics, data sync and dataflows/recipes are two distinct but complementary processes for bringing data into datasets:

Dataflows/Recipes – Extract, transform, and load (ETL) data from Salesforce objects, external sources, or uploaded files into datasets.

Data Sync – A separate feature that creates a replicated copy of Salesforce object data (standard/custom objects) directly into CRM Analytics, keeping it in near-real-time sync with the source.

When both are enabled, the refresh sequence is: Dataflow/Recipe runs first to process and transform the data, and then Data Sync runs to update the replicated Salesforce object data. Only after both complete successfully does the dataset reflect the latest data, and the dashboard automatically updates with the refreshed dataset. Therefore, the dashboard is refreshed when the entire pipeline (dataflow → data sync) completes.

Why the others are wrong:

B (When the viewer clicks Refresh):
The dashboard Refresh button reloads the current dataset's cached data but does not trigger a new dataflow/recipe or data sync job. It only refreshes the visualization with already-available data.

C (Data sync first, then dataflow):
The order is incorrect. Dataflows/recipes process and transform data, and data sync replicates raw Salesforce data. The transformation (dataflow) typically runs on the synced data, so data sync must be available first—but the completion sequence for a full refresh is dataflow → data sync (not the reverse) when both are scheduled together.

References:

Salesforce Help – "Data Sync and Dataflows": Explains the relationship and execution order.

CRM Analytics Data Preparation Guide: Data sync and dataflows can be used together; dataflows process data after ingestion.

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.