Explanation:

This is the correct approach in CRM Analytics (formerly Tableau CRM / Einstein Analytics). When you configure the schedule for a recipe, the Event-based option allows you to automatically trigger the recipe to run immediately after a specific event completes.

For this scenario:
You would navigate to the recipe's scheduling settings.
Select Event-based scheduling.
Choose the option to run the recipe after the External Connection Syncs (and select the specific Google BigQuery connection that needs to finish).

This ensures that the recipe only starts processing the data and generating the updated dataset after the external data sync from Google BigQuery has successfully finished loading the new data into CRM Analytics, guaranteeing the dashboard data is fresh.

Incorrect Answers and Why
B. Create 3 Salesforce flow to trigger the recipe to run once the connection sync has finished running.
While Salesforce Flow can be used to trigger certain CRM Analytics actions via API, it is an overly complex and custom-code approach for a task that is natively supported by the CRM Analytics scheduling interface.
The standard, no-code, and recommended solution is the Event-based scheduling feature within the CRM Analytics Data Manager.

C. Check the scheduled date/time of the sync and schedule the recipe to run 15 minutes after the start time of the sync.
This is an example of Time-based scheduling.
This approach is unreliable because it does not account for the variable duration of the data sync. If the BigQuery sync runs late (e.g., due to a large data volume or external network issues), the recipe will run on stale data 15 minutes after the scheduled start time. If the sync runs very fast, the recipe might run later than necessary.
Event-based scheduling (Option A) is specifically designed to solve this dependency problem by ensuring the recipe waits for the sync to complete successfully, regardless of how long it takes.

References
The scheduling functionality in CRM Analytics is documented in Salesforce Help. The concept of event-based scheduling allows jobs (like recipes or dataflows) to run only after a prerequisite job (like a data sync or another recipe/dataflow) has successfully completed.
Schedule a Recipe to Run Automatically - Salesforce Help (Mentions time-based and event-based scheduling)
Use Event-based Scheduling with External Connections (Beta) - Salesforce Help (Highlights the feature for external connections)

Explanation:

This question tests the consultant's understanding of how to manage the refresh schedule for an entire templated app and its associated data pipeline in CRM Analytics.

Why C is Correct:
Templated apps (like Sales Analytics) are designed as integrated, pre-built solutions. When you install such an app, it creates a complex, interdependent set of assets (dataflows, recipes, datasets, lenses, dashboards, and Einstein Discovery models). The App Install History page provides a centralized "master schedule" for the entire app. Scheduling from this location ensures that all the underlying components run in the correct, managed sequence. Scheduling the app itself guarantees that dataflows run first to bring in raw data, then recipes transform it, and finally, any dependent Einstein Discovery models are retrained—all automatically and in the right order.

Why A is Incorrect:
While technically possible, this is a highly inefficient, error-prone, and non-scalable approach. Manually scheduling each individual asset (every recipe, dataflow, connector, and Einstein model) is tedious. More importantly, it breaks the managed dependencies. You risk a recipe trying to run before its source dataflow has finished, or an Einstein model retraining before its source dataset is updated, leading to data inconsistencies and failures.

Why B is Incorrect:
This is an improvement over option A but is still incomplete. Scheduling only the recipes and dataflows would update the core datasets. However, it would not automatically trigger the refresh of the Einstein Discovery models and prediction definitions. These are separate assets that rely on the updated datasets. Using the App Schedule is the only method that encompasses the entire pipeline, including Einstein assets.

Key Concept
Managed App Schedules: The key concept here is that a templated app is a managed package of analytics content. The platform provides a top-level scheduling mechanism (App Install History) specifically to handle the orchestration of all its components. This is the Salesforce-recommended and most robust method for ensuring a consistent and reliable data refresh for the entire application.
Orchestration: A critical part of a consultant's role is understanding data pipeline dependencies. The App Schedule handles the orchestration automatically, eliminating the need for complex manual workflow management.

Explanation:

Providing access to CRM Analytics is a license and permission-based process, not a profile or app-sharing one. The system administrator must assign the specific "CRM Analytics User" permission set license and the accompanying permission sets to the new manager's user record. This automatically grants them access to the platform and makes the Analytics Studio app available in their App Launcher.

