AP-205 Practice Questions

The Shipment object is a core component of the Direct Store Delivery (DSD) data model in Consumer Goods Cloud. It represents the collection of products being transported from a van to a retail store, acting as the delivery manifest. While other objects like Delivery Task and Order are involved in the overall process, the Shipment object and its related ShipmentItem records specifically track the inventory being physically delivered, making it central to performing DSD operations.

B. Delivery Task

A Delivery Task is an activity that instructs a rep to perform a delivery; it does not represent the goods being delivered.

C. Order

An Order typically precedes the delivery and represents the customer's request for products, not the physical shipment itself during the DSD process.

D. ProductTransfer

ProductTransfer is used to track inventory movement between locations, such as from a warehouse to a delivery van, not the final delivery to the store.

Salesforce Help. (2023). Direct Store Delivery Data Model. The data model diagram shows Shipment as a central object that links a Delivery to ShipmentItem records, representing the products delivered.

Salesforce Help. (2023). Manage a Delivery. "A shipment record is created for the delivery... The shipment record contains details of the products and the quantity of products to be delivered."

Enterprise Sales Management (ESM) is the Salesforce Industries application suite designed for complex, high-volume B2B quoting scenarios. It leverages server-side, API-driven processing, which is essential for handling quotes with hundreds or thousands of line items, as described in the scenario. This architecture ensures performance and scalability for large enterprise deals, unlike client-side cart solutions that are better suited for smaller, simpler quotes.

B. Advertising Sales Management is a specialized application for the media and advertising industry to sell ad inventory, which is not applicable here.

C. Mobile Subscription Management is typically focused on B2C or small-to-medium business use cases for mobile services, not large-scale B2B connectivity products.

D. Subscriber Lifecycle Management is a broad business concept, whereas Enterprise Sales Management is the specific Salesforce Industries application that addresses the quoting part of this lifecycle.

1. Salesforce Help, Industries CPQ, Choose a Cart UI. "For large B2B quotes that have hundreds or thousands of line items, use the Enterprise Sales Management APIs."

2. Salesforce Help, Industries CPQ, Enterprise Sales Management. "Enterprise Sales Management (ESM) is a set of server-side APIs that enable you to create and manage large, complex quotes and orders for B2B sales."

The Assessment Indicator Definition object is used to establish and define a specific metric or Key Performance Indicator (KPI), such as planogram compliance. This object acts as a template for the KPI, defining its name, data type (e.g., percentage, currency), and category. It also includes a field for a default or standard target value. Therefore, an administrator would establish the fundamental definition and standard expected value for a planogram metric on the Assessment Indicator Definition record.

A. A Retail Store KPI record holds the specific target value for a metric at an individual store, but it does not establish the metric's fundamental definition.

B. The Assessment Task Definition defines an activity to be performed during a visit (e.g., "Check Planogram") and links to the indicator definition, but it does not hold the metric's value.

C. Delivery Tasks are related to product logistics and are not used for defining or tracking in-store execution metrics like planogram compliance.

Salesforce Help, Consumer Goods Cloud Documentation, "Set Up Assessment Indicator Definitions". This document explains that Assessment Indicator Definitions are used to "define the metrics for which you want to capture data during a visit."

Salesforce Developer Guide, "Consumer Goods Cloud Object Reference", AssessmentIndicatorDefinition. The object's field list includes TargetValue, confirming it can hold the expected value at the definition level.

To enable a Sales Manager to create and assign delivery tasks, three core configurations are required. First, the manager needs the "Action Plans" permission set to create and manage the underlying framework (E). Second, for Direct Store Delivery (DSD) functionality, the specific "Lightning Direct Store Delivery" permission set must be assigned to the user (B). Finally, the actual work is defined in an Action Plan Template, which must be created with a "Delivery Task" item. This template is then associated with a visit to generate the specific, assignable tasks for the delivery driver (A).

