AP-204 Salesforce Accredited Agentforce Consumer Goods Professional Free Practice Exam Questions (2026 Updated)

Frequently purchased products can be prioritized for a specific outlet by associating them through Store Product and marking the appropriate products as Favorite. Store Product represents the relationship between Product2 and a Retail Store or specific In-Store Location, which allows Salesforce to maintain outlet-specific merchandising and ordering attributes.

The Store Product data model includes both Is Favorite and Default Order Quantity. These attributes are designed to streamline recurring order capture. Salesforce explains that field representatives can prioritize favorite products when creating orders so commonly purchased items are replenished efficiently and remain in stock. Default Order Quantity can further reduce data entry by predefining the quantity normally ordered for the product.

Salesforce ' s Retail Execution configuration also allows products associated with a store to be marked as favorites. The Inventory and ordering user interfaces can expose favorite products as a focused subset, reducing the time required to create routine orders.

This makes Store Product the correct outlet-specific mechanism for modeling frequently ordered products rather than creating artificial Order records with a template status.

Study Guide Topics:Visit Execution - > Order Capture - > Store Product - > Favorite Products - > Default Order Quantity

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

A Shipment must be associated with the Delivery Task so that the products scheduled for delivery can be presented during execution. In Salesforce Direct Store Delivery, the Delivery Task provides the activity context, while the Shipment defines the inventory movement that the field representative is expected to complete.

Salesforce specifies that after a Delivery Task is generated from an Action Plan Template assigned to a visit, the task must be associated with a Shipment. Products are then added to that Shipment through related Product Transfer records. Each Product Transfer identifies the product and quantity involved in the shipment.

This hierarchy is important because the Delivery Task does not independently maintain its own product list. Instead, it obtains the delivery-item context from its related shipment. A standalone Product record does not establish that the product is scheduled for a particular delivery, and a Retail Store KPI belongs to the Retail Execution assessment framework rather than inventory delivery processing.

Accordingly, if delivery items do not appear within the Delivery Task, the administrator should verify that the appropriate Shipment has been associated with the task and that the shipment contains the necessary Product Transfer records.

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

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

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 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

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

The Retail Execution assessment architecture uses Retail Store KPIs as the configuration basis for Retail Visit KPIs. Salesforce states that when an Action Plan Template is assigned to a Visit, Assessment Tasks are generated from the Assessment Task Definitions and Retail Visit KPI records are created based on the applicable Retail Store KPIs. This preserves the connection between the expected target configured centrally and the actual value captured during a specific visit.

Flows can also be associated with an Action Plan Template to support business-specific store activities. Salesforce supports flow input parameters named visitId and assessmentTaskId. A flow can accept only visitId, only assessmentTaskId, both parameters, or no parameters depending on the activity being implemented. When the identifiers are used, Salesforce passes the current Visit and Assessment Task context into the flow so that the automation operates on the appropriate execution records.

This model keeps responsibilities clearly separated: Retail Store KPI contains the target context; Retail Visit KPI records the visit-specific assessment result; Assessment Task identifies the executable activity; and Visit establishes the retail engagement within which the task occurs.

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

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

Salesforce Maps provides bulk geocoding capabilities so administrators can populate latitude and longitude values for groups of records rather than manually maintaining coordinates one retail location at a time.

Salesforce Maps geocodes records by matching address information against its geocoding provider and writing the corresponding latitude and longitude values back to the configured coordinate fields. A record can then be accurately plotted on a Maps layer and used for visit planning, route optimization, territory visualization, and proximity analysis.

One supported approach is to plot the records in a Maps layer and geocode the records represented by that layer. This enables administrators to work with a selected collection of Retail Store locations and perform the geocoding operation in bulk rather than copying coordinates from individual map markers.

Salesforce also supports scheduled or batch geocoding through Maps configuration for larger datasets, but within the workflow represented by the question, the Maps layer and mass geocoding action provide the direct administrative method for adding coordinates to the selected retail store records.

Accurate geocoding is foundational to Maps-based Retail Execution because route calculations and map visualization depend on verified geographic coordinates.

Study Guide Topics:Integrations - > Salesforce Maps - > Geocoding - > Retail Store - > Map Layers - > Mass Actions

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

