Updated Jan-2024 Exam Engine for B2B-Commerce-Developer Exam Free Demo & 365 Day Updates
Exam Passing Guarantee B2B-Commerce-Developer Exam with Accurate Quastions!
NEW QUESTION # 66
What is a best practice when passing query parameters from user interface to an apex controller?
- A. Query parameters should be properly sanitized by using JSINHTMLENCODE within the VisualForce Page or Component.
- B. Query parameters should be passed only to Salesforce B2B Commerce classes that you are extending.
- C. String parameters should be trimmed using String.trim().
- D. Query parameters should be stored on a backbone model prior to passing them to the server
Answer: A
NEW QUESTION # 67
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. Order Life Cycle Type was Managed
- B. The export job did not fully complete
- C. The user does not have rights to some of the records
- D. The Status was still set to Draft
Answer: D
Explanation:
Explanation
The most likely cause of why some orders were missing from the Data Loader export is that the Status was still set to Draft. The Status is a field on the Order Summary object that indicates the current state of theorder.
The Status can have values such as Draft, Submitted, Confirmed, or Cancelled. A Draft order is an order that has not been submitted or confirmed by the customer or the seller. A Draft order is not considered a completed or valid order and is not included in reports or exports. When using Data Loader to export data from an org, Data Loader will only include orders that have a Status other than Draft, such as Submitted or Confirmed. If an order has a Status of Draft, Data Loader will not include it in the CSV file, which may result in missing orders.
The export job did not fully complete is not a likely cause of why some orders were missing from the Data Loader export, as it is not related to the order status or data filtering. Order Life Cycle Type was Managed is not a likely cause either, as it is not related to the order status or data filtering. The Order Life Cycle Type is a field on the Order Summary object that indicates whether the order is managed by Salesforce Order Management or by an external system. The user does not have rights to some of the records is not a likely cause either, as it contradicts the fact that some orders were exported successfully. If the user did not have rights to some of the records, Data Loader would not be able to access or export any orders at all. Salesforce References: B2B Commerce Developer Guide: Order Summary Object, B2B Commerce Developer Guide:
Order Status Enum, Data Loader Guide: Export Data from Salesforce
NEW QUESTION # 68
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. Order Life Cycle Type was Managed
- B. The export job did not fully complete
- C. The user does not have rights to some of the records
- D. The Status was still set to Draft
Answer: D
Explanation:
The most likely cause of why some orders were missing from the Data Loader export is that the Status was still set to Draft. The Status is a field on the Order Summary object that indicates the current state of the order. The Status can have values such as Draft, Submitted, Confirmed, or Cancelled. A Draft order is an order that has not been submitted or confirmed by the customer or the seller. A Draft order is not considered a completed or valid order and is not included in reports or exports. When using Data Loader to export data from an org, Data Loader will only include orders that have a Status other than Draft, such as Submitted or Confirmed. If an order has a Status of Draft, Data Loader will not include it in the CSV file, which may result in missing orders. The export job did not fully complete is not a likely cause of why some orders were missing from the Data Loader export, as it is not related to the order status or data filtering. Order Life Cycle Type was Managed is not a likely cause either, as it is not related to the order status or data filtering. The Order Life Cycle Type is a field on the Order Summary object that indicates whether the order is managed by Salesforce Order Management or by an external system. The user does not have rights to some of the records is not a likely cause either, as it contradicts the fact that some orders were exported successfully. If the user did not have rights to some of the records, Data Loader would not be able to access or export any orders at all. Salesforce Reference: B2B Commerce Developer Guide: Order Summary Object, B2B Commerce Developer Guide: Order Status Enum, Data Loader Guide: Export Data from Salesforce
NEW QUESTION # 69
Which two statements are true regarding the cc_CallContext class in Salesforce B2B Commerce? (2 answers)
- A. The userLocale variable returns the current Locale for storefront.
- B. The Salesforce session is accessible via the getSession method
- C. The current storefront is accessible via thisclass
- D. The class can be used internally within Salesforce B2B Commerce and in subscriber code to access context level parameters
Answer: C,D
Explanation:
Explanation
The cc_CallContext class is a utility class that provides access to various context level parameters, such as the current storefront, user, cart, price list, currency, locale, and session. The class can be used internally within Salesforce B2B Commerce and in subscriber code to access these parameters. The current storefront is accessible via this class by using the getStorefront method, which returns a cc_Storefront__c object. The userLocale variable returns the current Locale for storefront, but it is not part of the cc_CallContext class. It is a global variable that can be accessed from any Visualforce page or component by using {!userLocale}. The Salesforce session is accessible via the getSession method, but it is not part ofthe cc_CallContext class either.
It is a method of the cc_SessionUtil class, which is another utility class that provides methods for managing sessions. Salesforce References: [B2B Commerce Developer Guide: cc_CallContext Class], [B2B Commerce Developer Guide: cc_SessionUtil Class]
NEW QUESTION # 70
Universal Containers (UC) is ready to build a tax provider class using the interfaces available in the Buyer Experience SDK. When creating a tax provider, what are three things that a developer should consider first?
- A. Steps to complete in the Tax Service
- B. What events to fire in the Lightning web component
- C. WhethertouseJSONorXML
- D. What to implement
- E. How to handle results
Answer: A,D,E
Explanation:
When creating a tax provider, three things that a developer should consider first are: steps to complete in the tax service, how to handle results, and what to implement. Steps to complete in the tax service are the actions that the developer needs to perform to connect to and use the third-party tax service provider's API or service. These steps may include authentication, authorization, request formatting, response parsing, error handling, and logging. How to handle results are the actions that the developer needs to perform to process and apply the tax calculation results from the tax service to the cart or order. These actions may include creating or updating cart items with type of Charge and charge type of Tax, applying tax adjustments or exemptions, and displaying tax amounts and details on the storefront. What to implement are the methods that the developer needs to define in their custom Apex class that implements the sfdc_checkout.TaxCalculations interface. The interface provides methods for customizing the tax calculation logic for a cart or an order, such as getTaxRatesAndRules, applyTaxAmountsAndAdjustments, and handleTaxErrorsAndExceptions. Whether to use JSON or XML is not something that the developer should consider first, as it is not a critical or relevant factor for creating a tax provider. It may depend on the format that the tax service provider supports or prefers, but it does not affect the overall functionality or performance of the tax integration. What events to fire in the Lightning web component is not something that the developer should consider first either, as it is not related to creating a tax provider. It may be an optional feature that the developer can add to enhance the user interface or user experience of their storefront, but it does not affect the core logic or functionality of the tax integration. Salesforce Reference: B2B Commerce Developer Guide: Tax Integration, [B2B Commerce Developer Guide: Tax Calculations Interface]
NEW QUESTION # 71
How are version related upgrades passed on to subscriber API extensions/overrides?
- A. Copy and paste of specific code is "built-in"
- B. Extensions and overridden APIs don't support-related upgrades.
- C. The "delegate" allows inherited method calls access to the most recentlyspecified service version
- D. APIs callback with specific versions specified; the user must know which version number to use.
Answer: C
Explanation:
Explanation
Version related upgrades are passed on to subscriber API extensions/overrides by using the "delegate" keyword, which allows inherited method calls access to the most recently specified service version. For example, delegate.getCart() will invoke the getCart() method of the latest service version that is available for the current storefront. This way, extensions and overrides can leverage the new features and enhancements of the upgraded service versions without modifying their code.
NEW QUESTION # 72
How does a project implement the process to persist payment information datain the Checkout flow for Salesforce B2B Commerce version 4.2 and beyond?
- A. Trigger the externalprocessedPayment and pass in the payment information object as an argument.
- B. Trigger a remote action when the process payment button is selected to capture the payment.
- C. Trigger the processPayment event and pass in the payment information object as an argument.
- D. Trigger a remote action to store the payment information in the URL query parameters.
Answer: C
Explanation:
Explanation
To persist payment information data in the Checkout flow for Salesforce B2B Commerce version 4.2 and beyond, the project needs to trigger the processPayment event and pass in the payment information object as an argument. This event will invoke the processPayment method of the ccServicePayment class, which will validate and process the payment information and return a payment result object. The payment result object will contain the status and details of the payment transaction.
NEW QUESTION # 73
Which event is invoked by any CCRZ Salesforce B2B CommeceView after the view is rendered?
- A. view:*:load
- B. view:*:onload
- C. view:*:rendered
- D. view:*:refresh
Answer: D
NEW QUESTION # 74
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 org will turn off debug mode after 72 hours
- C. The user will begin getting JavaScript limit exceptions
- D. A banner will be displayed to the user indicating that the org is in debug mode
Answer: C
Explanation:
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 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
NEW QUESTION # 75
How are variables bound when services use the ccSercviceDao classto execute queries?
- A. Global variables
- B. Apex local variables
- C. String substitution
- D. Apex class variables
Answer: C
Explanation:
Explanation
When services use the ccServiceDao class to execute queries, variables are bound by string substitution. This means that the query string contains placeholders for variables that are replaced by their values at runtime. For example, ccrz.ccServiceDao.getQuery('SELECT Id FROM Account WHERE Name = :name') will replace :name with the value of the name variable.
NEW QUESTION # 76
A user wants to leverage a three columnlayout on a page. The user also wants to move the mini-cart widget from the right to the center column. How can this requirement be fulfilled?
- A. Subscriber Template
- B. HandleBar Template Override
- C. Gross Layout Override
- D. Page Include
Answer: C
Explanation:
Explanation
To leverage a three column layout on a page and move the mini-cart widget from the right to the center column, the requirement can be fulfilled by creating a Gross Layout Override. This is a custom Visualforce page that overrides the default layout of a page and allows changing its structure and content. The user can create a Gross Layout Override that uses a three column layout and places the mini-cart widget in the center column. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Gross Layout Overrides
NEW QUESTION # 77
In which two ways can events fired from Lightning web components be handled?
- A. Adding callbacks to components
- B. Listening for all possible events at the document root
- C. Attaching handlers to DOM elements
- D. Programmatically adding event listeners
Answer: C,D
Explanation:
Two ways that events fired from Lightning web components can be handled are programmatically adding event listeners and attaching handlers to DOM elements. Programmatically adding event listeners is a way of handling events by using JavaScript code to register functions that are invoked when an event occurs. The developer can use methods such as addEventListener or @wire to add event listeners to components or services that fire events. Attaching handlers to DOM elements is a way of handling events by using HTML attributes to bind functions that are invoked when an event occurs. The developer can use attributes such as onclick or onchange to attach handlers to DOM elements that fire events. Adding callbacks to components is not a valid way of handling events fired from Lightning web components, as it is not related to event handling, but rather to asynchronous programming. Listening for all possible events at the document root is not a valid way either, as it is not efficient or recommended for event handling, as it can cause performance issues or conflicts with other event listeners. Salesforce Reference: [Lightning Web Components Developer Guide: Handle Events], [Lightning Web Components Developer Guide: Communicate with Events]
NEW QUESTION # 78
In which three different ways can a theme be enabled in
Salesforce B2B Commerce? (3 answers)
- A. A Storefront setting
- B. Dynamically through a hook
- C. A per user setting
- D. Account
- E. An Account Group field value
Answer: A,B,E
NEW QUESTION # 79
Which code statement should a developer use to import the ID of the current Lightning Experience
- A. import id from '@salesforce/community/ld'
- B. import id from '@salesforce/experience/ld'
- C. import id from '@salesforce/site/ld'
- D. import id from '@salesforce/network/ld'
Answer: A
Explanation:
Explanation
To import the ID of the current Lightning Experience community, a developer should use the following code statement:
import id from '@salesforce/community/Id';
The @salesforce/community module allows the developer to access information about the current community, such as its ID, name, URL, and base path. The other modules do not exist or are not related to the community ID. The @salesforce/network module is used to access information about the current network, such as its ID and name. The @salesforce/experience module is used to access information about the current user experience, such as whether it is standard or custom. The @salesforce/site module is used to access information about the current site, such as its name and prefix. Salesforce References: [Lightning Web Components Developer Guide: Import Community Information], [Lightning Web Components Developer Guide: Import Salesforce Modules]
NEW QUESTION # 80
What is true regarding adding more Configuration Settings
to Salesforce B2B Commerce?
- A. Metadata can be added to existing modules, but you cannot add new modules.
- B. Configuration settings can only be extended through API's
- C. Select "New"in your storefront's Configuration Settings and create a custom setting.
- D. More modules and metadata can be added to Salesforce B2B Commerce.
Answer: D
Explanation:
More modules and metadata can be added to Salesforce B2B Commerce by creating custom configuration settings. Configuration settings are custom settings that store various values and parameters that affect the functionality and appearance of the storefront. They are organized into modules, which group related settings together. To create a custom configuration setting, the user needs to create a custom setting record in Salesforce and specify its module, name, value, and description. The custom setting will then appear in CCAdmin under the specified module. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Configuration Settings
NEW QUESTION # 81
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)
- A. The APEX method called by the remote action will be passed as a Salesforce B2B Commerce context object.
- B. Salesforce B2B Commerce includes do not support standard SalesForce remote actions.
- C. The Salesforce B2B Commerce logger cannot be utilized in standard remote actions
- D. A standard remote action will not have access to Salesforce B2B Commerce objects.
Answer: A,C
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.
NEW QUESTION # 82
A developer attempts to export data from an org by launching Data Loader, selecting a standard entity, clicking the "Select All Fields" button and clicking the Finish button. The developer finds that the CustomField_c field they added to the entity has no values under the header in the CSV file output. What is the root cause?
- A. The field is not populated
- B. The developer does not have the correct JDK that is recommended by Salesforce and this is known to cause issues with exporting custom attributes
- C. The user does not have rights to the custom field
- D. The developer does not have access to the object's metadata
Answer: C
Explanation:
The root cause of why the CustomField__c field they added to the entity has no values under the header in the CSV file output is that the user does not have rights to the custom field. A user's access to a field is determined by their profile and permission sets, which define their field-level security settings. Field-level security settings control whether a user can see, edit, or delete the value for a particular field on an object. If a user does not have access to a field, they will not be able to view or modify its value in any interface, including Data Loader. Data Loader is a tool that allows users to import or export data between Salesforce and CSV files. When using Data Loader to export data from an org, Data Loader will only include fields that are accessible to the user based on their field-level security settings. If a user does not have access to a field, Data Loader will not include that field in the CSV file, neither as a column header nor as a value. The developer does not have the correct JDK that is recommended by Salesforce and this is known to cause issues with exporting custom attributes is not the root cause of why CustomField__c has no values under the header in the CSV file output, as it is not related to field access or Data Loader functionality. The developer does not have access to the object's metadata is not the root cause either, as it is not related to field access or Data Loader functionality. The object's metadata defines its structure and properties, such as fields, relationships, and layouts. The field is not populated is not the root cause either, as it contradicts the fact that CustomField__c has no column header in the CSV file output. If the field was not populated but accessible to the user, Data Loader would still include CustomField__c as a column header in the CSV file, but leave its values blank. Salesforce Reference: Data Loader Guide: Export Data from Salesforce, [Data Loader Guide: Field Mapping], [Salesforce Help: Set Field-Level Security]
NEW QUESTION # 83
What are two ways a developer should ensure that a store verifies changes by using an external service?
- A. Create an Apex class to retrieve shipping charges from an external service and update the Cart Delivery Group Method.
- B. Create an Apex class implementing the sfdc_checkout.CartShippingCharges interface to retrieve shipping charges from an external service and register it as the .. calculation integration in the store administration.
- C. Create a flow using an action to retrieve shipping charges from an external service and update the Cart Delivery Group Methods.
- D. Create a trigger to retrieve shipping charges from an external service and update the Cart Delivery, Group Methods
Answer: A,B
Explanation:
Explanation
To verify changes by using an external service, a developer can use either of these two ways:
* Create an Apex class that implements the sfdc_checkout.CartShippingCharges interface and defines the getShippingCharges method. This method takes a Cart object as an input parameter and returns a list of CartDeliveryGroupMethod objects with the updated shipping charges. The developer then needs to register the Apex class as the Shipping Calculation Integration in the store administration. This way, the store can call the external service to calculate the shipping charges for each delivery group in the cart.
* Create an Apex class that defines a method to retrieve the shipping charges from an external service and update the Cart Delivery Group Method object. The developer then needs to invoke this method from a trigger on the Cart Delivery Group Method object. This way, the store can update the shipping charges whenever the delivery group method is inserted or updated.
The other options are not valid ways to verify changes by using an external service. Creating a flow using an action is not supported for B2B Commerce, and creating a trigger on the Cart Delivery Group object will not update the shipping charges for each delivery group method. References:
* Integrate with External Services
* CartShippingCharges Interface
* CartDeliveryGroupMethod Object
NEW QUESTION # 84
In which three ways should useful debugging information in Salesforce B2B Commerce implementation be garnered? (3 answers) A) Enabling the logging token via
- A. Admin andsubsequently inspecting the logs via the browser console.
- B. Enabling debugging options for the current user and visually inspecting the Salesforce debug logs.
- C. Logging into the community as a system administrator to identify any potential permissions or Visualforce exceptions.
- D. Placing a System.debug() statement anywhere in the class being debugged.
- E. Logging a case with Salesforce support to enable advanced debugging options.
Answer: A,B,C
Explanation:
Explanation
Useful debugging information in Salesforce B2B Commerce implementation can be garnered in three ways:
* Enabling the logging token via Admin and subsequently inspecting the logs via the browser console.
This will enable logging messages and errors to the browser console, which can be viewed by opening the Developer Tools in the browser. The logging token can be enabled by setting the value of CO.logToken to true in CCAdmin.
* Enabling debugging options for the current user and visually inspecting the Salesforce debug logs. This will enable logging messages and errors to the Salesforce debug logs, which can be viewed by opening the Debug Logs page in Salesforce Setup. The debugging options can be enabled by creating a Debug Level and a Trace Flag for the current user in Salesforce Setup.
* Logging into the community as a system administrator to identify any potential permissions or Visualforce exceptions. This will allow viewing any errors or warnings that may occur on the community pages due to insufficient permissions or Visualforce issues. The system administrator can also access CCAdmin and other tools from within the community. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Logging, Debug Your Code
NEW QUESTION # 85
Which method signature is used in the Global API's?
- A. ccrz.cc_Output (ccrz:cc_Input input)
- B. List<List<Object>>
- C. Changes based on API and Method name
- D. Map<String, Object>
Answer: A
Explanation:
The method signature that is used in the Global API's is ccrz.cc_Output (ccrz.cc_Input input). This signature indicates that the Global API methods take a single input parameter of type ccrz.cc_Input and return an output of type ccrz.cc_Output. These are custom classes that are defined in the cloudcraze managed package and contain various properties and methods for handling the input and output data. For example, ccrz.ccServiceProduct.getProducts(ccrz.cc_Input input) is a Global API method that takes an input object and returns an output object containing product data. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, API Classes, cc_Input Class, cc_Output Class
NEW QUESTION # 86
Which format is the custom Salesforce field with the API name
"My_Fiels_Name__c" transformed onto by default in Salesforce B2B Commerce?
- A. myfieldname
- B. MyFieldName
- C. myFieldName
- D. My_Field_Name__c
Answer: C
NEW QUESTION # 87
A developer is trying to troubleshoot why a field is not displaying on the Product Detail Page. What should be typed in the Developer Tools Console in the browser to view the fields available for the Product Detail Page?
- A. CCRZ.cartView
- B. CCRZ.productDetailModel
- C. CCRZ.productDetailView
- D. CCRZ.productSearchView
Answer: B
Explanation:
To view the fields available for the Product Detail Page, the developer should type CCRZ.productDetailModel in the Developer Tools Console in the browser. This will display the product detail model object, which contains the product data and attributes that are rendered on the page. The other options are either not valid or not relevant for the Product Detail Page.
NEW QUESTION # 88
What is default behavior for how theSalesforce B2B Commerce Global APIs transform Salesforce data?
- A. Fields names are returned with a lowercase first letter,camelcase convention
- B. Fields names can be mapped to any naming convention desired
- C. Fields names are returned using the Salesforce naming convention.
- D. Fields names are returned with prepended in their name.
Answer: A
Explanation:
Explanation
The default behavior for how the Salesforce B2B Commerce Global APIs transform Salesforce data is to return field names with a lowercase first letter, camelcase convention. For example, the field nameccrz__E_Product__c in Salesforce will be transformed to eProduct in the API. This is done to follow the JavaScript naming convention and to avoid conflicts with the standard Salesforce fields and relationships.
Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Query Transformation
NEW QUESTION # 89
......
Exam Questions for B2B-Commerce-Developer Updated Versions With Test Engine: https://www.premiumvcedump.com/Salesforce/valid-B2B-Commerce-Developer-premium-vce-exam-dumps.html
Test Engine to Practice Test for B2B-Commerce-Developer Valid and Updated Dumps: https://drive.google.com/open?id=1xNaYWsPrwYljRMPdMamjZJCZ1hbkP9Nm