Salesforce Certified B2B Commerce Administrator Practice Test - Questions Answers, Page 26

To handle changes on the combobox, the developer should use {handleChange} as the value for the onchange attribute. This syntax binds the handleChange function defined in the JavaScript file of the component to the change event fired by the combobox. The developer can then access the selected value from the event object passed to the function and perform any logic or action based on it.Reference:

lightning-combobox - documentation

Handle Events in Lightning Web Components

The correct set of steps to authorize the org for Command Line Interface (CLI) access so the developer can deploy Lightning web components is to run the command: 'sfdx force:auth:web:login -r ''https://login.salesforce.com'' and then supply the credentials in the browser when it opens. This command will open a browser window and prompt the user to log in to the org using their username and password. The -r flag specifies the login URL for the org, which is https://login.salesforce.com for production or developer orgs.The command will also create an alias for the org, which can be used to reference it in other CLI commands1.Reference:1: Authorize an Org - Trailhead2

The recommended path forward for a developer who needs to implement a Lightning web component that can read, create, and modify single records is to use base components. Base components are prebuilt Lightning web components that provide common functionality and user interface elements, such as forms, buttons, inputs, outputs, and more. Some of the base components, such as lightning-record-edit-form, lightning-record-form, and lightning-record-view-form, use Lightning Data Service to access and manipulate Salesforce data without requiring any Apex code.These components can handle CRUD operations on single records, as well as validation, layout, and error handling3.Using base components can save time and effort for the developer, as well as ensure consistency and performance across the application4.Reference:3: Work with Salesforce Records - Trailhead5,4: Use Base Lightning Components - Trailhead6

The product will not appear on the Portal and therefore cannot be added to the cart. This is because the product is not assigned to the price book that is related to the buyer group. The entitlement policy only determines which products the buyer group can see, but the price book determines which products the buyer group can buy. If a product is not in the price book, it will not be displayed on the Portal, regardless of the entitlement policy settings.Reference:

Organize How Customers Access Your Commerce Store

Set Up Pricing for Commerce Stores

The most likely root cause of the issue is that the user does not have access to the custom field MyCustomField__c. This means that the user's profile or permission set does not have the field-level security (FLS) enabled for this field, or the field is not visible on the page layout for the user's record type. Therefore, when the user exports data from the org using Data Loader, the custom field is not included in the CSV file, and neither its values nor its column header are shown. To resolve this issue, the user or an administrator should check and modify the FLS and page layout settings for the custom field, and then try to export the data again.Reference:

Field-Level Security

Data Loader Guide