Salesforce Consumer-Goods-Cloud-Accredited-Professional Dumps Questions Answers

Salesforce Communications Cloud supports rich pricing models using Matrix-Based Pricing (MBP). Matrix-based pricing is the recommended method when pricing depends on multiple attributes from Account, Product, or other context properties.

For One-Time Charges (OTCs), Salesforce recommends separate pricing matrices, not combining OTC logic inside recurring matrices. OTCs often have different conditioning logic, different triggers, and different applicability rules than recurring charges.

Option B follows the supported pattern:

Define a new matrix for OTC pricing

Use relevant Account attributes (tier, segment, SLA level)

Use relevant Product attributes (speed, class of service, add-ons)

Output the appropriate OTC amount

Options A and C introduce unnecessary custom logic or create nonstandard product artifacts. Option D is incorrect because recurring pricing matrices must not be overloaded with unrelated OTC fields—Salesforce documentation recommends separating matrices by charge 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.