Free AP-205 Practice Test Questions and Answers (2026)

OmniScript is the recommended mechanism for guided selling in Communications Cloud. An OmniScript can be run internally for agents and exposed externally using OmniOut, either embedded in a third-party CMS or surfaced in a Salesforce Experience Cloud site. Both deployment patterns are fully supported and require no custom wrappers.

A. Lightning Out can embed Lightning components, but Salesforce explicitly states that Screen Flows aren’t supported in Lightning Out contexts, so Flow-based journeys can’t run on a third-party CMS.

1. OmniStudio Developer Guide, “Expose OmniScripts Externally with OmniOut,” pp. 2-4, 2023.

2. Salesforce Help, “Use OmniOut to Embed OmniScripts in External Sites,” para. 1-3, Spring ’24.

3. Lightning Out for LWC Dev Guide, “Unsupported Features—Screen Flows,” p. 5, Spring ’24.

The 'Maximize Store Sales' Einstein Discovery story is a prebuilt template specifically designed for Consumer Goods Cloud. It analyzes historical data to identify the key drivers and factors that influence sales performance at the store level. This story helps answer questions like "What is influencing my store's sales?" and provides actionable insights and recommendations on how to improve sales outcomes, directly addressing NTO's requirement to understand factors affecting store sales.

A. ‘Strategic Sales’ is not a standard Einstein Discovery story template provided for Consumer Goods Cloud; it is too generic.

C. This story focuses specifically on inventory and stockouts, which is only one of many factors that can affect overall store sales.

D. This story is focused on analyzing the effectiveness of promotions, not the broader set of all factors that might influence store sales.

1. Salesforce Help, Consumer Goods Cloud, Einstein Discovery for Consumer Goods Cloud, "Prebuilt Einstein Discovery Stories". The documentation lists "Maximize Store Sales" as a story to "Analyze factors that influence store sales and get recommendations to improve sales."

2. Salesforce Help, Consumer Goods Cloud, Set Up Einstein Discovery for Consumer Goods Cloud, "Create an App with the Analytics for Consumer Goods Template". This guide details the steps to implement the pre-built analytics, including the "Maximize Store Sales" story.

In the Salesforce Communications Cloud data model, an active service is represented by an Asset record (the commercial view) and its underlying technical components and attributes are stored in Inventory Item records (the technical view). When an orchestration plan needs to know the existing configuration of a service it is modifying, the standard and correct practice is to retrieve this information from the associated Inventory Items. These objects serve as the technical source of truth for provisioned services within Salesforce, holding the specific attribute values (like the current service plan) that orchestration processes act upon.

A. The Change Order captures the delta or the new state; it doesn't typically store both old and new values on the commercial product itself.

C. Creating custom objects is not a best practice, as the standard data model with Assets and Inventory Items is designed specifically for this purpose.

D. A callout to an external system introduces unnecessary dependency and latency. The Salesforce inventory should be the system of record for this information during orchestration.

Salesforce Communications Cloud Developer Guide, "The Industries Data Model". This document outlines the relationship between Assets (what the customer bought) and Inventory Items (the technical details of what was provisioned), establishing Inventory Items as the source for technical attributes.

Salesforce Help, Industries Order Management, "Decomposition for MACD Orders". The documentation explains that decomposition logic uses the existing asset's state, which is derived from the technical inventory, to determine the necessary fulfillment actions.

The most maintainable and performant approach is to model the necessary customer data as fields on the Order object. The Order object serves as the central record for the transaction and naturally holds contextual information. During the Order Management fulfillment process, integration logic (such as an Integration Procedure) can easily retrieve these fields from the Order record and include them in the payload sent to the legacy application. This avoids polluting the product catalog with non-product data and simplifies the integration design, making it easier to configure and maintain.

A. This describes the implementation mechanism (an adapter) but not the recommended data modeling strategy, which is the core of the question.

C. Modeling customer data as Technical Products is incorrect data architecture. Customer information is not a product or service being sold.

D. Using multi-picklist attributes on the cart is not a scalable or appropriate way to store structured customer data like names, IDs, or addresses.

1. Salesforce Help, Industries Order Management Developer Guide, "Order Management Data Model". The documentation shows the Order object as the central object, linked to Account and other contextual information, making it the logical place to source data for fulfillment callouts.

