Salesforce Consumer-Goods-Cloud-Accredited-Professional - Consumer Goods Cloud Accredited Professional (AP-204)

In Salesforce Industries (formerly Vlocity), large-scale B2B quoting scenarios—especially those involving multiple service accounts, hundreds of simultaneous quotes, and high-volume line-item configurations—are supported by the Enterprise Sales Management (ESM) application suite. Public Salesforce Industries resources describe ESM as the solution specifically engineered for complex B2B sales cycles, high-volume quoting, and enterprise-level product configuration.

ESM extends the functionality of Industries CPQ to support “high-line-item quoting environments,” allowing sales teams to manage thousands of products, hierarchical product bundles, account-specific pricing, and approval workflows. It is optimized for organizations selling advanced connectivity solutions, WAN, MPLS, SD-WAN, Dedicated Internet, and other enterprise-grade telecom services—exactly the type of offerings ABC Telecom delivers.

Salesforce’s public feature descriptions highlight that ESM supports:

Large quoting volumes (hundreds of quotes per customer)

Complex commercial hierarchies (B2B enterprise accounts with multiple service locations)

Scalable CPQ performance for 1,000+ line items

Enterprise contract, pricing, and proposal workflows

Multi-site, multi-service configuration

Other choices do not fit:

Advertising Sales Management focuses on media/advertising inventory buys.

Mobile Subscription Management is for B2C mobile postpaid/prepaid subscriptions.

Subscriber Lifecycle Management manages consumer subscriber journeys, not enterprise B2B quoting.

Thus, for ABC Telecom’s enterprise customer scenario with large, complex quotes, Enterprise Sales Management is the correct and Salesforce-aligned solution.

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.

To allow Sales Managers to create and assign delivery tasks to deliver, the following setup steps should be configured:

Create an action plan template with a Delivery Task and assign it to a Visit. A Delivery Task is a type of action plan task that allows a field rep to deliver products to a retail store. A Visit is a scheduled or unscheduled interaction between a field rep and a retail store.

Assign the Lightning Direct store Delivery permissions set to the user. This permissions set grants access to the delivery task functionality and related objects, such as product transfers and shipments.

Assign the Action Plans permission set to the Sales Manager. This permissions set grants access to the action plan functionality and related objects, such as action plan templates, action plan tasks, and assessments. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 28-29.

An action plan is connected to a visit, which represents a scheduled or unscheduled interaction between a field rep and a retail store. A visit can have one or more action plans associated with it, depending on the tasks that need to be completed during the visit. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 25.

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.

In Communications Cloud, during a MACD (Modify/Add/Change/Disconnect) order, Order Management must determine which service plan the customer currently has. For asset-based ordering, Salesforce stores the current state of a service in the Inventory Items object. This includes all attribute values associated with the existing commercial product instance.

Because the commercial product is modeled with a plan attribute (Basic, Standard, Premium), the active value is part of the customer's Inventory Item record.

During MACD decomposition, Order Management retrieves the current state of the service—including all attribute values—from the Inventory Item. This allows the orchestration plan to compare:

“Existing value” (from Inventory Items)vs.

“New value” (from the Change Order)

This is core to Salesforce’s “Inventory-Driven MACD” design.

Option A is incorrect because the Change Order only stores the new values—Order Management must pull the existing value from Inventory.

Option C (custom objects) is unnecessary and not recommended.

Option D (callout to downstream system) defeats the purpose of asset-based ordering and introduces latency.

These fields on the Retail Store object differentiate it from the Account object, providing specific information about store operations, preferred visit timings, and shipping details.

These statements ensure that the necessary data, such as KPIs and IDs, are available within the flow for accurately performing and tracking flow-based tasks.

In Salesforce Communications Cloud, when multiple commercial offers decompose into the same technical product, the system performs attribute mapping during decomposition using the configured Commercial-to-Technical Product relationships. Public Industries documentation explains that when two or more commercial products share an attribute with the same target technical product attribute, the system does not throw an error automatically. Instead, Communications Cloud uses a “last write wins” behavior during value assignment.

In this scenario, both the Internet and TV commercial offers have the same attribute “Installation Type”, and both map to the same attribute on the shared technical product (access line). When a customer orders Internet + TV together, the decomposition engine executes sequentially. The attribute mapping is processed for the Internet offer first (or whichever is configured first in the order). Next, the TV offer decomposes and updates the same attribute on the same technical product instance.

Because no conflict-handling mechanism is defined out of the box, and no mutual-exclusivity rules are enforced by default, the value from the last processed offer simply overwrites the earlier one. This is expected behavior in native EPC + OM decomposition when two attributes of identical name and mapping collide.

Therefore:

No design-time error occurs → eliminating option B.

No runtime decomposition error occurs → eliminating option D.

The attribute is not set to null → eliminating option C.

The system instead sets the technical product’s Installation Type to whichever product’s value was processed most recently.

These steps enable the setup of survey assessment tasks in Consumer Goods Cloud, ensuring the surveys are well-defined and integrated with retail store activities.