Explanation:
In Consumer Goods Cloud, the standard and recommended way to track sample inventory distributed through distributors or third-party merchandisers is by using Delivery Tasks. These tasks allow the creation of product transfer orders that reduce the sample warehouse inventory and increase the distributor’s (or van’s) on-hand inventory for that specific SKU. The field execution app then continuously tracks and reports the real-time on-hand quantity of sample products in the field.

Correct Option:

A. By creating delivery tasks for the distributors and monitor their on hand inventory for the sample Product’s Stock Keeping Unit (SKU).
Delivery Tasks generate Product Transfer records that move sample stock from the company warehouse to the distributor’s mobile inventory.

The distributor’s on-hand inventory for the sample SKU is visible in real time in CG Cloud (Inventory → In-Field Inventory).

Subsequent in-store sample distribution further reduces the distributor’s on-hand balance, giving full end-to-end visibility.

Incorrect Options:

B. By creating a report for store locations to monitor the on hand inventory
Store locations do not hold sample inventory in this scenario; distributors do. Reporting only on retail stores would not reflect the actual sample stock in the field.

C. By assigning the asset to a custom task type and make the distributors enter the delivered quantity
Assets represent physical equipment (e.g., coolers), not consumable samples. Using assets for sample tracking is incorrect and not supported.

D. By creating delivery tasks for the distributors and track the shipping document status
Tracking only the shipping document status confirms shipment but does not provide ongoing visibility into the distributor’s remaining on-hand sample inventory after partial distribution.

Reference:
Salesforce Help: “Manage In-Field Inventory and Product Transfers in Consumer Goods Cloud”

Trailhead: “Distribute Samples and Track Inventory with Delivery Tasks”

CG Cloud Release Notes (Spring ’25 onward): In-Field Inventory for third-party users and distributors

Explanation:
Promotions in Consumer Goods Cloud, particularly in the context of Trade Promotion Management (TPM) and Retail Execution (RE), require several objects to define what is promoted, where it is promoted, and how the promotion's performance is measured. The central Promotion object uses relationships (often junction objects) to link to products, retail locations, and specific metrics (KPIs) used to set targets and capture actual results.

Correct Option:

B. Promotion Product, Promotion Channel, Retail Store KPI, and Retail Visit KPI:
This option correctly lists four essential objects tied to the Promotion object:

Promotion Product: A junction object (cgcloud__PromotionProduct__c) that explicitly links a Promotion to the Product2 records that are part of the promotional offer.

Promotion Channel: An object (cgcloud__PromotionChannel__c) that defines the location scope of the promotion by linking a Promotion to a specific Retail Store, Retail Store Group, or Account.

Retail Store KPI (RSKPI): Used in Setup to define the target performance for a KPI (e.g., "5 facings") in relation to a Promotion. The RSKPI record has a lookup field to the Promotion object.

Retail Visit KPI (RVKPI): Used during the Visit Execution to capture the actual performance data (e.g., "4 facings") against the target defined by an RSKPI, thus linking the captured result back to the executed Promotion Check. The RVKPI object has a lookup field to the Promotion object.

Incorrect Option:

A. Promotion Channel, Retail Store KPI, Retail Visit KPI and Delivery Task:
Delivery Task is a Retail Execution object tied to Direct Store Delivery (DSD). While a delivery may involve products that are on promotion, the Delivery Task object itself does not have a direct, core data model relationship with the Promotion object to define or measure the promotion itself. The missing Promotion Product is a fundamental link.

C. Promotion Channel, Retail Visit KPI, Assessment Task Definition and in Store Location:
Assessment Task Definition defines the task template (e.g., a "Promotion Check" task), which may reference a promotion, but it does not represent the direct association of the promotion itself. In Store Location (like an endcap) can be part of the Promotion Channel's scope, but it is not one of the four required distinct links as the others. The fundamental Promotion Product link is missing here.

D. Promotion Product, Retail Store KPI, Delivery Task and in Store Location:
This option incorrectly includes Delivery Task (irrelevant for promotion definition/measurement) and In Store Location (a location master data object). It is missing the crucial Promotion Channel (the scope definer) and Retail Visit KPI (the actual result capturer) from the correct set.

Reference:
Consumer Goods Cloud Data Model Key Objects: Promotion, Promotion Product, Promotion Channel, Retail Store KPI, and Retail Visit KPI relationships for Trade Promotion Management and Retail Execution.

