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

Explanation:

This question tests knowledge of which KPI Type values are natively supported for Retail Store KPI records in Consumer Goods Cloud. The KPI Type field categorizes the metric being measured and determines what values can be captured during retail execution tasks.

✅ Correct Option: B. Units
Units is a supported KPI Type used to measure product quantities during inventory checks. It tracks counts such as the number of products on a shelf or in an in-store location, making it a native metric for Retail Store KPIs .

✅ Correct Option: D. Facing
Facing is a supported KPI Type specifically used in planogram checks. It measures how products are positioned on shelves to ensure optimal display and compliance with merchandising standards .

✅ Correct Option: E. Revenue
Revenue is a supported KPI Type for tracking monetary performance metrics. It allows sales managers to define financial targets and measure actual sales outcomes against those targets .

❌ Incorrect options:

A. Price
Price is not a supported KPI Type for Retail Store KPI records. While price tracking exists as an Assessment Indicator Definition, it is not configured as a KPI Type in the standard picklist options .

C. Promotion
Promotion is not a KPI Type value. Promotion compliance is tracked through Assessment Indicator Definitions and task types, but it does not appear as a selectable KPI Type for Retail Store KPIs .

🔧 Reference:
→ Work with Metrics and Retail Store KPIs – Salesforce Trailhead — confirms that Retail Store KPIs define target values for metrics like Share of Shelf, Facing, and Revenue, and that KPI Type is used to categorize these metrics.

→ Assessment Tasks – Salesforce Help — confirms that Retail Visit KPIs are created based on Retail Store KPIs, which include metrics such as Facings, Units, and Revenue.

Explanation:

This question tests the combination of permissions required for Consumer Goods Cloud Retail Execution. Users need a Retail Execution permission set license together with the Industries Visit and Action Plans permission sets to work with visits, retail stores, and action plan templates.

🟢 A. Industries Visit
The Industries Visit permission set enables users to manage industry-specific visits. Salesforce lists Visit and Action Plan Template among the objects available through this permission set. This makes it an important part of providing users with access to the visit framework and related retail execution records.

🟢 B. Action Plans
The Action Plans permission set enables functionality for creating and managing action plans. Action Plan Templates are used to define reusable tasks and activities for retail execution. Therefore, this permission is required when users need to work with action plans and their templates as part of store visits.

🟢 D. Lightning Retail Execution Plus
Lightning Retail Execution Plus provides access to the core Consumer Goods Cloud Retail Execution features. Salesforce identifies it as one of the Retail Execution permission set licenses and notes that it provides access to Retail Execution capabilities. It works alongside Industries Visit and Action Plans for users performing day-to-day retail activities.

🔴 C. Sales Quotations
Sales Quotations is related to quotation functionality rather than the permissions required for Consumer Goods Cloud Retail Execution. It does not provide the required access to Visits, Retail Stores, or Action Plan Templates.

🔴 E. Visit Execution Action Plan
Visit Execution Action Plan is not one of the three required permission types identified by Salesforce for this access combination. The required setup uses Industries Visit, Action Plans, and a Retail Execution permission set such as Lightning Retail Execution Plus.

🔧 Reference:
⇒ Retail Execution Permission Sets – Salesforce Help — Confirms that Lightning Retail Execution Plus provides Retail Execution access, while Industries Visit and Action Plans enable visit and action-plan functionality.

⇒ Get Started with Retail Execution – Salesforce Trailhead — Shows Salesforce's setup process for assigning Lightning Retail Execution Plus, Action Plans, and Industries Visit permissions.

Explanation

This question tests understanding of Einstein Object Detection and image recognition metrics in Consumer Goods Cloud, specifically identifying which Key Performance Indicators (KPIs) are automatically derived through planogram detection analysis.

✅ A. Out of Stock, Share of Shelf, SKU Facings
When Einstein analyzes shelf images against reference planograms, it detects visual compliance and automatically calculates critical metrics: Out of Stock conditions (missing expected items), Share of Shelf (the percentage of total shelf space occupied by target products), and SKU Facings (the exact count of visible individual stock keeping unit product fronts).

❌ B. Out of Stock, Share of Shelf, Brand Facings
While brand performance is evaluated, planogram detection performs object detection and alignment verification at the granular SKU product level rather than defaulting exclusively to aggregated Brand Facings.

❌ C. Out of Stock, Shelf Size, SKU Facings
Shelf Size represents physical fixture dimensions configured prior to execution rather than a derived output from image recognition. Planogram detection analyzes item placement relative to space, deriving Share of Shelf instead.

❌ D. Out of Stock, Shelf Size, Brand Facings
This option combines static physical fixture properties (Shelf Size) with high-level brand counts, missing the precise SKU-level facing detection and calculated share-of-shelf ratios provided by planogram detection.

Reference
🔧 Einstein Object Detection in Consumer Goods Cloud - Salesforce Help confirms that planogram compliance checks analyze captured shelf images to derive metrics such as Out of Stock, Share of Shelf, and SKU Facings.

Explanation:

