Explanation:
The core requirement is that Industries OM must react to specific external milestones to progress an order. The challenge is to design an efficient, reliable, and governor-limit-aware orchestration flow. The solution must ensure only relevant milestones trigger OM workflows, avoid unnecessary processing, and clearly define the integration touchpoint (Push Events).

Correct Option:

A. Advise the intermediate layer to filter out only Industries OM relevant milestones to be forwarded to Communications Cloud. Implement a Push Event for each milestone to progress the order in the orchestration flow.
This is the most robust and scalable approach. It involves:

Filtering at the integration layer: The middleware or network provisioning system should send only milestones relevant to OM, reducing noise and unnecessary API calls to Salesforce.

Using Push Events: Salesforce OM uses Push Events (part of the Orchestration Plan) as the designated trigger to advance order stages based on external system input. This is the declarative, out-of-the-box mechanism for handling such external milestones.

Incorrect Options:

B. Configure a Push Event for Industries OM relevant milestones. Irrelevant milestones will not trigger the orchestration plan to progress so it will not count against governor limits.
This is partially correct in using Push Events but critically flawed. Even if an irrelevant milestone doesn't progress the plan, the Push Event itself is still invoked, consuming a platform event delivery and processing resources. This wastes governor limits and adds unnecessary load. Pre-filtering (as in Option A) is essential.

C. Configure a Push Event for each milestone from the network provisioning platform; this will allow a Sales representative to monitor order progress in the orchestration plan.
This sends all milestones, which is inefficient and violates best practices. While sales reps can monitor progress, this should be achieved by logging only relevant milestones. Sending every low-level network milestone would bloat the system, hit governor limits, and create a confusing activity log.

D. Configure an integration procedure to process each milestone and change the order status according to the milestone value. Let the integration procedure change the order status, this in turn will trigger out-of-the-box implementation that progresses the orchestration plan to the next stage.
This bypasses the designed Orchestration Plan and Push Event framework. Manually changing order status via an integration procedure is a custom, fragile approach that may not correctly trigger downstream order actions or honor OM's business logic. It defeats the purpose of using the orchestration engine.

Reference:
This design follows Salesforce Industries (Communications Cloud) implementation best practices for Order Orchestration. The Orchestration Plan uses Push Events as the canonical way for external systems to signal milestone completion. Documentation emphasizes filtering events at the source or middleware to ensure only relevant events are sent, optimizing performance and respecting platform limits.

Explanation:

Correct Option:

C. ✅ Through Detected Objects
The Detected Objects tab is the central place to review all results from the Object Detection model. Admins can view the images processed, see what objects were detected (e.g., products, shelves), and assess the model's accuracy by checking the confidence scores and validating or correcting the results, which helps improve the model.

Incorrect Option:

A. ❌ By creating a Custom Object
Creating a custom object is a general Salesforce administration task for storing custom data. It is not a specific feature or method provided for reviewing the performance and output of the pre-built Object Detection model in Consumer Goods Cloud.

B. ❌ By enabling Custom Object Detection
Enabling the feature is a prerequisite for using it, but it is not the method for reviewing its performance. The review and analysis happen after enabling it, within the specific interfaces designed for the results, like the Detected Objects related list.

D. ❌ Through Einstein Bots
Einstein Bots are for building conversational AI chatbots primarily in Service Cloud. This functionality is separate from the image-based Object Detection model used for identifying products on shelves in Consumer Goods Cloud.

➡️ Summary:
This question tests knowledge of where to find AI model outputs. After the Object Detection model processes images from field reps, its performance and results are reviewed and managed directly through the records on the Detected Objects tab.

Explanation:
When building custom pages in the Consumer Goods Cloud mobile app using the CG Mobile Designer (Lightning App Builder for mobile), administrators can add specific CG-supported Lightning components to the Visit and Retail Store pages. As of the current release, the officially supported and natively available components for CG Mobile custom pages are Quip Documents, Einstein Predictions, and Custom Object Task List. These components are explicitly listed in the CG Mobile Designer component panel

Correct Option:

B. Quip Documents, Einstein Predictions, and Custom Object Task List

Quip Documents: Allows reps to view and edit live Quip docs (e.g., planograms, sell sheets) directly in the mobile visit.

Einstein Predictions: Displays AI-driven recommendations such as next best action or no-visit predictions on the visit record.

Custom Object Task List: Enables display of tasks from custom objects related to the visit or store (e.g., maintenance tasks, competitor tasks).

Incorrect Options:

A. Quip Documents, Einstein Predictions, and Price Optimization
Price Optimization is not an available Lightning component in CG Mobile Designer; pricing analytics exist in Tableau CRM but cannot be embedded as a component on mobile pages.

