Free Practice Questions for Salesforce AP-204 Exam

Planogram analysis focuses on measurable shelf-compliance indicators such as Out of Stock, Share of Shelf, and product facings. These metrics allow a consumer goods organization to determine whether products are available, whether they occupy the expected proportion of shelf space, and whether the required number of product faces are visible to shoppers.

Salesforce defines Planogram Check as an assessment task used to track product displays and evaluate shelf execution. For planogram-related Retail Store KPIs, Salesforce explicitly maps Assessment Indicator Definitions to KPI types. Product-facing measurements use Facings, share-of-shelf measurements use Share of Shelf, and stock-availability measurements use Out of Stock. The facing measure is associated with individual products or SKUs when the organization needs to determine the number of visible product facings.

The underlying planogram model associates the reference Image with an In-Store Location and connects products to that location. During execution, those relationships provide the product-specific context required to assess whether the shelf configuration conforms to the intended merchandising arrangement. Shelf size itself is not one of the supported KPI types for this planogram-compliance configuration.

Study Guide Topics:Visit Execution - > Planogram Check - > Share of Shelf - > Facings - > Out-of-Stock Compliance

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

Promotions can be defined at the Product Category level or the individual Product level when the promotion has a product-specific commercial context. Salesforce also supports a general promotion with no product or product-category context, but among the listed options, Product Category and Product are the applicable promotion-definition levels.

A Product Category promotion applies the promotional activity to a collection of related products. This design is appropriate when the same commercial offer applies across an entire category, such as discounted beverages or energy bars. A Product-level promotion applies to one or more specific products, such as a new-product launch, sampling campaign, or SKU-specific discount.

Salesforce stores the relationship between a promotion and its individual products through Promotion Product. For category-based promotions, the relationship is represented through Promotion Product Category. Account, Retail Store Group, and Retail Store describe the reach or channel through which a promotion is distributed rather than the product level at which the promotion itself is defined. These destinations are associated through the Promotion Channel model.

This separation allows administrators to independently define what products a promotion concerns and where the promotion applies.

Study Guide Topics:Data Setup - > Promotions - > Product Level - > Product Category Level - > Promotion Product

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

Direct Store Delivery requires both the correct Action Plan configuration and the required user permissions. First, the administrator creates an Action Plan Template and adds a Delivery Task to it. When that template is assigned to a Visit, Salesforce creates the corresponding Delivery Task record for execution during the store visit.

Second, users who need to perform Direct Store Delivery functionality require the applicable Lightning Direct Store Delivery access. Salesforce identifies this permission set license for Direct Store Delivery capabilities in the Consumer Goods base data model. Delivery Tasks can then be associated with Shipments, which define the products to be delivered through related Product Transfer records.

Third, the Sales Manager requires access to Action Plans. Salesforce specifies the Action Plans permission set, or equivalent administrative privileges, for configuring and working with Action Plan Templates and Action Plans.

Assessment Indicator Definitions are used for KPI-based assessment activities and are not required to define the Delivery Task itself. The delivery process instead relies on the Delivery Task, Action Plan, Shipment, and Product Transfer architecture. Together, these three configuration steps provide the task definition, execution permission, and Action Plan access required for DSD operations.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Action Plan Template - > Permissions

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

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

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

A planogram is represented in Consumer Goods Retail Execution by an Image record. The Image object stores the reference representation of the expected product arrangement that a field representative uses during a Planogram Check.

Salesforce ' s Planogram Check prerequisites explicitly require administrators to create an Image record in the Image object representing the planogram at a store. The Image is then associated with the relevant In-Store Location, such as a primary shelf, aisle, checkout counter, or endcap. The Retail Store KPI subsequently references that Image through its Planogram field and combines it with the appropriate Assessment Indicator Definition, In-Store Location Category, Retail Store Group, and KPI Type.

When creating the Image record, the administrator can provide either the location URL of the image or upload an image file, specify the image category, activate the record, and make it available to field representatives.

During Planogram Check execution, representatives can open Product Details to review the expected reference image and compare the shelf arrangement against the merchandising standard.

Study Guide Topics:Data Setup - > Planogram - > Image Object - > In-Store Location - > Retail Store KPI

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

