CONSUMER-GOODS-CLOUD-ACCREDITED-PROFESSIONAL Practice Questions

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.

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.

During a promotion check task, a field representative's primary goal is to verify the execution and compliance of a promotion at a retail store. The Consumer Goods Cloud mobile application provides standard capabilities to support this. The rep can view a list of all products included in the promotion to ensure they are correctly displayed and available. Additionally, the application allows the rep to capture photos of the promotion display, which serves as visual evidence of compliance or non-compliance. These two functions are fundamental to the in-store auditing process for promotions.

B. Marking the promotion as complete: A promotion check is a single task during a visit; it does not alter the status of the overall promotion, which may run for weeks or months.

D. Changing the promotion planning dates: Modifying promotion dates is a strategic planning function typically performed by a Key Account Manager or planner, not a field rep during execution.

E. Changing the discounts on the products included in the promotion: Altering financial details like discounts is a back-office planning and management function, not a capability available to a field rep in the store.

1. Salesforce Help, Consumer Goods Cloud Documentation, "Execute a Promotion Check": This document explicitly states the process for a field rep. It notes, "On the Promotion Check page, you can see the promotion description, the products included in the promotion, and the promotion channel." It also instructs, "To capture an image of the promotion, tap [the camera icon]." This directly supports answers A and C.

2. Salesforce Trailhead, "Visit Execution in Consumer Goods Cloud" module, "Perform In-Store Audits" unit: This educational module describes the role of a field rep. In the context of a promotion check, it details the rep's actions: "...he checks whether the NTO branding is visible, the discounted price is correct, and the products are placed on the correct shelves. He also takes a picture of the promotion display." This confirms the ability to view product details (to check placement) and take photos.

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.

In Salesforce Consumer Goods Cloud, Key Performance Indicators (KPIs) are used to measure performance. To track the performance of specific locations within a store, such as end caps, the standard approach is to define a distinct set of KPIs for that location type. This is achieved by creating Retail Store KPI records and associating them with an In-Store Location Category (e.g., "End Cap"). This allows the business to define targeted metrics like "End Cap Planogram Compliance" or "Share of Shelf on End Cap" and assign specific assessment tasks to field reps for data capture only at those locations, enabling precise performance analysis.

A. Make a Custom object for In-Store location on the Retail Store Object to capture KPIs

This is incorrect because Consumer Goods Cloud provides a standard In-Store Location object designed specifically for this purpose. Creating a custom object is redundant and deviates from best practices.

B. Make In-Store locations as a record type on the Retail Store Object to capture the KPIs

This is architecturally incorrect. An in-store location is a component within a retail store, not a type of retail store. The In-Store Location object has a lookup relationship to the Retail Store object.

C. Make In-Store Locations as a record page on the In-Store Location Object to capture the KPIs

A record page is a user interface component used for displaying data. It is not the mechanism for defining or capturing the underlying KPI data, which is handled by objects like Retail Store KPI and Assessment Task.

---

1. Salesforce Help Documentation: Key Performance Indicators in Consumer Goods Cloud. This document explicitly states the capability to link KPIs to specific location types: "You can associate a retail store KPI with an in-store location category, a retail store group, or an account." This directly supports creating a specific set of KPIs for the "end cap" category.

Source: Salesforce Help, Consumer Goods Cloud, "Key Performance Indicators in Consumer Goods Cloud".

2. Salesforce Help Documentation: Set Up In-Store Locations. This guide confirms that "end cap" is a standard use case for the In-Store Location object. "For example, you can create in-store locations, such as aisle, shelf, and end cap." This invalidates the need for custom objects (Option A) or incorrect modeling (Option B).

Source: Salesforce Help, Consumer Goods Cloud, "Set Up In-Store Locations".

3. Salesforce Help Documentation: Create an In-Store Location Category. This document details the object used to group in-store locations. "Create in-store location categories to group in-store locations. For example, you can group shelves, end caps, and checkout counters." This is the foundational step for associating specific KPIs with all end caps.

Source: Salesforce Help, Consumer Goods Cloud, "Create an In-Store Location Category".

In Salesforce Consumer Goods Cloud, a Retail Store KPI defined at the product level becomes associated with a specific Retail Store through an Assortment. An Assortment acts as the crucial link, representing a list of products that are expected to be sold or stocked at a particular store or group of stores. For the system to apply a product-specific KPI (like an inventory check) to a store, it must first establish that the product is relevant to that store. Assigning the product to an Assortment, which is then assigned to the Retail Store, creates this necessary relationship.

A. The product needs to be linked to a Product Category. Linking a product to a category is for classification and allows for category-level KPIs, but it does not link a product-level KPI to a specific store.

C. The product needs to be linked to a Promotion. A promotion is a temporary sales activity. While it involves products and stores, it is not the standard mechanism for defining the core product list for which ongoing KPIs are measured.

D. The product needs to be linked to a Retail Store. The standard and scalable method to manage the relationship between many products and many stores is through Assortments, not by creating direct, individual links for each product to each store.

1. Salesforce Help, Consumer Goods Cloud Implementation Guide, "Assortments in Consumer Goods Cloud": This document explicitly states, "An assortment is a list of products that are targeted for a specific store or a store group." This establishes the Assortment as the object that links products to stores.

2. Salesforce Help, Consumer Goods Cloud Implementation Guide, "Set Up Assortments": This guide outlines the required process: "To set up an assortment, create an assortment, associate products with the assortment, and then associate the assortment with stores." This confirms that linking a product to an assortment is a prerequisite for linking it to a store.

