Explanation:
Assets are used for items that have an ongoing lifecycle after the sale—they are installed, provisioned, modified, billed repeatedly, or upgraded. One-time transactions with no future changes don't need assets.

Correct Options & Why:

A. The product/service sold will have child features added in the future.
Assets support hierarchical structures (parent/child assets). If you might add features (e.g., add Call Waiting to a phone line), assetization allows you to attach child assets later, reflecting the updated service structure.

B. The product/service sold has a recurring charge.
This is a primary trigger for assetization. Assets are tightly integrated with billing systems and subscription management. A recurring charge implies an ongoing service that needs to be tracked, billed each period, and potentially renewed or canceled—all managed via the asset lifecycle.

C. The product/service sold can undergo future attribute changes.
Assets have attributes (specifications) that can be updated over time (e.g., change data plan from 5GB to 10GB). Assetization allows you to modify these attributes while preserving the asset's history and relationship to the customer.

Why Others Are Incorrect:

D. The product/service sold is a high-volume, one-time billing event, such as a pay-per-view.
One-time events do not require an asset. They are transactional (recorded as Order Products or Quote Line Items) but don't have an ongoing lifecycle. Creating assets for high-volume one-time events would create unnecessary data volume and overhead.

E. The product sold is a device accessory, such as a phone case.
A physical accessory is typically a one-time sale with no recurring changes or billing. It might be tracked as an asset if it needs warranty/service history, but in telecom, accessories are often not assetized unless they are part of a managed service. It's not a main factor compared to A, B, C.

Reference:
In Salesforce Communications Cloud, assetization is driven by the need for service lifecycle management. The decision framework includes:

Recurring Billing? → Yes, assetize.

Future modifications or additions? → Yes, assetize.

One-time transaction? → No asset needed.
This is covered in Telecommunications Service Management (TSM) and asset lifecycle design guides

Explanation:
This question addresses a key data modeling decision when integrating a complex ERP product hierarchy into CGC. The goal is to measure share-of-shelf, a KPI based on the physical presence of distinct sellable products on a shelf. The consultant must identify the hierarchy level that corresponds to the granular, unique products that are individually stocked and faced.

Correct Option:

C. Which tier describes stock keeping units (SKU)?
Share-of-shelf is calculated by comparing the facings or linear shelf space of specific, sellable product items. The correct tier is the one containing Stock Keeping Units (SKUs), which are unique identifiers for each distinct product variant (e.g., "Brand X Shampoo, 500ml, Fragrance Y"). This is the level of granularity needed for in-store execution measurements.

Incorrect Option:

A. What tier has data describing the product with?
This is too vague. Many tiers may "describe" a product (e.g., category, brand, sub-brand). The critical factor is not description, but identification of the unique, physical item for shelf measurement.

B. Which tier has the data you trust most?
Data trust is important overall, but it doesn't answer the specific functional need. Even perfectly trusted data at a brand or category level is too aggregated for calculating share-of-shelf for individual products.

D. There is no need to ask a question choose level 7.
Making an arbitrary selection based on hierarchy depth is incorrect. The lowest level (often level 7) is frequently where SKUs reside, but this is not a given. The consultant must determine which tier corresponds to SKUs, not assume it's always the deepest level. The question's phrasing ("determine which tier") requires analysis.

Reference:
Consumer Goods Cloud implementation guides for product hierarchy and integration emphasize mapping the SKU-level data from the ERP to the Product object in Salesforce. Share-of-shelf and facing KPIs are measured at the individual product/SKU level, as these are the items physically placed on store shelves.

Explanation:
When a field representative performs an Inventory Check Task during a store visit in Consumer Goods Cloud, the system filters the product list to show only those items relevant to that specific location. This is crucial for efficiency, as it prevents the representative from having to search through the company's entire product catalog, which may contain thousands of SKUs irrelevant to the store being audited. The relevant products are defined by the Assortment or other Store Product relationships established in the back-office setup.

Correct Option:

B. All products associated with the retail store:
This is the accurate scope. The products available for selection in an Inventory Check task are determined by the Assortment assigned to the store or the specific Store Product records linking products to that retail store. This ensures the representative is only measuring inventory for products that the store is authorized and expected to carry. If a product is not associated with the store's assortment, it will not appear in the mobile search, thereby streamlining the process and maintaining data integrity.

Incorrect Option:

A. All products created by the user:
Product master data is typically created by a system administrator or integrated from an ERP system, not by the field user performing the check. Filtering by the user who created the product is irrelevant and would severely limit the available product list.

