Free Consumer-Goods-Cloud-Accredited-Professional Practice Test Questions (2026)

Explanation:
This is a decomposition conflict scenario. During decomposition, attributes from multiple commercial products (Internet, TV) are mapped to the same technical product (access line). If both source products have the same attribute name, the system must decide which value to use on the technical product.

Correct Option:

A. No errors will be returned; the value for "Installation Type" on the technical product will be set to the most recently modified attribute.
This is the standard decomposition behavior in Salesforce Industries. When multiple source attributes map to the same target attribute:

No design-time or run-time error occurs.

The system uses the last value processed (typically from the most recently modified or last-in-sequence line item).

This could lead to unpredictable results if the two offers have different values, so careful design is needed.

Why Others Are Incorrect:

B. An error at design time; an error will be returned while configuring the decomposition relationships because of the duplicate attributes.
The system does not throw a design-time error for duplicate attribute names during decomposition mapping. It allows the mapping but applies runtime logic (last value wins).

C. No errors will be returned; the "Installation Type" will be copied as empty/null after decomposition on the technical product.
The attribute does not become null. A value will be assigned (the last one processed). Empty/null would only happen if neither source provided a value.

D. An error at run time; no value will be assigned to the attribute "Installation Type" on the technical product.
No runtime error occurs. The system will assign a value (the last one), as explained in Option A.

Reference:
In Salesforce Industries (Communications Cloud) Order Management, decomposition maps attributes from commercial products to technical products. The "last value wins" rule for conflicting mappings is a documented behavior in decomposition design guides. It's a key consideration when designing product mappings for bundled offers.

Explanation:

Correct Option: 🟢 C. KPI Type
The KPI Type field is required when setting up Retail Store KPIs in Consumer Goods Cloud. It defines the type of key performance indicator, such as sales or compliance, which is essential for tracking store performance. This field ensures KPIs are categorized correctly for reporting and analysis.

Incorrect Options:

🔴 A. Effective to
The Effective to field is not required for Retail Store KPIs. It may be used to specify the end date for a KPI’s validity, but it’s optional and not mandatory for setup, unlike KPI Type.

🔴 B. Retail Store Group
Retail Store Group is not a required field for KPIs. KPIs are typically tied to individual retail stores or specific metrics, not necessarily a group, making this field optional in setup.

🔴 D. Promotions
Promotions are not a required field for Retail Store KPIs. While promotions may be tracked as part of KPIs, they are not mandatory for defining a KPI, as KPIs focus on broader metrics like sales or inventory.

Summary: 📝
This question focuses on setting up Retail Store KPIs in Consumer Goods Cloud, which track store performance metrics. The scenario involves configuring KPIs correctly, with KPI Type being the critical field to define the metric’s purpose. Understanding required fields ensures accurate KPI setup for retail analytics.

Reference: 📚
Salesforce Help: Retail Store KPIs

Explanation:
United Telecom wants to upgrade existing customers from legacy internet plans to new high-speed offerings after a network upgrade. In Communications Cloud, the cleanest and most supported way to move a customer from an old commercial product to a completely new commercial product (especially when speeds, pricing, and product codes differ significantly) is through the out-of-the-box “Change of Plan” MACD action, which performs a technical disconnect of the old asset and a new connection of the high-speed asset in a single orchestrated flow.

Correct Option:

A – Change of Plan
Change of Plan is the standard OOTB MACD process designed exactly for plan upgrades/downgrades. It automatically handles disconnect of the old internet service asset, creates a new asset based on the high-speed offer, preserves the same service account and location, and orchestrates the technical actions correctly through decomposition and fulfillment.

Incorrect Option:

B – Disconnect and new order
This is not a single OOTB MACD action; it would require two separate orders and would break asset continuity, lose historical data, and generate unnecessary cease/re-provide billing events.

C – Modify order
Modify Order is used for in-place attribute or quantity changes on the same commercial/technical product (e.g., changing speed tier within the same product definition). It cannot switch the customer to an entirely new high-speed product definition.

D – Apply Promotion
Promotions are for temporary discounts or bundles; they do not change the underlying commercial product or asset to a new high-speed offering.

Salesforce Communications Cloud Documentation → “MACD Actions Overview”

