Which Lightning web component path allows a developer to view or edit a record while maintaining control over specifying its layout and set of fields?
A. lightning-record-edit-form
B. lightning-record-imperative
C. lightning-record-view-form
D. lightning-record-form
Explanation:
The lightning-record-edit-form component allows a developer to view or edit
a record while maintaining control over specifying its layout and set of fields. This
component provides a way to create forms that respect the field-level security and layout
configuration defined in the Salesforce metadata. The developer can use lightning-inputfield components inside the form to display and edit the fields of a record. The other options
are incorrect because they either do not allow editing the record, do not respect the
metadata configuration, or do not exist as valid component paths. References: lightningrecord-edit-form | Lightning Web Components Developer Guide
A developer used slots to pass content from one Lightning Web Component to another. How can they access the. DOM for what was passed to those slots?
A. Call this.template.querySelector() and this.template.querySelectorAll()
B. Call this.querySelector() passing an id
C. Call this.querySelector() and this.querySelectorAll()
D. Call this.template.querySelector() passing an id
Explanation:
In Lightning Web Components, to access the DOM elements within the
component's template, including those passed into slots, developers use
this.template.querySelector()andthis.template.querySelectorAll(). These methods
allow for querying the component's local DOM. Direct DOM manipulation or querying
outside the component's template is discouraged to maintain component encapsulation
and security. For more information, see the Salesforce LWC documentation on accessing
the DOM:Salesforce LWC DOM Access Documentation.
What target does a developer need to set in the js-meta.xml file when creating a custom LWC component for use in the Checkout Flow?
A. lightning_FlowScreen
B. lightning__CheckoutFlow
C. Iwe__FlowComponent
D. lwe__flow
Explanation:
When creating a custom Lightning Web Component (LWC) for use in the
Checkout Flow, a developer must set the target in the js-meta.xml file to
lwc__FlowComponent. This target specifies that the LWC is intended for use within the
flow component framework, allowing it to be utilized specifically in the context of Salesforce
Flows, including those used in the checkout process. Salesforce documentation on
developing custom LWCs for various targets would detail this requirement, ensuring that
developers understand how to correctly package and deploy their components for the
intended use case.
Which HTML element can be used as a root tag for a Lightning Web Component's HTML file?
A.
B.
C.
D.
A developer needs to implement a business rule around shipping: Anything over a certain amount must be sent through freight at a fixed cost and cannot be sent through standard shipping channels. Which two considerations should the developer consider?
A. A class will need to implement the sfdc_commerce.CartShippingCharges interface
B. The implementing class cannot call out to another service
C. A class will need to implement the sfdc_checkout.CartShippingCharges interface
D. The implementing class may need to contain logical branching
Explanation:
The correct answer is A and D. To implement a business rule around shipping, the
developer will need to create a class that implements the
sfdc_commerce.CartShippingCharges interface and may need to contain logical
branching to handle different scenarios12.
The
sfdc_commerce.CartShippingCharges interface is a standard interface that defines
the methods for calculating shipping charges for a cart1. The developer can use
this interface to override the default shipping logic and apply custom rules based
on the cart amount or other factors12. The developer may also need to use
conditional statements or other logic to determine when to use freight shipping or
standard shipping3.
The implementing class cannot call out to another service and a class will need to
implement the sfdc_checkout.CartShippingCharges interface are not the correct
answers. The implementing class can call out to another service if needed, such
as an external shipping service or a pricing engine2.
The
sfdc_checkout.CartShippingCharges interface is a deprecated interface that was
used for calculating shipping charges for a cart only1. It has been replaced by the
sfdc_commerce.CartShippingCharges interface, which supports both carts and
orders1.
References:
B2B Commerce on Lightning Experience Developer Guide
B2B Commerce and D2C Commerce Developer Guide
Salesforce Accredited B2B Commerce Developer
sfdc_commerce.CartShippingCharges Interface
Integrate with Lightning B2B Commerce
Shipping Rules 101: Here’s What You Need to Know
A developer has made some changes to the products of an existing storefront, but they are unable to see the changes in the products from the store. Which action did the developer forget to take?
A. Activate the product list.
B. Publish the storefront.
C. Rebuild the search index.
D. Publish the catalog
Explanation:
The developer forgot to publish the storefront after making changes to the
products. Publishing the storefront is a necessary step to make the changes visible to the
store visitors. Publishing the storefront updates the site’s metadata and content, and also
triggers the site index and search index rebuilds. If the developer does not publish the
storefront, the changes will not be reflected on the live site.
The following actions are not required or relevant for the scenario:
Activate the product list. This action is only needed when creating a new product
list or modifying an existing one. It does not affect the visibility of the products on
the storefront.
Rebuild the search index. This action is automatically performed when the
developer publishes the storefront. It is not a separate step that the developer
needs to take manually.
Publish the catalog. This action is not applicable for Salesforce B2B Commerce for
Visualforce, which does not use catalogs. Catalogs are only used by Salesforce
B2B Commerce for Lightning Experience.
References:
Finalize and Publish Your Storefront
Customize the D2C Store Template
Configure Public Pages for a Storefront
Numerous flags, when set, have a direct impact on the result set provided by the Global API's. What is the default Global API DataSizing convention flag that is used by theAPI's unless otherwise specified?
A. CCRZ.ccPAI.SZ_XL
B. CCRZ.ccPAI.SZ_M
C. CCRZ.ccPAI.SZ_L
D. CCRZ.ccPAI.SZ_S
Explanation:
The default Global API Data-Sizing convention flag that is used by the API’s unless
otherwise specified is CCRZ.ccAPI.SZ_M. This flag indicates that the medium sizing block
should be used for retrieving data, which includes the most commonly used fields and
related entities. For example, ccrz.ccServiceProduct.getProducts() will use the SZ_M sizing
block by default, unless another sizing block is specified as a parameter.
Salesforce
References: B2B Commerce and D2C Commerce Developer Guide, Data Sizing
Conventions
What is likely to happen if a developer leaves debug mode turned on in an environment?
A. The performance of the org will become slower each day
B. The user will begin getting JavaScript limit exceptions
C. The org will turn off debug mode after 72 hours
D. A banner will be displayed to the user indicating that the org is in debug mode
Explanation:
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 userindicating that the org is in debug mode, as debug
mode is a transparent setting that does not affect the user interface.Explanation:Explanation:
Salesforce
References: Lightning Web Components Developer Guide: Debug Your Code, Lightning
Web Components Developer Guide: JavaScript Limit ExceptionsExplanation:Explanation:
A developer is creating a component to implement a custom Terms and Conditions checkbox at checkout in the Aura Commerce template. Which method should the developer implement on the Lightning web component to ensure the user accepts the terms and conditions?
A. ComponentValidity
B. Validate
C. SaveCheckout
D. CheckValidity
Explanation:
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 Date 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 add 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 before
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 an 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 CommerceDeveloper Guide: Checkout Flow, B2B
Commerce Developer Guide: Checkout Order Object, Lightning Web Components
Developer Guide: Communicate with Properties
What should a developer's implementation code return if the External Prices are the same as Sales Prices for Products in the Cart?
A. sfde_checkout.IntegrationStatus. Status. SUCCESS
B. sfdc_checkout.IntegrationStatus. FAILED. Status
C. sfdc_checkout.IntegrationStatus.Status.FAILED
D. sfdc_checkout.IntegrationStatus.Success. STATUS
Explanation:
When implementing code for external pricing comparisons, if the external
prices are the same as the sales prices for products in the cart, the implementation should
ideally return a status indicating success (such as
sfdc_checkout.IntegrationStatus.Status.SUCCESS). This indicates that the external
pricing verification has passed and there are no discrepancies between the external and
sales prices.
| Page 9 out of 22 Pages |
| Previous |
Copyright © - All Rights Reserved