Explanation:
This question tests understanding of the data relationship between execution activities in CGC. An Action Plan is a set of recommended tasks generated for a specific, scheduled store visit. It serves as the visit's agenda. The connection is direct and functional: the Action Plan exists to guide work during that particular Visit, and it is created and accessed within the context of that Visit record.

Correct Option:

B. Visit:
The Action Plan object is directly and primarily connected to the Visit object. It is a child object of Visit, meaning it cannot exist independently. When a rep schedules a Visit, an Action Plan (often from a template) can be generated for it, listing the tasks to be completed during that specific store appointment.

Incorrect Option:

A. Assessment Task:
An Assessment Task is a type of work item (child) that is connected to the Action Plan, not the other way around. The Action Plan contains tasks, including Assessment Tasks. The Action Plan itself is connected to the Visit.

C. Action Plan Template item:
An Action Plan Template Item is a component of an Action Plan Template, which is a master blueprint. Items from a template are copied into a live Action Plan when a Visit is created, but the live Action Plan object is not connected to the template item; it's connected to the Visit.

D. Retail Store:
The Retail Store is connected to the Visit (a visit is to a store). The Action Plan is connected to the Visit, not directly to the Retail Store. The store context is inherited through the Visit.

Reference:
The Consumer Goods Cloud data model shows that the Action Plan object has a master-detail relationship to the Visit object. The Salesforce Help article "Work with Store Visits and Action Plans" confirms that action plans are created and managed within the context of a specific visit.

Explanation:
This question tests knowledge of the specialized, pre-built Lightning components provided by Consumer Goods Cloud for specific assessment types. These components are designed to be added to the record pages of their corresponding task records to provide a tailored user interface for field reps to complete the task. An admin must choose the component that matches the assessment's purpose.

Correct Option:

B. Inventory Check:
The Inventory Check Lightning component is the dedicated component for tasks of the "Inventory Check" assessment type. When added to the task's record page, it provides the optimized interface for reps to count stock levels, view product details, and submit inventory data.

Incorrect Option:

A. In-Store Products Check:
This is not a standard, provided CGC Lightning component for assessment task pages. The standard components are named after the core assessment types: Inventory Check, Planogram Check, Promotion Check, etc.

C. Planogram Check:
The Planogram Check component is used for tasks of the "Planogram Check" assessment type. It provides the interface for taking photos and comparing them to a reference image. It is not the correct component for an Inventory Check task.

D. Promotion Check:
The Promotion Check component is used for tasks of the "Promotion Check" assessment type. It provides the interface for verifying promotional execution details like pricing and display. It is not the correct component for an Inventory Check task.

Reference:
Salesforce Help Article: "Add the Lightning Component for Consumer Goods Cloud Assessment to a Record Page" lists the available assessment components, including c:InventoryCheck, c:PlanogramCheck, and c:PromotionCheck. The admin must select the component that corresponds to the specific assessment task type.

Explanation:
In Salesforce Consumer Goods Cloud, the Sales Manager (also referred to as Field Sales Manager or Retail Execution Manager) is the primary persona responsible for the operational management of retail execution. This includes creating and scheduling store visits, generating action plans, assigning visits to field reps, monitoring daily execution KPIs, coaching reps, and ensuring in-store compliance. The role sits between strategic leadership (Divisional/Category Manager) and actual field execution (Field Rep).

Correct Option:

C. Sales Manager
Owns the day-to-day planning and assignment of visits via Visit Planner and Action Plan Templates.

Creates and assigns in-store tasks (orders, promotions, surveys, assessments).

Monitors real-time execution through dashboards (e.g., Sales Rep Performance, Store Insights) and approves or adjusts field activities.

Incorrect Options:

A. Category Manager
Focuses on strategic assortment, planogram design, promotion planning, and category performance analytics; does not manage daily visit scheduling or task assignment to reps.

B. Divisional Manager
Oversees higher-level regional or divisional P&L, targets, and team performance; typically does not handle granular daily visit creation or task assignment.

D. Store Manager
Represents the retailer (external user), not an internal CG Cloud persona; has no access to create or assign visits in the manufacturer’s org.

Reference:
Salesforce Help: “Consumer Goods Cloud Roles and Personas”