Trailhead → “Modify, Add, Disconnect, Change (MACD)” module

Industries CPQ & Order Management Guide → “Change of Plan Process Flow”.

Explanation:

Correct Option:

D. ✅ Assessment Indicator Definition
The Assessment Indicator Definition object is where an admin defines the specific criteria or metrics to be evaluated during a store visit, such as planogram compliance. This includes setting the expected value (e.g., "10 units"), the target, and the measurement unit for each metric, ensuring field reps know the standard to assess against.

Incorrect Option:

A. ❌ Retail Store KPI
Retail Store KPIs are used to track high-level performance metrics of a store over time, such as sales volume or sell-through rates. They are not used to define the expected values for specific, task-level planogram checks during an assessment.

B. ❌ Assessment Task Definition
This object defines the broader task to be performed during a visit, like "Check Planogram." However, it does not define the specific expected metric values; it simply groups together a set of individual Assessment Indicators.

C. ❌ Delivery Tasks
Delivery Tasks are related to the execution of a delivery, such as unloading products. They are part of the execution flow and are not used for defining expected values for planogram or audit metrics.

Summary:
This scenario involves configuring the details of a retail audit. To define what "good" looks for a planogram check, an admin must configure the Assessment Indicator Definition, which houses the specific expected values and targets for each measurable criterion.

Explanation:
This is a classic synchronous callout with response processing scenario. The standard Vlocity/Industries integration pattern uses: An Integration Procedure to orchestrate the callout.

A DataRaptor to transform the outgoing request (Extract) and process the incoming response (Load).

A Response DataRaptor Bundle is a specific configuration that maps the ERP response fields to Salesforce fields and saves them.

Correct Option:

A. Configure the Response DataRaptor Bundle to process CREATE response from ERP and save returned ERP order identifier to SFI order record.
This is the precise, declarative method. The Response DataRaptor Bundle is attached to the Callout step in the Integration Procedure. It processes the synchronous response, extracts the ERP order ID, and maps it directly to a field on the Salesforce Order record. This is the standard, low-code way to achieve the requirement.

Why Others Are Incorrect:

B. Configure integration procedure in conjunction with Auto Task to perform CREATE order in ERP and process response to save returned ERP order identifiers using Load DataRaptor.
An Auto Task is used for asynchronous post-order-creation actions (like updates), not for processing a synchronous response from the initial CREATE callout. The response should be processed immediately in the same Integration Procedure using a Response DataRaptor Bundle, not deferred to an Auto Task.

C. Enhance OOTB integration adapter to process CREATE response from ERP and save returned ERP order identifier to SFI order record.
This suggests custom code modifications to the Out-Of-The-Box (OOTB) integration adapter. This is anti-pattern; you should avoid modifying OOTB adapters. The platform provides a declarative way (Response DataRaptor Bundle) to handle this without code.

D. Configure GET ERP Order Callout task straight after the callout task that creates an order in ERP. Enhance the out-of-the-box integration adapter to process GET response from ERP and save returned ERP order identifier to SFI order record.
This is overly complex and incorrect. The ERP order ID is returned in the synchronous response of the CREATE call. There is no need for a separate GET callout. Additionally, it again incorrectly recommends modifying the OOTB adapter.

Reference:
In Salesforce Industries (Vlocity) Order Management, the pattern for synchronous callout and response saving is:

Integration Procedure with a Callout step.

Response DataRaptor Bundle configured on that Callout step to map response fields to the target Salesforce record.

This is documented in the Integration Procedures and DataRaptors guides for Order Management implementations.

Explanation:

Correct Option:

D. ✅ General Promotion, Individual Product, and Product Category
These are the three distinct methods for performing a promotion check. A General Promotion check is for store-wide campaigns. An Individual Product check is for promotions on specific SKUs. A Product Category check allows the rep to verify all products within a specific category that are on promotion.

Incorrect Option:

A. ❌ Clearance Promotion, Volume Promotion, and Product Coupons
These are types of promotions that can be created in the system, but they are not the three methods for performing the check during a visit. The method of checking (general, by product, by category) is separate from the promotion's type.

