To expose OmniScripts and FlexCards outside Salesforce (third-party CMS), Salesforce supports OmniOut, which packages OmniScripts/FlexCards for external consumption.

Because external users are unregistered, a backend “integration user” must authenticate against Salesforce to get a session token.

✔ A – Required for authentication

✔ C – Use OmniOut for external CMS

Canvas and Lightning Out are not appropriate for OmniStudio components.

Thus A and C are correct.

Salesforce Communications Cloud (formerly Vlocity Communications) provides a set of out-of-the-box omnichannel capabilities specifically designed to support buying, managing, and modifying telecom services across web, mobile, partner portals, and agent-assisted channels. Public Salesforce documentation describes two major components that enable this: Digital Commerce APIs and the Digital Commerce SDK.

Digital Commerce APIs (Option A)

Salesforce provides a full suite of REST-based Digital Commerce APIs that expose CPQ functions such as:

Product discovery

Product configuration

Pricing and promotions

Cart creation and management

Order submission

These APIs are channel-agnostic and built for web portals, mobile apps, in-store kiosks, and agent desktops, making them ideal for United Telecom’s requirement to support multiple sales and self-service channels. They leverage standardized product and pricing logic directly from the Enterprise Product Catalog, ensuring consistency across all channels.

Digital Commerce SDK (Option B)

The Digital Commerce SDK complements the APIs by providing reusable UI components, templates, and client-side tools to rapidly build modern commerce experiences. It supports Lightning, LWC, and headless storefronts, enabling companies to create branded, high-performing customer experiences with minimal custom code. This SDK allows UT to deliver responsive and consistent digital buying flows without building UI logic from scratch.

Options C (Cart-based APIs using OmniOut) and D (Custom APIs using LightningOut) involve custom or integration-heavy approaches that are not needed when out-of-the-box Digital Commerce capabilities already provide a complete omnichannel solution.

Therefore, the two correct out-of-the-box capabilities for multi-channel customer experience in Communications Cloud are A and B.

These components provide comprehensive information about promotions and inventory, vital for effective retail execution.

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.

Store Action Plan Templates for recommended tasks can be defined at various levels including Retail Store Group, Retail Store, and In-Store Location, allowing for granular and effective task management.

Two primary use cases for performing an in-store survey are:

Gathering feedback from customers, consumers, shoppers, and staff. An in-store survey can be used to collect feedback from various stakeholders who interact with the products or services offered by the consumer goods company. For example, an in-store survey can ask customers about their satisfaction, preferences, or suggestions; consumers about their awareness, perception, or loyalty; shoppers about their behavior, motivation, or barriers; and staff about their challenges, needs, or opinions.

Gathering data on promotions, inventory requirements and product quality. An in-store survey can be used to collect data on various aspects of the product performance and availability in the retail store. For example, an in-store survey can ask about the compliance, effectiveness, or impact of promotions; the demand, supply, or replenishment of inventory; and the condition, quality, or issues of products

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.

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.

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.

To make a brand-new product available for Industries CPQ initial sale and support order fulfillment, two major work items must be completed:

B. Decomposition Relationships

These define how the commercial product breaks into technical products required for fulfillment. Without decomposition, Order Management cannot generate Fulfillment Request Lines.

D. Product Model

The product must be fully modeled in the Enterprise Product Catalog (EPC):

Product Spec

Attributes

Prices

Cardinality

Bundles

Versioning

Incorrect options:

A. OmniScript is optional; CPQ can still operate via the Cart without custom OmniScripts.

C. MACD Orchestration is not needed for initial sale; only fulfillment of new orders is required at launch

Once a production data load is completed in Communications Cloud, Salesforce’s public data-migration and go-live readiness recommendations emphasize two mandatory activities: (1) remediation of failed records, and (2) validation of loaded data. These activities ensure that production contains a complete, accurate, and trusted data set before the system is opened to business users.

Option B – Analyze and resolve any errors and re-load failed records

Even if a full-data migration completed successfully in a Full Copy sandbox, the production environment may still produce new failures due to data differences, unexpected validation rules, org-specific automation, or sequence dependencies. Salesforce migration best practices require analyzing the error logs generated by Data Loader, Bulk API, or middleware, correcting failed data, and performing targeted reloads. No migration is considered complete until every failed record has been addressed. This is a standard post-migration requirement in Communications Cloud given the volume and interdependencies between Accounts, Subscriptions, Service Accounts, Billing Accounts, Premises, Assets, Orders, and Fulfillment objects.

Option D – Validate volumes and spot-check correctness

After the load finishes, the consultant must validate that record counts in production exactly match expected totals from source systems, including number of Accounts, Billing Accounts, Service Accounts, Subscriptions, Premises, and Assets. Salesforce also recommends targeted spot checks—opening individual customer records, ensuring relationships are correct, asset hierarchies are intact, and subscription data is consistent. This ensures data integrity before cutover and user access.

Incorrect options:

A – Salesforce does not provide a data load report via support case; all logs come from the tools used during migration.

C – You cannot assume “all errors were resolved earlier.” Every production load must be validated, and new issues frequently occur during the final cutover.

Therefore, the correct post-production-load actions are B and D.

The requirement is to introduce a limited-time offer that is available on the website (digital channel/DC APIs) and, once claimed, grants a 10% discount for three months.

This is the definition of a Promotion that uses a Time Plan to define the duration of the discount.

Promotion (A):

In Salesforce Industries CPQ, a Promotion is the container entity used to define a marketing offer that modifies the price of a product (in this case, a 10% discount).

The Promotion entity is what is typically exposed to digital channels (like the website via DC APIs) for customers to claim or qualify for. The search results confirm that Promotions are used to "apply temporary changes to product pricing, bundles, and product structure".

Time Plan (B):

The Time Plan is a sub-feature of Promotions (or Price Lists) that defines the duration for which the commercial change (the 10% discount) is active.

The requirement states the discount is only for "three months." A Time Plan is specifically configured to start the discount upon activation and automatically end it after the defined period (3 months), ensuring the billing system correctly handles the price change back to the original rate.

D (Discount) is a result of the configuration, not the feature itself. The discount value (10%) is defined within the promotion.

C (Offering) is a synonym often used for a product or bundle, but it does not specify the limited-time discount mechanism required.