Salesforce Consumer-Goods-Cloud-Accredited-Professional - Consumer Goods Cloud Accredited Professional (AP-204)

Promotion Product, Promotion Channel, Retail Store KPI, and Retail Visit KPI are four objects that have promotions associated with them using the Consumer Goods Cloud Data Model. These objects help users to define, execute, and measure promotions in retail stores. They are:

Promotion Product, which represents a product that is part of a promotion.

Promotion Channel, which represents a channel or segment where a promotion is applicable.

Retail Store KPI, which represents a key performance indicator that measures how well a retail store is performing against a specific promotion goal or target.

Retail Visit KPI, which represents a key performance indicator that measures how well a field rep executed a promotion during a store visit. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 30-31.

Salesforce Communications Cloud (formerly Vlocity Communications) provides a set of out-of-the-box omnichannel capabilities specifically designed to support buying, managing, and modifying telecom services across web, mobile, partner portals, and agent-assisted channels. Public Salesforce documentation describes two major components that enable this: Digital Commerce APIs and the Digital Commerce SDK.

Digital Commerce APIs (Option A)

Salesforce provides a full suite of REST-based Digital Commerce APIs that expose CPQ functions such as:

Product discovery

Product configuration

Pricing and promotions

Cart creation and management

Order submission

These APIs are channel-agnostic and built for web portals, mobile apps, in-store kiosks, and agent desktops, making them ideal for United Telecom’s requirement to support multiple sales and self-service channels. They leverage standardized product and pricing logic directly from the Enterprise Product Catalog, ensuring consistency across all channels.

Digital Commerce SDK (Option B)

The Digital Commerce SDK complements the APIs by providing reusable UI components, templates, and client-side tools to rapidly build modern commerce experiences. It supports Lightning, LWC, and headless storefronts, enabling companies to create branded, high-performing customer experiences with minimal custom code. This SDK allows UT to deliver responsive and consistent digital buying flows without building UI logic from scratch.

Options C (Cart-based APIs using OmniOut) and D (Custom APIs using LightningOut) involve custom or integration-heavy approaches that are not needed when out-of-the-box Digital Commerce capabilities already provide a complete omnichannel solution.

Therefore, the two correct out-of-the-box capabilities for multi-channel customer experience in Communications Cloud are A and B.

Store Products are integral to various tasks in Consumer Goods Cloud, including inventory and promotion checks, as well as search and scan functionalities.

In the Consumer Goods Cloud data model, several objects are linked to the Product2 object. These include Assortment Product, Assessment Task Product, and Promotion Product. This linkage is essential for comprehensive product management within the Consumer Goods Cloud.

For B2B telecom companies dealing with complex configurations exceeding 1000 line items, the only Salesforce Communications Cloud solution purpose-built for performance, scalability, and large enterprise quoting is Enterprise Sales Management (ESM).

ESM enhances the CPQ experience by supporting:

Extremely high cart volumes (hundreds to thousands of lines)

Multi-site, multi-location enterprise networks

Enterprise-grade discounting and contract structures

Scalable pricing, validation, and asset handlings

Better separation of commercial vs. technical configurations

Options A, C, and D do not address enterprise-scale CPQ needs with thousands of line items. Large Account Sales Management focuses on account planning, not CPQ performance. Multiplay Subscription Management and Multi-site CPQ do not solve the scalability challenge.

For auditing coolers, a new custom Task Type would be most appropriate, as it allows the creation of a task specifically tailored to the unique requirements of cooler audits.

In Communications Cloud, the single source of truth for commercial and technical products is the Enterprise Product Catalog (EPC). For external systems—like distributors’ CRMs—to consume product specifications, offerings, attributes, technical details, and bundled components, Salesforce provides EPC REST APIs.

These APIs expose:

Product Offerings

Product Specifications

Commercial & technical attributes

Versions

Prices (optional depending on configuration)

Relationships and hierarchies

They are designed explicitly for external catalog synchronization, making them the ideal starting point for distributors to pull up-to-date product definitions.

Why others are incorrect:

A (Product2 APIs): Product2 is not used for Communications Cloud catalog; EPC uses Vlocity EPC objects.

B (TMF620): Salesforce EPC is not natively TMF620 compliant. TMF620 requires a mediation layer; using EPC APIs directly is the recommended starting point.

D (getCartProducts): CPQ APIs require a cart context and do not expose full catalog specs.

To keep track of the inventory of the samples in the field, Alpine can create delivery tasks for the distributors and monitor their on hand inventory for the sample Product’s Stock Keeping Unit (SKU). A delivery task is a type of action plan task that allows a field rep to deliver products to a retail store. A product SKU is a unique identifier for a product that can be scanned and tracked in inventory systems. By creating delivery tasks and monitoring product SKUs, Alpine can ensure that the distributors have enough samples to distribute and also track how many samples have been delivered to each store. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 28-29.

Two primary use cases for performing an in-store survey are:

Gathering feedback from customers, consumers, shoppers, and staff. An in-store survey can be used to collect feedback from various stakeholders who interact with the products or services offered by the consumer goods company. For example, an in-store survey can ask customers about their satisfaction, preferences, or suggestions; consumers about their awareness, perception, or loyalty; shoppers about their behavior, motivation, or barriers; and staff about their challenges, needs, or opinions.

Gathering data on promotions, inventory requirements and product quality. An in-store survey can be used to collect data on various aspects of the product performance and availability in the retail store. For example, an in-store survey can ask about the compliance, effectiveness, or impact of promotions; the demand, supply, or replenishment of inventory; and the condition, quality, or issues of products