B. ❌ Individual product, Product Coupons, and Volume Promotion
"Individual product" is one correct method, but "Product Coupons" and "Volume Promotion" are promotion types, not methods for executing the check during a store visit. This option mixes concepts incorrectly.

C. ❌ Unit Promotion, Product Category, and Product Coupons
"Product Category" is a correct method, but "Unit Promotion" is not a standard term for a check type, and "Product Coupons" is a promotion type, not a method for performing the check.

Summary:
This scenario involves the execution of a common field task. When creating a promotion check task for a visit, an admin must define how it will be performed, choosing from these three distinct scopes: for the entire store (General), for a specific product (Individual), or for a group of products (Category).

Explanation:
The core need is product catalog syndication from the source of truth (Communications Cloud) to external systems. In Salesforce Industries (Communications Cloud), the Enterprise Product Catalog (EPC) is the centralized master for all product definitions, specifications, and offerings. The integration should use APIs designed specifically for extracting catalog data from EPC.

Correct Option:

C. Use Enterprise Product Catalog REST APIs to retrieve product specifications and product offerings.
This is the most direct and appropriate starting point. The Enterprise Product Catalog (EPC) in Communications Cloud is the system of record for the product catalog. The EPC REST APIs (part of the Industries OM/CPQ APIs) are specifically built for external systems to retrieve product information, including specifications, hierarchies, and offerings, in a structured format. This ensures distributors get the complete, authorized product data.

Incorrect Options:

A. Use Object REST APIs to retrieve data from Product2 Object.
This is a generic, low-level approach. While the catalog data may be stored in Product2 and related objects, using standard Salesforce REST APIs would require complex, custom queries to reconstruct the full product hierarchy, specifications, and offerings. It bypasses the business logic and relationships encapsulated in the EPC APIs, making it fragile and inefficient.

B. Use productized TM Forum 620 Catalog Open APIs to retrieve product specifications and product offerings.
TM Forum Open APIs (like TMF620 Product Catalog Management) are industry-standard interfaces for telecom product catalogs. While Salesforce supports TMF APIs, they are typically used for external system integration in a hybrid ecosystem. However, the question specifies ABC Telecom uses Communications Cloud and wants to share from it. The starting point should be the native Salesforce EPC APIs, which can then be mapped to TMF620 if needed for the distributors. Using TMF620 directly would require it to be exposed from Communications Cloud, which may involve additional configuration.

D. Use CPQ API getCartProducts to create a cart and retrieve product specifications and product offerings.
The getCartProducts API is part of the CPQ Cart APIs, designed for shopping cart interactions (e.g., adding products, pricing). It is not intended for bulk catalog extraction or syndication. Creating a cart to fetch product data is a misuse of the API, inefficient, and would not reliably provide the full catalog with technical specifications.

Reference:
In Salesforce Communications Cloud, the Enterprise Product Catalog (EPC) is the master catalog. The EPC REST APIs (documented in Salesforce Industries API guides) provide methods to retrieve product details, categories, and specifications. For catalog syndication to partners, these APIs are the recommended starting point, as they are optimized for product data exchange and align with the platform's product information management (PIM) capabilities.

Explanation:
The goal is to centralize the product catalog in the new Communications Cloud platform to ensure a single source of truth, eliminate synchronization errors, and leverage its built-in capabilities for both internal and external channels. The recommended approach must use Communications Cloud's native architecture and approved integration patterns.

Correct Option:

B. Maintain the product catalog in Communications Cloud Enterprise Product Catalog and use Digital Commerce APIs to extract the catalog to the web channels.
This is the correct, cloud-native approach. The Enterprise Product Catalog (EPC) within Communications Cloud is designed as the central product master. Using Digital Commerce APIs (like the Commerce Cloud SDK or APIs for headless commerce) is the standard, real-time method to expose product data to external digital channels (web/mobile). This provides a unified catalog, supports real-time updates, and follows Salesforce's recommended integration pattern.

Incorrect Options:

A. Manage the product catalog internally using Communications Cloud and use Cart APIs to expose the product catalog to web via OmniOut.
Cart APIs are for managing shopping cart operations, not for catalog extraction or syndication. OmniOut is not a standard Salesforce product for this purpose; it may refer to a misnamed component. This approach misuses APIs and does not follow the intended architecture for catalog distribution.

