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

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 Salesforce Communications Cloud, the B2C customer model follows a structured, layered hierarchy designed to support ordering, billing, service management, and asset lifecycle handling. When migrating existing B2C customers into Communications Cloud, Salesforce’s public architecture guidance specifies a top-down data dependency sequence to ensure that parent records exist before child records referencing them are inserted.

The migration sequence begins with Users, since many operational objects (orders, cases, ownership, provisioning workflows) require an active user as the record owner or last modified by. Next, Contacts are required for each B2C customer because Communications Cloud uses Contacts associated with a Consumer Account to represent the individual subscriber. Although Person Accounts are supported in some Salesforce products, Communications Cloud standard data model for B2C uses Consumer Accounts + Contacts, which aligns with option A—not C.

Once contacts are created, Consumer Accounts must be migrated so that customer identity, householding, service relationships, and billing mappings can be referenced. With accounts in place, Billing Accounts are imported next to link financial agreements, billing preferences, and invoicing relationships.

Service Accounts follow, serving as the service location or logical container for active telecom services. Only after these parent entities are established can Subscriptions be migrated, as they represent the commercial products the customer is consuming. Finally, Assets are migrated, representing the technical products or devices (routers, SIMs, set-top boxes) associated with active subscriptions and services.

Options B, C, and D omit Subscriptions, which are essential for B2C migration into Communications Cloud. Option C incorrectly uses Person Accounts, which does not match the Communications Cloud standard B2C data model.

These permissions ensure that users have the necessary access to view and interact with the Tableau CRM for Consumer Goods Cloud app, providing critical analytics and insights.

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.

This approach allows for an efficient and code-minimal way to check compliance of high-value assets in stores and trigger correction action plans based on Boolean values.

In Salesforce Industries Order Management, the scope of a technical product determines how decomposition looks for existing assets or inventory items. When a customer already owns a device (such as a router) and later orders a new service that can reuse the same hardware, the decomposition engine must search across the customer’s inventory at the account level, not the original order item or the top-level order item.

Public Salesforce Order Management documentation explains that Account Scope is used when the fulfillment system needs to evaluate inventory or assets that the customer already owns—for example, routers, ONTs, set-top boxes, SIM cards, or any CPE device. By setting the technical product to Account Scope, the decomposition engine checks the customer's entire installed base and finds the matching item, allowing it to generate the correct Fulfillment Request Lines (FRLs) without creating duplicates.

Other options do not support the scenario:

Order Item Scope and Top Order Item Scope only look at items within the current order and would not detect previously fulfilled devices.

Downstream Order Item Scope evaluates child order items but still only within that transaction.

Thus, only Account Scope ensures that the decomposition process properly references existing inventory and reuses the router rather than provisioning a new one, which is exactly what the scenario requires.

Warehouse agents manually entering router barcode and shipment tracking numbers requires a human task in Order Management. Salesforce best practice:

Use a Manual Task Orchestration Item when human input is required.

Launch an OmniScript to capture structured data, validate inputs, and update Fulfillment data.

Why the others are incorrect:

A (Flow) – Flows are not the recommended UI for OM tasks; OmniScripts provide better control, validations, dynamic forms, and DC/CPQ consistency.

B (Push Event) – Push tasks send tasks to external queues/systems, not internal warehouse agents.

C (Autotask) – Auto Tasks run without human interaction, so cannot capture barcodes manually.

Shelf Metrics allow a user to review the vision detection accuracy by comparing the actual shelf image with the expected planogram image. Model Metrics allow a user to review the vision detection accuracy by showing the confidence score and the number of detections for each object in the shelf image. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 23-24.

A merchandiser can perform a check-in to log the arrival time and geo coordinates for an inventory-check appointment by using the Salesforce Mobile App. The Salesforce Mobile App is a mobile version of Salesforce that allows users to access and use various features and tools on their mobile devices. A check-in is a feature that allows users to record their arrival at a location, such as a retail store, by using their device’s GPS. A check-in can be performed by tapping the Check In button on the visit record in the Salesforce Mobile App. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 34.

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