Trailhead module: “Get Started with Consumer Goods Cloud” → User Personas section

Explanation
The Consumer Goods Cloud (CGC) is built on the Salesforce platform, which leverages standard components for common tasks to minimize custom development.

C. The nearby map component on the promotion records page:
This is the correct solution because Salesforce provides a standard Lightning component specifically for displaying places on a map in the context of a record, often referred to as the Nearby Map component or similar functionality. By adding this out-of-the-box component to the Promotion Record Page (using the Lightning App Builder, which is configuration, not custom development), it can dynamically query and display related records—in this case, the associated Retail Stores (via the Promotion Channel object) that are geographically near the Sales Manager's current location or a specified location. This uses built-in features and requires the least amount of custom code.

A. A visual mashup that displays the required map on the promotions page:
A "visual mashup" typically implies integrating an external mapping service or building a custom Visualforce or Aura/LWC component. This involves custom development, which the requirement seeks to minimize.

B. An unmanaged package from the AppExchange modified to meet the requirements:
While using an AppExchange package can reduce the initial build, modifying an unmanaged package still requires deep knowledge and effort, counting as a significant form of custom development or customization.

D. The map component added to the home page:
The home page map component usually displays generic or recently accessed locations, not contextual information tied to a specific promotion record. To show stores running a specific promotion, the map must be on the Promotion Record Page to use the promotion's data as context.

Explanation:
This question evaluates knowledge of the administrative capabilities and characteristics of Action Plan Templates in CGC. These templates are reusable blueprints for recommended tasks during a store visit. Understanding what operations are allowed (like cloning for efficiency) versus what is restricted is key for effective setup and management.

Correct Option:

B. They can be Cloned.
This is accurate. Action Plan Templates can be cloned within Salesforce setup. This is a standard and efficient practice to create a new template based on an existing one, making modifications for a different store group or product line without starting from scratch.

Incorrect Option:

A. They can be associated with Assessment Task Definitions and Component Tasks.
This is inaccurate. Action Plan Templates are associated with Action Plan Template Items. These items define the type of task (e.g., "Inventory Check"), but they are not directly linked to the master Assessment Task Definition object. The definition governs the task's global properties, not its inclusion in a template.

C. They can be deleted.
This is generally inaccurate. Standard Salesforce behavior for master-detail and other critical configuration objects often restricts deletion if the template is in use (e.g., referenced by live Visits or other records). While deletion might be technically possible under specific conditions, it is typically restricted and not a recommended or reliable action, making the statement false in a practical sense.

D. They cannot be setup in the mobile application.
This is inaccurate. Field managers can create and manage Store Action Plan Templates directly from the Consumer Goods Cloud mobile app. This allows for agile, in-field creation of task templates for stores, groups, or in-store locations.

Reference:
Salesforce Help Article: "Create a Store Action Plan Template" confirms the ability to clone templates. The mobile app guide also states that managers can create templates in the app, contradicting option D. Deletion restrictions are a common data integrity feature in Salesforce for template objects.

Explanation:
In Consumer Goods Cloud, the most accurate and real-time way for an Account Manager (or Sales Manager) to see all store visits happening today in their territory, with live status (Not Started, In Progress, Completed), is to use the Visit object as the base for a map layer. Only the Visit object carries the actual visit record with its execution status, date, and assigned rep, enabling dynamic color-coding by status directly on the map.

Correct Option:

D. By creating a map layer using visits as the base object and color code the markers by status
Visit is the only object that has real-time status (Not Started/In Progress/Completed) and exact execution date.

Map layer on Visit object supports dynamic color-coding by Visit Status field out-of-the-box.

Filters can be applied for “Visit Date = TODAY” and territory/account manager ownership, giving a perfect daily execution heat map.

Incorrect Options:

A. By creating a Map Layer using retail store search filters by status and color code the markers by status
Retail Store Search does not natively support color-coding by visit status; it is a search tool, not a map layer with dynamic styling rules.

B. By creating a map layer using accounts as a base object and color code the markers by status
Account object has no visit status field; it would require complex aggregation or formula fields and still would not reflect multiple visits per day accurately.

C. By creating a map layer using retail store as the base object and represent the markers by shape
Retail Store can show the latest or planned visit status via roll-up, but shape (not color) is far less effective for quick status recognition, and it does not handle multiple same-day visits well.

