Salesforce Consumer Goods Cloud Accredited Professional (AP-204) Consumer-Goods-Cloud-Accredited-Professional Exam Dumps: Updated Questions & Answers (November 2025)

https://help.salesforce.com/s/articleView?id=sf.retail_task_admin_create_assessment_task_record_page.htm &type=5

 Inventory Check is a Lightning component that can be added to a Consumer Goods assessment task record page by an admin. An assessment task is a type of action plan task that allows users to collect data and perform actions related to a retail store. An inventory check is a type of assessment task that allows users to verify the availability and quantity of products in a store. The Inventory Check component displays the products that are associated with the store and allows users to search, scan, and update the product information. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 40.

The "Change of Plan" feature in Salesforce Communications Cloud (often accessed via Digital Commerce APIs or the Cart) is designed to handle the complex logic of modifying an existing customer's service portfolio. The three key offerings/capabilities are:

Supported by Digital Commerce APIs (A): Salesforce provides specific Digital Commerce (DC) APIs (e.g., getChangeOfPlanOffers or generateChangeOfPlan) that allow this complex logic to be exposed on self-service portals. This enables customers to view eligible upgrade/downgrade paths and execute the change without agent assistance, calculating pro-rated costs in real-time.

Moving to/out from the bundled offer (B): The feature is sophisticated enough to handle structural changes in the product hierarchy. It can take a standalone asset and move it into a bundle (e.g., moving a standalone internet line into a "Triple Play" bundle) or unbundle a service, maintaining the integrity of the commercial and technical data throughout the transition.

Service Continuity (E): A critical requirement in Telecom is that the "Change of Plan" (Commercial Change) does not accidentally disconnect the underlying technical service (Technical Change) unless intended. The Change of Plan feature ensures Service Continuity by preserving the link to the existing Technical Products (RFS) and Assets, ensuring that a customer upgrading their billing plan doesn't suffer a service outage during the provisioning process.

Why C and D are incorrect:

D (Customers can choose from all plans...): This is incorrect. The Change of Plan feature specifically uses Eligibility and Context Rules to filter the catalog. A customer on a Fiber plan cannot "choose" a legacy Copper plan if rules forbid it. They only see eligible target paths, not all plans.

C (History...): While Salesforce tracks field history and asset history, "Traceability" is a platform characteristic, whereas Service Continuity and Bundle manipulation are specific functional offerings of the Change of Plan logic engine.

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.

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 results or actual values of Custom Task KPIs are stored in the Retail Store KPI record, centralizing data related to performance indicators.

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

A data requirement to support successful creation of the Tableau CRM app for Consumer Goods Cloud is that products must be associated to retail stores. This is because the Tableau CRM app analyzes the sales performance and product distribution across different stores and segments, and identifies opportunities and gaps for product placement and availability. Without associating products to retail stores, the app cannot provide accurate and meaningful insights. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 37.

https://help.salesforce.com/s/articleView?id=sf.cg_concept_admin_notification_tasks.htm &type=5

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.

In Salesforce Industries (formerly Vlocity), large-scale B2B quoting scenarios—especially those involving multiple service accounts, hundreds of simultaneous quotes, and high-volume line-item configurations—are supported by the Enterprise Sales Management (ESM) application suite. Public Salesforce Industries resources describe ESM as the solution specifically engineered for complex B2B sales cycles, high-volume quoting, and enterprise-level product configuration.

ESM extends the functionality of Industries CPQ to support “high-line-item quoting environments,” allowing sales teams to manage thousands of products, hierarchical product bundles, account-specific pricing, and approval workflows. It is optimized for organizations selling advanced connectivity solutions, WAN, MPLS, SD-WAN, Dedicated Internet, and other enterprise-grade telecom services—exactly the type of offerings ABC Telecom delivers.

Salesforce’s public feature descriptions highlight that ESM supports:

Large quoting volumes (hundreds of quotes per customer)

Complex commercial hierarchies (B2B enterprise accounts with multiple service locations)

Scalable CPQ performance for 1,000+ line items

Enterprise contract, pricing, and proposal workflows

Multi-site, multi-service configuration

Other choices do not fit:

Advertising Sales Management focuses on media/advertising inventory buys.

Mobile Subscription Management is for B2C mobile postpaid/prepaid subscriptions.

Subscriber Lifecycle Management manages consumer subscriber journeys, not enterprise B2B quoting.

Thus, for ABC Telecom’s enterprise customer scenario with large, complex quotes, Enterprise Sales Management is the correct and Salesforce-aligned solution.