When a developer configures a tax integration for a store, what happens to the previously calculated tax entries during the checkout flow?
Correct Answer: C
When a developer configures a tax integration for a store, the previously calculated tax entries during the checkout flow are deleted from the Cart. A tax integration is an integration that calculates and applies tax rates and amounts to a Cart or an Order based on various factors, such as product type, price, quantity, location, and tax rules. A tax integration can use either an external tax service provider or custom Apex code to perform the tax calculation. When a developer configures a tax integration for a store, any existing tax entries in the Cart are deleted before calling the tax integration service or method. This ensures that the tax calculation is accurate and up-to-date based on the current state of the Cart and avoids any conflicts or inconsistencies with previous tax entries. The previously calculated tax entries are not ignored during recalculation, saved prior to recalculation, or modified with the new tax calculation, as these are not valid actions for handling existing tax entries. Salesforce Reference: B2B Commerce Developer Guide: Tax Integration, B2B Commerce Developer Guide: Tax Calculation Flow
Question 72
For which two reasons is it preferable to extend the Salesforce B2B Commerce remote invocation object instead of using the standard Salesforce remote action invocation manager (2 answers)
Correct Answer: B,D
Explanation It is preferable to extend the Salesforce B2B Commerce remote invocation object instead of using the standard Salesforce remote action invocation manager for two reasons: * The APEX method called by the remote action will be passed as a Salesforce B2B Commerce context object, which contains useful information such as the current user, cart, storefront, and configuration settings. This can simplify the development and testing of the remote action. * The Salesforce B2B Commerce logger can be utilized in the remote action, which allows logging messages and errors to the debug log or to a custom object. This can facilitate debugging and troubleshooting of the remote action.
Question 73
Which three actions are applicable when extendinga default Salesforce B2B Commerce page via a page include? (3 answers)
Correct Answer: B,D,E
Three actions that are applicable when extending a default Salesforce B2B Commerce page via a page include are: * Create the VisualForce page you wish to include to the Salesforce B2B Commerce page. This page will contain the custom content or logic that you want to add to the existing page. For example, youcan create a VisualForce page named MyPageInclude that displays some additional information or functionality on the product detail page. * Create a configuration setting for enabling the page include and assigning the new page include via CC Admin. This setting will specify which page include you want to use for which page and section. For example, you can create a configuration setting named CO.MyPageInclude with the value PDV.BodyIncludeBegin.MyPageInclude, which means you want to use MyPageInclude as the body include begin for the product detail view (PDV) page. * Build and activate a new configuration cache setting via CC Admin. This action will refresh the cache and apply the changes to the storefront. You need to do this whenever you make any changes to the configuration settings or VisualForce pages. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Page Includes
Question 74
Ursa Major is planning to implement Salesforce B2B Commerce, and a developer needs to configure taxes for their storefront. The company operates in multiple states, each with different tax rates and tax rules. What are two ways the developer should configure taxes in B2B Commerce?
Correct Answer: A,B
Two ways that a developer should configure taxes in B2B Commerce for Ursa Major are: configure a tax engine using third-party software and configure tax rates and rules for each state in Salesforce B2B Commerce. Configuring a tax engine using third-party software allows the developer to integrate with an external tax service provider that can calculate and apply accurate and up-to-date tax rates and rules for different states and jurisdictions. The developer can use the sfdc_checkout.TaxCalculations interface or the RegisteredExternalService object to connect to the third-party tax service provider's API or service. Configuring tax rates and rules for each state in Salesforce B2B Commerce allows the developer to implement their own custom tax calculation logic using Apex code. The developer can use custom objects, such as TaxRate__c and TaxRule__c, to store and manage tax rates and rules for different states and products. The developer can also use the sfdc_checkout.TaxCalculations interface to define how to retrieve and apply tax rates and rules for a cart or an order. Using a different pricebook for each state is not a good way to configure taxes in B2B Commerce, as it can create complexity and inconsistency in pricing and discounting logic. Using the Salesforce out-of-the-box tax calculator is not a good way either, as it does not support complex or dynamic tax scenarios that may vary by state or jurisdiction. Salesforce References: [B2B Commerce Developer Guide: Tax Integration], [B2B Commerce Developer Guide: Tax Calculations Interface], [B2B Commerce Developer Guide: TaxRate Object], [B2B Commerce Developer Guide: TaxRule Object]
Question 75
Which technique is used by Lightning Web Components to provide areas of swappable, customizable content?
Correct Answer: A
Lightning Web Components (LWC) use<slot>elements to define areas within the component's template where content can be inserted dynamically. This feature, part of the Web Components standard, allows for the creation of customizable and reusable components. Salesforce developer documentation on LWC outlines the use of slots to build flexible component interfaces, enabling developers to design components that can adapt to various content structures and layouts.