✅ Correct Option: A
This is the correct method. Access to Analytics Studio is granted by assigning the pre-defined "CRM Analytics User" permission set license and corresponding permission sets (e.g., "CRM Analytics User" or "CRM Analytics Explorer") to a user. This is the standard, scalable, and recommended practice for provisioning access to the Analytics platform, making the app appear in their App Launcher.

❌ Incorrect Option: B
This is incorrect. The Analytics Studio app is not shared directly to profiles like a custom app or a record. Access is controlled exclusively through permission sets and licenses. The profile itself may contain foundational permissions (like "Api Enabled"), but the specific feature access is unlocked by the Analytics-specific permission set.

❌ Incorrect Option: C
This is an inefficient and non-standard practice. While a profile might be associated with users who have analytics access, the enabling factor is the permission set assignment, not the profile itself. Administrators should assign the necessary permission sets to the user's existing profile rather than changing their entire profile, which could affect access to other critical system features and permissions.

🔖 Reference:
Salesforce Help: Assign CRM Analytics Permission Sets to Users

Explanation:

This question tests a critical and specific nuance of how CRM Analytics handles currency conversion in a multi-currency Salesforce org during data synchronization.

Why B is Correct:
In a multi-currency org, the Amount field on the Opportunity object is a roll-up that automatically converts the value into the corporate currency defined in the org's currency settings. When the CRM Analytics data sync runs, it connects to Salesforce using a specific user, known as the Integration User. The value of the Amount field that is extracted and landed in the initial dataset (OpportunityDataSet) will be the value converted to the Corporate Currency, which is effectively the currency of the Integration User for the purpose of the data extraction.

Why A is Incorrect:
The connected user's personal currency is irrelevant during the data synchronization phase. The dataflow/recipe runs on a schedule using the system's Integration User, not the individual business user who will later view the dashboard. User-specific currency conversion is a function that can be applied later, in a lens or dashboard, but the base data stored in the dataset is fixed at the corporate currency from the time of the sync.

Why C is Incorrect:
This option is vague and misleading. While there is a CurrencyIsoCode field on the Opportunity that records the currency of the transaction, the standard Amount field itself is already a converted value (to corporate currency). The dataset will contain both the corporate-currency Amount and the CurrencyIsoCode code, but the numeric value of Amount that is directly usable for aggregation will be in the corporate currency.

Key Concept
Multi-Currency Behavior: In a multi-currency Salesforce org, standard money fields like Opportunity.Amount are stored and reported in the Corporate Currency. This behavior is consistent and is what the CRM Analytics data sync captures.
Integration User Context: The data sync operates under the security and functional context of the Integration User. For multi-currency data, this means the sync pulls the corporate currency values.
Dynamic Currency Conversion in Dashboards: If there is a requirement to show amounts in a user's personal currency, this must be handled within CRM Analytics using features like dynamic currency conversion in a dashboard, which performs the conversion on-the-fly based on a live exchange rate and the viewing user's personal currency setting. The base dataset, however, remains in the corporate currency.

Explanation:

Correct Answer (A):
The connection mode directly impacts how data is synced. There are two primary modes for Salesforce connectors:

Full Sync: This mode brings in all records every time the data sync runs. It's reliable but can be slow and resource-intensive, especially for large objects.

Incremental Sync: This mode only syncs new or updated records since the last sync. It's significantly faster and more efficient, making it the preferred method for large objects with frequent changes.

By evaluating the connection mode, the consultant can switch objects from Full Sync to Incremental Sync where appropriate. This is a critical step to improve performance and reduce sync time after unused fields have been removed. The consultant should also ensure the objects have a field that can be used for incremental sync, such as SystemModstamp or another date/time field.

Incorrect Answers:

B. Contact Salesforce Support to increase sync speed.
Reason: Salesforce Support does not have a "sync speed" button to toggle. Performance improvements are almost always achieved through optimization within the CRM Analytics environment, not by an external change from Salesforce. This option is not a viable solution.

C. Enable fast sync in analytics settings.
Reason: There is no "fast sync" setting in CRM Analytics. This option is a fabricated term. The actual performance optimization relies on the methods mentioned in option A, such as leveraging incremental sync.