Free Salesforce-Accredited-Agentforce-Consumer-Goods-Professional Practice Test Questions (2026)

Explanation:

This question tests how to explain the business value of the Einstein for Consumer Goods Cloud Visit Recommendations feature. The correct explanation should focus on how the feature helps field professionals prioritize their work and use intelligent recommendations to stay competitive.

✅ Correct Option:

A. By adopting the Einstein for CG - Visit Recommendations with the consumer goods cloud, Professionals can focus on these work while having information served to them that will support them in being competitive
This option correctly describes the value proposition of Visit Recommendations. Einstein analyzes retail execution data, such as store priority, territory performance, and promotion schedules, to recommend the right stores to visit each day. This helps field reps focus on the stores that matter most, maximizing their limited selling time and improving competitive effectiveness.

❌ Incorrect options:

B. Einstein for Consumer Goods Cloud is a great tool, but like all software Consumer Goods Cloud is a work in progress
This option is vague and does not explain any specific capability or value of the Visit Recommendations feature. It fails to answer the question about what the feature does for NTO.

C. Consumer Goods Cloud Einstein for CG - Visit Recommendations feature is natively powered by market research data
This option is incorrect because Visit Recommendations are powered by internal retail execution data, such as store visits, territory performance, and promotions. The feature is not natively powered by external market research data.

D. By adopting the Einstein for CG - Visit Recommendations on the Consumer Goods Cloud the existing workforce can be terminated
This option is incorrect because Visit Recommendations are designed to augment and support field professionals, not replace them. The feature improves productivity and prioritization, not headcount reduction.

🔧 Reference:
→ Explore Einstein for Agentforce Consumer Goods This confirms that Einstein for Consumer Goods Cloud provides intelligent recommendations about the right stores to visit, based on multiple criteria like store priority and territory performance.

→ Request and Schedule a Visit Recommendation - Trailhead
This confirms that visit recommendations help field reps focus on the right stores to save time and meet targets more easily.

Explanation

This question tests how a Retail Store KPI is associated with a product in Consumer Goods Cloud. When the KPI is configured at the product level, the product must be part of an assortment so the KPI can apply to the appropriate product assortment and support retail execution activities.

🟢 C. The product needs to be linked to an Assortment
A product-level Retail Store KPI works with the product's assortment relationship. The product must be associated with an Assortment through an Assortment Product record so the KPI can be applied to that product within the retail execution setup. Salesforce identifies an assortment as the curated list of products eligible for sale or assessment in a store, making this relationship necessary for the KPI configuration.

🔴 A. The product needs to be linked to a Promotion
A promotion is used to represent targeted promotional activities and can have products associated with it. However, linking a product to a promotion is not the required relationship for a product-level Retail Store KPI.

🔴 B. The product needs to be linked to a Product Category
Product categories can be used when defining certain retail metrics, but a product-level KPI does not require the product to be linked to a category. The relevant relationship is the product's association with an assortment.

🔴 D. The product needs to be linked to a Retail Store
A product can be associated with a retail store through store-product records, but this is not the required next step for a product-level Retail Store KPI. The KPI uses the product's assortment relationship to establish the applicable retail context.

🔧 Reference:
⇒ Objects and Records in Retail Execution – Salesforce Help — Confirms that Assortment Products associate products with assortments and explains the role of Retail Store KPIs.

⇒ Consumer Goods Cloud Base Model – Salesforce Help — Shows how products, assortments, Retail Store KPIs, and retail execution are related.

Explanation

This question tests understanding of field execution capabilities in Consumer Goods Cloud, specifically what actions field reps can perform on the mobile app during a promotion check.

✅ A. Viewing which products are included in the promotion
During a promotion check visit task, field reps can view the full list of products associated with the active promotion. This visibility ensures reps can accurately verify on-shelf placement, stock availability, and display compliance for every promotional item mapped to that store.

✅ C. Taking a photo of the promotion
Consumer Goods Cloud enables reps to capture and attach photo evidence directly to the promotion task record using photo upload or Einstein Vision capabilities. This validates display compliance, promotional setup, and visual execution standards against corporate guidelines.

