Free Consumer-Goods-Cloud-Accredited-Professional Practice Test Questions and Answers (2026)

The Store Product object is a fundamental component in Consumer Goods Cloud that defines the specific assortment of products sold at a particular retail store. This association is critical for several core retail execution processes. It determines the list of products that appear for an Inventory Check task, ensuring field reps audit the correct items. It is also required for Promotion Check tasks to validate compliance for promotional products relevant to that specific store. Lastly, it drives the order capture functionality by populating the order template with only the products that are part of the store's authorized assortment.

A. Store Products are automatically When shipment related tasks are completed: This is incorrect. Store Products represent master data (the authorized assortment) and are typically set up administratively, not created transactionally upon shipment completion.

D. Store Products are required to search and scan functionality in the Inventory Check Task: While this statement is factually correct, it describes a specific feature within the broader function covered by option B. Option B is more fundamental, as the entire Inventory Check task, not just the search feature, relies on Store Products to function.

1. Salesforce Official Documentation, Consumer Goods Cloud Developer Guide, RetailStore Object: The documentation describes the relationship between a RetailStore and the products it carries. The Store Product (or Product2 via a junction object like StoreProduct) association is foundational for store-level activities. This supports the premise that inventory, orders, and promotions at a store level are filtered by the store's product assortment.

2. Salesforce Help, Consumer Goods Cloud, "Manage Product Assortments for a Store": This document states, "The Store Product object represents the products that are sold in a store... When a sales rep places an order for a store, the rep can see only the products that are associated with the store. When a sales rep records the inventory of products in a store, the rep can see only the products that are associated with the store." This directly validates answers B and E.

3. Salesforce Help, Consumer Goods Cloud, "Promotion Check": This page explains that promotion checks track and audit promotions at the store level. For product-specific promotions, the system must identify which promotional products are sold at that specific store to assess compliance (e.g., on-shelf availability, pricing). This requires the link provided by the Store Product record, thus validating answer C.

Salesforce Consumer Goods Cloud allows for the creation of custom Visit Recommendation strategies using two primary methods: Salesforce Flow or a custom Apex class. Flow Builder is the recommended declarative tool for building complex, scalable automation and business logic. It enables administrators and consultants to create sophisticated strategies that can query multiple objects and apply business rules to generate recommendations without writing code. This approach is highly scalable and more maintainable by a wider range of personnel than a code-based solution, making it the optimal choice for NTO's requirements.

A. Build the strategy using Workflows: Workflow Rules are a legacy automation tool being retired by Salesforce and do not have the capability to generate the complex VisitRecommendationInfo objects required for this feature.

C. Build the strategy using an Apex class: While using an Apex class is a valid and scalable method, Flow is the preferred low-code/declarative approach. It should be used unless the strategy's complexity exceeds Flow's capabilities, which is not indicated in the question.

D. Build the strategy using Process Builder: Process Builder is also a legacy automation tool being retired. It lacks the necessary functionality to create Visit Recommendation strategies and is less performant and scalable than Flow.

1. Salesforce Help, Consumer Goods Cloud Developer Guide, VisitRecommendationStrategy Interface: "To create your own logic for visit recommendations, create an Apex class that implements the cgcloud.VisitRecommendationStrategy interface." This reference validates that Apex is a possible, though not always preferred, method.

2. Salesforce Help, Consumer Goods Cloud Implementation Guide, "Create a Visit Recommendation Strategy": "You can create a visit recommendation strategy by using a flow or an Apex class." This section explicitly lists the two supported, scalable methods for creating a custom strategy.

3. Salesforce Help, Consumer Goods Cloud Implementation Guide, "Create a Flow for Visit Recommendations": "Create a flow that fetches data from various objects and recommends visits... The flow must have a collection variable of the Apex-defined data type VisitRecommendationInfo as output to store the visit recommendations." This document provides direct evidence for using Flow Builder as the primary declarative tool for this purpose.

4. Salesforce Architects, "Record-Triggered Automation Decision Guide": This guide outlines the reasons for choosing Flow over legacy tools like Process Builder and Workflow Rules, stating, "Flow is the future of low-code automation on the Salesforce Platform... We recommend that you build all new automations in Flow." This supports the deprecation of options A and D and the preference for B.

To associate an Action Plan with a Visit record in Consumer Goods Cloud, a foundational configuration step is required. You must first create an Action Plan Template and explicitly define the 'Visit' object as its 'Target Object'. This configuration tells the system that action plans derived from this template are intended to be used with Visit records. After defining the tasks and other attributes, the template must be published to make it active and available for use by sales representatives during their visit planning and execution.

