B2B-Commerce-Developer Practice Test

Explanation:

To debug a flow and watch all the variables changing as the checkout process is executed, the developer needs to enable two features: show the details of what is executed and render flow in either Lightning Runtime or Lightning Experience. These features are available in the debug options in Flow Builder, and they allow the developer to see real-time details of the flow actions, inputs, outputs, and outcomes in a panel on the right. The developer can also set input variables, restart the flow, and convert the debug run to a test. Option A is incorrect because there is no such thing as a debug tog in Flow Builder. Option C is incorrect because running the latest version of each flow called by subflow elements is not a feature that the developer can enable or disable, but rather a default behavior of Flow Builder. References: Debug a Flow in Flow Builder, B2B Commerce Checkout Flow (Aura), B2B Commerce Checkout Flow Core Actions

Explanation:

The root cause of why the custom field MyCustomField__c has no values and no column header in the CSV file is that the user does not have access to the field. A user’s access to a field is determined by theirprofile and permission sets, which define their field-level security settings. Field-level security settings control whether a user can see, edit, or delete the value for a particular field on an object. If a user does not have access to a field, they will not be able to view or modify its value in any interface, including Data Loader. Data Loader is a tool that allows users to import or export data between Salesforce and CSV files. When using Data Loader to export data from an org, Data Loader will only include fields that are accessible to the user based on their field-level security settings. If a user does not have access to a field, Data Loader will not include that field in the CSV file, neither as a column header nor as a value. The user needs to install a specific Zulu JDK that is recommended by Salesforce is not the root cause of why MyCustomField__c has no values and no column header in the CSV file, as it is not related to field access or Data Loader functionality.

A mapping file was not used when the data was loaded in is not the root cause either, as it is not related to field access or Data Loader functionality. A mapping file is an optional file that maps fields between Salesforce objects and CSV files when using Data Loader to import or export data. The user has rights to the field but there are no values in it is not the root cause either, as it contradicts the fact that MyCustomField__c has no column header in the CSV file. If the user had rights to the field but there were no values in it, Data Loader would still include MyCustomField__c as a column header in the CSV file, but leave its values blank. Salesforce References: [Data Loader Guide: Export Data from Salesforce], [Data Loader Guide: Field Mapping], [Salesforce Help: Set FieldLevel Security]

Explanation:

To check user permissions in Lightning web components, a developer should import two scoped modules: @salesforce/permission and @salesforce/customPermission. The @salesforce/permission module allows the developer to check if the user has access to a standard permission, such as View Setup or Modify All Data. The @salesforce/customPermission module allows the developer to check if the user has access to a custom permission, such as Enable Debug Mode or Manage Orders. The other modules do not exist or are not related to user permissions. Salesforce References: Lightning Web Components Developer Guide: Check User Permissions, Lightning Web Components Developer Guide: Import Salesforce Modules

Explanation:

To reflect the price values stored in an external ERP during the checkout flow, the requirement can be satisfied by overriding the computePricingCart method in ccrz.cc_api_CartExtension and making the callout in this method. This method is responsible for computing the pricing for the cart and its line items. By overriding this method, the user can make a callout to the external ERP and update the pricing information accordingly. Salesforce References: B2B Commerce and D2C Commerce

Explanation:

More modules and metadata can be added to Salesforce B2B Commerce by creating custom configuration settings. Configuration settings are custom settings that store various values and parameters that affect the functionality and appearance of the storefront. They are organized into modules, which group related settings together. To create a custom configuration setting, the user needs to create a custom setting record in Salesforce and specify its module, name, value, and description. The custom setting will then appear in CCAdmin under the specified module. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Configuration Settings