Pass the Salesforce Consumer Goods Cloud AP-204 Questions and answers with Dumpstech

Promotion Check functionality is intended to allow field representatives to validate whether a planned promotion has been executed correctly at a retail location. Two important execution capabilities are reviewing the products included in the promotion and capturing photographic evidence of the promotional display.

Salesforce supports promotions at Product Category, individual Product, and General Promotion levels. When performing the check, the representative needs visibility into the promotion context so the correct products or categories can be inspected. Product information establishes exactly what must be evaluated and prevents the representative from auditing unrelated merchandise.

Photo capture provides supporting visual evidence of the in-store execution. This is particularly useful for validating display placement, promotional materials, shelf presentation, or other compliance requirements. The recorded observation can then be evaluated together with applicable assessment indicators and Retail Store KPI targets.

Planning dates and discounts are part of promotion configuration and commercial planning rather than field compliance execution. The field representative ' s responsibility during the visit is to observe, validate, and record execution rather than modify the underlying promotional terms.

Therefore, viewing promoted products and taking photographs are the applicable standard field-execution capabilities.

Study Guide Topics:Visit Execution - > Promotion Check - > Products - > Compliance - > Photo Capture

===============

Consumer Goods can be customized declaratively through Lightning App Builder and Flow, while Lightning Web Components provide the component-level extensibility required for specialized user experiences.

Lightning App Builder allows administrators to configure Salesforce record pages by placing and configuring standard components without rebuilding the underlying application. This supports customer-specific page composition while remaining within the Salesforce Platform configuration model.

Where more specialized behavior is required, Lightning Web Components provide an extensibility layer. Salesforce supports custom LWCs that interact with standard components and extend or modify business functionality. For example, Salesforce ' s Consumer Goods extensibility documentation describes using custom LWCs alongside standard components so custom interactions and data changes can be reflected in the standard experience.

For process-oriented customization, administrators can create Flows and associate them directly with an Action Plan Template. Salesforce states that flows can implement activities specific to a business that are not covered by standard Consumer Goods task types. Once associated with the template, those flows become available to field representatives during store visits.

The Consumer Goods mobile platform also supports LWC-based mobile extensions through its integration framework, keeping customization aligned with Salesforce Platform technologies rather than requiring Apache Cordova development.

Study Guide Topics:Platform - > Mobile Customization - > Lightning App Builder - > Lightning Web Components - > Flow - > Action Plan Templates

===============

Einstein Visit Recommendations provide decision support for sales managers and field representatives by helping them determine which stores should receive attention and when those visits should be scheduled. The capability supplements the expertise of the field organization by presenting prioritized information derived from business rules and prediction insights.

Salesforce describes the feature as a mechanism for scheduling the right stores at the right time in order to maximize profit and deliver brand value. Visit Recommendations can identify stores that have not been serviced recently and present recommended visits that users can review and schedule. Managers remain responsible for deciding which recommendations to accept and for coordinating execution.

The recommendation architecture can use configurable flow strategies or Next Best Action strategies. Organizations can tailor the logic to their own business requirements rather than relying on a mandatory external market-research dataset. This enables field professionals to focus their expertise on selling, merchandising, customer relationships, and execution while Salesforce surfaces relevant visit-planning intelligence.

The intended value is therefore workforce augmentation and improved prioritization-not replacement of experienced personnel.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Recommendation Strategies - > Store Prioritization - > Field Productivity

===============

The Sales Manager persona is responsible for managing the day-to-day Retail Execution processes performed by the field organization. Salesforce explicitly defines the Sales Manager as a standard Retail Execution user who can create visits, create tasks, and assign visits to field representatives.

This division of responsibilities is fundamental to the Agentforce Consumer Goods operating model. Sales managers coordinate retail coverage and determine what activities field representatives should perform at each store. They typically work with Retail Stores, Visits, Action Plans, Assessment Task Definitions, and Action Plan Templates to organize execution activities. By contrast, field representatives have a more execution-focused role: they review assigned visits, complete assessment tasks, capture observations, process orders, and record the results of store activities.

The permission model is designed around these personas. Salesforce recommends establishing separate permission configurations for Sales Managers and Field Reps so that each role receives the appropriate object-level and feature access. Delivery representatives can also be configured separately when the organization uses Direct Store Delivery.

Consequently, responsibility for creating and coordinating visits and assigning field work belongs to the Sales Manager persona.

Study Guide Topics:Platform - > User Personas - > Sales Manager - > Visit Management - > Task Assignment

===============

The consultant must identify the hierarchy level that represents the stock keeping unit (SKU). In the Consumer Goods Retail Execution data model, individual products are represented through Product2 records, and Salesforce describes each Product2 record as a SKU or sellable unit. Consequently, the ERP hierarchy level that contains SKU-level information provides the appropriate product granularity for product-specific retail execution processes.

Share-of-shelf measurement requires Salesforce to identify precisely which products occupy shelf space so that actual shelf presence can be evaluated against configured targets. Retail Store KPIs can associate Assessment Indicator Definitions such as Share of Shelf with products, product categories, planograms, store groups, and in-store location categories. The underlying product master therefore needs a level that reliably represents the individual sellable products being measured.

