Pass the Salesforce Consumer Goods Cloud Consumer-Goods-Cloud-Accredited-Professional Questions and answers with ExamsMirror

Two explanations for why no surveys are available when field reps try to complete a visit survey on their mobile devices are:

The Salesforce admin has not created and activated a Salesforce survey. A Salesforce survey is a questionnaire that can be sent to customers or contacts to collect feedback. The admin needs to create and activate a survey before it can be used in an in-store survey task.

A related survey invitation has not been generated. A survey invitation is an object that represents an invitation to take a survey. A survey invitation needs to be generated and associated with the visit, the retail store, or the store primary contact before it can be displayed in an in-store survey task. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 27.

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.

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.

For integrations where the provisioning/ERP system returns an external order ID in a synchronous response, Salesforce recommends using the Response DataRaptor Bundle of the Integration Procedure or Process Library.

The Process Library already includes patterns for handling:

Create Order callouts

Handling synchronous responses

Mapping response fields into Salesforce objects (e.g., SFI Order, Fulfillment records)

You simply extend the Response DataRaptor to:

Extract ERP Order Identifier from the response payload.

Save it onto the corresponding Salesforce Order record for audit and troubleshooting.

Why other options are incorrect:

B: Auto Tasks are for async flows; the requirement is synchronous.

C: Enhancing the OOTB adapter is not recommended—declarative DR bundles should be used.

D: Creating a separate GET callout is unnecessary because the identifier is returned in the synchronous CREATE response.

Thus, A is the Salesforce-recommended approach.

The Action Plan Type that should be selected when creating an Action Plan for Consumer Goods Cloud is Visit Execution. An Action Plan Type is a metadata record that defines the type and configuration of an action plan. An action plan is a set of tasks that need to be completed for a specific purpose or goal. The Visit Execution Action Plan Type is designed for Consumer Goods Cloud users who need to create action plans for their store visits. A visit is an interaction between a field rep and a retail store. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 25.

To meet the requirements of offering regional pricing and ensuring customers can see the correct price before adding the product to the cart (i.e., while browsing the catalog), the solution must rely on Context Rules that evaluate the customer's profile (Region) prior to product configuration.

B. Create a Base Price List and Multiple Child Price Lists associated with Context Rules per region:

In Salesforce Industries (Communications Cloud) CPQ, Price Lists are the primary container for prices. You can create specific price lists for each region (e.g., "New York Price List," "Texas Price List") and use Context Rules to automatically assign the correct price list to the user's session based on their Account or Quote details (Region).

Because the Price List is selected before the product is viewed, the catalog automatically displays the price entries from that specific regional list, satisfying the visibility requirement.

D. Create multiple Price List Entries associated with Context Rules per region:

Alternatively, you can use a single global Price List but create multiple Price List Entries (PLEs) for the same "Business Internet" product (e.g., one entry for $50, another for $60).

You can apply Context Rules directly to these Price List Entries. When the catalog renders, the system evaluates the rules against the customer's context (Region) and filters the entries, showing only the one valid for that region.

This allows for granular control at the product price level without necessarily duplicating entire price lists.

Why A is incorrect: Attribute-based Pricing Matrices are typically used for calculating prices based on product attributes that a user selects during configuration (e.g., Speed, Color). Since the requirement is to see the price before adding to the cart (pre-configuration), and Region is a context of the customer not a feature they configure on the product, Context Rules (B & D) are the correct architectural choice.

In Communications Cloud, the correct end-to-end modeling pattern is:

Commercial Product → DSL Internet

Attributes → Speed (5 Mbps, 50 Mbps) and derived Technology (ADSL, VDSL)

Customer Facing Services (CFS): ADSL CFS, VDSL CFS

Resource Facing Services (RFS): Copper Pair, Bonded Copper Pair

Multi-level decomposition: Commercial → CFS → RFS

This follows the standard Salesforce service modeling approach where CFS represents logical service layers, and RFS represents physical resources required to deliver the service.

Salesforce EPC provides Object Types to group products that share common attributes. For mobile devices that all share color, storage, screen size, the correct modeling approach is:

✔ Create a Mobile Offer Spec Type

Add all common attributes (color, storage, screen size).

Set parent = Base Offer Spec Type (standard hierarchy).

Associate mobile device products with this Object Type.

This ensures:

Attribute reuse

Cleaner catalog modeling

Easier maintenance

Declared inheritance from Base Offer Spec Type → Mobile Offer Spec Type → Device Offer

Why others are incorrect:

A: Associates devices with Base Type instead of Mobile-specific type.

B: Suggests reversing hierarchy (incorrect structure).

D: Putting all attributes on Base Offer Spec Type violates specialization and bloats the base type.

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.

In Retail Store KPIs, you can define the assessment indicator definition that must be captured for a store group. Because the assessment indicator definition is associated with assessment task definition and store groups to stores, Retail Store KPIs are the link between a store and the tasks to be performed at a store. You can also define the expected values of an assessment indicator definition in Retail Store KPIs