A Revenue Cloud Consultant is helping a customer service operations manager determine which product lines have the most order fallout. Which steps…

To analyze order fallout by product line, the consultant must enable the pre-built analytics application designed for this purpose. The correct procedure involves using the "Revenue Management Intelligence Setup" flow. This process requires configuring Data Cloud to ingest and process the necessary order and fulfillment data. Once the data connection and modeling are complete within Data Cloud, the consultant can then install the "Dynamic Revenue Orchestrator Analytics App," which contains the specific pre-configured dashboards for monitoring order fallout trends.

A: This option is incomplete. Simply enabling a setting in "Revenue Settings" is insufficient; the critical step of configuring the data source via Data Cloud is missing, which is a prerequisite for the app to function.

C: This describes a manual, custom-build process. While possible, the question asks how to enable existing dashboards. The standard and most efficient approach is to use the pre-packaged analytics app, not build one from scratch.

1. Salesforce Help, Set Up Revenue Management Intelligence: This document outlines the official setup process. It explicitly states the required steps are: 1. Enable CRM Analytics, 2. Assign Permission Sets, 3. Set Up a Connection to Data Cloud, and 4. Configure, Create, and Share the Revenue Management Intelligence App. This confirms that Data Cloud configuration is a mandatory step before creating the app. (See "Prerequisites" and "Set Up a Connection to Data Cloud" sections).

2. Salesforce Help, Dynamic Revenue Orchestrator Analytics Template: This guide describes the purpose of the app: "The Dynamic Revenue Orchestrator Analytics app template helps you analyze your order fulfillment process and identify fallout trends." It also states a key prerequisite: "Before you create a Dynamic Revenue Orchestrator Analytics app, set up Revenue Management Intelligence," reinforcing the multi-step process described in option B. (See "Get Started with Dynamic Revenue Orchestrator Analytics" section).