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

An Einstein object-detection implementation depends on three essential elements: a suitable training dataset, a properly trained and evaluated model, and appropriate user access to the functionality.

The implementation begins by collecting representative images of the products or objects that must be detected. For object detection, the training images require labeled bounding boxes identifying the position and dimensions of each object. These examples are uploaded as a dataset and used by the training process to create an object-detection model.

The trained model should then be evaluated before deployment. Salesforce ' s model-training architecture reserves data for testing and provides model information that allows implementers to evaluate the model ' s detection performance. Reviewing model quality before exposing the capability to field representatives is essential because representative training data and adequate model performance directly affect detection results.

Finally, the field users who execute the functionality require the relevant access and permissions. Permissions are part of the Salesforce security model and determine whether users can access the required Consumer Goods and Einstein functionality.

OCR configuration and competitor-suppression datasets are not baseline requirements for this object-detection setup.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Dataset - > Model Training - > User Permissions

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

For the Agentforce Consumer Goods visit-execution model, the appropriate Action Plan Type is Visit Execution. Action Plan Templates provide reusable collections of activities that field representatives repeatedly perform during visits to retail stores.

Salesforce ' s Consumer Goods data-model training identifies Visit Execution as the Action Plan Type used for Retail Execution templates and Visit as the Target Object. The template can then contain tasks such as inventory checks, planogram checks, promotion checks, asset checks, surveys, order-related activities, and other recurring work.

The Action Plan Template separates reusable task configuration from individual Visit records. Administrators define the common activities once, establish their order and mandatory status, and then associate the template with multiple visits. When the template is applied, Salesforce creates the necessary visit-level tasks so the field representative receives a consistent execution workflow.

This approach is particularly important in consumer goods organizations where representatives may perform essentially the same merchandising, inventory, promotion, order, and compliance activities across hundreds or thousands of stores. Visit Execution provides the action-plan classification aligned with that Retail Execution business process.

Study Guide Topics:Visit Planning - > Action Plan Template - > Visit Execution - > Visit Target Object - > Assessment Tasks

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

An Action Plan Template can contain multiple Inventory Check, Planogram Check, and Promotion Check assessment tasks. These are KPI-based Retail Execution activities that may need to be repeated within a single store visit for different products, categories, promotions, or in-store locations.

Salesforce explicitly states that administrators can add multiple Inventory Check, Planogram Check, and Promotion Check tasks to one Action Plan Template. By contrast, Salesforce restricts the template to only one Order Creation task or one In-Store Survey task.

This flexibility is important because a typical consumer-goods visit can involve several independent merchandising objectives. A representative might perform separate inventory checks for different store areas, validate several planograms, and verify multiple promotions during the same visit. The Action Plan Template provides a reusable framework that groups these activities and controls their required status and display sequence.

Templates must also progress through the appropriate lifecycle before operational use; simply defining the structure does not substitute for making the template available for visit execution. Salesforce further supports extensibility through flows, component tasks, and other Action Plan mechanisms.

Therefore, the ability to include multiple planogram, inventory, and promotion checks is the accurate statement.

Study Guide Topics:Visit Planning - > Action Plan Templates - > Inventory Check - > Planogram Check - > Promotion Check

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

The Maximize Store Sales Einstein Discovery story is designed to identify factors that influence product sales and provide actionable insights that can help sales managers improve store performance.

Salesforce provides preconfigured Einstein Discovery stories within Analytics for Consumer Goods. The sales-focused story analyzes historical data to identify variables that have a positive or negative impact on product sales. Salesforce currently describes this capability as Maximize Store Product Sales, which provides insights into the factors affecting product sales and helps organizations devise strategies to increase sales at a store or store-group level.

Einstein Discovery uses the available analytics dataset to identify statistically relevant relationships and present explanations that business users can act upon. These insights can assist sales managers in understanding how factors such as product availability, assortment, store characteristics, and other operational conditions correlate with sales performance.

The Minimize Out-of-Stock story serves a different objective: it predicts products that are likely to run out of stock so representatives can mitigate availability problems. While out-of-stock conditions can affect revenue, the scenario specifically asks for broader insight into the factors affecting store sales, making the sales-maximization story the appropriate functionality.

Study Guide Topics:Analytics - > Einstein Discovery - > Maximize Store Sales - > Predictive Insights - > Sales Performance

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