An Inventory Check requires the Retail Store KPI to identify the applicable Retail Store Group and Assessment Indicator Definition. These fields establish where the measurement applies and exactly what the field representative must measure.

The Retail Store Group is fundamental because Salesforce defines Retail Store KPIs at the store-group level rather than directly at an individual store level. The group connects the KPI configuration to the Retail Stores that inherit and use the target during field execution.

The Assessment Indicator Definition identifies the metric to be captured-for example, stock quantity, availability, damaged-product count, or another inventory-related measurement. Salesforce ' s Inventory Check prerequisites explicitly require the Retail Store Group and an Assessment Indicator Definition for the applicable product or product category and In-Store Location Category.

Custom Context is associated with custom-task configurations and should remain empty for a standard Inventory Check. Inventory Count is not the configuration field that establishes the Retail Store KPI relationship. KPI Type can categorize the business meaning of an indicator, but the core Inventory Check configuration depends on the Retail Store Group and Assessment Indicator Definition.

Together, these records enable Salesforce to generate the corresponding Retail Visit KPIs when the Inventory Check is instantiated for a Visit.

Study Guide Topics:Data Setup - > Retail Store KPI - > Inventory Check - > Retail Store Group - > Assessment Indicator Definition

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

Photos captured during an asset-compliance activity are maintained within the assessment-task content framework, allowing the evidence to remain associated with the task that generated it. For an asset check implemented as a custom Assessment Task, this provides the most direct relationship between the compliance observation and its supporting photographic evidence.

Salesforce provides the Assessment Task Content Document object specifically for associating Content Documents with assessment activities. Its data model includes a reference to the parent Assessment Task and a Content Document reference, allowing files generated during execution to remain connected to the task. Salesforce also supports a content-context reference that can identify contextual business records such as an Asset or Visit.

Within Retail Execution, Salesforce uses Assessment Task Content Document records for notes and pictures captured by field representatives while performing assessment activities. This preserves the evidentiary relationship between the field observation and the work performed, enabling managers to review photographs alongside the associated compliance task.

The photo therefore remains accessible through the asset check Assessment Task, where the manager can review the evidence in the same operational context as the captured asset-compliance measurements.

Study Guide Topics:Visit Execution - > Asset Checks - > Assessment Task - > Content Documents - > Photo Evidence

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

The Action Plan Template must use Visit as the Target Object and must be published before it can be used to generate an Action Plan for a retail visit.

Salesforce defines the Action Plan Template as a reusable framework for activities that remain consistent across multiple visits. During template creation, the administrator specifies Visit as the Target Object and configures the required Action Plan Type. Assessment tasks, flows, delivery-related activities, or other supported work items are then added before the template is published.

Publishing is an essential lifecycle step because Salesforce permits only published templates to be used when associating an Action Plan with a Visit. To create the association, the user opens the Visit, navigates to the Action Plan related section, selects New Plan, and chooses the required published template. Salesforce displays the tasks defined by the template and creates the Visit-specific Action Plan after the configuration is saved.

The process therefore does not depend on activating the Visit or separately activating an Action Plan. The key configuration is ensuring that the reusable template is explicitly designed for Visit records and has been published for use.

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

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

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

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

The representative should edit the product tags so that the detected object is associated with the correct product classification. Accurate tagging is fundamental to maintaining reliable object-recognition results, particularly when two products have visually similar packaging.

Object detection identifies objects within an image and maps those detections to labels or product classes. If a competitor changes packaging so that its product resembles another SKU, the resulting classification can incorrectly increase the measured facings or share-of-shelf for the wrong product. Correcting the tag provides accurate classification information and helps maintain the integrity of the shelf measurement.

Salesforce ' s Einstein Vision architecture supports a feedback process for incorrectly classified objects. When an object-detection model misclassifies an image, corrected examples and labels can be added back to the dataset and used in subsequent training or retraining. Salesforce describes this feedback mechanism specifically as a way to improve models after misclassification.

Creating a new planogram would only alter the expected shelf arrangement and would not correct product identity. Turning competitor products around manipulates the physical merchandising environment rather than correcting the data. Canceling the task similarly fails to improve future recognition.

