Free and Premium Salesforce Consumer-Goods-Cloud-Accredited-Professional Dumps Questions Answers

To keep track of the inventory of the samples in the field, Alpine can create delivery tasks for the distributors and monitor their on hand inventory for the sample Product’s Stock Keeping Unit (SKU). A delivery task is a type of action plan task that allows a field rep to deliver products to a retail store. A product SKU is a unique identifier for a product that can be scanned and tracked in inventory systems. By creating delivery tasks and monitoring product SKUs, Alpine can ensure that the distributors have enough samples to distribute and also track how many samples have been delivered to each store. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 28-29.

For a residential B2C scenario in Communications Cloud, Salesforce recommends a short, direct sales flow that minimizes CRM steps like Leads and Opportunities. In B2C, the objective is usually to let customers (or agents on behalf of customers) configure, price, and purchase in as few steps as possible, often closing within a single interaction or within a very short time window—well within UC’s three-day target.

Communications Cloud provides a pattern where CPQ actions are performed directly on the Order object for B2C/B2B2C flows, especially when:

The sales cycle is short.

There is no need for complex pipeline management.

The customer is buying directly (web, community, call center).

Option C reflects this: a Custom Buyflow (OmniScript) is used as the guided selling UI, invoked in a way that works for agents and authenticated community users, and it operates directly on the Order as the commercial transaction record. CPQ logic (cart, pricing, validation, promotions) is executed on the Order, which aligns with standard B2C digital commerce patterns in Communications Cloud.

Option A and B introduce a heavier Lead → Opportunity → Quote → Order process, which is more appropriate for complex B2B sales and contradicts the “short sales process” requirement. Option D still centers the process on a Quote, which is typically used where negotiation or longer cycles are expected. For UC’s fast B2C use case with direct or assisted buying, Order-centric CPQ via a Buyflow (OmniScript) is the recommended approach, making C the correct choice.

To track pricing changes, Salesforce recommends enabling Field History Tracking on Price List Entry, which logs:

Old price

New price

User

Time of change

This is the simplest way to review previous pricing.

Why others are wrong:

A requires custom triggers—not recommended.

C EPC Project history tracks metadata changes, not price list values.

D Versioning is for product specifications, not PLE prices.

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.

To allow Sales Managers to create and assign delivery tasks to deliver, the following setup steps should be configured:

Create an action plan template with a Delivery Task and assign it to a Visit. A Delivery Task is a type of action plan task that allows a field rep to deliver products to a retail store. A Visit is a scheduled or unscheduled interaction between a field rep and a retail store.

Assign the Lightning Direct store Delivery permissions set to the user. This permissions set grants access to the delivery task functionality and related objects, such as product transfers and shipments.

Assign the Action Plans permission set to the Sales Manager. This permissions set grants access to the action plan functionality and related objects, such as action plan templates, action plan tasks, and assessments. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 28-29.

Creating a distinct set of KPIs for endcap locations allows NTO to specifically track and analyze the performance of these areas, providing targeted insights.

Industries Order Management should only react to relevant provisioning milestones. Sending every network event overwhelms the platform and wastes governor limits. Therefore:

The middleware/integration layer filters milestones.

Only relevant milestones trigger Push Event Orchestration Items inside OM.

OM receives the filtered event and progresses the order.

This is the recommended, scalable pattern.

Why others are incorrect:

B is wrong: irrelevant milestones still impact limits.

C sending all milestones is inefficient and unnecessary.

D letting an Integration Procedure manipulate order status is not how OM is triggered.

For B2B telecom companies dealing with complex configurations exceeding 1000 line items, the only Salesforce Communications Cloud solution purpose-built for performance, scalability, and large enterprise quoting is Enterprise Sales Management (ESM).

ESM enhances the CPQ experience by supporting:

Extremely high cart volumes (hundreds to thousands of lines)

Multi-site, multi-location enterprise networks

Enterprise-grade discounting and contract structures

Scalable pricing, validation, and asset handlings

Better separation of commercial vs. technical configurations

Options A, C, and D do not address enterprise-scale CPQ needs with thousands of line items. Large Account Sales Management focuses on account planning, not CPQ performance. Multiplay Subscription Management and Multi-site CPQ do not solve the scalability challenge.

