Free Practice Questions for Salesforce AP-204 Exam

A Retail Store can be associated with many Visit records, creating the required one-to-many relationship. Each Visit represents a particular scheduled or completed engagement between a field representative and a physical retail location, while the same store can naturally be visited repeatedly over time.

Salesforce describes the Visit object as tracking information about a field representative ' s visit to a Retail Store where retail activities are performed. Visit records hold information such as planned and actual start and end times, status, visitor, priority, and the related location.

For Consumer Goods implementations, the Visit ' s Place relationship identifies the Retail Store being visited. Salesforce Maps uses the same model when scheduling Consumer Goods visits: Visit records can derive their map location from the related Retail Store through Place ID, allowing Maps to position each Visit at the correct physical outlet.

Because representatives return to stores according to visit frequencies, merchandising schedules, promotions, deliveries, and sales requirements, a single Retail Store can accumulate multiple Visit records over its lifecycle. Each Visit remains a distinct transaction with its own Action Plans, tasks, KPIs, timing, and execution results.

Study Guide Topics:Data Setup - > Retail Store - > Visit - > Place Relationship - > Store Visit History

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

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

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

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

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

The appropriate action is to edit the product tags so that the incorrectly detected object is associated with its correct product classification. Product identification depends on the relationship between the detected item and the product label assigned to it. When two packages have highly similar visual characteristics, a detected object can require correction to ensure subsequent shelf-analysis results reflect the correct SKU or competitor product.

Share-of-shelf measurements depend on accurate identification of the products occupying the shelf. If an item belonging to a competitor is classified as the company ' s own product, the calculated shelf presence becomes overstated and the resulting compliance data is unreliable. Correcting the product tag addresses the classification problem at its source rather than manipulating the physical shelf or abandoning the assessment.

This approach also aligns with the underlying object-detection model. Detection systems generate identified objects and associate those detections with product classifications. Accurate labels and representative examples are fundamental to reliable image-based object recognition. Where product appearance changes substantially, maintaining accurate classification information is essential to preserving measurement quality.

Creating a different planogram would change the expected merchandising arrangement but would not correct an incorrectly classified detected product.

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

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

In-Store Surveys are primarily designed to capture qualitative feedback from people associated with the retail location and to gather information about operational topics such as promotions, inventory requirements, and product quality.

Salesforce explicitly defines the In-Store Survey capability as a method for gathering feedback from store staff and customers about promotions, inventory needs, and product-quality conditions. The survey is executed as part of a Visit and can be incorporated into an Action Plan Template through an Assessment Task Definition of type In-Store Survey.

This model allows consumer goods organizations to collect information that is difficult to derive from purely transactional records. For example, store personnel can provide feedback about product availability, promotional effectiveness, packaging issues, shopper reactions, or changing inventory requirements. Surveys can also capture consumer or shopper opinions about products or promotional activities.

Inventory reconciliation is handled through inventory-management and Inventory Check processes rather than primarily through surveys. Point-of-sale information is normally imported or integrated as structured sales data for analytics rather than collected manually through an In-Store Survey.

Study Guide Topics:Visit Execution - > In-Store Survey - > Customer Feedback - > Promotions - > Inventory Requirements - > Product Quality

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

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

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

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

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

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

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

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

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