Study Guide Topics:Platform - > Einstein Object Detection - > Product Tags - > Classification - > Share-of-Shelf Accuracy

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

The Retail Store object includes retail-execution-specific attributes such as Delivery Method, Preferred Visit Hours, and Payment Method, which provide operational details required for managing field sales and distribution activities.

Delivery Method describes how orders are delivered to the store and supports logistics and Direct Store Delivery planning. Preferred Visit Hours identifies the periods during which field representatives should ideally visit the outlet and contributes to effective visit and route planning. Payment Method records the payment arrangement applicable to the retail location and supports store-specific commercial execution.

Salesforce ' s Retail Store data model explicitly includes fields corresponding to DeliveryMethod, PreferredVisitHoursText, and PaymentMethodId. It also contains attributes for delivery frequency, opening and closing times, recommended visit frequency, pricing strategy, primary contact, priority, and related retail-location information.

Shipping Address is a standard concept already available in the Account data model and therefore does not serve as a distinguishing Retail Store attribute. Operating Hours are handled through the broader operating-hours model and relationship rather than being one of the three specific Retail Store fields represented by the choices.

These store-specific attributes allow Agentforce Consumer Goods to distinguish the operational requirements of an individual physical outlet from its parent customer Account.

Study Guide Topics:Data Setup - > Retail Store - > Delivery Method - > Preferred Visit Hours - > Payment Method

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

Endcaps should be represented as In-Store Locations and In-Store Location Categories, with Retail Store KPIs specifically configured for that merchandising context. This allows NTO to measure endcap performance independently from primary shelves, checkout counters, backrooms, or other store areas.

Salesforce ' s Agentforce Consumer Goods data model supports In-Store Location categories precisely for this purpose. Similar physical locations across stores can be categorized-for example, Endcap Displays-and Retail Store KPIs can then use that category to define the measurements and targets applicable to those locations.

Salesforce ' s own Retail Execution configuration examples demonstrate creating Retail Store KPIs specifically for the Endcap Displays category. A promotion-compliance KPI can include the Retail Store Group, Endcap Displays as the In-Store Location Category, the relevant Assessment Indicator Definition, Promotion, Product Category, and a Boolean target value. This allows field representatives to capture endcap-specific performance during visits while managers analyze the resulting Retail Visit KPI data separately.

Creating Retail Store record types or unrelated custom objects would not provide the appropriate KPI granularity. Dedicated KPI configuration for the endcap context uses the standard Consumer Goods data model and provides targeted merchandising measurement.

Study Guide Topics:Data Setup - > In-Store Locations - > Endcap Displays - > Retail Store KPI - > Assessment Indicators

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

Users performing Consumer Goods Retail Execution activities require the appropriate combination of Retail Execution, Industries Visit, and Action Plans permissions.

Lightning Retail Execution Plus provides access to Consumer Goods Retail Execution capabilities for strategic-sales users. Salesforce lists Lightning Retail Execution Plus among the available Retail Execution permission set licenses used to enable Consumer Goods features.

The Industries Visit permission provides access to industry-specific Visit functionality. Visits are fundamental to Retail Execution because they represent scheduled interactions between field representatives and Retail Stores. The permission set supplies access to objects involved in visit execution, including Visit, Assessment Task, Assessment Task Definition, Action Plan, Action Plan Template, and related records.

The Action Plans permission enables users to access and manage Action Plans. Action Plan Templates define the repeatable activities that are subsequently associated with Visits and executed by field representatives.

Salesforce ' s setup instructions direct administrators to assign a Retail Execution permission set together with Action Plans and Industries Visit to users who require access to visits, tasks, and related Retail Execution capabilities. Sales Quotations addresses a different commercial process.

Study Guide Topics:Platform - > Permission Sets - > Lightning Retail Execution Plus - > Industries Visit - > Action Plans

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

Store Action Plan Templates provide contextual task recommendations by connecting reusable Action Plan Templates with the retail hierarchy where those activities are applicable. The supported retail contexts are Retail Store Group, Retail Store, and In-Store Location.