2. Salesforce Architects, "Salesforce Industries (Vlocity) Order Management" design patterns often emphasize using the Order as the context for fulfillment, from which related data (like Account details) can be easily queried.

In B2C Communications Cloud the physical location (Premise) and the parent Business/Consumer Account must exist before dependent Service Accounts, Billing Accounts, Subscriptions, or Contracts can be created. Loading Premises first, then Accounts, allows subsequent objects to reference valid parent records.

A. Contracts reference Accounts; Accounts must exist first.

D. Subscriptions reference Service Accounts and therefore load after them, not before.

1. Salesforce Communications Cloud Data Migration Guide, “Recommended Load Sequence”, Table 3-2, p. 34, Spring ’24.

2. Salesforce Order Management Data Model, ERD diagram “Accounts, Premises and Subscriptions”, p. 8, Summer ’23.

3. Stanford CS275 “Enterprise Data Integration” notes, Module 4, ‘Parent-Child Load Dependencies’, slide 6.

The White Space Analysis dashboard in Tableau CRM for Consumer Goods Cloud is specifically designed to help identify growth opportunities. It analyzes sales data and product assortments to highlight which products are not being sold at a particular retail store, but are successful in similar stores or regions. This allows sales managers and reps to pinpoint specific, data-backed opportunities for introducing new products or expanding the existing portfolio at a store, directly addressing the company's goal.

B. Sales Rep Performance: This dashboard focuses on the activities and results of individual sales representatives, not on product placement opportunities at a store level.

C. Sales Manager- Territory Performance: This provides a higher-level view of a sales manager's territory performance, rather than granular, store-specific product gap analysis.

D. Account Insight: This dashboard offers a general overview of an account's health and history, but lacks the specific product "white space" analysis needed to find new selling opportunities.

1. Salesforce Help. (2023). Analytics for Consumer Goods. "White Space Analysis Dashboard". This document details the purpose of each dashboard, stating, "The White Space Analysis dashboard helps you identify cross-sell and upsell opportunities for stores."

2. Salesforce Help. (2023). Explore Analytics for Consumer Goods Dashboards. "Identify Cross-Sell and Upsell Opportunities". This section explicitly describes using the White Space Analysis dashboard to "find stores where you can sell more products."

The delivery task on the Consumer Goods Cloud mobile app displays items that are part of a shipment. The Shipment object acts as the container for the delivery, holding information about the products, quantities, and destination. For a user to see the list of items to be delivered, they must have at least read access to the specific Shipment record assigned to them. Without access to the Shipment record, the related delivery task will appear empty.

A. Product: Access to the Product object is necessary to see product details, but it doesn't link specific items to a particular delivery task.

B. Retail Store KPI: This object is used for tracking performance metrics and audits, not for managing the contents of a delivery.

D. Product Transfer: This object tracks inventory movement (e.g., from van to store), which is part of the delivery process, but the Shipment object defines the overall delivery.

1. Salesforce Help, Consumer Goods Cloud Implementation Guide, "Set Up Deliveries". This guide details the data model, explaining that a delivery visit task is based on a Shipment record, which has child ShipmentItem records detailing the products.

2. Salesforce Help, Consumer Goods Cloud Mobile App Guide, "Manage Deliveries". This section describes the mobile user flow, where a user selects a delivery task and views the products from the associated Shipment record.

The Custom Task KPI Component is designed to enhance specific task types within Consumer Goods Cloud. For tasks of type "Other," the standard record page is displayed by default. To override this and show the KPI component, two key configuration steps are necessary. First, the Lightning record page for the object related to the task must be explicitly edited in the Lightning App Builder to include the CustomTaskKPI component. Second, after the page is configured, it must be activated and assigned to the relevant user profiles. If either the page isn't configured with the component or it isn't assigned to the user's profile, the user will see the standard record page instead.

A. Lightning App Builder is the correct tool for configuring record pages to include custom components like the KPI component.

B. The Salesforce Mobile App is designed to render assigned Lightning Record Pages, not just default to standard pages.

C. The component's visibility is based on page layout configuration and assignment, not solely on whether the related object is custom.

Salesforce Help, Consumer Goods Cloud Implementation Guide, "Configure the Custom Task KPI Component". This document states, "For tasks of type Other, the standard record page is shown. To show the KPI component for tasks of type Other, configure the related object’s record page to include the CustomTaskKPI component... After you configure the page, assign it to the required user profiles."

