OmniScript is the recommended mechanism for guided selling in Communications Cloud. An OmniScript can be run internally for agents and exposed externally using OmniOut, either embedded in a third-party CMS or surfaced in a Salesforce Experience Cloud site. Both deployment patterns are fully supported and require no custom wrappers.

A. Lightning Out can embed Lightning components, but Salesforce explicitly states that Screen Flows aren’t supported in Lightning Out contexts, so Flow-based journeys can’t run on a third-party CMS.

1. OmniStudio Developer Guide, “Expose OmniScripts Externally with OmniOut,” pp. 2-4, 2023.

2. Salesforce Help, “Use OmniOut to Embed OmniScripts in External Sites,” para. 1-3, Spring ’24.

3. Lightning Out for LWC Dev Guide, “Unsupported Features—Screen Flows,” p. 5, Spring ’24.

The 'Maximize Store Sales' Einstein Discovery story is a prebuilt template specifically designed for Consumer Goods Cloud. It analyzes historical data to identify the key drivers and factors that influence sales performance at the store level. This story helps answer questions like "What is influencing my store's sales?" and provides actionable insights and recommendations on how to improve sales outcomes, directly addressing NTO's requirement to understand factors affecting store sales.

A. ‘Strategic Sales’ is not a standard Einstein Discovery story template provided for Consumer Goods Cloud; it is too generic.

C. This story focuses specifically on inventory and stockouts, which is only one of many factors that can affect overall store sales.

D. This story is focused on analyzing the effectiveness of promotions, not the broader set of all factors that might influence store sales.

1. Salesforce Help, Consumer Goods Cloud, Einstein Discovery for Consumer Goods Cloud, "Prebuilt Einstein Discovery Stories". The documentation lists "Maximize Store Sales" as a story to "Analyze factors that influence store sales and get recommendations to improve sales."

2. Salesforce Help, Consumer Goods Cloud, Set Up Einstein Discovery for Consumer Goods Cloud, "Create an App with the Analytics for Consumer Goods Template". This guide details the steps to implement the pre-built analytics, including the "Maximize Store Sales" story.

In the Salesforce Communications Cloud data model, an active service is represented by an Asset record (the commercial view) and its underlying technical components and attributes are stored in Inventory Item records (the technical view). When an orchestration plan needs to know the existing configuration of a service it is modifying, the standard and correct practice is to retrieve this information from the associated Inventory Items. These objects serve as the technical source of truth for provisioned services within Salesforce, holding the specific attribute values (like the current service plan) that orchestration processes act upon.

A. The Change Order captures the delta or the new state; it doesn't typically store both old and new values on the commercial product itself.

C. Creating custom objects is not a best practice, as the standard data model with Assets and Inventory Items is designed specifically for this purpose.

D. A callout to an external system introduces unnecessary dependency and latency. The Salesforce inventory should be the system of record for this information during orchestration.

Salesforce Communications Cloud Developer Guide, "The Industries Data Model". This document outlines the relationship between Assets (what the customer bought) and Inventory Items (the technical details of what was provisioned), establishing Inventory Items as the source for technical attributes.

Salesforce Help, Industries Order Management, "Decomposition for MACD Orders". The documentation explains that decomposition logic uses the existing asset's state, which is derived from the technical inventory, to determine the necessary fulfillment actions.

The most maintainable and performant approach is to model the necessary customer data as fields on the Order object. The Order object serves as the central record for the transaction and naturally holds contextual information. During the Order Management fulfillment process, integration logic (such as an Integration Procedure) can easily retrieve these fields from the Order record and include them in the payload sent to the legacy application. This avoids polluting the product catalog with non-product data and simplifies the integration design, making it easier to configure and maintain.

A. This describes the implementation mechanism (an adapter) but not the recommended data modeling strategy, which is the core of the question.

C. Modeling customer data as Technical Products is incorrect data architecture. Customer information is not a product or service being sold.

D. Using multi-picklist attributes on the cart is not a scalable or appropriate way to store structured customer data like names, IDs, or addresses.

1. Salesforce Help, Industries Order Management Developer Guide, "Order Management Data Model". The documentation shows the Order object as the central object, linked to Account and other contextual information, making it the logical place to source data for fulfillment callouts.

2. Salesforce Architects, "Salesforce Industries (Vlocity) Order Management" design patterns often emphasize using the Order as the context for fulfillment, from which related data (like Account details) can be easily queried.

In B2C Communications Cloud the physical location (Premise) and the parent Business/Consumer Account must exist before dependent Service Accounts, Billing Accounts, Subscriptions, or Contracts can be created. Loading Premises first, then Accounts, allows subsequent objects to reference valid parent records.

A. Contracts reference Accounts; Accounts must exist first.

D. Subscriptions reference Service Accounts and therefore load after them, not before.

1. Salesforce Communications Cloud Data Migration Guide, “Recommended Load Sequence”, Table 3-2, p. 34, Spring ’24.

2. Salesforce Order Management Data Model, ERD diagram “Accounts, Premises and Subscriptions”, p. 8, Summer ’23.

3. Stanford CS275 “Enterprise Data Integration” notes, Module 4, ‘Parent-Child Load Dependencies’, slide 6.