C. DEX Electronic Data Interchange (EDI), Custom Object Task List, and Customer Onboarding
DEX (Data Exchange) and EDI are back-end integration features, not mobile page components. Customer Onboarding is not a component in CG Mobile.

D. DEX Electronic Data Interchange (EDI), Price Optimization, and Customer Onboarding
None of these three are actual Lightning components available in the Consumer Goods Mobile Designer palette.

Reference:
Salesforce Help: “Customize Consumer Goods Mobile Pages” → Available Components section (Winter ’25 & Spring ’26 releases)

Trailhead: “Extend Consumer Goods Cloud Mobile Experience” – CG Mobile Designer component list

CG Cloud Release Notes (v16.0+): Supported Lightning components for CG Mobile

Explanation:
This question tests knowledge of the purpose and data focus of different pre-built Tableau CRM dashboards in CGC. A Field Sales Manager needs to analyze store-level execution metrics (KPIs like Facing, Share of Shelf, etc.) to identify underperforming locations. The correct dashboard must aggregate and visualize these specific Retail Store KPI trends at the store level.

Correct Option:

A. Store Performance Dashboard:
This dashboard is specifically designed to analyze the performance of individual retail stores. It visualizes key Retail Execution KPIs (e.g., Planogram Compliance, Out-of-Stock) over time, allowing a manager to easily spot trends, compare stores, and identify which ones have a decline in KPIs and thus need attention.

Incorrect Option:

B. Team Performance Dashboard:
This dashboard focuses on the productivity and activity metrics of the field team members or reps (e.g., visits completed, tasks per day). It is used to manage rep performance, not to diagnose store-level KPI problems.

C. Lost Visit Store Performance Dashboard:
This dashboard analyzes the impact of missed store visits (Lost Visits) on sales and KPIs. While it involves store data, its primary lens is understanding the consequence of visit coverage gaps, not providing a general analysis of all stores' KPI trends.

D. Product Performance Dashboard:
This dashboard focuses on the performance of products across stores or regions (e.g., sales velocity, distribution). It is used for brand or category management, not for assessing the execution health of specific retail store locations.

Reference:
The Consumer Goods Cloud Tableau CRM dashboard descriptions identify the Store Performance Dashboard as the tool for managers to monitor and compare store-level execution metrics and compliance over time, directly fulfilling the need to identify stores with declining KPIs.

Explanation:
The Retail Store KPI object is used in Consumer Goods Cloud to define targets for assessment metrics that field reps must measure during store visits. When creating a record to set an expected value (a target) for an Inventory Check task, you must define what is being measured and where that measurement applies. The system generally requires KPIs to be defined at a group level to efficiently cascade targets across multiple similar stores, making the Retail Store Group mandatory. The Assessment Indicator Definition defines the specific metric being tracked (e.g., "Inventory Count"), making it the second core requirement.

Correct Option:

A. Retail Store Group:
This field is a required lookup on the Retail Store KPI object. In CGC, Key Performance Indicators are generally not defined for a single store, but rather for a group of stores that share characteristics (e.g., store size, format). This allows for efficient target setting and management across the entire chain.

D. Assessment Indicator Definition:
This is also a required lookup field. It links the KPI record to the specific metric template being measured (e.g., 'Out of Stock', 'Facing', or 'Inventory'). For an Inventory Check, the relevant Assessment Indicator Definition (AID) is selected here to define the exact metric that the target value relates to.

Incorrect Option:

B. Custom Context:
This field is a lookup used only when associating an Assessment Indicator Definition with a Custom Object for a custom task. It is not required for standard tasks like Inventory Check, which relies on standard product and store master data relationships.

C. Inventory Count:
This is not a standard field on the Retail Store KPI object itself. Instead, the desired inventory value (the target) is stored in a generic target value field on the object, such as TargetIntegerValue__c or TargetDecimalValue__c, depending on the data type defined by the Assessment Indicator Definition.

E. KPI Type:
The Retail Store KPI object does have a picklist field for KPI Type (e.g., Facing, Inventory, Price), but this is technically an attribute defined by or closely related to the Assessment Indicator Definition (Option D), which is the required lookup. The system requires the lookup to the AID which implicitly contains the KPI Type information, rather than requiring the picklist field directly for the record to be created for an inventory check.

Reference:
Consumer Goods Cloud Data Model: Retail Store KPI object field requirements and object creation prerequisites, particularly the necessity of associating a KPI with both an Assessment Indicator Definition (what is measured) and a Retail Store Group (where it is measured).