Consumer-Goods-Cloud-Accredited-Professional Practice Test Questions

Explanation:
This question tests understanding of the primary relationship for a Promotion record in Consumer Goods Cloud (CGC). A Promotion is a foundational object used to define discounts, offers, or incentives. While a promotion can be linked to many related entities like channels or stores for execution, its core, defining association is with the specific products or product groups it is meant to discount. The system must first know what is being promoted.

Correct Option:

D. Products:
A Promotion object is directly associated with Products (or Product Groups) through the "Promoted Products" related list. This is a mandatory relationship because a promotion's primary purpose is to apply an incentive to specific items. The promotion mechanics (like discount value) are defined in relation to these products.

Incorrect Option:

A. Retail Store Group:
Promotions are associated with stores or store groups indirectly via the Promotion Channel and its related Targeting Rules, not through a direct object relationship.

B. Promotion Channel:
While a Promotion must be linked to a Channel (e.g., Retail, E-commerce), the Channel defines where the promotion runs, not what is being promoted. The direct association for the "what" is with Products.

C. Retail Store:
Similar to Store Group, individual stores are targets for promotion distribution set through Channel targeting rules, not a direct object-level association on the Promotion record itself.

Reference:
Salesforce Help Article: "Create a Promotion" in the Consumer Goods Cloud guide, which shows the "Promoted Products" related list as a primary component of the promotion setup.

Explanation:
The Product2 object in Salesforce is the core master data record for all products your company sells. In Consumer Goods Cloud, this standard object is related to several custom CGC objects to track products in the context of retail activities, such as which products should be sold at a store, which are part of a promotion check, or which are included in a specific product assortment for a retail store. The relationship is typically implemented using a lookup field on the custom CGC object that points back to the Product2 record.

Correct Option:

A. Assortment Product:
This is a junction object (cgcloud__AssortmentProduct__c) that links a Product2 record to an Assortment record. Assortments define the specific list of products that are eligible for sale at a particular store or group of stores, making this a fundamental link to the Product2 object.

C. Assessment Task Product:
While the direct object name might be AssessmentTaskProduct or similar (and is often part of the AssessmentTask setup), it is an essential object used to define which Product2 records are the focus of a retail execution task, such as an Inventory Check or Promotion Check, during a store visit.

E. Store Product:
This object (cgcloud__StoreProduct__c) explicitly associates a Product2 record with a Retail Store or a specific In-Store Location within that store. It is used to manage product-related details specific to a physical retail store location.

Incorrect Option:

B. Delivery Product:
While Consumer Goods Cloud does handle delivery via Direct Store Delivery (DSD), there is no standard custom object named "Delivery Product" in the data model that directly relates to Product2 to define delivery-specific product details. Delivery tasks are handled by the DeliveryTask object.

D. Promotion Product:
This object (cgcloud__PromotionProduct__c) does exist in the CGC data model. However, it is a junction object used to link a Promotion record to a Product2 record. While it is linked to Product2, it is typically considered part of the Trade Promotion Management (TPM) structure, and the standard list of core CGC objects directly linked to Product2 for Retail Execution focus on the Assortment, Task, and Store product relationships (A, C, E). In the context of the three most common and core objects, A, C, and E are the stronger set. Self-Correction: Given that PromotionProduct (cgcloud__PromotionProduct__c) is a valid junction object linking a Promotion to Product2, a set including D might be plausible, but the most foundational objects are Assortment Product, Store Product, and the product linkage within Assessment Tasks (often via a related object like Assessment Task Product or similar setup for checks).

Reference:
Consumer Goods Cloud Data Model Overview: Product Assortment Key Objects, Standard Objects for Retail Execution, and Assessment Task Definitions.

Explanation:
This question focuses on the technical setup required to enable a specific visual execution task: a Planogram Check assessment. In Consumer Goods Cloud, the Planogram Check assessment type relies on comparing a field-captured photo against a reference image to verify compliance. The system needs a standard image as the baseline for this comparison.

Correct Option:

D. The team member must upload an image of the planogram to the assessment task's related documents.
A Planogram Check task is fundamentally an image comparison. The reference planogram image must be uploaded to the related Documents of the assessment task definition. When a field user performs the check, they take a photo of the shelf, and the Einstein Vision service compares it to this uploaded reference image to generate a compliance score.

Incorrect Option:

A. The team member must make sure Einstein Object Detection has been enabled.
While Einstein Vision services (which include object detection) are used in the background for image analysis, enabling it is a prerequisite setup by an admin. The required step for the team member creating the task is to provide the reference image.

B. The team member must populate the custom context field on the assessment task.
Custom context fields are for additional metadata, not the core functional requirement of providing the reference image for a visual check.

C. The team member must associate the In-Store Location to the Planogram for the functionality to work.
Associating a Planogram to an In-Store Location is important for organization and reporting, but the Planogram Check assessment functionality itself is enabled by attaching the reference image to the task.

Reference:
Salesforce Help Article: "Create a Planogram Check Assessment" states that to create this assessment type, you must add a planogram image to the related Content (or Documents) on the task record. This image is used as the baseline for comparison.

Explanation:
In Salesforce Consumer Goods Cloud, field reps capture KPIs during store visits using assessment tasks, which are generated from assessment task definitions. For specialized activities like checking the functionality of in-store assets (e.g., Computer Display Units for backpack fitting), creating a custom record type on the Assessment Task object allows tailored fields, layouts, and indicators specific to the task. This ensures reps can efficiently record metrics like "Backpack fit properly" while associating it with the relevant asset, promoting standardized execution and reporting across visits.

Correct Option:

B. Create an Assessment Task Record type called ‘Backpack Fit’ for the Computer Display Units to capture the KPIs.
Assessment Task supports record types to customize data capture for unique scenarios, such as asset functionality checks.
This approach links the task to the asset record, enabling reps to input Boolean or numeric KPIs (e.g., fit compliance) via assessment indicators.

It integrates seamlessly with action plan templates for reusable visit workflows, improving compliance tracking and mobile app usability for field execution.

Incorrect Options:

A. Create an asset called ‘Computer Display Unit’ and capture KPI called ‘Backpack fit properly’ using an assessment task.
Creating the asset record is necessary but insufficient alone; it doesn't specify how to customize the assessment task for targeted KPI capture.

Assessment tasks require definitions and potentially record types for specialized indicators, not just asset creation, to ensure structured data entry during visits.

C. Add ‘Backpack Fit’ for the Computer Display Units checkbox to the In-Store Survey Assessment Task.
In-Store Survey tasks are predefined for customer/store feedback via Salesforce Surveys, not equipment/asset functionality checks.

Repurposing it for asset KPIs risks data inconsistency and violates best practices for task separation, as surveys focus on qualitative responses rather than asset-specific metrics.

D. Create an Asset record named ‘Backpack Fit’ for the Computer Display Units and link it to the Assessment Task via a lookup field.
Naming the asset "Backpack Fit" misrepresents its purpose; assets should represent physical items like the display unit, not the check activity.

While lookup fields enable association, this doesn't create a dedicated task structure for KPI capture, leading to ad-hoc data entry without standardized templates or indicators.

Reference:
Salesforce Help: "Assessment Tasks in Consumer Goods Cloud" and "Set Up Assessment Task Definitions"