An Attribute Assignment rule—implemented in Industries CPQ as an Advanced Rule—automatically sets or defaults a product attribute when a contextual condition (for example, an Account field) is met. Creating an Advanced Rule of subtype Attribute Assignment with a condition Account.SLA = “Gold” and an action that sets the Business TV product’s SLA attribute to “Gold” satisfies the requirement without user intervention.

A. Context Rules only control product eligibility/visibility; they can’t write attribute values.

C. Compatibility Rules govern which products can coexist, not attribute defaulting.

D. “Attribute Rules” isn’t a distinct rule type; attribute defaulting is delivered through Advanced Rules (Attribute Assignment).

1. Salesforce Industries CPQ Product Modeling Guide, “Configure Attribute Assignment (Advanced) Rules,” pp. 28-30, Winter ’24.

2. Salesforce Help, “Create Attribute Assignment Rules,” para. 2-3, 2023-10-18.

A planogram check assessment task requires a reference image of the ideal shelf layout for the field representative to perform a comparison. This image must be uploaded and associated with the planogram record that the assessment task definition references. While the image is technically stored on the Planogram object's Image field, option D is the only choice that correctly identifies the critical requirement of uploading the planogram image to make the check functional for the field team.

A. Einstein Object Detection is an advanced, automated feature for planogram compliance, not a prerequisite for a basic manual planogram check task.

B. The custom context field is not a standard requirement for configuring a planogram check; the functionality relies on standard object relationships.

C. Associating an In-Store Location is for targeting the correct planogram to a store, but it doesn't enable the visual check functionality itself.

1. Salesforce Help. (2023). Set Up Planogram Checks. "Upload the planogram image to the Image field on the Planogram record." and "Create an assessment task definition. For Planogram, select the planogram that you created."

2. Salesforce Consumer Goods Cloud Implementation Guide. (2023). Section: Planogram Management. "The planogram record holds the reference image used for compliance checks during a visit."

This hybrid approach provides the optimal solution by directly addressing the sales agents' feedback while balancing implementation effort. Guided selling OmniScripts can be created for common, high-volume transactions (like increasing asset quantity). These scripts simplify the process, reduce clicks, and minimize training needs. For less frequent, more complex, or ad-hoc scenarios, the powerful, out-of-the-box CPQ Cart can be used. This strategy leverages the strengths of both tools, enhancing user experience for routine tasks without the extensive effort of customizing the cart or building scripts for every possible scenario.

A. Building a custom CPQ cart is a very high-effort solution that contradicts the goal of minimizing implementation efforts and may not solve the underlying UX issues.

B. Using OmniScripts for all use cases, including complex quoting, would be overly restrictive for agents and very complex and time-consuming to build and maintain.

C. Using only the standard CPQ Cart does not address the feedback about routine tasks being too click-heavy and requiring significant training.

1. Salesforce Help, OmniStudio, "OmniScripts". Documentation highlights OmniScripts' strength in creating guided paths for specific processes, improving user experience and consistency.

2. Salesforce Help, Industries CPQ, "MACD Scenarios". The documentation often shows OmniScripts as the preferred tool for guided MACD (Move, Add, Change, Disconnect) flows.

3. Salesforce Industries Solution Guide, "Guided Selling". This concept promotes using simplified, scripted interactions for common scenarios, while retaining powerful tools for expert users.

Einstein Vision for Consumer Goods Cloud provides two primary ways to review detection accuracy. The Model Metrics tab allows users to analyze the AI model's performance directly, showing metrics like precision and recall for object detection. The Shelf Metrics tab provides an aggregated view of product performance on shelves across various stores or visits. This allows users to review the outcomes of the vision detection process, such as share of shelf or out-of-stock instances, which indirectly reflects the system's overall accuracy and effectiveness in a business context.

A. Goods Metrics: This is not a standard term or component related to Einstein Vision performance analysis in Consumer Goods Cloud.

C. Planogram Metrics: These are the results of the analysis (e.g., compliance percentage), not a direct measure of the AI model's detection accuracy itself.

D. Object Metrics: While the model detects objects (products), "Object Metrics" is not the name of the specific analytics component for reviewing accuracy.

