Explanation:

🟢 Correct Option: D. At the energy bar product category level.
Defining the Retail Store KPIs at the energy bar product category level is the most efficient approach. This ensures that the audit is focused on the entire promotion rather than individual products. By grouping all energy bars into a single category, the merchandiser can check for the BOGO promotion's compliance without needing to audit each individual SKU, which significantly reduces the number of records created while still capturing the necessary promotional data.

🔴 Incorrect Option: A. At the energy bar product SKU level.
Defining KPIs at the SKU level would require the merchandiser to audit every single energy bar product individually. Since the promotion applies to all energy bars, this would create an unnecessary number of records, making the audit process very time-consuming and inefficient. It does not align with the goal of minimizing records.

🔴 Incorrect Option: B. At the Alpine brand catalog level.
Auditing at the brand level would be too broad. Alpine might have other products besides energy bars in their catalog that are not part of the BOGO promotion. This would lead to irrelevant data being collected and would not provide a focused audit on the specific promotion, which is the primary goal of the visit.

🔴 Incorrect Option: C. At the custom context field level.
While custom context fields can be used to add detail, they are not a level at which Retail Store KPIs are defined for an audit. KPIs are defined on a data model object, such as a product category, to measure performance. Using a custom context field alone would not provide the necessary structure to group and audit the promotion effectively.

Summary:
Alpine's promotion applies to all energy bars. To ensure an efficient audit and minimize data, the KPIs should be defined at a level that encompasses all promoted products without going into unnecessary detail. Auditing at the product category level (energy bars) achieves this goal perfectly, allowing the merchandiser to check for promotional compliance for the entire group of products with a single set of metrics, thus optimizing the process and reducing the number of records created.

Reference:
Salesforce Official Documentation: Retail Execution KPIs

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:
This is a dynamic configuration requirement: the value of one field (account SLA) should automatically determine the value of a product attribute (TV tier) during sales configuration. In Salesforce Industries CPQ (Communications Cloud), this is achieved through rules that enforce logic during the quoting process.

Correct Option:

B. Advanced Rules
Advanced Rules in Salesforce Industries CPQ are used for complex conditional logic and validations during product configuration. They can:

Read contextual data (like the Account's SLA field).

Set attribute values based on conditions (e.g., "If Account.SLA = 'Gold', then set TV_Tier = 'Gold'").

Execute during the configuration process in real-time.

This directly meets the requirement.

Incorrect Options:

A. Context Rules
Context Rules are used to filter which products or attributes are displayed based on context (e.g., hide/show products for certain customer segments). They control visibility, not automatically set attribute values.

C. Compatibility Rules
Compatibility Rules define which products can or cannot be sold together (e.g., "Product A requires Product B"). They don't set attribute values based on external fields.

D. Attribute Rules
While this sounds plausible, "Attribute Rules" is not a standard primary rule type in Salesforce Industries CPQ. The main rule types are Context, Advanced, Compatibility, and Validation Rules. The functionality described is covered by Advanced Rules.

Reference:
In Salesforce Industries CPQ, Advanced Rules (sometimes called Configuration Rules) are used to implement conditional logic that sets default values, calculates fields, or performs actions based on contextual data (Account, Opportunity, or other product attributes). This is documented in CPQ configuration guides under "Advanced Rules for Product Configuration."

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:

Correct Option

A. Category Insights
This dashboard provides insights into product categories, helping managers and reps track category-level performance across stores. It highlights trends and supports decision-making for category growth strategies.

C. Sales Rep Performance
This dashboard focuses on measuring the effectiveness of field reps. It displays metrics like visits completed, tasks executed, compliance scores, and overall contribution to sales goals.

D. Store Insights
This dashboard gives a store-level view of performance, compliance, and execution. It helps field reps and managers evaluate how each store is performing against KPIs and identify improvement areas.

Incorrect Options

B. Inventory Performance
While inventory is important in retail, this is not one of the native dashboards provided by Tableau CRM for Consumer Goods Cloud. Inventory-related insights may come from custom dashboards but not out-of-the-box.

E. Product Performance
Similar to inventory, product-level dashboards may be built by customizing Tableau CRM, but they are not available as standard, prebuilt dashboards.

Summary:
Tableau CRM for Consumer Goods Cloud includes prebuilt dashboards to help field reps and managers quickly analyze performance. The three dashboards provided natively are Category Insights, Sales Rep Performance, and Store Insights. Other dashboards like inventory and product performance can be created through customization but are not included out-of-the-box.

Reference:
Salesforce Help: Tableau CRM for Consumer Goods Cloud