C. All products owned by the user:
In Salesforce, "ownership" usually refers to the record owner. Products are typically "owned" by an administrator or a generic system user. Filtering by the field representative's ownership would again be irrelevant to the inventory check process, as the check is about the store's inventory, not the rep's personal assets.

D. All products in the organization:
Listing every product in the organization would create a massive, unusable list for a single retail store audit. This approach would be highly inefficient and counter-productive for the mobile user, who needs a highly targeted, store-specific product selection.

Reference:
Consumer Goods Cloud Retail Execution: Product Filtering, Assortment Management, and Mobile Application Logic.

Explanation:
This is a classic synchronous callout with response processing scenario. The standard Vlocity/Industries integration pattern uses: An Integration Procedure to orchestrate the callout.

A DataRaptor to transform the outgoing request (Extract) and process the incoming response (Load).

A Response DataRaptor Bundle is a specific configuration that maps the ERP response fields to Salesforce fields and saves them.

Correct Option:

A. Configure the Response DataRaptor Bundle to process CREATE response from ERP and save returned ERP order identifier to SFI order record.
This is the precise, declarative method. The Response DataRaptor Bundle is attached to the Callout step in the Integration Procedure. It processes the synchronous response, extracts the ERP order ID, and maps it directly to a field on the Salesforce Order record. This is the standard, low-code way to achieve the requirement.

Why Others Are Incorrect:

B. Configure integration procedure in conjunction with Auto Task to perform CREATE order in ERP and process response to save returned ERP order identifiers using Load DataRaptor.
An Auto Task is used for asynchronous post-order-creation actions (like updates), not for processing a synchronous response from the initial CREATE callout. The response should be processed immediately in the same Integration Procedure using a Response DataRaptor Bundle, not deferred to an Auto Task.

C. Enhance OOTB integration adapter to process CREATE response from ERP and save returned ERP order identifier to SFI order record.
This suggests custom code modifications to the Out-Of-The-Box (OOTB) integration adapter. This is anti-pattern; you should avoid modifying OOTB adapters. The platform provides a declarative way (Response DataRaptor Bundle) to handle this without code.

D. Configure GET ERP Order Callout task straight after the callout task that creates an order in ERP. Enhance the out-of-the-box integration adapter to process GET response from ERP and save returned ERP order identifier to SFI order record.
This is overly complex and incorrect. The ERP order ID is returned in the synchronous response of the CREATE call. There is no need for a separate GET callout. Additionally, it again incorrectly recommends modifying the OOTB adapter.

Reference:
In Salesforce Industries (Vlocity) Order Management, the pattern for synchronous callout and response saving is:

Integration Procedure with a Callout step.

Response DataRaptor Bundle configured on that Callout step to map response fields to the target Salesforce record.

This is documented in the Integration Procedures and DataRaptors guides for Order Management implementations.

Explanation:
In Consumer Goods Cloud, the In-Store Survey task in CG Mobile automatically displays only the relevant Salesforce Survey invitations that the field rep can realistically complete during the current store visit. The system filters invitations to those explicitly linked to the Visit record, the Retail Store record itself, or the store’s designated Primary Contact, ensuring the rep sees only context-appropriate surveys (e.g., store manager feedback, mystery shopper, promotion compliance).

Correct Options:

A. Survey invitations associated with the visit
Surveys directly linked to the current Visit record (via Action Plan Template or manual assignment) always appear first in the In-Store Survey task.

D. Survey invitations associated with the Retail Store
Any active survey invitation targeted to the Retail Store object (regardless of contact) is displayed, as it is considered store-level feedback.

E. Survey invitations associated with the Store Primary Contact
Surveys sent to the person listed as “Primary Contact” on the Retail Store record are shown, because the rep is most likely to meet that specific store manager.

Incorrect Options:

B. All Survey invitations targeted to a contact or user
The task does not show every survey in the org; only those relevant to the current store/visit are displayed.

C. All open Survey invitations
Global open surveys are never pushed into the In-Store Survey task; this would overwhelm reps and is not supported behavior.

Reference:
Salesforce Help: “In-Store Survey Task in Consumer Goods Cloud Mobile” (Winter ’25–Summer ’26)

Trailhead: “Capture In-Store Feedback with Surveys” – Survey Invitation Filtering logic

CG Cloud Release Notes: In-Store Survey task displays invitations linked to Visit, Retail Store, or Store Primary Contact