ExamGecko
Home Home / Salesforce / Certified B2B Commerce Developer

Salesforce Certified B2B Commerce Developer Practice Test - Questions Answers, Page 19

Question list
Search
Search

List of questions

Search

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
A.
lightning_FlowScreen
Answers
B.
lightning__CheckoutFlow
B.
lightning__CheckoutFlow
Answers
C.
Iwe__FlowComponent
C.
Iwe__FlowComponent
Answers
D.
lwe__flow
D.
lwe__flow
Answers
Suggested answer: C

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 interface does a developer have to implement to override Inventory in Checkout?

A.
sfdc_commerce.ValidationCartinventory
A.
sfdc_commerce.ValidationCartinventory
Answers
B.
sfdc_commerce.CartinventoryValidation
B.
sfdc_commerce.CartinventoryValidation
Answers
C.
sfdc_checkout.InventoryCartVvalidation
C.
sfdc_checkout.InventoryCartVvalidation
Answers
D.
sfdc_checkout.CartinventoryValidation
D.
sfdc_checkout.CartinventoryValidation
Answers
Suggested answer: D

Explanation:

To override inventory in the checkout process, a developer must implement the sfdc_checkout.CartinventoryValidation interface. This interface provides the necessary methods for custom inventory validation logic, allowing developers to define how inventory checks are conducted during the checkout process. Salesforce documentation on extending and customizing the checkout functionality in B2B Commerce would include guidance on implementing this interface to meet specific inventory validation requirements.

A developer is implementing an Inventory class for checkout. All the error states have been handled and now the developer needs to take the next step to indicate that inventory is available for all of the items and amounts in the cart. What should the next step be?

A.
Return TRUE
A.
Return TRUE
Answers
B.
Return sfde_checkout.InventoryStatus. SUCCESS
B.
Return sfde_checkout.InventoryStatus. SUCCESS
Answers
C.
Return sfdc_checkout.IntegrationStatus. Status. SUCCESS
C.
Return sfdc_checkout.IntegrationStatus. Status. SUCCESS
Answers
D.
Return sfdc_checkout.InventoryStatus.Status. SUCCESS
D.
Return sfdc_checkout.InventoryStatus.Status. SUCCESS
Answers
Suggested answer: D

Explanation:

When implementing an Inventory class for checkout and indicating that inventory is available for all items and amounts in the cart, the correct step is to return sfdc_checkout.InventoryStatus.Status.SUCCESS. This indicates to the checkout process that the inventory check has passed and the items are available. Salesforce documentation on customizing inventory validation in the checkout process would detail the expected return types and values, ensuring that developers implement the inventory checks in a manner consistent with the platform's requirements.

What happens to all previous tax entries during tax implementation?

A.
Modified with the new Tax calculation
A.
Modified with the new Tax calculation
Answers
B.
They are deleted from the Cart
B.
They are deleted from the Cart
Answers
C.
Saved prior to recalculation
C.
Saved prior to recalculation
Answers
D.
Ignored with the recalculation
D.
Ignored with the recalculation
Answers
Suggested answer: C

Explanation:

In general best practices for tax implementation in systems like Salesforce B2B Commerce, previous tax entries are usually preserved or saved before any recalculation is performed. This ensures that there is a record of the original tax calculations before any modifications, which can be crucial for auditing, historical data integrity, and in case the new tax calculation needs to be rolled back for any reason.

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
A.
sfde_checkout.IntegrationStatus. Status. SUCCESS
Answers
B.
sfdc_checkout.IntegrationStatus. FAILED. Status
B.
sfdc_checkout.IntegrationStatus. FAILED. Status
Answers
C.
sfdc_checkout.IntegrationStatus.Status.FAILED
C.
sfdc_checkout.IntegrationStatus.Status.FAILED
Answers
D.
sfdc_checkout.IntegrationStatus.Success. STATUS
D.
sfdc_checkout.IntegrationStatus.Success. STATUS
Answers
Suggested answer: A

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.

A developer is writing custom code to compare External Prices and Sales Prices for cart items. What should be returned if the External Prices are the same as Sales Prices for Products in the Cart? ~.

A.
sfdc_checkout.IntegrationStatus.Status.SUCCESS
A.
sfdc_checkout.IntegrationStatus.Status.SUCCESS
Answers
B.
sfdc_checkout.IntegrationStatus.Status.SUCCEEDED
B.
sfdc_checkout.IntegrationStatus.Status.SUCCEEDED
Answers
C.
sfdc_checkout.IntegrationStatus.Status.ERROR
C.
sfdc_checkout.IntegrationStatus.Status.ERROR
Answers
D.
sfdc_checkout.IntegrationStatus.Success.FAILED
D.
sfdc_checkout.IntegrationStatus.Success.FAILED
Answers
Suggested answer: A

