Free Consumer Goods Cloud Accredited Professional (AP-204) Practice Questions

Assetization is the process in Salesforce Industries (Communications/Consumer Goods) where a successfully fulfilled order line item is converted into a permanent Asset record. This Asset record serves as the single source of truth for what the customer currently owns.

A Consultant should recommend assetization for a commercial product or service when it is likely to be involved in future customer management and transactions. The three main factors that necessitate creating an Asset record are:

The product/service sold has a recurring charge (B):

A recurring charge means the service/product will be billed repeatedly (e.g., monthly). To ensure the billing system receives the correct information and to manage any future pricing changes (like applying a promotional discount for a specific period), the service must exist as a persistent Asset record. Billing systems typically interface with the Asset/Subscription object to determine what to invoice each cycle.

The product/service sold can undergo future attribute changes (C):

The core purpose of the Move, Add, Change, Delete (MACD) process is to allow customers to modify their existing services. If a product attribute (e.g., Internet speed, color of a device, service plan) can be changed, the system needs an Asset record to track the current attribute values (the "As-Is" state). When a customer initiates a change, the system converts this Asset's current state into an order line item for modification.

The product/service sold will have child features added in the future (A):

Products that are part of a bundle or have a hierarchical structure (Parent $\rightarrow$ Child) must be tracked as Assets so that their children or sub-features can be managed, added, or removed later. For example, if a base service (Asset) allows for the addition of premium channels (new Assets), the base service must first exist as an Asset to act as the parent for the new features.

Why D and E are incorrect:

D (High-volume, one-time billing event, such as a pay-per-view): One-time, high-volume transactional items (like PPV events or movie rentals) are typically not assetized. They are billed once and retired. Creating millions of short-lived asset records would rapidly consume storage and severely degrade system performance.

E (Device accessory, such as a phone case): Simple, one-time purchase equipment without a service component (like a phone case or charger) is rarely assetized, as it has no recurring charge (B) and generally does not undergo MACD changes (C).

Store Products are integral to various tasks in Consumer Goods Cloud, including inventory and promotion checks, as well as search and scan functionalities.

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.

When migrating product data into the Enterprise Product Catalog (EPC), Salesforce recommends product rationalization as a mandatory first step. Legacy systems often contain hundreds or thousands of products accumulated over years. Not all of them should be migrated into EP

C.  

Two critical questions a consultant must ask are:

A.  

EPC is designed for modular, reusable, and hierarchical product specifications. Many legacy products can be consolidated into a smaller, more efficient set using attributes, rules, and cardinality instead of copying fixed bundles. This drastically improves CPQ speed, product maintenance, and time-to-market.

B.  

Salesforce advises migrating only active commercial offers, prerequisites, and required technical products. Inactive, obsolete, or sunset products add noise and complexity and should typically be excluded.