Consumer-Goods-Cloud-Accredited-Professional Questions and Answers

Action Plan Templates in Consumer Goods Cloud can be cloned, enabling users to replicate and modify templates for various purposes and scenarios.

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.

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.

For auditing coolers, a new custom Task Type would be most appropriate, as it allows the creation of a task specifically tailored to the unique requirements of cooler audits.

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.

To prevent Einstein from marking the competitor’s product incorrectly as their own product when measuring their share-of-shelf, the field rep should edit product tags. Product tags are labels that identify and count products in an image using Einstein Vision. Einstein Vision is a feature that uses artificial intelligence to detect and count objects in an image. By editing product tags, the field rep can correct any errors or inaccuracies in the object detection process and ensure that their own products and their competitor’s products are tagged correctly. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 24.

Einstein Visit Recommendations take into account factors like store operating hours to ensure that suggested visits are feasible and practical.

Salesforce Communications Cloud includes the Enterprise Product Catalog (EPC), which provides a structured and measurable approach to product lifecycle management. To track and measure time-to-market, Salesforce recommends leveraging the EPC Project framework, which is specifically designed to manage, bundle, and monitor product-related changes—from initial design through testing and deployment.

Option A: Leverage the EPC Project functionality

EPC Projects act as containers for all product modifications, including Product Specifications, Pricing, Rules, Attributes, and Versions. They include timestamps for creation, modification, approval, and deployment. Public Salesforce EPC guidance highlights Projects as the recommended mechanism for governance, visibility, and tracking across the product lifecycle. EPC Projects therefore provide the primary dataset required to calculate time-to-market (TTM).

Option C: Create a Salesforce Report on the EPC Project object

Because EPC Project records store metadata about the start, modification, and completion dates of product work, Salesforce Reports on the EPC Project object allow UC to measure cycle times directly. Using reporting tools, UC can track KPIs such as:

Time from Project creation to approval

Time from design to activation

TTM per product type or product launch initiative

Delays in approval or deployment

Why not B or D?

B (CRM Analytics template) — Salesforce does not provide a predefined "Product Time-To-Market" app template specific to EPC, and TTM cannot be measured solely from analytics without EPC Project metadata.

D (Reporting on Product object) — Product records themselves do not reflect lifecycle timestamps or governance workflows, so they cannot measure TTM accurately.

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.

Action plan templates can have multiple planogram, inventory and promotion checks, which are predefined tasks that can be assigned to field reps to perform during their store visits. These tasks help to ensure compliance and optimize product placement and availability. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 26-27.

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.

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.

Before migrating Communications Cloud data to a new org, Salesforce documentation stresses two critical readiness steps:

A. Ensuring all required fields and data points exist in the target org

Communications Cloud relies on a complex data model (EPC, Order Mgmt, Pricing, Attributes, EPC Projects, Fulfillment records). The target org must have all necessary fields and object configurations before importing data.

D. Metadata must match before migration

Migration cannot succeed unless product specs, attributes, price lists, technical product models, decomposition mappings, and orchestration metadata exist in the target org.

Metadata alignment is the #1 prerequisite for moving Communications Cloud data.

Incorrect options:

B: Running validation during migration is risky and not recommended.

C: Testing in production is strictly prohibited.

The Tableau CRM for Consumer Goods Cloud dashboard that can provide the required data for a Field Sales Manager to determine which stores have a decline in Retail Execution KPIs and therefore need attention is the Store Performance Dashboard. The Store Performance Dashboard shows the performance and compliance of the retail stores in relation to their KPIs and promotions. The dashboard allows users to filter and analyze the data by various dimensions, such as store group, store location, product category, or visit date. The dashboard also displays metrics such as store compliance score, store revenue, store visits, and promotion compliance score. By using this dashboard, a Field Sales Manager can identify which stores are underperforming or non-compliant and take appropriate actions to improve their performance. 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.

In Communications Cloud, the correct end-to-end modeling pattern is:

Commercial Product → DSL Internet

Attributes → Speed (5 Mbps, 50 Mbps) and derived Technology (ADSL, VDSL)

Customer Facing Services (CFS): ADSL CFS, VDSL CFS

Resource Facing Services (RFS): Copper Pair, Bonded Copper Pair

Multi-level decomposition: Commercial → CFS → RFS

This follows the standard Salesforce service modeling approach where CFS represents logical service layers, and RFS represents physical resources required to deliver the service.

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

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

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.

To ensure the field rep knows that the product is located in the frozen food aisle when performing an inventory check, the consultant should create an In-Store Location called Frozen Food Aisle’. An In-Store Location is an object that represents a specific area within a retail store, such as an aisle, a shelf, or a cooler. By creating an In-Store Location for the frozen food aisle, the consultant can associate it with the products that are stocked in that area and display it on the inventory check task. This way, the field rep can easily locate and verify the products in the frozen food aisle. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 20.

Assigning the Shipment object to the user enables the listing of items in the delivery task, as this object tracks the movement of products from warehouses to retail locations.

The Shipment object is specifically designed for managing direct store delivery processes, tracking the movement of goods from distribution to retail locations.

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.

Store Products are integral to various tasks in Consumer Goods Cloud, including inventory and promotion checks, as well as search and scan functionalities.

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.

In Salesforce Industries (formerly Vlocity) environments—especially relevant for Telecom, Media, and Energy—scenarios involving runtime price changes, agent-driven adjustments, and approval workflows are handled through Discounts, not Promotions or Context Rules. Discounts are specifically designed to allow flexible, rule-driven, and approval-controlled adjustments across the catalog, making them ideal when a company wants to equip call-center or retention agents with the ability to negotiate offers with outgoing customers.

Salesforce’s public guidance explains that Discounts support both manual and automated application methods. Administrators can enable runtime/manual discounts, specify discount types (percentage or fixed amount), and attach approval rules via the Industries Pricing Compliance framework. These can be targeted across the entire product catalog, specific product hierarchies, or only selected offers. This aligns perfectly with ABC Telecom’s requirement to apply pricing adjustments across the catalog and allow agents to make on-the-spot price changes.

While Promotions are useful for predefined marketing offers, they do not support agent-driven runtime flexibility. Context Rules automate pricing logic but do not provide agent-level manual control. CPQ Hooks require custom development and are not intended for business-driven discounting workflows.

Therefore, Discounts are the recommended and Salesforce-aligned feature for agent-controlled runtime adjustments, catalog-wide applicability, and approval process integration, exactly matching the needs of a telecom retention team.

In the Consumer Goods Cloud data model, several objects are linked to the Product2 object. These include Assortment Product, Assessment Task Product, and Promotion Product. This linkage is essential for comprehensive product management within the Consumer Goods Cloud.

Survey invitations associated with the visit, the Retail Store, and the Store Primary Contact are three survey invitations that are displayed in the In-Store Survey task during a visit. These survey invitations are relevant to the context of the visit and can help users to collect feedback from the store staff or customers. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 27.

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.

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.

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.

These permissions ensure that users have the necessary access to view and interact with the Tableau CRM for Consumer Goods Cloud app, providing critical analytics and insights.