Explanation:

Similar to question 198, when custom code compares external prices with sales prices for cart items and finds them to be the same, the appropriate return value should indicate a successful comparison (such as sfdc_checkout.IntegrationStatus.Status.SUCCESS). This signifies that the external prices are aligned with the sales prices, and there are no conflicts.

Universal Containers (UC) needs to display data from standard objects (entities) in a different format than what comes with B2B Commerce out of the box. In doing this, what is one advantage of using the Lightning Data

Service vs using a custom Controller class?

A.
Lightning Data Service translates the developer's component implementation to a VisualForce page for backward compatibility.
A.
Lightning Data Service translates the developer's component implementation to a VisualForce page for backward compatibility.
Answers
B.
JavaScript proxies for transport objects are created in the developer's IDE automatically.
B.
JavaScript proxies for transport objects are created in the developer's IDE automatically.
Answers
C.
The developer can read, create, or modify single records or metadata without writing Apex code.
C.
The developer can read, create, or modify single records or metadata without writing Apex code.
Answers
D.
There is a Visual Studio add-in that accelerates the layout process
D.
There is a Visual Studio add-in that accelerates the layout process
Answers
Suggested answer: C

Explanation:

Lightning Data Service (LDS) is a Salesforce UI API layer that empowers developers to perform CRUD operations and manage Salesforce data without the need for custom Apex controllers. LDS is designed to improve performance, user interface consistency, and developer productivity by handling data operations and sharing rules, thus reducing the need for server-side code. For more details, refer to the Salesforce documentation on Lightning Data Service: Salesforce Lightning Data Service Documentation.

Which HTML element can be used as a root tag for a Lightning Web Component's HTML file?

A.
<body>
A.
<body>
Answers
B.
<article>
B.
<article>
Answers
C.
<html>
C.
<html>
Answers
D.
<template>
D.
<template>
Answers
Suggested answer: D

Explanation:

In Lightning Web Components (LWC), the root tag for the component's HTML file must be <template>. This tag defines the markup structure for the component and is essential for the LWC framework to correctly render the component in the Salesforce Lightning Experience. The <template> tag is unique to LWC and is not interchangeable with standard HTML tags like <body>, , or <html>. For more information, see the Salesforce LWC documentation: Salesforce LWC HTML Templates Documentation.

A developer is attempting to write a Lightning Web component from scratch by first creating the HTML markup and receives an error. Which three tags when used as the first element in the file would produce an error?

A.
<template>
A.
<template>
Answers
B.
<article>
B.
<article>
Answers
C.
<body>
C.
<body>
Answers
D.
<html>
D.
<html>
Answers
Suggested answer: B, C, D

Explanation:

In a Lightning Web Component's HTML file, using , <body>, or <html> as the first (root) element would produce an error because the LWC framework requires <template> as the root tag. The <template> tag is necessary for defining the component's structure and supports the framework's reactive and rendering capabilities. The use of other HTML tags as the root element is not supported and will result in an error during component compilation or runtime. Refer to the Salesforce LWC documentation for proper component structure: Salesforce LWC Component Structure Documentation.

A dev at Northern Trail Outfitters (NTO) exported Order Summary records via Data Loader, but noticed that some orders were missing. What is the most likely cause?

A.
Status was not in Created
A.
Status was not in Created
Answers
B.
Billing Contact was missing
B.
Billing Contact was missing
Answers
C.
Original Order information was missing
C.
Original Order information was missing
Answers
D.
Order Life Cycle Type was Managed
D.
Order Life Cycle Type was Managed
Answers
E.
Currency mapping was not done correctly
E.
Currency mapping was not done correctly
Answers
Suggested answer: A

Explanation:

When exporting Order Summary records via Data Loader, if some orders are missing, a common cause could be that those orders did not have a status that was included in the export criteria, such as 'Created'. Salesforce data exports can be filtered based on specific criteria, and if the status of some orders doesn't match the criteria, those orders will not be included in the export. The other options listed are less likely to be direct causes for missing orders in an export operation. For more information on using Data Loader and understanding export criteria, refer to the Salesforce Data Loader Guide: Salesforce Data Loader Guide.

Total 221 questions
Go to page: of 23