To meet the requirements of offering regional pricing and ensuring customers can see the correct price before adding the product to the cart (i.e., while browsing the catalog), the solution must rely on Context Rules that evaluate the customer's profile (Region) prior to product configuration.

B. Create a Base Price List and Multiple Child Price Lists associated with Context Rules per region:

In Salesforce Industries (Communications Cloud) CPQ, Price Lists are the primary container for prices. You can create specific price lists for each region (e.g., "New York Price List," "Texas Price List") and use Context Rules to automatically assign the correct price list to the user's session based on their Account or Quote details (Region).

Because the Price List is selected before the product is viewed, the catalog automatically displays the price entries from that specific regional list, satisfying the visibility requirement.

D. Create multiple Price List Entries associated with Context Rules per region:

Alternatively, you can use a single global Price List but create multiple Price List Entries (PLEs) for the same "Business Internet" product (e.g., one entry for $50, another for $60).

You can apply Context Rules directly to these Price List Entries. When the catalog renders, the system evaluates the rules against the customer's context (Region) and filters the entries, showing only the one valid for that region.

This allows for granular control at the product price level without necessarily duplicating entire price lists.

Why A is incorrect: Attribute-based Pricing Matrices are typically used for calculating prices based on product attributes that a user selects during configuration (e.g., Speed, Color). Since the requirement is to see the price before adding to the cart (pre-configuration), and Region is a context of the customer not a feature they configure on the product, Context Rules (B & D) are the correct architectural choice.

&type=5

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.

KPI Type is a required field for setting up Retail Store KPIs. Retail Store KPIs are key performance indicators that measure how well a retail store is performing against a specific goal or target. The KPI Type defines the type of metric that is being measured, such as share of shelf, out of stock, or promotion compliance. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 30.

These steps enable the setup of survey assessment tasks in Consumer Goods Cloud, ensuring the surveys are well-defined and integrated with retail store activities.

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

The Click2Create function is a feature of Consumer Goods Cloud that allows a field rep to create a new retail store record from the mobile app by tapping on a point of interest on a map. This function automatically fills in the address fields with the data from the map and also allows the field rep to attach a follow up case or lead to onboard the outlet on an onboarding journey. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 34-35.

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.

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.

In the Consumer Goods Cloud, Retail Store KPI records support various KPI types, including Units, Facing, and Revenue. These KPIs are critical for assessing retail performance.

A consultant at NTO should determine which tier of data contains the information required to set up products in Consumer Goods Cloud by asking which tier describes stock keeping units (SKU). A SKU is a unique identifier for a product that can be scanned and tracked in inventory systems. SKU is the level of data that is needed to measure share of shelf, which is the percentage of space occupied by a product or brand on a shelf. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 19.

When performing a search in an inventory check task, only the products that are associated with the retail store are considered for the search. This is because the inventory check task is designed to verify the availability and quantity of products in a specific store location. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 28.

Salesforce best practice for Order Management is:

▶ Use a single Orchestration Plan Definition when the overall fulfillment flow is the same,

but

▶ Use conditional Orchestration Items to handle differences (e.g., activation vs. deactivation).

In this case, the provisioning system needs different payloads for activation and deactivation, but the product is the same. Designing two separate orchestration plan definitions creates duplication, maintenance overhead, and inconsistent lifecycle behavior.

Instead:

Use one Orchestration Plan Definition.

Include two Orchestration Item Definitions, one for Activation and one for Deactivation.

Apply mutually exclusive conditions using Product Action = Add (activation) or Disconnect (deactivation).

Map both actions in one Scenario.

This achieves minimal configuration and full flexibility.

This approach allows for an efficient and code-minimal way to check compliance of high-value assets in stores and trigger correction action plans based on Boolean values.

For integrations where the provisioning/ERP system returns an external order ID in a synchronous response, Salesforce recommends using the Response DataRaptor Bundle of the Integration Procedure or Process Library.

The Process Library already includes patterns for handling:

Create Order callouts

Handling synchronous responses

Mapping response fields into Salesforce objects (e.g., SFI Order, Fulfillment records)

You simply extend the Response DataRaptor to:

Extract ERP Order Identifier from the response payload.

Save it onto the corresponding Salesforce Order record for audit and troubleshooting.

Why other options are incorrect:

B: Auto Tasks are for async flows; the requirement is synchronous.

C: Enhancing the OOTB adapter is not recommended—declarative DR bundles should be used.

D: Creating a separate GET callout is unnecessary because the identifier is returned in the synchronous CREATE response.

Thus, A is the Salesforce-recommended approach.

These dashboards provide comprehensive insights into various aspects of consumer goods operations, from category performance to individual sales rep and store analyses.

In Salesforce Communications Cloud, the B2C customer model follows a structured, layered hierarchy designed to support ordering, billing, service management, and asset lifecycle handling. When migrating existing B2C customers into Communications Cloud, Salesforce’s public architecture guidance specifies a top-down data dependency sequence to ensure that parent records exist before child records referencing them are inserted.

The migration sequence begins with Users, since many operational objects (orders, cases, ownership, provisioning workflows) require an active user as the record owner or last modified by. Next, Contacts are required for each B2C customer because Communications Cloud uses Contacts associated with a Consumer Account to represent the individual subscriber. Although Person Accounts are supported in some Salesforce products, Communications Cloud standard data model for B2C uses Consumer Accounts + Contacts, which aligns with option A—not C.

Once contacts are created, Consumer Accounts must be migrated so that customer identity, householding, service relationships, and billing mappings can be referenced. With accounts in place, Billing Accounts are imported next to link financial agreements, billing preferences, and invoicing relationships.

Service Accounts follow, serving as the service location or logical container for active telecom services. Only after these parent entities are established can Subscriptions be migrated, as they represent the commercial products the customer is consuming. Finally, Assets are migrated, representing the technical products or devices (routers, SIMs, set-top boxes) associated with active subscriptions and services.

Options B, C, and D omit Subscriptions, which are essential for B2C migration into Communications Cloud. Option C incorrectly uses Person Accounts, which does not match the Communications Cloud standard B2C data model.

The key to identifying the technically feasible options for creating a guided ordering process in Salesforce Communications Cloud (Industries) is understanding how OmniStudio components (specifically OmniScripts) are deployed across different channels (internal agents vs. external customers on different platforms).

Agents: For internal Sales Agents, the standard and recommended approach is to use OmniScript. OmniScripts are designed to guide users through complex processes like CPQ ordering, providing a step-by-step interface directly within the Salesforce Console. This validates the "Use OmniScript... for agents" part of options B and C.

B2C Customers (Third-Party CMS): When customers interact via a third-party Content Management System (CMS) (e.g., Adobe Experience Manager, WordPress) rather than a Salesforce-hosted site, you cannot simply embed a standard Lightning Web Component. OmniOut is the specific Salesforce Industries feature designed for this scenario. It allows you to compile an OmniScript into a framework-agnostic web component (Standard Web Component) that can be hosted on an external server or CMS while maintaining connectivity to Salesforce logic. This validates Option B.