A. Create an Action Plan based on the template where the template owners are the Sales Reps.

Ownership of the template does not determine its linkability to an object. The 'Target Object' field on the template is the sole determinant for this association.

C. Activate the Visit to generate Action Plan Tasks.

Activating a Visit is a subsequent action that occurs after an Action Plan has already been linked to it. This status change often triggers the generation of tasks from the associated plan.

D. Activate the Action Plan.

Activating the Action Plan is a step in the execution lifecycle of the plan itself, which happens after it has been created and linked to the target Visit record.

1. Salesforce Help: Action Plans in Consumer Goods Cloud

Section: Action Plans in Consumer Goods Cloud

Content: "You can associate an action plan with a visit to ensure that the field rep completes all the required tasks during the visit. To associate an action plan with a visit, create an action plan template and select Visit as the target object." This directly confirms that setting 'Visit' as the target object on the template is the required step.

2. Salesforce Help: Create Action Plan Templates

Section: Create Action Plan Templates

Content: "In the Target Object field, select the object on which to run action plans that are based on the template." This document outlines the standard procedure for creating templates and highlights the critical role of the 'Target Object' field in determining where the template can be applied.

The Retail Visit KPI object is the standard location where the results, or actual values, of KPIs captured during a specific store visit are stored. This object serves as a junction between the Visit record and the Assessment Indicator Definition (the KPI definition). When a field representative completes a custom task designed to measure a KPI, a Retail Visit KPI record is created or updated with the captured value in fields such as ActualNumberValue or ActualStringValue. This ensures that KPI data is directly associated with the visit in which it was collected.

A. In the custom object.

This is incorrect because while a custom task might leverage a custom object, the standard Consumer Goods Cloud data model uses the Retail Visit KPI object to store KPI results for reporting and processing.

C. In the Retail Store KPI record.

This is incorrect. The Retail Store KPI record tracks a KPI's target value and overall performance for a store over time, not the specific result from a single visit. Its actual value may be updated based on an aggregation of Retail Visit KPI records.

D. In the Visit Record.

This is incorrect. The Visit record itself stores general information about the visit (e.g., date, time, visitor), but it does not have standard fields to hold the results of individual KPI assessments. These are stored in the related Retail Visit KPI records.

---

1. Salesforce Help - Consumer Goods Cloud Data Model: The official data model documentation illustrates the relationships between objects. The RetailVisitKpi object is shown as the junction object linking Visit and AssessmentIndicatorDefinition, designed to capture visit-specific results.

Reference: Salesforce Help, "Consumer Goods Cloud Data Model," RetailVisitKpi object details.

2. Salesforce Developer Guide - RetailVisitKpi Object: The object reference explicitly states its purpose. "Represents the key performance indicators (KPIs) for a visit to a retail store... When a field rep captures the actual value for a KPI during a visit, a Retail Visit KPI record is created."

Reference: Salesforce Developer Guide, "Object Reference for Salesforce and Lightning Platform," RetailVisitKpi entry.

3. Salesforce Help - Set Up KPIs for Your Field Reps: This guide details the process and data flow. It confirms, "When a field rep captures the actual value for a KPI during a visit, a Retail Visit KPI record is created."

Reference: Salesforce Help, "Set Up KPIs for Your Field Reps," section on KPI data capture.

The Shipment object is the central component in the Direct Store Delivery (DSD) data model. It serves as the primary container record for a driver's entire tour. A back-office user prepares or "sets up" the Shipment record with crucial details like the driver, vehicle, and the complete product inventory for the day's route. This prepared Shipment then governs the subsequent delivery records and tasks for each store visit. While not a configuration item in the Salesforce Setup menu, it is the foundational object that is configured in preparation for the DSD field execution process.

B. Delivery Task: This is a transactional record representing a specific action (e.g., unload goods) performed during a store visit, not a preparatory object for the entire tour.

C. Order: This is a standard sales object that can be part of a DSD process (pre-order or van sales) but does not represent the tour's overall setup or logistics.

D. ProductTransfer: This object tracks the movement of inventory, such as loading the van. It is a preparatory action, but the Shipment is the master record for the tour itself.

---

1. Salesforce Help: Direct Store Delivery Data Model (Consumer Goods Cloud)

Reference: This document outlines the object relationships in the DSD process. It explicitly states, "A shipment contains information about the driver, the vehicle, the products, and the quantity of products for a tour. A delivery is created for each store in a shipment." This establishes the Shipment as the primary, parent object that is set up for a tour.

