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

In Communications Cloud, modifying an existing commercial service to a higher speed tier (or upgraded variant) is handled through the Change of Plan MACD process. Salesforce defines Change of Plan as the out-of-the-box MACD scenario used when an existing active subscription is upgraded, downgraded, or migrated to a different configuration within the same offer family.

High-speed upgrades typically involve the same commercial product family (e.g., “Internet”) but with modified attributes such as speed tier, bandwidth profile, SLA level, etc. The Change of Plan MACD:

Reuses the existing asset

Captures the new configuration

Decomposes into new or modified technical actions

Avoids unnecessary disconnect/reconnect cycles

Preserves billing continuity

Minimizes order orchestration overhead

Options B (Disconnect & New Order) and C (Modify Order) are not correct: Disconnect/New Order is used only when replacing an entire product with a materially different offering, not speed upgrades. A Modify Order MACD adjusts non-plan attributes—not plan-tier changes. Option D (Apply Promotion) is irrelevant here.

Thus, Change of Plan is the correct MACD for upgrading customers to high-speed offers.

For a Tier-1 Telco with a massive data volume (20 million subscribers), a "Big Bang" migration (shutting down and moving everything at once) is impossible due to the required downtime and risk. The Consultant must recommend a Hybrid Migration Strategy that ensures business continuity.

Staged/Partitioned Migration (The "Bulk" Strategy):

To handle the 20 million records, the data must be partitioned into logical blocks (e.g., by Region, Billing Cycle, or Account Status).

These blocks are migrated in multiple stages (batches) over time in the background. This minimizes system load and allows for validation at each stage.

This aligns with the prompt's requirement to address the "long time to migrate."

On-Demand / Just-In-Time (JIT) Migration (The "Continuity" Strategy):

The critical requirement is to process orders "uninterrupted through the Salesforce platform".

If a customer whose data has not yet been migrated calls to place an order, the system cannot tell them to wait.

Instead, the system must perform an On-Demand (Just-In-Time) migration for that specific customer record immediately, bringing their asset data into Salesforce so the order can be captured and processed within Salesforce.

Why other options are incorrect:

A (Disable production): Impossible for a Tier-1 Telco; downtime for 20M records would be unacceptable.

B (Direct requests to legacy): This violates the requirement to process orders through the Salesforce platform. Relying on the legacy system for active orders creates a "split brain" scenario and prevents Salesforce from becoming the system of record.

C (Migrate on-demand...): While partially correct, Option D is the better architectural answer because it explicitly defines the Partitioning/Staging strategy required to manage the bulk volume, whereas C is less specific about how the background migration is handled.

The results or actual values of Custom Task KPIs are stored in the Retail Store KPI record, centralizing data related to performance indicators.

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.

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 Communications Cloud, integrations performed during Order Management—especially callouts for provisioning, billing, and customer synchronization—should use the Order object as the primary integration payload source. Salesforce’s public Order Management design principles specify that customer data required for external provisioning should be modeled directly on the Order when the data is stable, required frequently, and does not belong to technical products.

This approach offers:

Simple configuration (fields on Order object rather than product attributes)

High maintainability, because administrators can adjust mappings without changing product models or decomposition rules

Performance efficiency, as Order-based callouts do not require deep decomposition navigation or attribute inheritance logic

Clear separation of commercial vs. technical data, one of the core EPC principles

Options C and D introduce unnecessary complexity. Customer data does not belong on Technical Products (C) nor should it be modeled as multi-picklist cart attributes (D), as these degrade performance and complicate decomposition. A custom adapter (A) adds code and contradicts Salesforce’s declarative-first approach.

The Retail Execution Lightning Plus permission set enables end-users to access

and leverage the Einstein Visit Recommendation feature in Consumer Goods Cloud, enhancing visit planning and optimization.

White Space Analysis is a Tableau CRM dashboard that shows opportunities to sell new products in a retail store location. It analyzes the sales performance and product distribution across different stores and segments, and identifies gaps or white spaces where new products can be introduced or existing products can be expanded. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 37.

Salesforce Maps integrated with Consumer Goods Cloud allows the creation of layers of Retail Stores, aiding in geographical and spatial analysis for field operations.