❌ B. Marking the promotion as complete
Field reps complete the specific visit task or assessment indicator associated with the promotion check, but they do not mark the overall business promotion itself as complete. Global promotion lifecycle statuses are managed centrally, not completed at individual store levels.

❌ D. Changing the promotion planning dates
Promotion planning dates define campaign duration across stores and are managed centrally by trade marketers and account managers. Field reps executing store checks do not have administrative authority to alter overall promotional schedules from the field app.

❌ E. Changing the discounts on the products included in the promotion
Product pricing and promotional discount rates are controlled centrally through pricing strategy and trade promotion management setup. Field reps perform compliance checks and audit current conditions rather than modifying active discount rates during store visits.

Reference
🔧 Audit Promotions in Consumer Goods Cloud - Salesforce Help confirms that field reps can inspect promotional product lists and capture compliance photos during promotion audit tasks.

Explanation

This question tests the metrics available for evaluating vision-detection results in Consumer Goods Cloud. Users need visibility into both the accuracy of the shelf-level comparison and the AI model’s confidence in identifying objects from a captured shelf image.

✅ B. Shelf Metrics
Shelf Metrics allow users to review detection accuracy at the shelf level by comparing the actual shelf image with the expected planogram or reference shelf arrangement. This comparison helps identify whether products are placed, counted, and positioned as expected. It provides insight into how accurately the vision process recognizes the overall shelf layout and compliance conditions.

✅ E. Model Metrics
Model Metrics provide information about the vision model’s detection performance for objects identified in a shelf image. Users can review measures such as the confidence score and number of detections associated with recognized objects. These metrics help determine whether the AI model is reliably identifying products and whether further model training or image-quality improvements are needed.

❌ A. Goods Metrics
Goods Metrics are not a standard metric category for reviewing vision-detection accuracy. Consumer Goods Cloud uses shelf-level metrics to assess detected shelf conditions and model-level metrics to evaluate detection confidence. This option does not represent the metrics used to validate the quality or accuracy of AI-powered shelf-image detection.

❌ C. Planogram Metrics
Planogram information provides the expected product arrangement or reference layout, but Planogram Metrics are not used to review vision-detection accuracy. Shelf Metrics use the shelf image and expected planogram to assess compliance, while Model Metrics focus on the AI model’s recognition confidence and object-detection results.

❌ D. Object Metrics
Object Metrics are not the standard area for reviewing vision-detection accuracy in this context. Although the vision model detects individual objects in an image, users assess detection quality through Model Metrics. Those metrics provide confidence and detection-count information needed to evaluate how accurately the model recognized the objects.

Reference
→ Planogram Checks — Salesforce Help confirms that Consumer Goods Cloud uses shelf images and reference planograms to assess retail shelf execution.

Explanation

This question tests understanding of how an admin can automate adding geocoordinates to store records at scale in Salesforce Maps, rather than doing it manually for each location.

✅ B. Set up a batch job through Salesforce Maps automation to read an address field and add geocoordinates to selected fields.
Salesforce Maps triggers geocoding either on demand when a record is plotted, or through batch automation, which runs a scheduled batch to read the address field on retail store records and populate the configured latitude and longitude fields. This is the supported method for bulk-adding geocoordinates without manual entry.

❌ A. Under geolocation in setting, enable the 'automate geocoordinate mapping to retail store' option.
There's no such setting in Salesforce Maps. Geocoding isn't turned on through a single toggle; it depends on how base objects are configured with address and coordinate fields, which then drives either on-demand or batch geocoding.

❌ C. Click on the individual retail store marker and copy/paste the coordinates from the tooltip to the corresponding retail store longitude and latitude fields.
This describes a manual, record-by-record workaround, not a supported methodology for bulk geocoding. It doesn't scale across many store locations and isn't how Salesforce Maps is designed to populate coordinate fields.

❌ D. Create a new map layer containing the desired retail store locations and execute the 'add geocodes' mass action.
Map layers are used to visualize and filter records that are already plotted with coordinates; there's no "add geocodes" mass action tied to layer creation. Geocoding happens through base object configuration and batch automation, not layer actions.