C. Define Assessment Indicator Definitions for Delivery task: Assessment Indicators are for capturing metrics (e.g., number of facings). A simple delivery task (e.g., drop off goods) does not require them to function.

D. Change the Action Plan Type Delivery: The 'Type' field on an Action Plan is for categorization and reporting. While useful, it is not a mandatory technical step to enable the creation and assignment of delivery tasks.

1. Salesforce Help. (2023). Set Up Direct Store Delivery. This guide explicitly lists "Assign the Lightning Direct Store Delivery permission set to users" as a required setup step.

2. Salesforce Help. (2023). Action Plans in Consumer Goods Cloud. This documentation details the need for the "Action Plans" permission set for users who create Action Plan Templates and Action Plans.

3. Salesforce Help. (2023). Create Action Plan Templates for Visits. This document explains that to generate tasks for a visit, an admin must first create a template and add the required task items, such as a delivery task.

Einstein Visit Recommendations are generated based on a set of configurable rules and data points to suggest the most impactful store visits. A fundamental constraint in this logic is the store's operating hours, which are defined on the Retail Store record. The system will not recommend a visit for a time when the store is closed, ensuring that all suggestions are practical and actionable for the field representative. This is a core part of the recommendation engine's logic to ensure feasibility.

A. Visit Recommendations are automatically generated by recent case activities: Recommendations are based on sales data, store priority, and defined rules, not typically on service-related case activities.

B. Visit Recommendations automatically take into consideration already created visits for the store: While the system does filter out stores with existing visits, this is a de-duplication step rather than a primary rule that generates the recommendation itself.

D. Visit Recommendations can be created using the Next Best Action Strategy: Einstein Visit Recommendations is a distinct feature with its own configuration and logic, separate from the broader Next Best Action/Einstein Next Best Action framework.

1. Salesforce Help. (2023). How Einstein Visit Recommendations Work. This document lists the factors Einstein considers, explicitly stating, "Store’s operating hours" as a key factor.

2. Salesforce Help. (2023). Set Up Einstein Visit Recommendations. Step 4 of the setup process, "Create Recommendation Rules," details how the logic uses store attributes, and the prerequisite section mentions ensuring operating hours are set on retail store records.

The In-Store Location object is the standard, purpose-built feature in Consumer Goods Cloud for defining specific physical locations within a retail store, such as aisles, shelves, or checkout counters. Creating an 'In-Store Location' record named 'Frozen Food Aisle' and associating it with the retail store is the foundational step. This allows inventory check tasks and products to be linked to that specific location, providing clear guidance to the field representative.

B. Create a record type called 'Frozen Food Aisle on the task.

Record types define business processes and page layouts for an object, not a physical location within a store.

C. Create a picklist field called location' to document the Frozen Food Aisle.

While technically possible, this is not the standard or scalable solution. It bypasses the relational data model provided by the In-Store Location object.

D. Nothing as Product2 captures that the product is frozen.

The Product2 object describes the product's attributes, not its specific placement within every individual retail store.

E. Create a record type called 'Frozen Food Aisle' on the retail store.

A record type on the Retail Store object would classify the entire store (e.g., supermarket vs. convenience store), not a section within it.

Salesforce Help. (2023). Manage In-Store Locations. "Create in-store locations such as an aisle, a shelf, or a payment counter to help sales reps easily locate them within a retail store."

Salesforce Help. (2023). Consumer Goods Cloud Data Model. The entity relationship diagram shows In-Store Location as a child object of Retail Store, designed to model the store's layout.

The Retail Store KPI (RetailStoreKpi) object in Consumer Goods Cloud is used to track key performance indicators for stores. The KpiType field on this object defines the data type or category of the metric being measured. According to the official Salesforce documentation, the standard supported picklist values for this field include "Units," "Facing," and "Revenue." These types allow for tracking metrics such as the number of product units on a shelf, the count of product facings for planogram compliance, and the total revenue generated at the store, respectively. "Price" and "Promotion" are not standard values for the KpiType field.