Trailhead: "Consumer Goods Cloud Data Model – Work with Metrics and Retail Store KPIs" (Winter '26 Release)

Consumer Goods Cloud Developer Guide: Assessment Task Object and Record Types (API v59.0+)

Explanation:
This question tests knowledge of structuring retail execution data to provide location context for field tasks. In CGC, the In-Store Location object is the standard, scalable way to map the physical layout of a store (e.g., aisles, shelves, coolers). Associating products to these predefined locations allows the system to automatically inform field reps where to find items during tasks like inventory checks, ensuring efficiency and accuracy.

Correct Option:

A. Create an In-Store Location called 'Frozen Food Aisle'.
This is the foundational first step. The consultant must create this master location record. Subsequently, this In-Store Location can be linked to relevant Products and to the specific Retail Store. Once configured, tasks generated for those products at that store will display the "Frozen Food Aisle" location to the field rep.

Incorrect Option:

B. Create a record type called 'Frozen Food Aisle' on the task.
Record types control page layouts and picklist values for types of tasks (e.g., Inventory Check, Planogram). They are not used to specify variable, store-specific physical locations for individual products.

C. Create a picklist field called 'location' to document the Frozen Food Aisle.
While functional, this is a custom, less scalable approach. CGC provides the dedicated In-Store Location object for this purpose, which supports hierarchies, associations to multiple stores, and integration with other features like planograms.

D. Nothing as Product2 captures that the product is frozen.
The Product2 record can indicate a product category (e.g., Frozen Food), but it does not specify the physical location within a specific store (e.g., Aisle 7). This store-level mapping is essential for execution tasks.

E. Create a record type called 'Frozen Food Aisle' on the retail store.
Record types on the Retail Store object could categorize store types (e.g., "Supercenter," "Express"). They cannot specify internal aisle locations for product lookup.

Reference:
Consumer Goods Cloud data model documentation emphasizes the In-Store Location object as the primary method for defining and managing physical store layouts to guide field representatives during store visits.

Explanation:
The Shipment object is the object used in Consumer Goods Cloud (CGC), primarily within the context of Direct Store Delivery (DSD) and Van Sales, that allows for the administrative setup of inventory transport from a warehouse or vehicle (Source Location) to a retail store (Destination Location). It defines what is being transported and where it is going, which is a key administrative step performed in the back-office Setup before the physical delivery execution.

Correct Option:

A. Shipment:
This object is a standard Salesforce object that is heavily utilized in CGC for DSD. It represents the actual consignment or transport of products to be delivered. In the setup phase, an administrator or back-office user associates a Shipment record with a Delivery Task to define the inventory (via the related ProductTransfer object) that the driver will be delivering during a specific store visit. It's the core object for setting up the inventory logistics.

Incorrect Option:

B. DeliveryTask:
While central to DSD, the DeliveryTask object is primarily the execution object. It is a type of task that field users (drivers/sales reps) see and complete on the mobile app during a store visit. It is usually created automatically via an Action Plan Template and then linked to the administrative Shipment record by a back-office user, but it's not the exclusive setup object.

C. Order:
The standard Order object is used to capture a customer's request for products. In DSD, an Order can be fulfilled by a delivery, but the Order itself is a sales object, not an object exclusively used in the setup of the delivery/shipment logistics. Orders can be placed, and then a shipment is created to fulfill it.

D. ProductTransfer:
This object is used to define the specific products and quantities within a Shipment or to track transfers between locations (like from the vehicle to the store). It is a detail object related to the Shipment object. The Shipment record itself is the higher-level object used in setup to initiate the transport.

Reference:
Consumer Goods Cloud Data Model for Direct Store Delivery (DSD), specifically the relationship between Shipment, Delivery Task, and Product Transfer objects.

Explanation:
This question checks knowledge of the standard Key Performance Indicator (KPI) types available for tracking retail store performance within Consumer Goods Cloud. Retail Store KPIs are quantitative measurements used in surveys and assessments. The platform provides a defined set of KPI Type picklist values that determine how the KPI's numeric data is categorized and interpreted.

Correct Option:

A. Units: This KPI type measures product volume, such as the number of items sold or in stock.

D. Facing: This KPI type measures shelf space, specifically the number of product facings on the shelf.

E. Revenue: This KPI type measures monetary sales value.

These three are standard, supported picklist values for the KPI Type field on the Retail Store KPI object, allowing field reps to record different quantitative aspects of in-store execution.

Incorrect Option:

B. Price:
While price is a critical metric, it is not a standard KPI Type for tracking performance data entered by field reps. Price is typically managed as a field on the Product or Pricebook entry, or as part of a promotion. KPIs focus on measurable outcomes like units sold or revenue generated from that price.

C. Promotion:
Promotion is a catalyst for performance, not a performance measurement type itself. The effectiveness of a promotion would be measured using supported KPI Types like Units or Revenue. Promotion is a separate object in CGC.

Reference:
The Salesforce Consumer Goods Cloud Object Reference for the Retail Store KPI object lists the standard picklist values for the KPI Type field, which includes Facing, Revenue, and Units (among others like Distribution). Price and Promotion are not included in this standard list.

Explanation:
The requirement is to check the compliance of high-value assets and, if non-compliant, automatically trigger an action plan. The most low-code/no-code approach in Consumer Goods Cloud (CGC) is to leverage the standard Retail Execution assessment task types (like Inventory Check, Planogram Check) combined with a Salesforce Flow for automation. An Inventory Check task is the most appropriate standard task for auditing physical items like assets, and Flow can handle the logic to determine compliance and trigger the follow-up action plan.

Correct Option:

A. Use an inventory check task with flow:
This is the recommended approach for minimal custom code. CGC's Inventory Check task type can be configured to include specific questions about an asset's status or condition using an Assessment Indicator Definition that captures a Boolean (Yes/No or Compliant/Non-Compliant) value. A Flow can then be configured to run immediately after the task is completed, checking that Boolean value. If the value is 'Non-Compliant' (False), the Flow can easily create a new record (like an Asset Repair task or a follow-up Visit) to trigger the correction action plan.

Incorrect Option:

B. Use a custom task with flow:
While a custom task can be used, it's generally best practice to utilize an out-of-the-box (OOTB) task type when a suitable one exists, such as the Inventory Check. Creating a Custom Task is typically reserved for activities that don't fit any of the standard types (Inventory, Promotion, Planogram, Survey). Using the standard Inventory Check task provides OOTB mobile app features and data model structure, making it more efficient than creating a custom task, thus this option is less optimal.

C. Use a promotion check task with apex:
Promotion Check tasks are specifically designed for auditing the placement and execution of sales promotions, such as display materials, pricing, and shelf presence. This is not the correct standard task type for checking the physical status and compliance of a high-value asset like a cooler or display unit. Furthermore, using Apex introduces custom code, which the requirement explicitly seeks to limit in favor of declarative tools like Flow.

D. Use a custom task with apex:
This option involves two unnecessary customizations: creating a Custom Task when a standard one (Inventory Check) would suffice, and using Apex (code) when the powerful, low-code Flow automation tool is more appropriate for a simple compliance check and record creation trigger. This approach violates the principle of limiting custom code and using OOTB features.

Reference:
Consumer Goods Cloud Retail Execution: Assessment Task Definitions (Inventory Check) and Salesforce Flow for Automation.

Explanation:
Store Action Plan Templates allow managers to pre-define recommended tasks for store visits, ensuring consistency and focus. In CGC, these templates must be associated with a specific context to determine where they are applicable. The platform supports defining these templates at three hierarchical levels, from broad groups down to specific store sections.

Correct Option:

B. Retail Store Group: Templates can be defined for a group of stores (e.g., "All Premium Tier Stores") to apply a standard set of recommendations across that segment.

C. Retail Store: Templates can be defined for a single, specific store to provide highly tailored recommendations for that individual location.

D. In-Store Location:Templates can be defined for a specific area within a store (e.g., "Checkout Aisles"), allowing for micro-level task recommendations focused on a particular section, regardless of the overall store.

Incorrect Option:

A. Location:
While "Location" might sound similar to In-Store Location, it is not a standard object in the CGC hierarchy for associating Action Plan Templates. The precise term is In-Store Location (D).

E. Account:
The CGC model uses the Retail Store object as the primary point of interaction for field execution, not the generic Salesforce Account object. Action Plan Templates are specifically designed for the retail execution layer (Store, Store Group, In-Store Location), not the generic account layer.

Reference:
Salesforce Help Article: "Create a Store Action Plan Template" explicitly states that when creating a template, you "select the scope: a retail store, retail store group, or in-store location." This confirms the three supported association levels.

Explanation:
This question focuses on the prerequisite setup steps to enable and use Einstein Vision's automated product detection for shelf audits within CGC. The process involves activating the AI service, preparing the visual recognition model with the right product images, and then creating the specific field task type that utilizes this technology.

Correct Option:

B. Enable Einstein Object Detection:
This is the fundamental administrative step. An admin must enable the Einstein Object Detection permission and set up the connected app in the Salesforce setup to make the AI service available for use within CGC.

D. Define planogram check task:
The field execution mechanism for using this technology is the "Planogram Check" assessment task. This task type is configured to use the trained Einstein Vision model to compare a photo taken in-store against a reference planogram image.

E. Train Einstein Vision Models with marketing images of products to yield optimal results:
For accurate automated detection, the Einstein Vision model must be trained. This involves creating a dataset and labeling it with clear, high-quality product images (typically marketing or studio shots) to teach the model what each product looks like.

Incorrect Option:

A. Setup in store location and associate planogram:
While important for overall store layout and task organization, setting up In-Store Locations is not a required step for enabling the core Einstein Vision detection functionality. It is more related to task routing and reporting.

C. Upload the training pictures as attachments to the planogram for Einstein Object Detection to work:
This is incorrect on two points. First, training images are uploaded to a Dataset in Einstein Vision, not as simple attachments to a planogram. Second, the reference image attached to a planogram task is for visual comparison during a check, not for training the core AI model.

Reference:
Salesforce Help Article: "Set Up Einstein Object Detection for Consumer Goods Cloud" outlines the key steps: 1. Enable the feature, 2. Train a model with product images in Einstein Vision, and 3. Create a Planogram Check task that uses the trained model.