2. Salesforce Help: Direct Store Delivery Process (Consumer Goods Cloud)

Reference: This guide describes the end-to-end workflow. The process begins with the driver reviewing their assigned tour, which is encapsulated by the Shipment record. The guide notes, "The delivery driver starts the day by loading the van with products listed in a shipment." This confirms the Shipment is the pre-configured plan for the day's activities.

A Consumer Goods Cloud user can review vision detection accuracy through two primary mechanisms. Model Metrics provide a technical assessment of the underlying Einstein Vision model's performance, using standard machine learning metrics like F1 Score, Precision, and Recall. This allows administrators to evaluate the overall health and accuracy of the AI model itself. Shelf Metrics, which are the Key Performance Indicators (KPIs) generated after an image is analyzed (e.g., Share of Shelf, Facing Count, Out-of-Stock), allow field reps and managers to review and validate the accuracy of the detection for a specific shelf image taken during a store visit.

A. Goods Metrics: This is not a standard term used within Salesforce Consumer Goods Cloud for evaluating the accuracy of the Einstein Vision model or its outputs.

C. Planogram Metrics: This typically refers to the planogram compliance score, which is an outcome of the vision analysis, not a direct measure of the object detection model's accuracy.

D. Object Metrics: This is a generic term. The specific and correct terminology used in Salesforce for evaluating the AI model's performance is "Model Metrics."

1. Salesforce Help Documentation, "Monitor Your Einstein Vision Model": This document details the process of evaluating model performance. It states, "Use the Model Metrics tab on the Einstein Vision Model record page to see how your model performs. The tab shows metrics such as F1 Score, Precision, and Recall for the model." This directly supports the correctness of 'Model Metrics' (E).

2. Salesforce Help Documentation, "How Image Recognition Works": This document explains the output of the image analysis process. It states, "The service analyzes the image and identifies the products on a shelf... The results are saved as retail store KPIs. For example, share of shelf, out-of-stock, or planogram compliance." These KPIs are the Shelf Metrics (B) that a user reviews to confirm the accuracy of a specific scan.

Planogram detection in Salesforce Consumer Goods Cloud, powered by Einstein Vision, analyzes images of retail shelves to ensure compliance and measure performance. The system is trained to recognize specific products (SKUs). From a single shelf image, it can directly derive several key KPIs:

1. SKU Facings: It counts the number of visible instances of each specific product.

2. Out of Stock: By comparing the detected products against the planogram's requirements, it identifies products that are missing from their designated spots.

3. Share of Shelf: It calculates the percentage of visible shelf space occupied by specific products or brands relative to the total shelf space or competitors.

B. Out of Stock, Share of Shelf, Brand Facings: While Brand Facings can be calculated by aggregating SKU Facings, "SKU Facings" is the more direct and granular metric that the image recognition model provides.

C. Out of Stock, Shelf Size, SKU Facings: The system does not determine the absolute physical dimensions ("Shelf Size") of the shelf from an image; it analyzes the relative space occupied by products on it.

D. Out of Stock, Shelf Size, Brand Facings: This option is incorrect because, as with option C, the system does not calculate the physical "Shelf Size" from the image analysis.

1. Salesforce Help Documentation, "Planogram Check": "With Planogram Check, you can monitor planogram compliance at stores. You can check whether a product is available on the shelf, the number of facings of the product, and the share of the product on a shelf." This directly confirms that Out of Stock (availability), SKU Facings (number of facings), and Share of Shelf are primary outputs.

2. Salesforce Help Documentation, "How Einstein Object Detection Works": "Einstein Object Detection lets you train models to recognize one or more distinct objects in an image... When you give it an image, the model returns the objects it detects, the location of each object, and the probability that the object is what the model claims it is." This foundational technology enables the counting of individual product facings (SKUs).

3. Salesforce Help Documentation, "Key Performance Indicators for Retail Execution": This section details the various KPIs used in Consumer Goods Cloud. While it lists many KPIs, the ones specifically related to image recognition and planogram compliance are facings, share of shelf, and out-of-stock, which are derived from the underlying object detection capability.

In Salesforce Consumer Goods Cloud, Action Plan Templates are used to standardize tasks for field representatives during store visits. To provide flexibility and targeted task assignment, the system allows these templates to be associated at three distinct hierarchical levels. They can be linked directly to an individual Retail Store, to a Retail Store Group (which applies the template to all stores within that group), or to a parent Account (which can represent a national chain or a key account). This structure enables managers to define tasks that are specific to a single location, common to a region or type of store, or standard across an entire customer account.