This question tests which standard Lightning components can be configured on Assessment Task record pages within the Consumer Goods Cloud mobile app. Salesforce provides documentation on the standard components available for customization in Lightning App Builder.

✅ Correct Option: B. Promotion List
The Promotion List component is designed for Promotion Check tasks. It displays promotions associated with the store or store group so field reps can evaluate promotional compliance and capture related KPIs during the assessment.

✅ Correct Option: C. Promotion Details
The Promotion Details component provides visibility into individual promotions during assessment tasks. It enables reps to review specific promotion terms, targets, and compliance requirements as part of the Promotion Check workflow.

✅ Correct Option: E. Inventory Check
The Inventory Check component is a standard Lightning component for Assessment Task record pages. It displays products associated with the store and allows users to search, scan, and update product quantities and availability.

❌ Incorrect options:

A. In Store Products
While "In-Store Products" relates to Consumer Goods Cloud functionality, it is not the standard Lightning component name for Assessment Task record pages. The correct component for product verification is "Inventory Check."

D. Cart Review
Cart Review is not a standard component for Assessment Task record pages. It is associated with order capture functionality rather than assessment tasks.

🔧 Reference:
→ Standard Consumer Goods Components – Salesforce Help — Documents the standard Lightning components available for Consumer Goods Cloud pages, including Inventory Check and Promotion components.

→ Extend Agentforce Consumer Goods with More Features – Trailhead — Confirms that admins can customize record pages by adding standard and custom Lightning components using Lightning App Builder.

Explanation:

This question tests how Consumer Goods Cloud identifies the specific area where an inventory check should be performed. In-Store Locations represent areas within a retail store, and inventory checks can be associated with these locations. Creating the Frozen Food Aisle as an In-Store Location lets the field rep identify where the product is stocked and perform the check in the correct area.

🟢 A. Create an In-Store Location called “Frozen Food Aisle”
An In-Store Location is the standard way to identify a specific area inside a retail store. For an inventory check, the field rep can select the applicable location and see the products associated with it. Creating “Frozen Food Aisle” as an In-Store Location therefore provides the required context for the inventory check and tells the rep where to perform it.

🔴 B. Create a record type called “Frozen Food Aisle” on the task
A record type is not used to represent physical areas within a retail store. Consumer Goods Cloud provides the In-Store Location object specifically for identifying locations such as aisles, shelves, or other store areas.

🔴 C. Create a picklist field called “location” to document the Frozen Food Aisle
A custom picklist is unnecessary because Consumer Goods Cloud already provides standard In-Store Location functionality. Using the standard location structure allows inventory checks and KPIs to be associated with the appropriate store area.

🔴 D. Nothing as Product2 captures that the product is frozen
Product2 identifies product information but does not by itself tell the field rep where that product is physically stocked in the store. The location must be represented separately through an In-Store Location and associated with the relevant retail execution configuration.

🔴 E. Create a record type called “Frozen Food Aisle” on the retail store
A Retail Store record represents the store itself, while an aisle is a location within that store. Consumer Goods Cloud uses In-Store Locations for these internal areas, so creating a Retail Store record type would not provide the required location context.

🔧 Reference:
⇒ Types of Assessment Tasks Definitions – Salesforce Help — Confirms that inventory checks can track products at specific In-Store Locations and allow field reps to select the location where the check is performed.

Explanation

This question tests understanding of the Consumer Goods Cloud data model, specifically identifying which standard object stores physical location details and operational data for an individual retail outlet.

✅ C. Retail Store
The Retail Store object is the standard Consumer Goods object used to store detailed information about a specific physical store, such as its location address, store manager, operating hours, and priority level. It links directly to a parent Account record representing the corporate retailer.

❌ A. Retail Store Groups
Retail Store Groups are used to cluster multiple physical stores into logical sets based on common characteristics (such as region, size, or format). They allow managers to apply shared assortment lists, targets, and KPIs rather than storing individual store records.

❌ B. Assortments
Assortment records define lists of eligible products available for sale within specific store locations or store groups. They govern product eligibility and inventory tracking rather than storing information about physical store locations.

❌ D. Account
Account records represent corporate entities, retail chains, or business partners (such as the overarching retailer). While a Retail Store is linked to a parent Account, individual store attributes and field execution details are captured on the Retail Store object.

Reference
🔧 RetailStore Object - Consumer Goods Cloud Developer Guide Salesforce confirms that RetailStore creates records for physical retail stores associated with business accounts.

Explanation

This question tests understanding of which build approach Consumer Goods Cloud recommends when a visit recommendation strategy needs to scale to meet complex or high-volume business requirements, rather than just basic rule logic.

✅ C. Build the strategy using an Apex class
Apex is used when visit recommendations are too complex to implement with regular flows alone. By annotating the relevant method with @InvocableMethod and adding the Apex class as an action element within a flow, admins and developers can scale the recommendation generation to match NTO's business requirements, handling more complex logic and larger data volumes than a flow-only approach.