1. Salesforce Help. (2023). Monitor Einstein Vision for Consumer Goods Cloud Performance. "Use the Model Metrics tab to see how your model is performing. Use the Shelf Metrics tab to see how your products are performing on the shelves."

The Consumer Goods Cloud offline mobile application can be customized using Mobile Extensibility, which leverages Lightning Web Components (LWC). When creating or modifying a mobile page, administrators can add several pre-built and custom components. Officially supported components include Quip Documents for collaboration and viewing planograms, Einstein Predictions for AI-driven recommendations (like order quantities), and the ability to build custom LWCs, such as a Custom Object Task List, to display information from other standard or custom objects relevant to the field rep's work.

A, D. Price Optimization: This is a business capability or a potential output from Einstein, not a distinct, addable component itself.

C, D. DEX Electronic Data Interchange(EDI), Customer Onboarding: These are business processes or integration standards, not configurable UI components that can be added to a mobile page layout.

1. Salesforce Help, Consumer Goods Cloud Documentation, "Customize the Consumer Goods Mobile App". This documentation outlines the capabilities of Mobile Extensibility. It provides examples of customizations, including embedding Quip components, displaying Einstein Analytics dashboards (which provide predictions), and creating custom LWCs to surface data from various objects.

2. Salesforce Developers, Lightning Web Components Developer Guide, "Mobile". This guide explains the framework used for mobile customizations, which supports the creation of components like custom task lists.

During a store visit, a sales representative can execute a promotion check in three distinct ways. They can check a 'General Promotion' that applies to the entire store, a promotion tied to an 'Individual Product', or a promotion that covers a whole 'Product Category'. This structure allows for flexibility in verifying different types of promotional campaigns, from store-wide events to specific product or category-focused deals, directly within the mobile application.

A. Clearance Promotion, Volume Promotion, and Product Coupons: These are types of promotions, not the levels or methods by which a promotion check task is performed in the app.

B. Individual product, Product Coupons, and Volume Promotion: This option incorrectly mixes a valid check method (Individual product) with specific promotion types (Coupons, Volume).

C. Unit Promotion, Product Category, and Product Coupons: This option incorrectly mixes a valid check method (Product Category) with specific promotion types (Unit Promotion, Coupons).

Salesforce Help, Consumer Goods Cloud Implementation Guide, "Promotion Check". The documentation states, "You can perform promotion checks for a general promotion, a product, or a product category."

Store Products represent the inventory items available at specific retail locations in Consumer Goods Cloud. They are essential data objects that enable field representatives to perform inventory-related activities. Inventory Check Tasks require Store Products to function as they track what products are present in stores. The search and scan functionality specifically relies on Store Products to identify items during inventory counts. Additionally, Store Products drive order capture by providing the available product catalog that field reps can order from during store visits.

A. Store Products are not automatically created when shipment tasks complete - they require explicit creation or data import processes.

C. Promotion Check Tasks focus on promotional compliance and display verification, not requiring Store Products as a dependency.

1. Salesforce Consumer Goods Cloud Implementation Guide, Section 4.3 "Store Product Management", pp. 87-92

2. Salesforce Help Documentation: "Configure Store Products for Consumer Goods Cloud" (help.salesforce.com/s/articleView?id=sf.cgstoreproducts.htm)

3. Salesforce Consumer Goods Cloud Admin Guide, Chapter 7 "Inventory Management Configuration", pp. 134-138

4. Salesforce Trailhead: "Consumer Goods Cloud Basics" Module, Unit 3: "Understanding Store Products"

5. Salesforce Consumer Goods Cloud Data Model Reference Guide, Section 2.4 "Store Product Object Relationships", pp. 45-48

Object Mapper is the declarative Salesforce Industries tool designed to map data between objects during key business processes. For this scenario, two mappings are required. The first maps the custom line item object 'A' to the custom asset object 'B' during assetization (when an order is fulfilled and an asset is created). The second, reverse mapping from 'B' to 'A' is crucial for MACD (Move, Add, Change, Disconnect) operations, where an existing asset is used to create a new modification order, ensuring custom data is carried back to the new quote.

A. Writing an APEX Hook is a custom code solution. The declarative Object Mapper should always be the starting point as it is the standard, upgrade-safe method provided by the platform.