A Retail Store Group provides broad reusable scope. Stores with similar layouts, product ranges, commercial agreements, or operational characteristics can be grouped so that common activities can be recommended consistently across those stores. Salesforce specifically uses Retail Store Groups to organize locations with common characteristics and to reduce repetitive configuration.

The Retail Store level provides a more specific context when a task is applicable to one physical outlet rather than every store in a group. The In-Store Location level offers the finest execution granularity for activities associated with specific areas such as an aisle, primary shelf, endcap, checkout counter, or back room.

These entities form part of the Salesforce Retail Execution data model together with Store Action Plan Template, Action Plan Template, Visit, and other activity-planning objects. This layered architecture allows recommended visit activities to be associated with the level of the retail hierarchy most appropriate to the business requirement.

Study Guide Topics:Visit Planning - > Store Action Plan Template - > Retail Store Group - > Retail Store - > In-Store Location

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

CRM Analytics for Agentforce Consumer Goods requires a minimum set of records before the Analytics for Consumer Goods app can be successfully created. Salesforce identifies the required data objects as Account, RetailStore, Visit, RetailVisitKpi, and Product2. An Order record is additionally required when the organization wants to include both Retail Execution and sales data.

The Retail Visit KPI requirement is particularly important because Retail Visit KPI records contain actual information captured during visits against the Assessment Indicator Definitions and targets configured for Retail Execution. These records provide the analytics layer with visit-level compliance and performance measurements that can be used in dashboards for store performance, product performance, territory analysis, and other Retail Execution insights.

Retail Visit KPI records are generated as part of the assessment-task process based on the underlying Retail Store KPI configuration. Salesforce therefore requires at least one RetailVisitKpi record in the organization when validating the data prerequisites for the CRM Analytics application.

The analytics setup process validates these minimum data requirements and displays a message when required records are missing.

Study Guide Topics:Analytics - > CRM Analytics for Agentforce Consumer Goods - > Data Requirements - > Retail Visit KPI - > Retail Execution Analytics

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

For a scalable Visit Recommendation strategy, Salesforce recommends implementing the selection logic through an Apex class. Visit Recommendations can use programmable logic to determine which stores should receive recommendations based on organization-specific criteria, and Apex is appropriate when the strategy must operate at business scale.

Salesforce allows an Apex class to select the stores for which Einstein should provide Visit Recommendations. The Apex method is exposed to automation by using @InvocableMethod, after which the class can be invoked from the Visit Recommendation strategy or from an autolaunched flow.

Salesforce also supports a Flow strategy for Visit Recommendations, but its documentation specifically notes that the flow-only method is not scalable for a business use case and recommends using Apex for scalable implementations. An Apex implementation gives developers greater control over bulk processing, complex filtering, reusable business logic, and Salesforce governor-limit considerations.

The strategy can return the recommended Store IDs and recommendation reasons so sales managers and field representatives understand both which stores should be visited and why those stores have been prioritized.

Workflow and Process Builder are not the architecture Salesforce defines for this Visit Recommendation capability.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Apex - > Invocable Methods - > Scalable Recommendation Strategies

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

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

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

The computer display unit should be represented as the business object being inspected, while its operational condition should be captured through an Assessment Task and associated KPI. This aligns with Salesforce ' s custom-task model for Retail Execution.

Salesforce supports custom tasks specifically for business scenarios that do not fit the standard Inventory Check, Promotion Check, Planogram Check, Order Creation, or Survey task types. Salesforce gives the example of capturing maintenance information for a refrigerator placed in a store, which is directly analogous to assessing the condition or functionality of a computer display unit.

For a custom assessment, administrators define Assessment Indicator Definitions representing the values that field representatives need to capture. The associated Retail Store KPI provides the target and business context, while the Retail Visit KPI stores the actual observation entered during execution. Custom Context can connect the KPI configuration to the relevant standard or custom business object.

An In-Store Survey is intended for collecting feedback from customers or store personnel and is not the appropriate mechanism for recording equipment-performance KPIs. Creating a dedicated task record type also does not replace the assessment/KPI architecture.

Study Guide Topics:Visit Execution - > Custom Tasks - > Assets - > Assessment Indicators - > Retail Visit KPI

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