B2C Customers (Salesforce Experience): When customers interact via a Salesforce Experience (formerly Community Cloud), the native way to deploy the guided process is to use the OmniScript component directly in the Experience Builder. While the phrasing "OmniScript via OmniOut on a Salesforce Experience" in Option C is slightly redundant (you don't need OmniOut for a Salesforce site), technically, OmniOut can run anywhere a web component runs, and some complex architectures might use it for consistency. However, in the context of exam questions where "OmniScript via Community Builder" is the standard answer, Option C is often presented alongside Option B as the "Customer" solutions.

Correction/Refinement: Looking at the search results (Source 1.1, 1.4), the exam dumps explicitly list the correct answer set as A, C, D (where A is Flow for agents/customers via Lightning Out - technically feasible but rare, C is OmniScript for agents + OmniScript via Community Builder for customers, and D is OmniScript for agents + OmniScript via OmniOut for CMS).

Wait, let's re-examine the provided options in your specific question text. You only listed A, B, C.

Option A: Flow for Agents + Flow via Lightning Out on CMS. (Technically feasible, but not the "Comms Cloud" standard).

Option B: OmniScript for Agents + OmniScript via OmniOut on CMS. (Strong Yes - This is the textbook definition of OmniOut's use case).

Option C: OmniScript for Agents + OmniScript via OmniOut on Salesforce Experience. (Technically "feasible" but weird/wrong best practice). However, if the option meant "OmniScript on Salesforce Experience" (without OmniOut), it would be perfect.

Exam Dump Verification: In the search results (Source 1.1), the options are slightly different:

"Use Omni Script for building the guided ordering journey for agents and call Omni script via community builder on a salesforce community..." (This corresponds to your Option C if we interpret "via OmniOut" as a typo or a distractor in your text, or if your text is a variation).

"Use OmniScript... and expose OmniScript via OmniOut on a third-party CMS..." (This corresponds to your Option B).

Given the options provided in your prompt (A, B, C), and knowing that Communications Cloud relies heavily on OmniScript for CPQ:

B is definitely correct. (OmniScript for Agents, OmniOut for CMS).

C is likely the second correct answer intended, despite the "via OmniOut on Salesforce Experience" phrasing potentially being a trick or typo for "via Community Builder". (Or, it implies using the Off-platform capability within an Experience site, which is possible if you are doing a complete headless implementation).

A (Flow) is generally incorrect for Comms Cloud CPQ ordering because Flows do not natively handle the Vlocity CPQ APIs (Cart-based APIs) as effectively as OmniScripts with Integration Procedures.

Constraint Check: You asked for two options.

B and C represent the two valid OmniScript deployment models (External CMS vs. Salesforce Community), which is the core learning objective.

The Einstein Vision model is a representation of how objects are detected and counted in an image. The model needs to be created as part of the development process using a base set of images. The base set of images should contain images of the products that need to be detected on the shelf, as well as labels and annotations for each product. The model is then trained and tested using these images and can be improved by adding more images or adjusting the parameters. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 23-24.

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

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.

To visualize store visits in their territory for the day by their current status, an Account Manager can create a map layer using visits as the base object and color code the markers by status. A map layer is a visual representation of data on a map that can be filtered and customized. A visit is an object that represents a scheduled or unscheduled interaction between a field rep and a retail store. The status of a visit indicates whether it is planned, in progress, completed, or canceled. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 34.

Einstein for CG- Visit Recommendations is a feature that uses artificial intelligence to suggest optimal store visits for field reps based on predefined rules and criteria. By adopting this feature with the consumer goods cloud, professionals can focus on their work while having information served to them that will support them in being competitive. For example, they can prioritize the most profitable or strategic stores, avoid unnecessary or redundant visits, and optimize their routes and schedules. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 36.

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.

Retail Store KPIs are key performance indicators that measure how well a retail store is performing against a specific goal or target. For a promotional end cap audit, Retail Store KPIs should be defined at the energy bar product category level, as this would capture all the energy bars that are included in the BOGO promotion and also minimize the number of records created. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 30-31.

This scenario involves managing the lifecycle of data stored in custom child objects (Object A attached to Order Items, and Object B attached to Assets). To ensure data integrity throughout the full commercial cycle—Sale (Assetization) and Change (MACD)—a bidirectional mapping strategy is required using the Custom Object Map feature (referred to as Object Mapper in the options).

Assetization (Order to Asset Flow):

When an order is completed, the system runs the "Assetize" process.

To move data from the custom object under the Order Item (Object A) to the custom object under the Asset (Object B), you must define a Source-to-Destination mapping.

This is the A $\rightarrow$ B mapping. Without this, the custom data entered during the sale would be lost and not stored on the customer's asset record.

MACD / Asset-Based Ordering (Asset to Order Flow):

When a customer requests a Move, Add, Change, or Delete (MACD), the system creates a new Order/Quote by reading the existing Asset data.

To ensure the new "Change Order" includes the current details from the Asset (Object B) back onto the line items (Object A) for the agent to view or modify, the system requires a reverse mapping.

This is the B $\rightarrow$ A mapping.

Why other options fail:

Option A (Apex Hook): While feasible for complex edge cases, using Apex is not the best practice when a declarative configuration tool (Object Maps) exists for this exact purpose. It increases maintenance debt.

Option B (Map A to B only): This handles the initial sale but fails during MACD. When the customer tries to change their service later, the data from Object B would not copy back to the new order, leading to data loss or errors.

Option C (Field Mapper): Field Mappers are typically used for mapping specific fields on the primary objects (e.g., OrderLineItem.Description to Asset.Description). For mapping entire related child objects, the Object Map mechanism is the correct architectural component.

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.