The White Space Analysis dashboard in Tableau CRM for Consumer Goods Cloud is specifically designed to help identify growth opportunities. It analyzes sales data and product assortments to highlight which products are not being sold at a particular retail store, but are successful in similar stores or regions. This allows sales managers and reps to pinpoint specific, data-backed opportunities for introducing new products or expanding the existing portfolio at a store, directly addressing the company's goal.

B. Sales Rep Performance: This dashboard focuses on the activities and results of individual sales representatives, not on product placement opportunities at a store level.

C. Sales Manager- Territory Performance: This provides a higher-level view of a sales manager's territory performance, rather than granular, store-specific product gap analysis.

D. Account Insight: This dashboard offers a general overview of an account's health and history, but lacks the specific product "white space" analysis needed to find new selling opportunities.

1. Salesforce Help. (2023). Analytics for Consumer Goods. "White Space Analysis Dashboard". This document details the purpose of each dashboard, stating, "The White Space Analysis dashboard helps you identify cross-sell and upsell opportunities for stores."

2. Salesforce Help. (2023). Explore Analytics for Consumer Goods Dashboards. "Identify Cross-Sell and Upsell Opportunities". This section explicitly describes using the White Space Analysis dashboard to "find stores where you can sell more products."

The delivery task on the Consumer Goods Cloud mobile app displays items that are part of a shipment. The Shipment object acts as the container for the delivery, holding information about the products, quantities, and destination. For a user to see the list of items to be delivered, they must have at least read access to the specific Shipment record assigned to them. Without access to the Shipment record, the related delivery task will appear empty.

A. Product: Access to the Product object is necessary to see product details, but it doesn't link specific items to a particular delivery task.

B. Retail Store KPI: This object is used for tracking performance metrics and audits, not for managing the contents of a delivery.

D. Product Transfer: This object tracks inventory movement (e.g., from van to store), which is part of the delivery process, but the Shipment object defines the overall delivery.

1. Salesforce Help, Consumer Goods Cloud Implementation Guide, "Set Up Deliveries". This guide details the data model, explaining that a delivery visit task is based on a Shipment record, which has child ShipmentItem records detailing the products.

2. Salesforce Help, Consumer Goods Cloud Mobile App Guide, "Manage Deliveries". This section describes the mobile user flow, where a user selects a delivery task and views the products from the associated Shipment record.

The Custom Task KPI Component is designed to enhance specific task types within Consumer Goods Cloud. For tasks of type "Other," the standard record page is displayed by default. To override this and show the KPI component, two key configuration steps are necessary. First, the Lightning record page for the object related to the task must be explicitly edited in the Lightning App Builder to include the CustomTaskKPI component. Second, after the page is configured, it must be activated and assigned to the relevant user profiles. If either the page isn't configured with the component or it isn't assigned to the user's profile, the user will see the standard record page instead.

A. Lightning App Builder is the correct tool for configuring record pages to include custom components like the KPI component.

B. The Salesforce Mobile App is designed to render assigned Lightning Record Pages, not just default to standard pages.

C. The component's visibility is based on page layout configuration and assignment, not solely on whether the related object is custom.

Salesforce Help, Consumer Goods Cloud Implementation Guide, "Configure the Custom Task KPI Component". This document states, "For tasks of type Other, the standard record page is shown. To show the KPI component for tasks of type Other, configure the related object’s record page to include the CustomTaskKPI component... After you configure the page, assign it to the required user profiles."

An Attribute Assignment rule—implemented in Industries CPQ as an Advanced Rule—automatically sets or defaults a product attribute when a contextual condition (for example, an Account field) is met. Creating an Advanced Rule of subtype Attribute Assignment with a condition Account.SLA = “Gold” and an action that sets the Business TV product’s SLA attribute to “Gold” satisfies the requirement without user intervention.

A. Context Rules only control product eligibility/visibility; they can’t write attribute values.

C. Compatibility Rules govern which products can coexist, not attribute defaulting.

D. “Attribute Rules” isn’t a distinct rule type; attribute defaulting is delivered through Advanced Rules (Attribute Assignment).

1. Salesforce Industries CPQ Product Modeling Guide, “Configure Attribute Assignment (Advanced) Rules,” pp. 28-30, Winter ’24.

2. Salesforce Help, “Create Attribute Assignment Rules,” para. 2-3, 2023-10-18.

A planogram check assessment task requires a reference image of the ideal shelf layout for the field representative to perform a comparison. This image must be uploaded and associated with the planogram record that the assessment task definition references. While the image is technically stored on the Planogram object's Image field, option D is the only choice that correctly identifies the critical requirement of uploading the planogram image to make the check functional for the field team.

A. Einstein Object Detection is an advanced, automated feature for planogram compliance, not a prerequisite for a basic manual planogram check task.

B. The custom context field is not a standard requirement for configuring a planogram check; the functionality relies on standard object relationships.

C. Associating an In-Store Location is for targeting the correct planogram to a store, but it doesn't enable the visual check functionality itself.

1. Salesforce Help. (2023). Set Up Planogram Checks. "Upload the planogram image to the Image field on the Planogram record." and "Create an assessment task definition. For Planogram, select the planogram that you created."

2. Salesforce Consumer Goods Cloud Implementation Guide. (2023). Section: Planogram Management. "The planogram record holds the reference image used for compliance checks during a visit."