Free Practice Questions for Salesforce Consumer-Goods-Cloud-Accredited-Professional Exam

KPI Type is a required field for setting up Retail Store KPIs. Retail Store KPIs are key performance indicators that measure how well a retail store is performing against a specific goal or target. The KPI Type defines the type of metric that is being measured, such as share of shelf, out of stock, or promotion compliance. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 30.

A possible reason for failing all the test cases related to delivery tasks is that the tester did not have the lightning direct store delivery Permission Set added. A Permission Set is a collection of settings and permissions that grant users access to various tools and features. The lightning direct store delivery Permission Set is required for users who need to use the delivery task functionality and related objects, such as product transfers and shipments. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 29.

Before migrating Communications Cloud data to a new org, Salesforce documentation stresses two critical readiness steps:

A. Ensuring all required fields and data points exist in the target org

Communications Cloud relies on a complex data model (EPC, Order Mgmt, Pricing, Attributes, EPC Projects, Fulfillment records). The target org must have all necessary fields and object configurations before importing data.

D. Metadata must match before migration

Migration cannot succeed unless product specs, attributes, price lists, technical product models, decomposition mappings, and orchestration metadata exist in the target org.

Metadata alignment is the #1 prerequisite for moving Communications Cloud data.

Incorrect options:

B: Running validation during migration is risky and not recommended.

C: Testing in production is strictly prohibited.

Uploading an image of the planogram is essential for enabling field teams to perform planogram checks, providing a visual reference for in-store product placement and arrangement.

As part of digital transformation, Salesforce strongly recommends consolidating all product definitions into a single Enterprise Product Catalog (EPC) within Communications Cloud. EPC becomes the system of record for all commercial and technical products across channels.

To expose this single catalog to external sales channels, Salesforce provides Digital Commerce APIs, which deliver:

Product discovery

Attribute & configuration rules

Pricing & Promotions

Availability & context-driven offerings

These APIs allow web channels, portals, mobile apps, and external systems to retrieve catalog data in real time without duplicating product definitions. This removes the need for separate catalog maintenance and guarantees consistency across channels.

Option A uses Cart APIs, which only apply once a product is already in the cart. It does not expose catalog discovery.

Option C (periodic sync) is not recommended—Salesforce discourages dual catalogs.

Option D (new catalog system) adds unnecessary complexity.

Salesforce Communications Cloud supports product dependencies through Relies-On Relationships. These relationships enforce commercial dependencies (e.g., Roaming requires Voice Service) and guide technical decomposition so that dependent products are fulfilled together.

To satisfy the requirement that the provisioning system receive a single activation request for both Voice Service and Roaming, the dependency must be modeled using:

✔ Relies-On Relationship

This ensures the commercial cart enforces prerequisite activation rules—Roaming cannot be purchased or activated without Voice Service.

✔ Decomposition Scope = Order Item

When decomposition scope is set to Order-Item for the technical product relationship, both commercial products decompose into a single technical activation request for fulfillment. This is the exact Salesforce-recommended pattern when dependent commercial products must trigger one consolidated orchestration/activation flow.

Why other options are incorrect:

A (Scope = Account): would merge across the whole account, not just the order.

C (Scope = Relies-On): no such decomposition scope exists; invalid choice.

D (Bundle Product + Multilevel Decomposition): bundling is not required, and it changes the commercial product structure unnecessarily.

In Salesforce Communications Cloud Order Management, orchestration steps execute through Apex-based orchestration jobs. When order volume rises sharply—as happens when additional sellers or regional teams begin submitting orders—the system may hit Salesforce’s platform limit for queued Apex jobs (50 × number of licensed Salesforce users). Once this limit is reached, orchestration fails.

Salesforce’s official scalability recommendation is to enable Platform Events for Orchestration. This switches Order Management from synchronous Apex-queue processing to asynchronous, event-driven orchestration, which drastically reduces reliance on Apex jobs. Platform Events allow OM to process far more concurrent orchestration steps without hitting queue limits and provide better throughput and resilience for enterprise-scale flows.

Options A and B are incorrect because Salesforce does not increase Apex job limits, and splitting orders is not a best-practice. Option D reduces automation and violates OM design principles.