Which component can be used in other Salesforce Experience templates outside of B2B Commerce?
A. Quick Order
B. CMS Collection
C. Product Detail Data
D. Results Layout
Explanation:
In Salesforce Experience Cloud, components like CMS Collection and
Results Layout are designed to be reusable across different Experience templates, not just
limited to B2B Commerce. CMS Collection allows for the display of CMS content in a
flexible and dynamic layout, while Results Layout can be used to present search or query
results in a customizable format. Salesforce documentation on Experience Cloud
components emphasizes the reusability and adaptability of these components across
various templates and contexts.
What class must a developer implement to override Pricing during the checkout?
A. sfdc_commerce.CartPriceCalculations
B. sfdc_commerce.PriceCalculations
C. sfdc_checkout.PriceCalculations
D. sfdc_checkout.CartPriceCalculations
Explanation:
To override pricing during the checkout process in Salesforce B2B
Commerce, a developer must implement a class specifically designed for this purpose,
such assfdc_checkout.CartPriceCalculations. This class would provide the necessary
framework for custom pricing logic to be applied during checkout, ensuring that any custom
pricing requirements are met.
When a developer configures a tax integration for a store, what happens to the previously calculated tax entries during the checkout flow?
A. Ignored during recalculation
B. Saved prior to recalculation
C. Deleted from the Cart
D. Modified with the new tax calculation
Explanation:
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 References: B2B Commerce Developer
Guide: Tax Integration, B2B Commerce Developer Guide: Tax Calculation Flow
What is the purpose of connected Call back in a Lightning web component?
A. It performs actions when a network request is made.
B. It perform actions when a component makes a call to a Connect APL.
C. It performs actions when a component is removed from the DOM.
D. It performs actions when a component is added to the DOM.
Explanation:
The connectedCallback is a lifecycle hook that is invoked when a Lightning
web component is inserted into the DOM. It is used to perform any initialization tasks that
depend on the component being rendered, such as fetching data, setting up event
listeners, or creating timers. The connectedCallback can fire more than once, for example,
when a component is moved or rerendered. The connectedCallback should not be used to
change the state of a component, such as loading values or setting properties. Use getters
and setters instead. The other options are incorrect because they do not describe the
purpose of the connectedCallback.
References: Lifecycle Hooks | Lightning Web
Components Developer Guide, connectedCallback() in Lightning Web Component -
Salesforce Diaries, Chapter 23: connnectedCallback() in Lightning Web Component
Which of these is a key pattern leveraged when building Lightning Web Components? 39m 36s
A. Composition
B. Inventory
C. Juggling
D. Normalization
Explanation:
Composition is a key pattern in building Lightning Web Components (LWCs).
This approach involves creating small, reusable components that can be assembled to
form more complex interfaces. This pattern promotes modularity, reusability, and
maintainability in the development of web components, aligning with web standards and
best practices.
Page 7 out of 43 Pages |
Previous |