Reference
🔧 Configure for Location Accuracy – Salesforce Trailhead → confirms batch automation as the supported method for geocoding records in Salesforce Maps.

Explanation:

This question tests how flow-based tasks work with visits and Retail Visit KPIs in Consumer Goods Cloud. Flow tasks can receive the relevant Assessment Task and Visit identifiers, while the flow can use an Assessment Indicator Definition to create the Retail Visit KPI without requiring a predefined Retail Store KPI.

🟢 C. Assessment Task IDs and Visit IDs are passed to the flow in a flow task
Flow-based tasks operate within the context of an assessment task and a visit. The corresponding Assessment Task ID and Visit ID provide the flow with the records it needs to process the task and associate resulting information with the correct visit. Salesforce's data model confirms that both Assessment Tasks and Retail Visit KPIs maintain relationships to the Visit and Assessment Task records.

🟢 D. Retail Store KPIs are not needed, as long as an Assessment Indicator Definition is available within the flow to create the Retail Visit KPI
A flow-based task can create a Retail Visit KPI using an Assessment Indicator Definition supplied within the flow. Therefore, a predefined Retail Store KPI isn't mandatory for this approach. Retail Store KPIs are normally used to define targets and associate indicators with store groups, but flow-based processing can create the visit KPI directly.

🔴 A. A Retail Store KPI is always needed and is passed to the flow in the variable Retail Store KPI
A Retail Store KPI isn't always required for a flow-based task. The flow can use an Assessment Indicator Definition to create the Retail Visit KPI. Therefore, stating that an RSKPI is always required and passed as a flow variable is incorrect.

🔴 B. Retail Visit KPIs always need a corresponding Retail Store KPI
Retail Visit KPIs commonly result from Retail Store KPI configuration, but they aren't universally dependent on an existing RSKPI when flow-based processing is used. A flow can create the Retail Visit KPI using the relevant Assessment Indicator Definition.

🔴 E. Flow based tasks should never be used for tasks that require a Retail Visit KPI
This is incorrect because flow-based tasks can create and work with Retail Visit KPIs. Salesforce describes Retail Visit KPIs as records that store actual information captured during a visit, and flow-based processing can be used to create the required KPI record.

🔧 Reference:
⇒ Create a Retail Store KPI – Salesforce Help — Confirms the normal role of Retail Store KPIs in defining targets and associating Assessment Indicator Definitions.

⇒ Consumer Goods Cloud Data Model Objects – Salesforce Help — Confirms that Assessment Tasks and Retail Visit KPIs contain relationships to Assessment Task IDs and Visit IDs.

Explanation:

This question tests the correct methodology for tracking performance metrics for specific in-store areas like endcaps. The key is understanding that Consumer Goods Cloud tracks location-specific data through In-Store Location records and associated KPIs.

✅ Correct Option:

D. Make a separate set of KPIs specifically for capturing the endcap In-Store Location
This option correctly identifies that endcap performance should be tracked through dedicated KPIs associated with the In-Store Location. Consumer Goods Cloud allows KPIs to be defined against specific In-Store Locations, enabling targeted measurement of endcap displays . The In-Store Location Category field (such as "Endcap Displays") allows KPIs to be configured for these specific areas .

❌ Incorrect options:

A. Make a Custom object for In-Store location on the Retail Store Object to capture KPIs
This approach is incorrect because In-Store Locations are already a standard related record on the Retail Store object. Creating a custom object would duplicate existing functionality and bypass the standard data model.

B. Make In-Store Locations as a record type on the Retail Store Object to capture the KPIs
Record types define different layouts and picklist values for a single object. In-Store Locations are separate records related to a Retail Store, not a record type on the Retail Store object itself.

C. Make In-Store Locations as a record page on the In-Store Location Object to capture the KPIs
Record pages are user interface configurations, not data modeling solutions. A record page displays information but does not create the underlying data structure needed to capture and store KPI values.

🔧 Reference:
→ Retail Visit KPI DMO - Salesforce Developers
This confirms the InStoreLocationId field that associates KPI values with specific in-store locations.