B. "Price" is not a standard KPI Type value. Metrics related to price would typically be captured using the "Currency" KPI Type.

C. "Promotion" is not a standard KPI Type. Promotion compliance might be measured using "Percentage" or "Number" types, but "Promotion" itself is not a type.

Salesforce Help, Consumer Goods Cloud Developer Guide, "RetailStoreKpi". The object's field reference for KpiType lists the standard picklist values, which include 'Units', 'Facing', and 'Revenue'.

Salesforce Help, Consumer Goods Cloud Implementation Guide, "Key Performance Indicators in Consumer Goods Cloud". This guide details the standard KPI types, confirming that Units, Facing, and Revenue are supported values.

Action Plan Templates are designed to standardize repeatable business processes, such as retail store visits. A core function in retail execution is performing various checks. Therefore, a template can be configured to include multiple assessment tasks for checking planogram compliance, on-shelf availability (inventory), and promotion execution at a single store. This allows for comprehensive and consistent data collection during a visit.

A. Action plan templates can have multiple orders and delivery tasks: While possible to create tasks named this, option B describes a more fundamental and standard use case for assessment tasks in CG Cloud.

C. Action plan templates are ready to use after saving: Templates must be set to 'Active' status after being saved before they can be used to generate action plans.

D. Action plan templates are not extensible through Apex: This is incorrect; like most Salesforce objects, Action Plans and their templates can be interacted with and extended via Apex.

1. Salesforce Help. (2023). Create Action Plan Templates. "To make a template available for users, click Activate."

2. Salesforce Trailhead. (2023). Retail Execution in Consumer Goods Cloud. Unit: Manage Field Rep Visits. This module describes the common tasks included in visits, such as inventory, planogram, and promotion checks.

The most efficient design that minimizes configuration is to use a single Orchestration Plan Definition. This plan would contain two separate Orchestration Item Definitions—one for activation and one for deactivation. Each item would have a mutually exclusive condition based on the order item's action (Actionc = 'Add' or Actionc = 'Disconnect'). This approach reuses all common steps in the orchestration plan and isolates only the parts that differ (the callouts), which is a core principle of scalable and maintainable orchestration design.

A: Creating two separate plan definitions is redundant if the overall process is similar, which violates the "minimize unnecessary configurations" requirement.

B: This option illogically combines two separate plans with internal conditions, which is an inefficient and confusing design pattern.

C: A single scenario cannot map multiple actions to different plans; it would require two separate scenario definitions, adding to the configuration.

1. Salesforce Help, Industries Order Management, "Conditionalizing an Orchestration Item Definition". This document explicitly describes setting conditions on orchestration items based on fields from the order item, such as the action.

2. Salesforce Help, Industries Order Management, "Orchestration Plan Definitions". This documentation explains that a plan is a reusable template, and best practice is to make them generic and control logic via conditional items rather than creating many similar plans.

Best-practice catalog modeling follows TM Forum SID: sell a Commercial Product (DSL Internet) that decomposes to a Customer-Facing Service (ADSL/VDSL) and then to a Resource-Facing Service (Copper Pair/Bonded Copper Pair). Bandwidth tiers are product attributes so one SKU covers both 5 Mbps and 50 Mbps. This three-level decomposition enables clear separation of customer offer, service activation, and network resource allocation.

A. Treats the customer offer as a technical product, violating commercial-to-service separation.

B. Uses fields instead of attributes, preventing rule-driven pricing and eligibility.

D. Models all layers as technical products, eliminating the CFS/RFS abstraction.

1. Salesforce Communications Cloud Service Catalog Modeling Best Practices, “Multi-Level Decomposition (Commercial → CFS → RFS),” pp. 8-10, 2022.

2. Salesforce Industries CPQ Admin Guide, “Using Attributes to Represent Variants of a Commercial Product,” p. 14, Winter ’24.