The requirement is:

Product A should be included by default (default=1)

User can remove it (Min=0)

They cannot increase quantity beyond 1 (Max=1)

This exactly aligns with cardinality settings:

Min = 0 (optional)

Max = 1 (only one allowed)

Default = 1 (pre-included)

Auto Add (A) does not allow opt-out.

Recommend Rule (C) only suggests the product — does not auto-include.

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.

Quip Documents, Einstein Predictions, and Custom Object Task List are three components that can be added to a new page for the Consumer Goods Cloud mobile application. These components provide additional functionality and information for users in the field. They are:

Quip Documents, which allows users to access and collaborate on Quip documents within the app. Quip documents are cloud-based documents that can include text, images, spreadsheets, charts, and more.

Einstein Predictions, which allows users to see predictions and recommendations from Einstein AI based on their data and actions. For example, users can see predictions for sales revenue, product demand, or visit outcomes.

Custom Object Task List, which allows users to create and complete tasks related to custom objects within the app. Custom objects are objects that are defined and configured to suit specific business needs. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 40-41

Promotions within the Consumer Goods Cloud can be defined at different levels, including the Account, Product, and Retail Store levels. This flexibility allows for targeted and effective promotion strategies.

A possible reason for failing all the test cases related to delivery tasks is that the tester did not have the lightning direct store delivery Permission Set added. A Permission Set is a collection of settings and permissions that grant users access to various tools and features. The lightning direct store delivery Permission Set is required for users who need to use the delivery task functionality and related objects, such as product transfers and shipments. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide] , page 29.

ABC Telecom requires that assets be synchronized to their assurance platform immediately after fulfillment , and they operate in a high-volume wholesale environment (5,000+ orders per reseller/day and hundreds of concurrent users). Salesforce recommends event-driven, near-real-time integration for high-scale fulfillment notifications.

Platform Events are Salesforce’s native, scalable publish/subscribe mechanism designed for high throughput and low latency. When an order completes fulfillment, Communications Cloud can publish an event that external systems subscribe to. The assurance platform can then call the GetAsset API to retrieve the exact asset structure needed for assurance workflows.

This pattern is explicitly recommended in Salesforce high-throughput integration architectures because it:

Eliminates polling

Handles large transaction volume

Provides near-real-time sync

Decouples fulfillment from assurance systems

Scales horizontally across resellers

Option A (using OM orchestration) is synchronous and not optimal for high throughput.

Option B (on-demand REST pull) causes latency and excessive polling.

Option C (Bulk API) is batch-oriented, not real-time, and unsuitable for near-immediate updates.

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.

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.

Salesforce Maps Advanced includes features like real-time traffic-based routing, constraint-based routing, and visit windows to optimize field service operations and improve efficiency in planning store visits.

The nearby map component on the promotion records page allows a user to see which stores are running a promotion within their vicinity. This solution meets the requirement and also involves the least amount of custom development, as it is a standard feature of Consumer Goods Cloud. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 32.