Actual KPI values captured by a field representative during visit execution are stored in the Retail Visit KPI record. Salesforce separates KPI configuration from transactional execution data so that planned or target values remain distinct from values observed during individual visits.

The Retail Store KPI defines the target or expected value for a particular Assessment Indicator Definition. It provides the planning context, including the Retail Store Group, product or product category, In-Store Location Category, Custom Context, and target value. When an assessment task is generated for a visit, Salesforce creates the corresponding Retail Visit KPI records that represent the runtime measurements.

During execution, the field representative records the observed value. Salesforce stores fields such as the Actual Value, Target Value, Assessment Indicator Definition, Product, In-Store Location, and Custom Context on the Retail Visit KPI.

This architecture allows Salesforce to compare expected performance with actual field results across multiple visits. The custom object can supply the business context for a custom task, but it does not replace the Retail Visit KPI as the repository for actual assessment measurements.

Study Guide Topics:Data Setup - > Custom Tasks - > Retail Store KPI - > Retail Visit KPI - > Actual Values

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

The Retail Visit KPI provides the visit-level relationship between the configured KPI framework and the Assessment Task that is executed in the field. Retail Store KPI defines expected values, while Retail Visit KPI captures the actual measurement generated during a specific Visit and Assessment Task.

Salesforce ' s Consumer Goods data model shows that Retail Visit KPI includes references to Assessment Task, Visit, Assessment Indicator Definition, Product, Product Category, In-Store Location, Promotion, Planogram, and other assessment context. It also contains the Target Value and Actual Value used to evaluate store performance.

The records are created as part of the assessment-task generation process. When an Action Plan Template is assigned to a Visit, Salesforce creates Assessment Tasks based on the included Assessment Task Definitions and creates Retail Visit KPIs based on the applicable Retail Store KPIs.

This design enables one centrally configured Retail Store KPI to drive repeated measurements across many store visits. Each individual visit receives its own Retail Visit KPI record, allowing the actual execution result to remain associated with the Assessment Task that produced it.

Study Guide Topics:Data Setup - > Retail Visit KPI - > Retail Store KPI - > Assessment Task - > Actual and Target Values

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

Action Plan Templates can contain both Assessment Task Definitions and Component Tasks, allowing organizations to combine standard Retail Execution activities with customized Lightning Web Component-based tasks in a reusable visit framework.

An Assessment Task Definition represents a recurring field activity such as an Inventory Check, Planogram Check, Promotion Check, In-Store Survey, Order Creation activity, or custom assessment. Salesforce allows administrators to add these Assessment Task Definitions to an Action Plan Template. When that template is used for a Visit, the corresponding tasks become associated with the visit and are presented to the assigned field representative.

Salesforce also supports Component Tasks. Administrators can select Add Component Task on an Action Plan Template, provide a name and description, select the required Lightning Web Component through its fully qualified name, and determine whether the task is mandatory. This allows organizations to extend store execution with specialized interactive experiences while continuing to use the standard Action Plan framework.

Action Plan Templates are configured administratively and function as reusable frameworks for repeatable business processes. Their ability to combine multiple task types is fundamental to creating consistent and scalable store-visit execution plans.

Study Guide Topics:Visit Planning - > Action Plan Templates - > Assessment Task Definitions - > Component Tasks - > Visit Execution

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

A Store Product represents the relationship between a Product2 record and a particular Retail Store or In-Store Location. This relationship supplies the store-specific product context required by several Retail Execution processes.

For Inventory Checks, Salesforce must determine which products are relevant to the store being visited. Store Product records provide that relationship, allowing the Inventory Check experience to present applicable products rather than the entire enterprise product catalog. The same store-level product context supports the Search and Scan experience, where field representatives locate a product directly or scan its barcode while performing an inventory assessment.

Store Products also contribute to order capture. Salesforce stores operational attributes on the Store Product relationship, including the associated Product, Retail Store, In-Store Location, default order quantity, and favorite-product indicator. These fields allow the order experience to identify products that are relevant to a specific outlet and facilitate efficient repeat ordering.

Salesforce distinguishes Store Product from Store Assortment: Store Product represents products directly associated with a store or in-store location, while assortments define broader groups of products eligible for sale.

Study Guide Topics:Data Setup - > Store Product - > Inventory Check - > Search and Scan - > Order Capture

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