Salesforce Consumer Goods Cloud Accredited Professional (AP-204)

https://help.salesforce.com/s/articleView?id=sf.retail_task_admin_create_assessment_task_record_page.htm&type=5InventoryCheckisaLightningcomponentthatcanbeaddedtoaConsumerGoodsassessmenttaskrecordpagebyanadmin.
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.
References:
[Salesforce Consumer Goods Cloud Implementation Guide], page 40.

The Retail Execution Lightning Plus permission set enables end-users to access and leverage the Einstein Visit Recommendation feature in Consumer Goods Cloud, enhancing visit planning and optimization.

To visualize store visits in their territory for the day by their current status, an Account Manager can create a map layer using visits as the base object and color code the markers by status. A map layer is a visual representation of data on a map that can be filtered and customized. A visit is an object that represents a scheduled or unscheduled interaction between a field rep and a retail store. The status of a visit indicates whether it is planned, in progress, completed, or canceled. Verified References:
[Salesforce Consumer Goods Cloud Implementation Guide], page 34.

The requirement is to introduce a limited-time offer that is available on the website (digital channel/DC APIs) and, once claimed, grants a 10% discount for three months. This is the definition of a Promotion that uses a Time Plan to define the duration of the discount.
Promotion (A):
In Salesforce Industries CPQ, a Promotion is the container entity used to define a marketing offer that modifies the price of a product (in this case, a 10% discount). The Promotion entity is what is typically exposed to digital channels (like the website via DC APIs) for customers to claim or qualify for. The search results confirm that Promotions are used to "apply temporary changes to product pricing, bundles, and product structure".
Time Plan (B):
The Time Plan is a sub-feature of Promotions (or Price Lists) that defines the duration for which the commercial change (the 10% discount) is active. The requirement states the discount is only for "three months." A Time Plan is specifically configured to start the discount upon activation and automatically end it after the defined period (3 months), ensuring the billing system correctly handles the price change back to the original rate. D (Discount) is a result of the configuration, not the feature itself. The discount value (10%) is defined within the promotion.

C (Offering) is a synonym often used for a product or bundle, but it does not specify the limited-time discount mechanism required.

Assetization is the process in Salesforce Industries (Communications/Consumer Goods) where a successfully fulfilled order line item is converted into a permanent Asset record. This Asset record serves as the single source of truth for what the customer currently owns. A Consultant should recommend assetization for a commercial product or service when it is likely to be involved in future customer management and transactions. The three main factors that necessitate creating an Asset record are: The product/service sold has a recurring charge (B): A recurring charge means the service/product will be billed repeatedly (e.g., monthly). To ensure the billing system receives the correct information and to manage any future pricing changes (like applying a promotional discount for a specific period), the service must exist as a persistent Asset record. Billing systems typically interface with the Asset/Subscription object to determine what to invoice each cycle. The product/service sold can undergo future attribute changes (C): The core purpose of the Move, Add, Change, Delete (MACD) process is to allow customers to modify their existing services. If a product attribute (e.g., Internet speed, color of a device, service plan) can be changed, the system needs an Asset record to track the current attribute values (the "As-Is" state). When a customer initiates a change, the system converts this Asset's current state into an order line item for modification.
The product/service sold will have child features added in the future (A): Products that are part of a bundle or have a hierarchical structure (Parent $\rightarrow$ Child) must be tracked as Assets so that their children or sub-features can be managed, added, or removed later. For example, if a base service (Asset) allows for the addition of premium channels (new Assets), the base service must first exist as an Asset to act as the parent for the new features.
Why D and E are incorrect: D (High-volume, one-time billing event, such as a pay-per-view): One-time, high-volume transactional items (like PPV events or movie rentals) are typically not assetized. They are billed once and retired.
Creating millions of short-lived asset records would rapidly consume storage and severely degrade system performance.
E (Device accessory, such as a phone case): Simple, one-time purchase equipment without a service component (like a phone case or charger) is rarely assetized, as it has no recurring charge (B) and generally does not undergo MACD changes (C).

