The B2B Commerce for Developers Accredited Professional (AP-202) (B2B-Commerce-Developer)

 According to the  B2B Commerce Developer Guide , the Order List Component (Aura) for B2B stores displays a list of orders that the user c an view and reorder. The component filters the orders based on the current storefront and the current effective account. The current effective account is the account that the user is currently acting on behalf of, which can be different from the user’s own account. The component does not show orders placed in other storefronts or related to other accounts, even if the user has access to them. Therefore, the correct answer is A. Orders placed in the current storefront and related to the current effective acc ount. The other options are incorrect because they do not match the criteria of the component.  References:   B2B Comme rce Developer Guide ,  Show the Order List Widget

The event that is triggered within Salesforce B2B Commerce whenever a cart’s state changes is cartChange. This event is triggered by the updateCart method of the CCRZ.Cart class, which is responsible for updating the cart data and performing any actions that depend on the cart state, such as applying discounts, taxes, or shipping charges. The event can be used to notify all the components that are listening to it that the cart has changed a nd they should refresh their data accordingly. Salesforce References:  B2B Commerce and D2C Commerce Developer Guide ,  Events ,  Cart Class

This approach effectively removes the payment page from the list of allowed pages, ensuring it is not displayed during the checkout process.

The Global API Data-Sizing convention flag that prevents an API request from propagating to further requests when provided as a Boolean parameter with a value of true is ccrz.ccAPI.SZ_ASSC. This flag indicates that only one API request should be executed with the specified sizing block, and any subsequent requests should use their own default sizing blocks. For example,  ccrz.ccServiceCart.getCart(ccrz.ccAPI.SZ_L,true)  will use the SZ_L sizing block for retrieving the cart data, but any other requests that are triggered by this method will use their own default sizing blocks. Salesforce References:  B2B Commerce and D2C Commerce Developer Guide ,  Data Sizing Conventi ons

To automatically add 1 unit of Product A to the cart when a user buys 10 units of Product B, the requirement can be fulfilled by overriding the prepareToAdd method in ccrz.cc_api_CartExtension. This method is responsible for preparing the cart line items before they are added to the cart. By overriding this method, the user can check the quantity and product ID of the c art line items and add an additional cart line item for Product A if the condition is met. Salesforce References:  B2B Comme rce and D2C Commerce Developer Guide ,  API Classes ,  cc_api_CartExtension Class

If a developer leaves debug mode turned on in an environment, the user will begin getting JavaScript limit exceptions. Debug mode is a setting that enables more detailed logging and error reporting for Lightning web components. However, it also increases the size and complexity of the JavaScript code that is delivered to the browser, which can cause performance issues and JavaScript limit exceptions. The JavaScript limit exceptions are errors that occur when the browser reaches its maximum capacity for executing JavaScript code, such as memory heap size or script execution time. The performance of the org will not become slower each day, as debug mode only affects the client-side performance, not the server-side performance. The org will not turn off debug mode after 72 hours, as debug mode is a persistent setting that can only be changed manually by an administrator. A banner will not be displayed to the user indicating that the org is in debug mode, as debug mode is a transparent setting that does not affect the user interface. Salesforce References: Lightning Web Components Developer Guide: Debug Your Code, Lightning Web Components Developer Guide: JavaScript Limit Exceptions

To implement a custom Terms and Conditions checkbox at checkout in the Aura Commerce template, a developer should add a Desired Delivery Date input field during the checkout flow. The Desired Delivery Da te input field allows the customer to enter a date when they want their order to be delivered. The developer can use the @api decorator to expose this field as a public property of the Lightning web component and bind it to the ccCheckoutOrder object. The developer can also use the @wire decorator to get the current cart object and use its properties, such as shipping address and shipping method, to calculate and display an estimated delivery date based on the desired delivery date. The developer can also a dd validation logic to ensure that the desired delivery date is valid and acceptable. Adding the Expected Delivery Date field to the order confirmation email is not a good solution, as it does not allow the customer to choose or see their delivery date bef ore placing their order. Displaying the Expected Delivery Date on the order page with a Lightning web component is not a good solution either, as it does not allow the customer to enter or change their delivery date after placing their order. Configuring a n email alert to the customer when the Expected Delivery Date changes is not a good solution either, as it does not provide a consistent or reliable way of informing the customer about their delivery date. Salesforce References:  B2B Commerce Developer Guide: Checkout Flow ,  B2B Commerce Developer Guide: Checkout Order Object ,  Lightning Web Components Developer Guide: Com municate with Properties

A valid way of referencing the global cc_api_CartExtension apex class via subsc riber code is to use ccrz.cc_api_CartExtension. This is the name of the class that is defined in the cloudcraze managed package. The class is global, so it can be accessed by subscriber code. The other options are either invalid or incorrect. Salesforce Re ferences:  B2B Commerce and D2C Commerce Developer Guide ,  API Classes

Three pages that should be enabled for the Guest user profile for a storefront to have anonymous checkout are:

CCPaymentInfo: This page allows the guest user to enter their payment information, such as credit card number, expiration date, and security code. The page also displays the order summary and total amount.

CheckoutNew: This page allows the guest user to enter their shipping and billing information, such as name, address, phone number, and email. The page also displays the cart items and shipping options.

OrderConfirmation: This page displays the confirmation message and order number after the guest user places their order. The page also provides a link to view the order details or print the invoice. Salesforce References:  B2B Commerce and D2C Commerce Developer Guide ,  Anonymous Checkout