Salesforce Updated Consumer-Goods-Cloud-Accredited-Professional Exam Questions and Answers by tommie

The Tableau CRM for Consumer Goods Cloud dashboard that can provide the required data for a Field Sales Manager to determine which stores have a decline in Retail Execution KPIs and therefore need attention is the Store Performance Dashboard. The Store Performance Dashboard shows the performance and compliance of the retail stores in relation to their KPIs and promotions. The dashboard allows users to filter and analyze the data by various dimensions, such as store group, store location, product category, or visit date. The dashboard also displays metrics such as store compliance score, store revenue, store visits, and promotion compliance score. By using this dashboard, a Field Sales Manager can identify which stores are underperforming or non-compliant and take appropriate actions to improve their performance. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 37.

When assets are migrated into Communications Cloud, Salesforce best practices require performing a “No-Change MACD Order” after data loading. This process creates a technical MACD order that does not modify any service, but instead tests whether the MACD orchestration, decomposition, and asset-based ordering logic work correctly with the migrated asset records.

Salesforce documentation explains that migrated assets must be fully compatible with:

Order decomposition mappings

Technical product relationships

Association to Service Accounts, Billing Accounts, Premises

Child/parent asset hierarchies

Fulfillment Request Line generation

Change order processing (A → B transitions)

A no-change MACD validates that the migrated assets are structurally correct and “MACD-ready.” If this test fails, the migration did not properly map assets to the Communications Cloud asset data model.

Options A and C overlap with validation but do not address MACD execution. Option B (Inventory Items) is not created through MACD and is unrelated.

To visualize store visits in their territory for the day by their current status, an Account Manager can create a map layer using visits as the base object and color code the markers by status. A map layer is a visual representation of data on a map that can be filtered and customized. A visit is an object that represents a scheduled or unscheduled interaction between a field rep and a retail store. The status of a visit indicates whether it is planned, in progress, completed, or canceled. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 34.

In Salesforce Industries (formerly Vlocity) environments—especially relevant for Telecom, Media, and Energy—scenarios involving runtime price changes, agent-driven adjustments, and approval workflows are handled through Discounts, not Promotions or Context Rules. Discounts are specifically designed to allow flexible, rule-driven, and approval-controlled adjustments across the catalog, making them ideal when a company wants to equip call-center or retention agents with the ability to negotiate offers with outgoing customers.

Salesforce’s public guidance explains that Discounts support both manual and automated application methods. Administrators can enable runtime/manual discounts, specify discount types (percentage or fixed amount), and attach approval rules via the Industries Pricing Compliance framework. These can be targeted across the entire product catalog, specific product hierarchies, or only selected offers. This aligns perfectly with ABC Telecom’s requirement to apply pricing adjustments across the catalog and allow agents to make on-the-spot price changes.

While Promotions are useful for predefined marketing offers, they do not support agent-driven runtime flexibility. Context Rules automate pricing logic but do not provide agent-level manual control. CPQ Hooks require custom development and are not intended for business-driven discounting workflows.

Therefore, Discounts are the recommended and Salesforce-aligned feature for agent-controlled runtime adjustments, catalog-wide applicability, and approval process integration, exactly matching the needs of a telecom retention team.