Flow-based activities execute within the context of the Visit and Assessment Task, while the Retail Execution KPI architecture maintains the relationship between Retail Store KPIs and Retail Visit KPIs.

Salesforce supports adding flows directly to an Action Plan Template. A flow can receive visitId, assessmentTaskId, or both as input parameters. These identifiers allow the flow to operate against the specific Visit and Assessment Task instance from which it was launched, ensuring that business automation remains tied to the correct retail execution transaction.

Retail Visit KPIs provide the transactional measurement layer for a visit. Salesforce documents that when an Action Plan Template is assigned to a Visit, Assessment Tasks are generated from Assessment Task Definitions and Retail Visit KPI records are created based on the applicable Retail Store KPIs. The Retail Store KPI defines the expected target and assessment context, while the Retail Visit KPI captures the visit-specific actual measurement against that target.

Salesforce ' s data model also records the Assessment Task ID, Visit ID, Assessment Indicator Definition, Target Value, and Actual Value on Retail Visit KPI records.

Study Guide Topics:Visit Execution - > Flow Tasks - > visitId - > assessmentTaskId - > Retail Store KPI - > Retail Visit KPI

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

The Delivery Task is the Consumer Goods Retail Execution object specifically designed to support Direct Store Delivery activities during a visit. It represents the delivery activity assigned to the field or delivery representative and provides the execution context through which shipments and individual product transfers are processed.

Salesforce separates the delivery process into several related records. The Delivery Task defines the activity that must be performed as part of the Action Plan associated with the Visit. A Shipment is then associated with that Delivery Task to identify the inventory that must be delivered. Products and quantities within the Shipment are represented through Product Transfer records.

This architecture allows the same delivery task framework to control execution while shipment records manage the physical movement of inventory. Salesforce specifies the Lightning Direct Store Delivery permission for users who perform Delivery Task functionality. When an Action Plan Template containing a delivery task is assigned to a visit, Delivery Task records are created and can subsequently be associated with shipments.

Therefore, Delivery Task is the purpose-built Consumer Goods object for initiating and managing Direct Store Delivery execution.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Shipment - > Product Transfer

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

The consultant should create an In-Store Location named Frozen Food Aisle. In-Store Locations represent distinct physical areas within a Retail Store and provide the location context required by Retail Execution tasks such as Inventory Checks and Planogram Checks.

Salesforce uses In-Store Location records to model store areas including shelves, aisles, checkout counters, backrooms, and promotional displays. Each location can be associated with an In-Store Location Category so equivalent physical areas across stores can be grouped and managed consistently. Salesforce ' s Retail Execution guidance demonstrates creating specific In-Store Location records directly from the Retail Store record and assigning appropriate location types and categories.

Products can then be associated with the relevant store location through Store Product. During an Inventory Check, the representative can select the appropriate In-Store Location and capture product availability, facings, share of shelf, or out-of-stock information for products located there.

Product2 represents the commercial SKU and does not identify its physical placement inside an individual outlet. Creating custom picklists or record types would duplicate the standard store-location model.

Study Guide Topics:Data Setup - > In-Store Location - > Inventory Check - > Store Product - > Store Layout

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

Einstein Visit Recommendations support Next Best Action strategies for determining which retail stores should be recommended for visits. Salesforce allows administrators to configure a recommendation strategy that evaluates relevant records and business criteria and produces prioritized visit recommendations for sales managers and field representatives.

A Next Best Action strategy can load relevant data, apply business rules, generate scores and reasons, and return recommendations that support store-visit planning. When a user creates a Visit Recommendation Request, the selected recommendation strategy is executed for the specified store and date context. Salesforce can also incorporate prediction information from Einstein Discovery when organizations require model-based recommendations.

The architecture separates recommendation logic from visit execution. Administrators can therefore create multiple strategies for different business priorities-for example, prioritizing stores with declining inventory, important upcoming promotions, or revenue opportunities. Salesforce documentation specifically supports both flow-based strategies and Next Best Action strategies for Einstein Visit Recommendations, enabling organizations to select the implementation approach that aligns with their planning logic and scalability requirements.

Accordingly, the ability to create Visit Recommendations through a Next Best Action Strategy is a standard supported configuration.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Next Best Action - > Recommendation Strategies - > Visit Prioritization

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