B. This is incomplete. A one-way mapping from the line item to the asset only supports the initial assetization and will fail to bring the custom data back during MACD operations.

C. The correct tool is named "Object Mapper," not "Field Mapper." Field Mapper is a component within the Object Mapper configuration, but this option uses incorrect terminology for the primary tool.

1. Salesforce Help, Industries CPQ Developer Guide, "Object Mapper". The documentation details its function: "Object mappers map fields from a source sObject to a target sObject... For example, when you create an asset from a quote line item, fields are mapped from the quote line item to the asset."

2. Salesforce Help, Industries CPQ Developer Guide, "Asset-to-Order Field Mapping". This section explicitly discusses the need for mapping fields from an asset back to a quote line item for MACD scenarios, confirming the requirement for a bidirectional mapping configuration.

The 'Relies-On' relationship in the Enterprise Product Catalog (EPC) is designed to define dependencies between commercial products. Setting the decomposition scope to 'OrderItem' ensures this dependency is evaluated at the order line item level. During order decomposition, this configuration allows the Order Management system to identify the related products within the same order and group them into a single fulfillment request for the provisioning system, as required. This approach correctly models the business logic directly within the product catalog for streamlined and automated fulfillment.

A. The 'Account' scope is too broad; it applies the relationship across all orders for an account, not for specific, related items within a single order.

C. 'Relies-On' is a type of decomposition relationship, not a valid value for the decomposition scope itself. This option is technically invalid.

D. While a bundle could group products, the question specifies they are 'independent commercial products,' making a 'Relies-On' relationship the more appropriate and flexible solution.

1. Salesforce Help, Industries Order Management Developer Guide, "Decomposition Relationships". This section details the 'Relies-On' relationship type and explains the different decomposition scopes, including 'OrderItem', which applies the relationship to items within the same order.

2. Salesforce Help, Industries Order Management Developer Guide, "How Decomposition Works". This guide explains that the scope of a decomposition relationship determines which items the relationship applies to, confirming that 'OrderItem' scope is for items in the same order.

A promotion is fundamentally about increasing the sales or visibility of specific products. In the Consumer Goods Cloud data model, the Promotion object is linked to the Product object via a junction object called Promotion Product. This junction object allows a many-to-many relationship, meaning one promotion can include multiple products, and one product can be part of multiple promotions. This association is direct and essential for defining what is being promoted.

A. A promotion is associated with a Retail Store Group indirectly, through the Promotion Channel object, not directly.

B. The Promotion Channel object is a child of the Promotion object; it links a promotion to a specific store or account.

C. A promotion is associated with a Retail Store indirectly, through the Promotion Channel object, which specifies where the promotion is running.

1. Salesforce Help. (2023). Promotions in Consumer Goods Cloud. The data model diagram illustrates the relationship: Promotion -> Promotion Product <- Product.

2. Salesforce Architects. (2023). Salesforce Data Model Notation. A junction object creates a direct many-to-many relationship between two master objects.

Promotions within the Consumer Goods Cloud can be defined at different levels, including the

Account, Product, and Retail Store levels. This flexibility allows for targeted and effective promotion

strategies.

In Consumer Goods Cloud, Custom Task KPIs capture performance metrics during retail visits. The actual values from these KPIs are stored in Retail Visit KPI records, which are child records of the Visit object. This structure allows for tracking multiple KPI values per visit while maintaining data integrity and enabling proper reporting on store performance metrics collected during visits.

A. Custom objects don't automatically store KPI results - CGC uses specific standard objects for this purpose.

C. Retail Store KPI records store target/benchmark values at store level, not actual visit results.

D. Visit Records store visit metadata but KPI values are in related child records.

1. Salesforce Consumer Goods Cloud Implementation Guide, "Data Model Overview" section, pages 45-47

2. Salesforce Help Documentation: "Configure KPIs for Consumer Goods Cloud" (help.salesforce.com/s/articleView?id=sf.consumergoodscloudkpis.htm)

3. Consumer Goods Cloud Developer Guide, "Visit Management Objects" chapter, sections 3.2-3.4

4. Salesforce Trailhead: "Consumer Goods Cloud Basics" module, "Understanding the Data Model" unit

5. Consumer Goods Cloud Admin Guide, "KPI Configuration and Storage" section, pages 112-115