Reference:
Salesforce Help: “Visualize Visits on Maps in Consumer Goods Cloud” → Create Visit-based Map Layers

Trailhead: “Plan and Execute Visits with Consumer Goods Cloud” – Territory Mapping & Visit Status Visualization

CG Cloud Winter ’25–Summer ’26 Release: Enhanced Map Layers on Visit object with status-based styling

Explanation:
The most common reason for a user to be unable to execute core functions in a specialized Salesforce Cloud product like Consumer Goods Cloud (CGC) is missing permissions. Delivery tasks are a specific, high-priority feature of CGC designed for Direct Store Delivery (DSD) and Van Sales scenarios. This functionality is locked down by a specific, dedicated permission set, which must be assigned to the user to grant them the necessary object and field access, as well as the mobile application's specific components and logic for delivery tasks.

Correct Option:

B. The tester did not have the Lightning Direct Store Delivery Permission Set added:
This is the most likely cause. The Lightning Direct Store Delivery Permission Set is the specific package-provided license and permission set that grants users access to the Delivery Task object, the Shipment object, the Product Transfer records, and the necessary components and flows in the mobile app to actually process a delivery, including check-in/out, product adjustments, and signature capture. Without it, the user has no ability to interact with the delivery functionality, causing all related test cases to fail.

Incorrect Option:

A. The tester did not have the Lightning Retail Execution Plus Permission Set added:
This permission set is for general retail execution tasks (like inventory, promotion, and planogram checks) and access to the main mobile features. While necessary for general use, it does not specifically grant the permissions needed for the highly specialized Delivery Task functionality (DSD/Van Sales), which is typically covered by a separate, dedicated permission set.

C. The tester is outside the geofence for the store:
Being outside the geofence usually only prevents a user from checking in or checking out of the Visit, or may limit the ability to see tasks, but it would not typically cause all delivery-related test cases to fail across the board. If the user could see the delivery task but couldn't proceed, geofencing might be a factor, but a total failure suggests a fundamental access issue.

D. The KPIs are too extreme and causing the system to fail:
Key Performance Indicators (KPIs) are primarily used to define targets and capture results for assessment tasks (like Inventory Check). Delivery tasks are focused on physical transactions (transfers, returns, orders, invoicing). Extreme KPIs might cause an Assessment task to fail validation, but they would not prevent a user from accessing or executing the core logic of a Delivery task.

Reference:
Consumer Goods Cloud Direct Store Delivery (DSD) Setup and User Permission Requirements. The DSD functionality requires the specific Lightning Direct Store Delivery permission set (or a custom permission set granting equivalent access) to function

Explanation:
This question addresses a key data modeling decision when integrating a complex ERP product hierarchy into CGC. The goal is to measure share-of-shelf, a KPI based on the physical presence of distinct sellable products on a shelf. The consultant must identify the hierarchy level that corresponds to the granular, unique products that are individually stocked and faced.

Correct Option:

C. Which tier describes stock keeping units (SKU)?
Share-of-shelf is calculated by comparing the facings or linear shelf space of specific, sellable product items. The correct tier is the one containing Stock Keeping Units (SKUs), which are unique identifiers for each distinct product variant (e.g., "Brand X Shampoo, 500ml, Fragrance Y"). This is the level of granularity needed for in-store execution measurements.

Incorrect Option:

A. What tier has data describing the product with?
This is too vague. Many tiers may "describe" a product (e.g., category, brand, sub-brand). The critical factor is not description, but identification of the unique, physical item for shelf measurement.

B. Which tier has the data you trust most?
Data trust is important overall, but it doesn't answer the specific functional need. Even perfectly trusted data at a brand or category level is too aggregated for calculating share-of-shelf for individual products.

D. There is no need to ask a question choose level 7.
Making an arbitrary selection based on hierarchy depth is incorrect. The lowest level (often level 7) is frequently where SKUs reside, but this is not a given. The consultant must determine which tier corresponds to SKUs, not assume it's always the deepest level. The question's phrasing ("determine which tier") requires analysis.

Reference:
Consumer Goods Cloud implementation guides for product hierarchy and integration emphasize mapping the SKU-level data from the ERP to the Product object in Salesforce. Share-of-shelf and facing KPIs are measured at the individual product/SKU level, as these are the items physically placed on store shelves.