In Salesforce Communications Cloud, the B2C customer model follows a structured, layered hierarchy designed to support ordering, billing, service management, and asset lifecycle handling. When migrating existing B2C customers into Communications Cloud, Salesforce's public architecture guidance specifies a top-down data dependency sequence to ensure that parent records exist before child records referencing them are inserted. The migration sequence begins with Users, since many operational objects (orders, cases, ownership, provisioning workflows) require an active user as the record owner or last modified by.
Next, Contacts are required for each B2C customer because Communications Cloud uses Contacts associated with a Consumer Account to represent the individual subscriber. Although Person Accounts are supported in some Salesforce products, Communications Cloud standard data model for B2C uses Consumer Accounts + Contacts, which aligns with option A-not C.
Once contacts are created, Consumer Accounts must be migrated so that customer identity, householding, service relationships, and billing mappings can be referenced. With accounts in place, Billing Accounts are imported next to link financial agreements, billing preferences, and invoicing relationships. Service Accounts follow, serving as the service location or logical container for active telecom services. Only after these parent entities are established can Subscriptions be migrated, as they represent the commercial products the customer is consuming. Finally, Assets are migrated, representing the technical products or devices (routers, SIMs, set-top boxes) associated with active subscriptions and services. Options B, C, and D omit Subscriptions, which are essential for B2C migration into Communications Cloud. Option C incorrectly uses Person Accounts, which does not match the Communications Cloud standard B2C data model.

To make a brand-new product available for Industries CPQ initial sale and support order fulfillment, two major work items must be completed:
B. Decomposition Relationships
These define how the commercial product breaks into technical products required for fulfillment. Without decomposition, Order Management cannot generate Fulfillment Request Lines.
D. Product Model
The product must be fully modeled in the Enterprise Product Catalog (EPC): Product Spec Attributes Prices Cardinality Bundles Versioning Incorrect options:
A. OmniScript is optional; CPQ can still operate via the Cart without custom OmniScripts. C. MACD
Orchestration is not needed for initial sale; only fulfillment of new orders is required at launch

Once a production data load is completed in Communications Cloud, Salesforce's public data-migration and go-live readiness recommendations emphasize two mandatory activities: (1) remediation of failed records, and (2) validation of loaded data. These activities ensure that production contains a complete, accurate, and trusted data set before the system is opened to business users. Option B - Analyze and resolve any errors and re-load failed records Even if a full-data migration completed successfully in a Full Copy sandbox, the production environment may still produce new failures due to data differences, unexpected validation rules, org-specific automation, or sequence dependencies. Salesforce migration best practices require analyzing the error logs generated by Data Loader, Bulk API, or middleware, correcting failed data, and performing targeted reloads. No migration is considered complete until every failed record has been addressed. This is a standard post-migration requirement in Communications Cloud given the volume and interdependencies between Accounts, Subscriptions, Service Accounts, Billing Accounts, Premises, Assets, Orders, and Fulfillment objects.
Option D - Validate volumes and spot-check correctness After the load finishes, the consultant must validate that record counts in production exactly match expected totals from source systems, including number of Accounts, Billing Accounts, Service Accounts, Subscriptions, Premises, and Assets. Salesforce also recommends targeted spot checks -opening individual customer records, ensuring relationships are correct, asset hierarchies are intact, and subscription data is consistent. This ensures data integrity before cutover and user access.
Incorrect options:
A - Salesforce does not provide a data load report via support case; all logs come from the tools used
during migration.
C - You cannot assume "all errors were resolved earlier." Every production load must be validated, and new issues frequently occur during the final cutover.
Therefore, the correct post-production-load actions are B and D.

Inventory Check is the standard component used on assessment task record pages for verifying product inventory in the field. Promotion Details serves a different purpose, Shipment Review is for delivery processes, and Action Plan Clone is not a standard record-page component for this use case.