C. Maintain the product catalog in Communications Cloud and periodically synchronize to the web channels automatically.
Periodic synchronization (batch sync) introduces latency and risks data inconsistency between systems. It does not provide real-time accuracy, which is critical for web channels where pricing, availability, and promotions must be immediate. This is an outdated integration pattern.

D. Introduce a new product catalog primary application that will synchronize both Communications Cloud and the web channels when updates occur.
This adds an unnecessary third system (a new "primary application"), complicating the architecture and creating another point of failure and maintenance. It contradicts the digital transformation goal of consolidating into Communications Cloud as the single source of truth.

Reference:
This solution aligns with Salesforce Communications Cloud implementation guides, which position the Enterprise Product Catalog (EPC) as the central product master. Integration with digital channels is achieved via Commerce Cloud Digital APIs for headless commerce, ensuring real-time, consistent product data across all touchpoints.

Explanation:

🟢 Correct Option: D. At the energy bar product category level.
Defining the Retail Store KPIs at the energy bar product category level is the most efficient approach. This ensures that the audit is focused on the entire promotion rather than individual products. By grouping all energy bars into a single category, the merchandiser can check for the BOGO promotion's compliance without needing to audit each individual SKU, which significantly reduces the number of records created while still capturing the necessary promotional data.

🔴 Incorrect Option: A. At the energy bar product SKU level.
Defining KPIs at the SKU level would require the merchandiser to audit every single energy bar product individually. Since the promotion applies to all energy bars, this would create an unnecessary number of records, making the audit process very time-consuming and inefficient. It does not align with the goal of minimizing records.

🔴 Incorrect Option: B. At the Alpine brand catalog level.
Auditing at the brand level would be too broad. Alpine might have other products besides energy bars in their catalog that are not part of the BOGO promotion. This would lead to irrelevant data being collected and would not provide a focused audit on the specific promotion, which is the primary goal of the visit.

🔴 Incorrect Option: C. At the custom context field level.
While custom context fields can be used to add detail, they are not a level at which Retail Store KPIs are defined for an audit. KPIs are defined on a data model object, such as a product category, to measure performance. Using a custom context field alone would not provide the necessary structure to group and audit the promotion effectively.

Summary:
Alpine's promotion applies to all energy bars. To ensure an efficient audit and minimize data, the KPIs should be defined at a level that encompasses all promoted products without going into unnecessary detail. Auditing at the product category level (energy bars) achieves this goal perfectly, allowing the merchandiser to check for promotional compliance for the entire group of products with a single set of metrics, thus optimizing the process and reducing the number of records created.

Reference:
Salesforce Official Documentation: Retail Execution KPIs

Explanation:
This question addresses the correct method for extending the standard task types in CGC when a specific business process (cooler auditing) is not covered by the out-of-the-box types. The platform provides a specific Task Type value to indicate a user-defined, custom assessment that will require a tailored setup and potentially a custom Lightning component.

Correct Option:

D. Custom:
When creating a new Assessment Task Definition for a non-standard process like "Cooler Audit," the user must select Custom as the Task Type. This signals that the task does not use a standard CGC component (like Inventory or Planogram Check) and will require custom configuration for data capture, such as a custom object, page layout, and potentially a custom Lightning component for the mobile app.

Incorrect Option:

A. Other:
This is not a valid Task Type value for an Assessment Task Definition in CGC. The standard picklist includes specific types like Inventory Check, Planogram Check, Promotion Check, and Custom.

B. Planogram Check:
This task type is specifically for visual compliance checks comparing a shelf photo to a reference image. A cooler audit may involve different data points like temperature, cleanliness, or equipment functionality, making it a distinct process.

C. Inventory Check:
This task type is for counting stock levels of products. While a cooler audit might include inventory, its primary focus is on the cooler unit's condition and performance, which is broader than a simple product count.

Reference:
The Salesforce Help article on "Create an Assessment Task Definition" lists the available Task Type picklist values. For creating a new, unique assessment not covered by the standard types, the Custom option must be selected. This allows administrators to then define the custom fields, page layout, and mobile experience required for the specific audit process.