→ Set Up Task Definitions and Action Plan Templates - Trailhead
This explains that field reps gather information on product counts "in specific in-store locations such as shelves and end caps" and that the Retail Store KPI object has a Custom Context field for defining specific locations .

Explanation

This question tests the Salesforce object specifically used for direct store delivery (DSD) activities. In Consumer Goods Cloud, DSD supports processes such as order fulfillment, store deliveries, payments, returns, and driver-led delivery execution. The correct object records delivery work associated with store orders and shipments.

✅ B. Delivery Task
The Delivery Task object is specifically available for direct store delivery in Consumer Goods Cloud. It stores information about shipments and orders that must be delivered to a store during a visit. Sales managers can create and assign delivery tasks to drivers, who then access the tasks on their mobile devices to complete delivery execution.

❌ A. Shipment
Shipment is a standard Salesforce object that can represent shipment-related information, but it is not the Consumer Goods Cloud object exclusively intended to manage direct store delivery work. In DSD, a Delivery Task provides the operational record that connects delivery execution with the relevant store, order, and shipment information.

❌ C. Order
An Order records the products requested or purchased by a customer, but it does not manage the execution of a store delivery. Direct store delivery requires a delivery-focused work record for drivers. Delivery Task is designed to organize and track the actual delivery activity associated with orders and shipments.

❌ D. ProductTransfer
ProductTransfer represents an inventory movement between locations and is associated with Field Service inventory-management capabilities. It is not the Consumer Goods Cloud object exclusively used to execute direct store delivery. DSD uses Delivery Tasks to manage the driver’s store delivery work, including the orders and shipments to be delivered.

Reference
→ Standard Objects for Retail Execution— Salesforce Developers confirms that DeliveryTask represents shipment and order information to be delivered to a store during a visit.

Explanation

This question tests understanding of how field representatives interact with Einstein Object Detection in Consumer Goods Cloud to correct image recognition discrepancies directly during store visits.

✅ D. Edit product tags.
When Einstein Vision misidentifies products due to similar packaging, field reps can manually correct the detection results by editing product tags on the analyzed image before submitting. These manual tag adjustments provide feedback that helps retrain and refine the object detection model, improving future recognition accuracy.

❌ A. Turn the competitor ' s products around and re-perform the check.
Physically moving or hiding competitor products distorts real shelf conditions and leads to inaccurate audit data. The goal of shelf execution is to record actual store conditions rather than manipulating the shelf layout to pass image recognition.

❌ B. Contact the manager to create a new planogram.
Planograms define overall visual merchandising standards and shelf space allocations, not image recognition models. Changing a planogram will not fix visual identification errors caused by similar product packaging in Einstein Vision.

❌ C. Cancel the task and perform the planogram check manually.
Canceling the task bypasses the built-in Einstein Object Detection workflow entirely. Bypassing the automated detection step prevents the system from capturing feedback data needed to refine and improve model accuracy for future visits.

Reference
🔧 Review Object Detection Results - Salesforce Help confirms that field reps can manually edit product tags on detected images to correct misclassifications and improve model precision.

Explanation

This question tests understanding of which field is essential to defining a Retail Store KPI record, since KPIs can be scoped in many optional ways but always need to identify what type of metric is being tracked.

✅ C. KPI Type
KPI Type defines the category of metric a Retail Store KPI record measures, such as Facing, Share of Shelf, Out of Stock, Price, or Revenue. Since a KPI exists to track a specific kind of compliance or performance measure, this field is what gives the record its purpose and is required when setting up a Retail Store KPI.

❌ A. Effective to
Effective To (End Date) marks when the association between a store group and the assessment indicator definition ends, but it's an optional field on the Retail Store KPI object. Many KPIs are set up without a defined end date and remain active indefinitely until manually updated.

❌ B. Retail Store Group
Retail Store Group lets you apply a KPI target across multiple stores at once, but it's optional. Admins can define KPIs at a more granular level, such as an individual store or in-store location category, without ever selecting a store group.

Reference
🔧 RetailStoreKpi – Salesforce Developer Docs → confirms KPI Type as a defining field of the Retail Store KPI object, while End Date and Retail Store Group are optional (Nillable) fields.