Explanation
To present different user experiences to different buyers in a storefront, an admin can take two steps: create audiences to define different segments and use page variations. Audiences are groups of users who share common characteristics, such as location, language, account type, etc. Page variations are different versions of a page that can be shown to different audiences based on criteria such as device type, browser type, user profile, etc. References: Create Audiences; Use Page Variations

Explanation
According to the Kit Product Type page and the Bundle Product Type page, kit product type and bundle product type are two different product types that consist of multiple components. The difference between a kit product type and a bundle product type is that the pricing of a bundle is determined by the price list item associated with the bundle, while the pricing of a kit is determined by the sum of the prices of the components selected by the customer. Therefore, option A is correct. Option B is false because a bundle is not constructed by the customer, but predefined by the administrator. Option C is false because the pricing of a bundle is not determined by the products contained in the bundle, but by the price list item associated with the bundle.
Option D is false because a bundle is not a tightly related set of products, but a fixed set of products that are sold together. References: Kit Product Type, Kit Product Type Overview; Bundle Product Type, Bundle Product Type Overview

The Lightning Message Service (LMS) is a feature that allows communication across different UI technologies, such as Lightning Web Components, Aura Components, and Visualforce pages. LMS uses message channels to publish and subscribe to messages. A message channel is a custom metadata type that defines the shape and scope of the messages1. The lightning_commerce_cartChanged channel is a standard message channel that is used by the B2B Commerce Cloud platform to notify components of changes to the cart items and quantities2. A developer can use the LMS API to subscribe to events on this channel and update the custom component accordingly. The developer needs to import the lightning/messageService module and the lightning_commerce_cartChanged channel in the JavaScript file of the custom component, and then use the subscribe method to register a callback function that handles the message payload3. For example:
// cartCustomComponent.js import { LightningElement, wire } from 'lwc'; import { subscribe, MessageContext } from 'lightning/messageService'; import CART_CHANGED_CHANNEL from '@salesforce/messageChannel/lightning_commerce_cartChanged__c'; export default class CartCustomComponent extends LightningElement { // Declare a message context @wire(MessageContext) messageContext;
// Declare a subscription variable subscription = null;
// Subscribe to the message channel in the connected callback connectedCallback() { this.subscribeToMessageChannel(); }
// Subscribe to the message channel using the LMS API subscribeToMessageChannel() { if (!this.subscription) { this.subscription = subscribe( this.messageContext, CART_CHANGED_CHANNEL, (message) => this.handleCartChange(message) ); } }
// Handle the message payload and update the component logic handleCartChange(message) { // Do something with the message payload, such as: // - Display the cart items and quantities // - Calculate the cart total // - Apply discounts or taxes // - etc. } }