A. Location: Action Plan Templates are associated with the business entity (Account/Retail Store) for visit execution, not the generic Salesforce Location object.

D. In-Store Location: Templates define tasks for an entire visit. While individual tasks within a template can be tied to specific in-store locations, the template itself is not defined at this granular level.

1. Salesforce Help, Consumer Goods Cloud Documentation, "Set Up Recommended Tasks": This official guide explicitly states, "To recommend tasks for a visit, associate an action plan template with a retail store, a retail store group, or an account. You can create an action plan template and then associate it with a target." This directly confirms the three correct levels.

2. Salesforce Developer Guide, Object Reference, ActionPlanTemplateStore: The documentation for this junction object details its purpose: "Represents the association between an action plan template and a retail store, a retail store group, or an account." This object is the mechanism used to create these three types of associations.

3. Salesforce Help, Consumer Goods Cloud Documentation, "Action Plans in Consumer Goods Cloud": This section provides context on how Action Plan Templates are a core component for creating standardized visit tasks. It describes their role in ensuring consistent execution, which is achieved by associating them with the appropriate business entities like Accounts, Retail Stores, and Retail Store Groups.

A promotion's fundamental purpose is to market or increase sales for specific goods. In the Consumer Goods Cloud data model, the Promotion object is directly linked to the Product2 object via the Promotion Product junction object. This association is critical because it defines what is being promoted. While a promotion is also associated with channels and stores (defining where it runs), the products are the core subject of the campaign, making this the most essential direct association.

A. Retail Store Group: This is a targeting mechanism to define a collection of stores for a promotion. The promotion's core subject remains the product, not the store group.

B. Promotion Channel: This defines the type of outlet (e.g., Supermarket) for the promotion. It is a targeting attribute, not the fundamental subject of the promotion itself.

C. Retail Store: This specifies the exact location for a promotion's execution. The promotion is defined by the products it includes before it is assigned to specific stores.

1. Salesforce Help - Consumer Goods Cloud Data Model: The official data model diagram illustrates the relationships. The Promotion Product object is shown as a junction object with master-detail relationships to both the Promotion and Product2 objects, establishing a direct, many-to-many association.

2. Salesforce Help - Promotions in Consumer Goods Cloud: The documentation defines a promotion as "a time-bound marketing or sales campaign for specific products at specific stores." This highlights that products are a primary component in the definition of a promotion.

3. Salesforce Help - Create a Promotion in Consumer Goods Cloud: The procedural documentation for creating a promotion outlines adding "Tactic Products" as a key step after defining the promotion's basic attributes, reinforcing the centrality of the product association in the business process.

The 'Maximize Store Sales' story is a pre-built Einstein Discovery model included with the CRM Analytics for Consumer Goods Cloud application. It is specifically designed to analyze historical store performance data and identify the key drivers that impact sales revenue. The story provides actionable insights and predictions on how factors like store visits, promotion effectiveness, out-of-stock situations, and planogram compliance influence sales outcomes. This directly addresses the consultant's goal of gaining insights into factors affecting store sales, enabling sales managers to make data-driven decisions to improve performance.

A. 'Strategic Sales' is not a standard, pre-built Einstein Discovery story provided with the CRM Analytics for Consumer Goods Cloud template.

C. 'Minimize Out-of-Stock occurrences' is a key performance indicator (KPI) and a factor analyzed within the 'Maximize Store Sales' story, but it is not the name of the story itself.

D. 'Promotion Management' is too narrow. While promotion effectiveness is analyzed, the 'Maximize Store Sales' story provides a more comprehensive analysis of multiple factors affecting sales, not just promotions.

1. Salesforce Help Documentation: Einstein Discovery for Consumer Goods Cloud. This document explicitly names and describes the purpose of the pre-built story. It states, "The Einstein Discovery for Consumer Goods Cloud app includes the Maximize Store Sales story that helps sales managers analyze their business and understand what they can do to improve their numbers."

2. Salesforce Help Documentation: CRM Analytics for Consumer Goods. This guide details the components of the analytics application, including the dashboards and the underlying Einstein Discovery story. It confirms that the app template is designed to provide insights into sales, compliance, and visit execution, with the 'Maximize Store Sales' story as a core component for predictive analysis.