3. Salesforce Help, Consumer Goods Cloud Implementation Guide, "Retail Store KPIs": This section details how KPIs are defined. For a product-level KPI to be calculated during a visit, the product must be part of the store's defined product list, which is managed via Assortments. The system uses the store's assortment to determine which product-level KPIs are applicable.

In Salesforce Consumer Goods Cloud, the Assessment Indicator Definition object is used to define the specific metrics or questions that a field representative will answer during a retail execution task. For a planogram check, an administrator would create indicator definitions for each metric being measured (e.g., "Share of Shelf," "Number of Facings," "On-Shelf Availability"). The expected or target value for each of these metrics is established within its corresponding Assessment Indicator Definition record. This allows the system to compare the actual value captured during the visit against the predefined expected value.

A. Retail Store KPI: This object tracks the actual performance of a Key Performance Indicator for a specific retail store over time, rather than defining the expected value for a task metric.

B. Assessment Task Definition: This object defines the overall task (e.g., "Planogram Check") but does not contain the specific, individual metrics or their expected values. It acts as a container for Assessment Indicator Definitions.

C. Delivery Tasks: This is related to the logistics and delivery of products to a store and is not used for defining in-store execution metrics like planogram compliance.

1. Salesforce Help Documentation - Set Up Retail Execution: "Create Assessment Indicator Definitions. Assessment indicator definitions are the individual metrics that you want to capture as part of a task... For example, for a promotion check task, you can create assessment indicator definitions for these questions: Is the promotion active? What's the in-store price of the promoted product?" This establishes that metrics are defined at this level. The expected value is a core component of this definition.

Source: Salesforce Help, Consumer Goods Cloud, "Create Assessment Indicator Definitions".

2. Salesforce Help Documentation - Assessment Indicator Definition Fields: The fields within the AssessmentIndicatorDefinition object, such as TargetDecimal, TargetInteger, TargetText, and TargetBoolean, are specifically designed to hold the expected or target values for the metric being defined.

Source: Salesforce Developer Guide, Object Reference for the Salesforce Platform, "AssessmentIndicatorDefinition".

3. Salesforce Help Documentation - Retail Execution Data Model: The official data model shows that an AssessmentTaskDefinition (the task) is a parent to one or more AssessmentIndicatorDefinition records (the metrics). This hierarchical relationship confirms that the specific metrics and their expected values are defined at the indicator level, which then roll up into a task.

Source: Salesforce Help, Consumer Goods Cloud, "Retail Execution Data Model".

The performance of the Einstein Object Detection model is reviewed by analyzing its output, which is stored in the RetailVisitDetectedObject. Each time an image is processed, the model creates records in this object detailing the products it identified and their counts. Administrators can create reports, dashboards, and list views on the "Detected Objects" to compare the model's predictions against actual shelf conditions or manually entered data. This analysis provides direct, granular insight into the model's accuracy and effectiveness in real-world scenarios.

A. By creating a Custom Object: This is incorrect because Salesforce provides a standard object, RetailVisitDetectedObject, specifically for storing the model's results. Creating a custom object is unnecessary.

B. By enabling Custom Object Detection: This is a one-time setup step required to use the feature. It is not a method for monitoring or reviewing the model's ongoing performance.

D. Through Einstein Bots: This is incorrect as Einstein Bots are a separate conversational AI product used for customer service automation and are not related to image analysis or object detection.

1. Salesforce Help, Consumer Goods Cloud, Einstein Object Detection: "When a field rep uploads an image of a shelf, Einstein Object Detection identifies products, counts them, and checks planogram compliance. The results are saved to the RetailVisitDetectedObject." This confirms that the object stores the direct output needed for performance review.

2. Salesforce Help, Consumer Goods Cloud, Set Up Einstein Object Detection: This documentation outlines the setup process, which is distinct from performance monitoring. It details the permissions required to access objects like RetailVisitDetectedObject, implicitly confirming its role in the process.

3. Salesforce Developer Documentation, RetailVisitDetectedObject: The object reference for RetailVisitDetectedObject describes its fields, such as DetectedCount and ProductName, which are the core data points an administrator would use to build reports and analyze the model's performance.

The optimal user experience on a tablet, which has a larger screen, is to leverage a two-column layout. This allows the field rep to view their primary tasks (the visit list) and monitor team messages simultaneously without navigating away or switching context. This design minimizes clicks and interruptions, directly addressing the need to monitor communications while actively working through daily tasks. This solution is both efficient and user-friendly, making the best use of the tablet's form factor.

A. Navigating to a separate Chatter page disrupts the user's workflow, forcing them to leave their task list. This is inefficient and not an optimal experience for continuous monitoring.

C. This option addresses sending messages (creating a note), not the primary requirement of monitoring incoming team messages from the entire team.

D. Constant notifications for every message can be highly disruptive and overwhelming, leading to a poor user experience. They don't provide a consolidated view for monitoring conversation history.

1. Salesforce Consumer Goods Cloud Developer Guide, "Extend the Consumer Goods Mobile App": This guide details how developers can use Lightning Web Components (LWCs) to create custom user interfaces. A two-column layout is a standard responsive design pattern achievable with LWCs to optimize the experience on larger screens like tablets.

2. Lightning Web Components Developer Guide, "Create Responsive Layouts with lightning-layout": The lightning-layout component is the official tool for building responsive UIs. Its small-device-size, medium-device-size, and large-device-size attributes are used to create multi-column layouts that adapt specifically to different form factors, such as tablets.

3. Salesforce Consumer Goods Cloud Implementation Guide, "Set Up the Consumer Goods App": This guide emphasizes configuring the application to enhance field rep productivity. A solution that allows simultaneous task management and communication aligns directly with this core implementation principle of optimizing field execution.

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.