Free Salesforce Consumer-Goods-Cloud-Accredited-Professional Practice Exam with Questions & Answers | Set: 3

Warehouse agents manually entering router barcode and shipment tracking numbers requires a human task in Order Management. Salesforce best practice:

Use a Manual Task Orchestration Item when human input is required.

Launch an OmniScript to capture structured data, validate inputs, and update Fulfillment data.

Why the others are incorrect:

A (Flow) – Flows are not the recommended UI for OM tasks; OmniScripts provide better control, validations, dynamic forms, and DC/CPQ consistency.

B (Push Event) – Push tasks send tasks to external queues/systems, not internal warehouse agents.

C (Autotask) – Auto Tasks run without human interaction, so cannot capture barcodes manually.

Flow Builder is a scalable and flexible tool for building visit recommendation strategies, allowing for customization and adaptation to meet NTO's specific needs.

Industries Order Management (OM) provides multiple orchestration item types to manage human tasks, system tasks, and external service calls. For field technician data capture, Salesforce recommends manual data capture orchestration items combined with OmniScripts, so technicians enter information directly instead of relaying it verbally—reducing errors and improving data quality.

A Manual Orchestration Item (Option C) creates a human task assigned to a technician and pauses the orchestration until the technician completes the task. This is the exact pattern used when capturing installation details, device identifiers, serial numbers, modem MAC addresses, or activation parameters.

A Push Orchestration Item (Option A) is also applicable when a task must be automatically “pushed” to an external party (like a field technician mobile app). The Push item assigns the work and embeds the OmniScript UI, enabling the technician to directly enter data, ensuring accuracy and eliminating the error-prone phone call process.

Options B and D (Milestone and Callout items) represent automated system tasks and do not support interactive technician data capture.

To link an Action Plan to a Visit record, the first step is to create an Action Plan Template by specifying Visit’ as the target object and publish it. An Action Plan Template is a template that defines the tasks and steps for an action plan. An action plan is a set of tasks that need to be completed for a specific purpose or goal. A visit is an object that represents a scheduled or unscheduled interaction between a field rep and a retail store. By specifying Visit as the target object, the Action Plan Template can be linked to any visit record that matches the criteria defined in the template. By publishing the template, the Action Plan Template becomes available for use. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 25.

Einstein for CG- Visit Recommendations is a feature that uses artificial intelligence to suggest optimal store visits for field reps based on predefined rules and criteria. By adopting this feature with the consumer goods cloud, professionals can focus on their work while having information served to them that will support them in being competitive. For example, they can prioritize the most profitable or strategic stores, avoid unnecessary or redundant visits, and optimize their routes and schedules. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 36.

Salesforce Maps integrated with Consumer Goods Cloud allows the creation of layers of Retail Stores, aiding in geographical and spatial analysis for field operations.

https://help.salesforce.com/s/articleView?id=sf.retail_task_admin_create_assessment_task_record_page.htm &type=5

 Inventory Check is a Lightning component that can be added to a Consumer Goods assessment task record page by an admin. An assessment task is a type of action plan task that allows users to collect data and perform actions related to a retail store. An inventory check is a type of assessment task that allows users to verify the availability and quantity of products in a store. The Inventory Check component displays the products that are associated with the store and allows users to search, scan, and update the product information. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 40.

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.

Quip Documents, Einstein Predictions, and Custom Object Task List are three components that can be added to a new page for the Consumer Goods Cloud mobile application. These components provide additional functionality and information for users in the field. They are:

Quip Documents, which allows users to access and collaborate on Quip documents within the app. Quip documents are cloud-based documents that can include text, images, spreadsheets, charts, and more.

Einstein Predictions, which allows users to see predictions and recommendations from Einstein AI based on their data and actions. For example, users can see predictions for sales revenue, product demand, or visit outcomes.

Custom Object Task List, which allows users to create and complete tasks related to custom objects within the app. Custom objects are objects that are defined and configured to suit specific business needs. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 40-41

Salesforce Communications Cloud includes the Enterprise Product Catalog (EPC), which provides a structured and measurable approach to product lifecycle management. To track and measure time-to-market, Salesforce recommends leveraging the EPC Project framework, which is specifically designed to manage, bundle, and monitor product-related changes—from initial design through testing and deployment.

Option A: Leverage the EPC Project functionality

EPC Projects act as containers for all product modifications, including Product Specifications, Pricing, Rules, Attributes, and Versions. They include timestamps for creation, modification, approval, and deployment. Public Salesforce EPC guidance highlights Projects as the recommended mechanism for governance, visibility, and tracking across the product lifecycle. EPC Projects therefore provide the primary dataset required to calculate time-to-market (TTM).

Option C: Create a Salesforce Report on the EPC Project object

Because EPC Project records store metadata about the start, modification, and completion dates of product work, Salesforce Reports on the EPC Project object allow UC to measure cycle times directly. Using reporting tools, UC can track KPIs such as:

Time from Project creation to approval

Time from design to activation

TTM per product type or product launch initiative

Delays in approval or deployment

Why not B or D?

B (CRM Analytics template) — Salesforce does not provide a predefined "Product Time-To-Market" app template specific to EPC, and TTM cannot be measured solely from analytics without EPC Project metadata.

D (Reporting on Product object) — Product records themselves do not reflect lifecycle timestamps or governance workflows, so they cannot measure TTM accurately.