Setting up Einstein Vision for product detection in Consumer Goods Cloud involves three primary stages. First, the feature must be technically enabled in Salesforce Setup (B). Second, the AI model must be trained to recognize the products; this is accomplished by creating a dataset with product images and training the Einstein Vision model (E). Finally, to make this functionality available to field reps, a specific "Planogram Check" task must be defined within the retail execution process (D). This task type is specifically designed to trigger the image capture and analysis workflow using the trained model.

A. Setup in store location and associate planogram: This is a foundational step for general retail execution, not a specific configuration step for the Einstein Vision feature itself.

C. Upload the training pictures as attachments to the planogram for Einstein Object Detection to work: Training images are uploaded to a dataset and associated with product records to train the model, not attached to individual planogram records.

1. Salesforce Help, Consumer Goods Cloud Documentation, "Set Up Einstein Object Detection for Consumer Goods Cloud": This guide explicitly outlines the required setup process. It lists the main steps as: "Enable Einstein Object Detection," "Create a Planogram Check Task," and "Train Your Einstein Vision Model." This directly supports options B, D, and E.

2. Salesforce Help, Consumer Goods Cloud Documentation, "Einstein Object Detection": This overview states, "To get started, enable Einstein Object Detection. Then, create a planogram check task. Finally, train your Einstein Vision model." This confirms the sequence and validity of options B, D, and E.

3. Salesforce Help, Consumer Goods Cloud Documentation, "Guidelines for Creating a Training Dataset": This document details the process of preparing images for training the model. It specifies associating images with products to create a dataset, which contradicts the idea of attaching images to a planogram (Option C). It also implicitly supports the necessity of training the model (Option E).

Salesforce Maps Advanced provides powerful route and schedule optimization for field representatives. Its capabilities are designed to create the most efficient plans while adhering to business rules. The system incorporates real-time and predictive traffic data (A) to calculate accurate travel times and avoid delays. The core of the tool is its constraint-based routing engine (B), which allows planners to define rules such as working hours, break times, and skills. A critical constraint for store visits is respecting Visit Windows (C), which ensures that representatives arrive at a location only during its specified hours of operation or appointment times. These three capabilities work together to generate realistic and productive daily schedules.

D. Visit Prioritization: While Salesforce Maps Advanced can prioritize visits, this is a specific rule handled by the broader Constraint based Routing (B) engine and is less foundational than the core engine itself or hard constraints like visit windows.

E. Gantt-chart Routing: This is not a standard Salesforce feature or industry term for a routing capability. A Gantt chart is a method for visualizing a schedule, not a mechanism for creating one.

1. Salesforce Help, Optimize Routes with Salesforce Maps Advanced: This document explicitly states that the optimization engine "considers various factors, such as work hours, travel time, stop duration, traffic conditions, and visit priorities." This confirms the use of traffic data (A) and the general principle of constraint-based logic (B).

2. Salesforce Help, Salesforce Maps Route and Schedule Optimization: This guide details the scheduling policies and work rules that form the basis of constraint-based routing. Under "Field Service Settings," it describes the use of an "Arrival Window Start Field" and "Arrival Window End Field" for Service Appointments, which directly corresponds to the Visit Windows capability (C).

3. Salesforce Help, Routing and Optimization Services: This documentation for the underlying engine explains the different types of constraints (called "work rules") that can be applied, such as "Match Skills," "Time-Bound," and "Service Territory." This confirms the fundamental nature of constraint-based routing (B) as the core capability.

When a flow is initiated as part of a visit task, the Salesforce platform automatically passes crucial contextual information into the flow as input variables. This includes the VisitId and the AssessmentTaskId, enabling the flow to perform actions on the correct records. Furthermore, if the task involves creating a RetailVisitKpi record, a corresponding RetailStoreKpi must exist for that store. The ID of this RetailStoreKpi is passed to the flow in the RetailStoreKPI variable, providing the necessary context for the flow to calculate and record the visit-specific KPI value against the store-level target.

B. This describes the general data model, not a specific mechanism of flow-based tasks. Options A and C are more precise about the flow's execution context.

D. This is incorrect. A Retail Store KPI is a mandatory prerequisite for a flow to create a corresponding Retail Visit KPI record.

E. This is incorrect. A primary use case for flow-based tasks is to implement custom logic for calculating and creating Retail Visit KPIs.

1. Salesforce Help, Consumer Goods Cloud Documentation, "Create a Flow for a Task": This document explicitly states the input variables for a flow-based task.

Reference for C: Under the section "Create a Flow for a Task," the documentation notes, "When you create a flow for a task, the Assessment Task ID and the Visit ID are passed to the flow."

