Free Salesforce Consumer-Goods-Cloud-Accredited-Professional Practice Exam with Questions & Answers

Assigning the Shipment object to the user enables the listing of items in the delivery task, as this object tracks the movement of products from warehouses to retail locations.

ABC Telecom requires that assets be synchronized to their assurance platform immediately after fulfillment, and they operate in a high-volume wholesale environment (5,000+ orders per reseller/day and hundreds of concurrent users). Salesforce recommends event-driven, near-real-time integration for high-scale fulfillment notifications.

Platform Events are Salesforce’s native, scalable publish/subscribe mechanism designed for high throughput and low latency. When an order completes fulfillment, Communications Cloud can publish an event that external systems subscribe to. The assurance platform can then call the GetAsset API to retrieve the exact asset structure needed for assurance workflows.

This pattern is explicitly recommended in Salesforce high-throughput integration architectures because it:

Eliminates polling

Handles large transaction volume

Provides near-real-time sync

Decouples fulfillment from assurance systems

Scales horizontally across resellers

Option A (using OM orchestration) is synchronous and not optimal for high throughput.

Option B (on-demand REST pull) causes latency and excessive polling.

Option C (Bulk API) is batch-oriented, not real-time, and unsuitable for near-immediate updates.

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.

The object where a Consumer Goods Cloud Admin needs to establish the expected value for the planogram metrics is Assessment Indicator Definition. A planogram is a visual representation of how products should be arranged on a shelf. A planogram metric is a measure of how well the actual shelf image matches the expected planogram image. An Assessment Indicator Definition is an object that defines an indicator or metric that can be used to assess the performance or compliance of a retail store or an action plan task. By creating an Assessment Indicator Definition for the planogram metric, such as out of stock, share of shelf, or SKU facings, an admin can establish the expected value for that metric and use it to calculate the actual value based on the shelf image. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 23-24.

A Sales Manager is the user persona that manages day-to-day Retail Execution processes such as creating visits, creating tasks, and assigning visits to Field Representatives. A Sales Manager is responsible for planning and overseeing the retail activities of a team of field reps, as well as analyzing and reporting on the performance and compliance of the retail stores in their territory. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 18.

When performing a search in an inventory check task, only the products that are associated with the retail store are considered for the search. This is because the inventory check task is designed to verify the availability and quantity of products in a specific store location. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 28.

These components provide comprehensive information about promotions and inventory, vital for effective retail execution.

To track pricing changes, Salesforce recommends enabling Field History Tracking on Price List Entry, which logs:

Old price

New price

User

Time of change

This is the simplest way to review previous pricing.

Why others are wrong:

A requires custom triggers—not recommended.

C EPC Project history tracks metadata changes, not price list values.

D Versioning is for product specifications, not PLE prices.

During the High-Level Design (HLD) phase of a Communications Cloud implementation, Salesforce strongly recommends performing a storage assessment to ensure that data storage, file storage, and archival processes align with expected volumes. Public Salesforce architecture and data management guidance outlines three key tasks:

(A) Identify storage needs between data storage and file storage

Salesforce divides storage into Data Storage (records such as Accounts, Orders, Order Items, Subscriptions, Assets) and File Storage (documents, attachments, proofs, device images). A consultant must distinguish which objects consume which category because each impacts licensing and cost differently.

(D) Assess archiving strategy

Salesforce recommends establishing an archiving plan early to manage growth of high-volume objects (Orders, Order Items, Fulfillment Requests, Assets). Communications Cloud generates large order orchestration records, so storage must account for how data will be archived, purged, or externalized. This directly reduces storage consumption and improves performance.

(E) Calculate storage based on expected volumes and file requirements

Using volume estimates from HLD (records per month, attachment sizes, expected number of orders, subscriptions, assets), the consultant can calculate projected consumption for both data and file storage. This is standard planning guidance for Communications Cloud projects.

Options B and C are not part of Salesforce’s required steps for determining org storage needs. Analyzing legacy storage (B) is helpful but not required for Salesforce storage estimation. Considering an external storage system (C) is optional and not part of Salesforce’s recommended baseline steps.

The requirement is to introduce a limited-time offer that is available on the website (digital channel/DC APIs) and, once claimed, grants a 10% discount for three months.

This is the definition of a Promotion that uses a Time Plan to define the duration of the discount.

Promotion (A):

In Salesforce Industries CPQ, a Promotion is the container entity used to define a marketing offer that modifies the price of a product (in this case, a 10% discount).

The Promotion entity is what is typically exposed to digital channels (like the website via DC APIs) for customers to claim or qualify for. The search results confirm that Promotions are used to "apply temporary changes to product pricing, bundles, and product structure".

Time Plan (B):

The Time Plan is a sub-feature of Promotions (or Price Lists) that defines the duration for which the commercial change (the 10% discount) is active.

The requirement states the discount is only for "three months." A Time Plan is specifically configured to start the discount upon activation and automatically end it after the defined period (3 months), ensuring the billing system correctly handles the price change back to the original rate.

D (Discount) is a result of the configuration, not the feature itself. The discount value (10%) is defined within the promotion.

C (Offering) is a synonym often used for a product or bundle, but it does not specify the limited-time discount mechanism required.