❌ A. Build the strategy using Workflows
Workflow Rules are a legacy automation tool that Salesforce has deprecated in favor of Flow Builder, and they aren't part of the supported mechanism for building visit recommendation strategies. They lack the logic and scalability needed to drive Einstein-based visit recommendations.

❌ B. Build the strategy using Flow Builder
Flows are the standard way to run a visit recommendation strategy and work well for straightforward rules, but on their own they aren't positioned as the scalable option for complex requirements. Flows are typically paired with an Apex class specifically when scalability and complexity demand it.

❌ D. Build the strategy using Process Builder
Process Builder is a retired Salesforce automation tool, superseded by Flow Builder, and isn't part of the visit recommendation configuration process at all. It plays no role in defining or scaling Einstein visit recommendation strategies.

Reference
🔧 Set Up Visit Recommendations Using Next Best Action Strategy and Apex – Salesforce Trailhead → confirms Apex classes with invocable actions are used to scale visit recommendation generation for complex business requirements.

Explanation:

This question tests understanding of why the standard record page appears instead of the Custom Task KPI component for tasks of type "Other". The "Other" task type is designed for flexible, custom scenarios that require additional configuration beyond standard task types.

✅ Correct Option: B. The related object record page has not been configured to include Custom Task KPI Component in Lightning App Builder
For tasks of type "Other", the Custom Task KPI component must be manually added to the record page in Lightning App Builder. If the admin has not configured the related object's record page to include this component, the standard record page will display instead .

✅ Correct Option: D. The record page, custom task KPI Component, has not been assigned to the concerned user profile
Even if the record page is configured with the Custom Task KPI component, it must be assigned to the correct user profile. Without this assignment, users will see the standard record page rather than the customized version containing the KPI component .

❌ Incorrect options:

A. Lightning app builder does not support configuration of the standard record pages to include the KPI Component
This is incorrect because Lightning App Builder fully supports adding custom and standard components to record pages, including the Custom Task KPI component .

C. If the related object is a custom object, it will always display the standard record page
This is incorrect because custom objects can have customized record pages with KPI components. The visibility of the standard page depends on configuration, not on whether the object is custom .

E. Salesforce Mobile app always displays the standard record pages
This is incorrect because the Salesforce Mobile app displays the configured record page. If the Custom Task KPI component is properly added and assigned, it will appear on mobile as well .

🔧 Reference:
→ Enhance Consumer Goods Cloud Capabilities – Trailhead — confirms that admins customize record pages by adding custom and standard Lightning components and assigning them to users.

Explanation:

Sales Managers need a map that identifies stores running a promotion near a given location. The standard Nearby Map component provides location-based visualization directly on a record page, making it the appropriate solution while avoiding unnecessary custom development.

🟢 Correct Option:

C. The nearby map component on the promotion records page
The Nearby Map component is designed to display nearby records based on location information and can be added to Lightning record pages through configuration. Placing it on the promotion record page lets Sales Managers view relevant nearby stores without building a custom mapping solution. This uses standard Salesforce functionality and therefore requires the least custom development.

🔴 Incorrect Options:

A. A visual mashup that displays the required map on the promotions page
Incorrect because a visual mashup would require additional development or integration to provide the mapping functionality. Since Salesforce provides a standard Nearby Map component for location-based visualization, building a custom mashup introduces unnecessary development effort.

B. An unmanaged package from the AppExchange modified to meet the requirements
Incorrect because modifying an unmanaged AppExchange package adds customization and maintenance requirements. The requirement can be addressed using Salesforce's standard Nearby Map component, making an external package unnecessary for this use case.

D. The map component added to the home page
Incorrect because the requirement is specifically related to stores associated with a promotion. A home-page map does not provide the same record-contextual experience as placing the Nearby Map component on the relevant promotion record page.

🔧 Reference:
⇒ Salesforce Help — Nearby Map Component
Confirms that the Nearby Map component can display nearby records based on location information.

Explanation

This question tests understanding of product hierarchy mapping between external ERP systems and Consumer Goods Cloud, specifically identifying which level of product granular detail is necessary for execution monitoring like share-of-shelf.

✅ C. Which tier describes stock keeping units (SKU)?
Share-of-shelf measurements and shelf audit tasks in Consumer Goods Cloud require granular evaluation at the individual Stock Keeping Unit (SKU) level. Identifying which tier in the ERP's 7-tier hierarchy corresponds to individual SKUs ensures that products, variants, and competitors are accurately mapped for precise shelf space assessment and image detection models.

❌ A. What tier has data describing the product with?
This option is too vague regarding product attributes. Merely knowing which tier describes generic product details does not clarify whether the data reflects individual salable SKUs or higher-level product categories that lack the specificity needed for shelf auditing.

❌ B. Which tier has the data you trust most?
Data governance and organizational trust across tiers are general data quality considerations, but they do not define the structural granularity required to set up inventory, planograms, and share-of-shelf auditing tasks at the store level.

Reference
🔧 Product Hierarchy - Salesforce Help confirms that store-level execution and audit metrics like share-of-shelf must be mapped to individual SKU-level records within the product hierarchy.