Free CONSUMER-GOODS-CLOUD-ACCREDITED-PROFESSIONAL Exam Dumps Preview

Lightning Direct Store Delivery is the correct permission set because it grants access to delivery task functionality and the related direct store delivery objects. Tableau CRM View and CG Analytics User are analytics-related permissions, while Retail Execution Lightning Plus is not the permission set used specifically for direct store delivery access.

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

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.
References:
[Salesforce Consumer Goods Cloud Implementation Guide], page 27.

https://help.salesforce.com/s/articleView?id=sf.retail_task_admin_create_assessment_task_record_page.htm&type=5InventoryCheckisaLightningcomponentthatcanbeaddedtoaConsumerGoodsassessmenttaskrecordpagebyanadmin.
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.
References:
[Salesforce Consumer Goods Cloud Implementation Guide], page 40.

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

Visits must be the base object because the requirement is to visualize visits, not stores or accounts. Color-coding by status directly supports the need to distinguish current visit states. The other options are based on the wrong records or do not match the requested behavior.

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.

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.

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.

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

Promotions are linked to Retail Stores through Promotion Channel records, which define the connection and details of the promotional activities.

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.

Industries Order Management (OM) provides multiple orchestration item types to manage human tasks, system tasks, and external service calls. For field technician data capture, Salesforce recommends manual data capture orchestration items combined with OmniScripts, so technicians enter information directly instead of relaying it verbally-reducing errors and improving data quality. A Manual Orchestration Item (Option C) creates a human task assigned to a technician and pauses the orchestration until the technician completes the task. This is the exact pattern used when capturing installation details, device identifiers, serial numbers, modem MAC addresses, or activation parameters. A Push Orchestration Item (Option A) is also applicable when a task must be automatically "pushed" to an external party (like a field technician mobile app). The Push item assigns the work and embeds the OmniScript UI, enabling the technician to directly enter data, ensuring accuracy and eliminating the error-prone phone call process.
Options B and D (Milestone and Callout items) represent automated system tasks and do not support
interactive technician data capture.

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

As part of digital transformation, Salesforce strongly recommends consolidating all product definitions into a single Enterprise Product Catalog (EPC) within Communications Cloud. EPC becomes the system of record for all commercial and technical products across channels. To expose this single catalog to external sales channels, Salesforce provides Digital Commerce APIs, which deliver: Product discovery Attribute & configuration rules Pricing & Promotions Availability & context-driven offerings.
These APIs allow web channels, portals, mobile apps, and external systems to retrieve catalog data in real time without duplicating product definitions. This removes the need for separate catalog maintenance and guarantees consistency across channels.
Option A uses Cart APIs, which only apply once a product is already in the cart. It does not expose catalog discovery.
Option C (periodic sync) is not recommended-Salesforce discourages dual catalogs.
Option D (new catalog system) adds unnecessary complexity.

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 survey task surfaces invitations that are relevant to the visit context: those linked to the visit, the retail store, and the primary contact. It does not display all invitations in the org, and closed invitations are not the intended task focus.

A promotion check is a type of action plan task that allows a field rep to verify if a promotion is running correctly at a retail store. When executing a promotion check in the field, two standard capabilities are available: viewing which products are included in the promotion and taking a photo of the promotion.
These capabilities help to ensure compliance and capture evidence of promotional execution. Verified
References:
[Salesforce Consumer Goods Cloud Implementation Guide], page 27-28.

Planogram detection supports KPI analysis such as Out of Stock, Share of Shelf, and SKU Facings.
Promotion Cost and Delivery Variance are not standard planogram-detection outputs.

Salesforce Communications Cloud supports rich pricing models using Matrix-Based Pricing (MBP). Matrix- based pricing is the recommended method when pricing depends on multiple attributes from Account, Product, or other context properties.
For One-Time Charges (OTCs), Salesforce recommends separate pricing matrices, not combining OTC logic inside recurring matrices. OTCs often have different conditioning logic, different triggers, and different applicability rules than recurring charges.
Option follows the supported pattern: B
Define a new matrix for OTC pricing
Use relevant Account attributes (tier, segment, SLA level)
Use relevant Product attributes (speed, class of service, add-ons) Output the appropriate OTC amount Options A and C introduce unnecessary custom logic or create nonstandard product artifacts. Option D is incorrect because recurring pricing matrices must not be overloaded with unrelated OTC fields-Salesforce documentation recommends separating matrices by charge type.

In the future-state Communications Cloud architecture, integrations such as real-time credit checks must be performed using an adaptive, low-code, API-driven layer. Salesforce's recommended capability for this is OmniStudio -specifically Integration Procedures and DataRaptors -which provide: Highly performant server-side callouts Ability to orchestrate multiple APIs in a single transaction Transformation, mapping, and response handling Reusability across Digital Commerce, CPQ, and Order Management Zero Apex requirement Order Management (B) handles fulfillment orchestration, not customer qualification or credit checks. CPQ (A) performs configuration and pricing logic. EPC (D) is catalog-only and does not manage integrations.
Thus, OmniStudio is the correct capability for credit check integrations.

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 reflects this: a C 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 the correct choice.
C