Reference for A & D: In the "Considerations for Creating a Flow for a Task" section, it specifies, "To create a Retail Visit KPI record, you must have a Retail Store KPI record. The Retail Store KPI ID is passed to the flow in the RetailStoreKPI variable." This confirms A is correct and D is incorrect.

Reference for E: The entire purpose of the documentation page is to describe how to use flows for tasks, including those that create KPIs, which directly refutes option E.

2. Salesforce Help, Consumer Goods Cloud Documentation, "Consumer Goods Cloud Data Model": This resource details the object relationships.

Reference for B: The data model shows that the RetailVisitKpi object has a master-detail relationship to both Visit and RetailStoreKpi, confirming a Retail Store KPI is required for a Retail Visit KPI to exist. This supports why option B is a generally true statement but less specific to the process of a flow task than A and C.

The standard process for a field representative, such as a merchandiser, is to use the Salesforce Mobile App to manage their daily tasks. When arriving at a customer location for a scheduled visit (appointment), the user navigates to the specific Visit record within the app and uses the "Check-In" quick action. This action is specifically designed to capture and record the exact time of arrival and the device's current geo-coordinates, fulfilling the requirements of the inventory-check appointment.

A. Check-in through Einstein Vision: Einstein Vision is used for image recognition tasks like planogram compliance or shelf analysis, not for the primary action of checking into a visit to log time and location.

B. Check-in through standard location picker Lightning Web Component in Salesforce Mobile App: This is overly specific and incorrect. The check-in is a dedicated, pre-built action on the Visit object, not a generic Lightning Web Component that a user would select independently.

D. Check-in through Salesforce Maps on mobile: While Salesforce Maps is used for routing and location intelligence, the core check-in functionality is a standard feature of the Consumer Goods Cloud application on the Salesforce Mobile App and does not require Salesforce Maps.

1. Salesforce Help Documentation, "Execute Visits on the Mobile App": This document explicitly outlines the procedure for field reps. It states, "When a field rep reaches a store, the rep can check in to the store to record the time and location of the visit... From the navigation bar, tap Today's Visits. Tap a visit. Tap Check-In." This confirms the action is performed within the Salesforce Mobile App on the Visit record.

2. Salesforce Help Documentation, "Visit Execution": This section details the lifecycle of a visit, which begins with the check-in process. It describes how the check-in action captures the ActualVisitStartTime and location data, which is fundamental to tracking field rep activity and performance.

3. Trailhead, "Consumer Goods Cloud: Offline Mobile App" Module, "Manage Your Visits" Unit: This educational module describes the capabilities of the mobile app for field reps. It details how reps can "start their day, check in to a store, perform their tasks, and check out," reinforcing that the check-in/check-out process is a core feature of the mobile application experience for visit management.

The KPI Type field is a mandatory field when creating a Retail Store KPI record in Salesforce Consumer Goods Cloud. This field is a picklist that defines the specific metric being measured, such as 'Share of Shelf', 'Out of Stock', or 'Count of Facings'. Without defining the KPI Type, the record would lack its fundamental purpose, as the system would not know what performance indicator to track or how to evaluate it during a store visit.

A. Effective to: This field specifies the end date for the KPI's validity. It is not a required field, as a KPI can be set up to be ongoing without a defined end date.

B. Retail Store Group: A Retail Store KPI must be associated with either a Retail Store Group or an individual Retail Store, but not necessarily the group. Therefore, this specific field is not universally required.

D. Promotions: While KPIs can be linked to promotions to measure their effectiveness, they are also used for standard, non-promotional compliance checks. This makes the link to a promotion optional, not required.

1. Salesforce Help, Consumer Goods Cloud Implementation Guide, "Set Up Retail Store KPIs": This document outlines the process for creating Retail Store KPIs. It implicitly requires a type to define what is being measured. The core function of a KPI record is to define a metric, which is handled by the KPI Type field.

2. Salesforce Object Reference for Consumer Goods Cloud, RetailStoreKpi Object: The official object documentation lists KpiType as a required picklist field. It states, "The type of KPI. For example, Share of Shelf, Count of Facings, or Out of Stock." This confirms its mandatory nature for record creation.

3. Salesforce Help, Consumer Goods Cloud Data Model, "Retail Execution Objects": The data model diagram and descriptions show that the RetailStoreKpi object's definition is centered around the type of KPI it represents, distinguishing it from other optional associations like RetailStoreGroupId or time-bounding fields like EffectiveToDate.