Explanation:
Delivery Tasks in Consumer Goods Cloud are created and assigned to field reps (or distributors) via Action Plan Templates that are applied to visits. Sales Managers need specific permissions to create action plans and to work with Direct Store Delivery (DSD) functionality, including the Delivery Task type. The three mandatory setup elements are an Action Plan Template containing a Delivery Task, the DSD-specific permission set, and the core Action Plans permission set.

Correct Options:

A. Create an action plan template with a Delivery Task and assign it to a Visit
Delivery Tasks can only be generated from an Action Plan Template that includes a task of type “Delivery”.

The template is then applied manually or automatically to visits, enabling Sales Managers to push stock to reps’ in-field inventory.

B. Assign the Lightning Direct Store Delivery permissions set to the user
This permission set (Lightning Direct Store Delivery) grants access to Delivery Task object, fields, and related DSD functionality (product transfers, in-field inventory).

Without it, users cannot create or view Delivery Tasks even if Action Plans are enabled.

E. Assign the Action Plans permission set to the Sales Manager
The core “Action Plans” permission set is required for any user to create, edit, or execute Action Plan Templates, which is the only way to generate Delivery Tasks.

Incorrect Options:

C. Define Assessment Indicator Definitions for Delivery task
Assessment Indicators are used only for Assessment Tasks (surveys, audits, asset checks), not for Delivery Tasks. Delivery Tasks use Product Items and quantities, not indicators.

D. Change the Action Plan Type Delivery
There is no “Action Plan Type” field value called Delivery. Action Plan Templates contain individual tasks of type Delivery, but the template itself has no such type.

Reference:
Salesforce Help: “Set Up Delivery Tasks in Consumer Goods Cloud” (Winter ’25–Summer ’26)

Trailhead: “Manage In-Field Inventory with Direct Store Delivery” → Required Permissions section

CG Cloud Administrator Guide: Permission Sets – Lightning Direct Store Delivery & Action Plans (API v60.0+)

Explanation:
Einstein Vision (specifically for Object Detection in Consumer Goods Cloud) relies on a cycle of data, model training, and user access. Before field users can successfully take a photo and get accurate shelf compliance results (e.g., facings, out-of-stock), the consultant must first train the AI model on the client's specific products, ensure the model is high-quality, and then grant the users the necessary permissions to use the feature on their mobile devices.

Correct Option:

A. Build the model to be used and review its quality prior to deployment to support a positive first experience:
This is a crucial step. Consultants must first gather labeled product images, train the Einstein Vision model, and then evaluate its accuracy (e.g., F1 Score, Precision, Recall). Deploying a high-quality model is essential to ensure field users get reliable, useful results from the start, driving adoption and trust in the system.

C. Assign a permission set for users who need to use Einstein to provide access to functionally:
Users must be explicitly granted access to Einstein Vision features, the underlying APIs, and the mobile components via the appropriate Permission Set (e.g., one that includes the necessary custom permissions for Einstein Object Detection or the core Retail Execution Mobile license). Without this, the functionality will not load or execute on the mobile app.

E. Upload a data set for Einstein to leverage for object detection so the system can have a baseline to perform its AI:
The data set is the foundation of the AI model. This involves gathering hundreds or thousands of annotated images (with bounding boxes identifying products/SKUs) and uploading them to the Einstein platform. This data set is what the platform uses to train the model, providing the essential "baseline" knowledge required for accurate product recognition on store shelves.

Incorrect Option:

B. Populate the custom object for Einstein optical character recognition so that the system can have a baseline to perform its AI:
While Einstein does support Optical Character Recognition (OCR), the core function for checking shelf compliance (like facings and share of shelf) is Object Detection, not OCR. Object Detection identifies the product packaging itself, which is what is primarily required for Planogram/Inventory Checks. Setting up OCR is not a required step for the fundamental object detection use case.

D. Upload a suppression data set for known competitor products so Einstein can avoid the detection:
While competitor data might be used in advanced analysis (e.g., calculating share of shelf against competitors), there is no standard requirement to upload a specific "suppression data set" just to avoid detection. The model is typically trained to detect only the client's products, and anything else (including competitor products) is inherently treated as a background object, making this step unnecessary for basic functionality.

Reference:
Salesforce Consumer Goods Cloud Setup Guide: Configuring Retail Execution and Enabling Einstein Object Detection.