Consumer-Goods-Cloud-Accredited-Professional Practice Questions

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.

The "Change of Plan" feature in Salesforce Communications Cloud (often accessed via Digital Commerce APIs or the Cart) is designed to handle the complex logic of modifying an existing customer's service portfolio. The three key offerings/capabilities are:

Supported by Digital Commerce APIs (A): Salesforce provides specific Digital Commerce (DC) APIs (e.g., getChangeOfPlanOffers or generateChangeOfPlan) that allow this complex logic to be exposed on self-service portals. This enables customers to view eligible upgrade/downgrade paths and execute the change without agent assistance, calculating pro-rated costs in real-time.

Moving to/out from the bundled offer (B): The feature is sophisticated enough to handle structural changes in the product hierarchy. It can take a standalone asset and move it into a bundle (e.g., moving a standalone internet line into a "Triple Play" bundle) or unbundle a service, maintaining the integrity of the commercial and technical data throughout the transition.

Service Continuity (E): A critical requirement in Telecom is that the "Change of Plan" (Commercial Change) does not accidentally disconnect the underlying technical service (Technical Change) unless intended. The Change of Plan feature ensures Service Continuity by preserving the link to the existing Technical Products (RFS) and Assets, ensuring that a customer upgrading their billing plan doesn't suffer a service outage during the provisioning process.

Why C and D are incorrect:

D (Customers can choose from all plans...): This is incorrect. The Change of Plan feature specifically uses Eligibility and Context Rules to filter the catalog. A customer on a Fiber plan cannot "choose" a legacy Copper plan if rules forbid it. They only see eligible target paths, not all plans.

C (History...): While Salesforce tracks field history and asset history, "Traceability" is a platform characteristic, whereas Service Continuity and Bundle manipulation are specific functional offerings of the Change of Plan logic engine.

In Salesforce Industries Enterprise Product Catalog (EPC), hierarchical product modeling with child specifications and cardinalities is natively supported, which makes option E correct. Defining a voice offer with a “phone add-on” child product and a cardinality of up to 700 leverages standard EPC capabilities such as product specifications, child relationships, and cardinality rules.

However, Salesforce guidance for EPC and Industries CPQ warns that very large cardinalities on child products can introduce performance and processing challenges, especially in high-volume telecom scenarios. During MACD (Modify, Add, Change, Disconnect) operations, every instance of the child product (each phone device) has to be evaluated, updated, and sometimes decomposed into order items or service orders. With hundreds of instances, this can lead to processing inefficiencies and long-running transactions, which supports statement A.

Additionally, although the model technically uses out-of-the-box features, extreme volumes (such as hundreds of children per parent) can stress the decomposition engine. Under heavy load or complex rule combinations, decomposition may time out or fail when the maximum number of instances are ordered, making C valid as well.

Option B is incorrect because EPC does support this pattern; flat-only modeling is not a requirement. Option D is incorrect because using OOTB features does not guarantee optimal MACD and decomposition behavior at very high instance volumes.

For customer migration into Communications Cloud, Salesforce public documentation outlines a specific parent-child dependency order for customer-related data. The objective is to ensure that all parent records exist before loading child or dependent records (Billing Accounts, Service Accounts, Subscriptions, Assets).

(B) Business or Consumer Accounts should be loaded before Billing or Service Accounts

Accounts represent the parent customer entity. Billing Accounts and Service Accounts depend on the root customer account. Salesforce clearly emphasizes that Billing Accounts must have a parent Account, and Service Accounts must be tied to either the Billing Account or Consumer/Business Account. Therefore, loading Accounts before Billing/Service Accounts is mandatory.

(C) Premises should be loaded before Service Accounts

In Communications Cloud, Premises represent physical service locations. Service Accounts reference the PremiseId and cannot be created before the premise record exists. This dependency is frequently highlighted in Salesforce migration patterns, especially for broadband, fiber, and fixed-line providers.

Incorrect options:

A (Contracts before Accounts): Contracts depend on Accounts; Accounts must exist first.

D (Subscriptions before Accounts): Subscriptions require Accounts, Billing Accounts, and Service Accounts—therefore cannot be loaded first.

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