Salesforce product master data can contain multiple hierarchy levels such as categories, subcategories, brands, and SKUs. The numerical position of a tier is not itself significant; what matters is the business meaning of that tier. For this requirement, the tier representing SKUs provides the required product-level data for shelf measurement and Retail Execution processing.

Study Guide Topics:Data Setup - > Product2 - > Product Hierarchy - > SKU - > Share-of-Shelf KPI

===============

An Action Plan Template intended for retail visit execution must be configured with Visit as its Target Object and then published before it can be associated with an individual Visit. The Target Object determines the Salesforce record type against which Action Plans created from the template can operate.

Salesforce ' s Consumer Goods configuration procedure specifies that administrators create an Action Plan Template, select Visit in the Target Object field, configure the appropriate Action Plan Type, add the required tasks and flows, and publish the template. A published template can subsequently be reused across multiple Visit records, which enables standardized store-execution processes.

To apply the template, a user opens the applicable Visit, selects New Plan from the Action Plan related section, and chooses the published Action Plan Template. Salesforce then presents the tasks contained in the template and creates the Action Plan for that specific visit. Only one Action Plan can be assigned to a Visit through this standard process.

This architecture separates reusable process design from visit-specific execution and ensures consistent field activities across stores.

Study Guide Topics:Visit Planning - > Action Plan Template - > Target Object - > Visit - > Publish Template

===============

A custom task implemented with Flow is the appropriate architecture when the information to be captured does not fit the standard Inventory Check, Planogram Check, Promotion Check, Order Creation, or In-Store Survey task types. Salesforce specifically provides the Other assessment task type for custom business activities that require organization-specific data capture.

For asset compliance, an administrator can create an Assessment Indicator Definition with a Boolean data type to capture whether the asset meets the required compliance condition. Assessment Indicator Definitions support Number, Boolean, Date Time, Text, Decimal, and Picklist data types, making Boolean appropriate for a compliant/non-compliant assessment.

The custom task can be connected to the relevant business record through the Custom Context field of the Retail Store KPI. Salesforce supports standard or custom objects as custom-task context when the object supports activities. Flow can then evaluate the captured Boolean value and invoke the required follow-up automation, such as generating corrective actions or other downstream processes.

Using Flow instead of Apex follows Salesforce ' s declarative automation model and minimizes custom code while keeping the logic maintainable by administrators.

Study Guide Topics:Visit Execution - > Custom Tasks - > Assessment Indicator Definition - > Boolean KPI - > Flow Automation

===============

Users who need to access the CRM Analytics application for Consumer Goods require both the CRM Analytics Plus User entitlement and the CG Analytics User permission set. In the terminology used by this question, CRM Analytics Plus User corresponds to Tableau CRM Plus User.

Salesforce separates platform analytics access from Consumer Goods-specific analytics permissions. CRM Analytics Plus User provides access to CRM Analytics capabilities, while CG Analytics User grants the permissions required to consume the Consumer Goods analytics application and its associated dashboards and datasets.

Salesforce ' s documented setup process instructs administrators to open the user ' s Permission Set Assignments and assign CG Analytics User together with CRM Analytics Plus User when the organization uses CRM Analytics for Consumer Goods Cloud.

This dual-permission approach ensures that the user has both the underlying analytics platform entitlement and the Consumer Goods application-level access required to view dashboards such as product, store, field-representative, and territory performance analytics.

Administrative permissions such as CRM Analytics Plus Admin are intended for administrators who configure and maintain analytics applications. They are not necessary for ordinary application consumers who only need to view and interact with Consumer Goods analytics.

Study Guide Topics:Analytics - > CRM Analytics - > CG Analytics User - > CRM Analytics Plus User - > User Permissions

===============

Users performing Delivery Tasks in the Consumer Goods base data model require access to the Lightning Direct Store Delivery functionality. Salesforce specifically identifies the Lightning Direct Store Delivery permission set license as the feature-specific entitlement required for Direct Store Delivery and van-sales functionality on the base data model.

Delivery Tasks involve objects and functionality beyond general Retail Execution. The delivery process can include Delivery Task, Shipment, Product Transfer, and Product Item records. Salesforce documentation also identifies Lightning Direct Store Delivery as the required user permission when creating Delivery Tasks in Action Plan Templates and when associating those tasks with Shipments.

If the tester does not have the required Direct Store Delivery access, delivery-related test cases can fail even when the underlying visits, action plans, shipments, and products have been configured correctly. General Retail Execution permissions alone do not provide the full set of Direct Store Delivery capabilities.

Geofencing is not the controlling authorization mechanism for Delivery Task access, and Retail Store KPI target values are unrelated to whether the tester can execute the Direct Store Delivery functionality.

Therefore, permission assignment should be verified early in delivery-task rollout testing.

Study Guide Topics:Platform - > Permissions - > Lightning Direct Store Delivery - > Delivery Tasks - > User Access

===============