Pass Salesforce Developer B2B-Commerce-Developer exam [Dec 25, 2023] Updated 142 Questions
Salesforce B2B-Commerce-Developer Actual Questions and 100% Cover Real Exam Questions
Salesforce B2B-Commerce-Developer Certification Exam is an accreditation that is designed for individuals who wish to demonstrate their proficiency in developing and implementing solutions within the Salesforce B2B Commerce platform. Salesforce Accredited B2B Commerce Developer certification is ideal for developers who specialize in building B2B Commerce solutions and are looking to enhance their skills and knowledge in this field. Salesforce Accredited B2B Commerce Developer certification exam evaluates the candidate's understanding of the B2B Commerce platform, its features, and its capabilities.
NEW QUESTION # 63
Which wire adapter should a developer use to retrieve metadata about a specific picklist?
- A. getPicklistMetadataValues
- B. getPicklistValues
- C. getPicklist
- D. getPicklistMetadata
Answer: B
Explanation:
To retrieve metadata about a specific picklist, a developer should use the getPicklistValues wire adapter. The getPicklistValues wire adapter imports data from the @salesforce/ui-api module and returns an object that contains information such as the picklist's label, value, default value, validity, and controlling field values. The getPicklistMetadataValues wire adapter does not exist. The getPicklistMetadata wire adapter does not exist either. The getPicklist wire adapter does not exist either. Salesforce Reference: [Lightning Web Components Developer Guide: getPicklistValues], [Lightning Web Components Developer Guide: Import User Interface API]
NEW QUESTION # 64
In checkout, what event should the developer's code listen for in order to help troubleshoot and respond to actions?
- A. CommerceErrorEvents
- B. CommerceDiagnosticEvents
- C. CommerceActionEvents
- D. CommerceBubbleEvents
Answer: B
Explanation:
To help troubleshoot and respond to actions in checkout, the developer's code should listen for CommerceDiagnosticEvents. CommerceDiagnosticEvents is an event that is fired by Salesforce B2B Commerce when an error occurs in the storefront. CommerceDiagnosticEvents contains information about the error, such as error code, error message, error type, and error details. CommerceDiagnosticEvents can be subscribed by other components or services that want to handle or display the error information in different ways. The developer's code can listen for CommerceDiagnosticEvents using an aura:handler tag in Aura Components or an @wire decorator in Lightning web components. The developer's code can also use the event information to perform custom logic or actions based on the error, such as logging, reporting, or notifying. CommerceBubbleEvents is not an event that the developer's code should listen for in checkout, as it is not related to troubleshooting or responding to actions. CommerceBubbleEvents is an event that is fired by Salesforce B2B Commerce when a user interacts with a bubble component in the storefront. A bubble component is a user interface element that displays information or options in a pop-up window when clicked or hovered over. CommerceBubbleEvents contains information about the user interaction, such as bubble name, bubble type, and bubble value. CommerceErrorEvents is not an event that the developer's code should listen for in checkout either, as it is not related to troubleshooting or responding to actions. CommerceErrorEvents is an event that is fired by Salesforce B2B Commerce when a validation error occurs in the storefront. CommerceErrorEvents contains information about the validation error, such as field name, field label, and error message. CommerceActionEvents is not an event that the developer's code should listen for in checkout either, as it is not related to troubleshooting or responding to actions. CommerceActionEvents is an event that is fired by Salesforce B2B Commerce when a user performs an action in the storefront. CommerceActionEvents contains information about the user action, such as action name, action type, and action parameters. Salesforce Reference: B2B Commerce Developer Guide: Handle Errors, B2B Commerce Developer Guide: Handle User Interactions with Bubble Components, B2B Commerce Developer Guide: Handle Validation Errors, B2B Commerce Developer Guide: Handle User Actions
NEW QUESTION # 65
A user wants the pricing to reflect the price values stored in an external ERP during the checkout flow. In what way can this requirement be satisfied?
- A. Override the computePricingCart methos in ccrz.cc_api_CartExtension and make the callout in this method.
- B. None of the above
- C. Override the computePricingReview method in ccrz.cc_CartExtension and make the callout in this method.
- D. Override the computePricingCart method in ccrz.cc_api_PriceAdjustoment and make the callout in this method.
Answer: B
NEW QUESTION # 66
Which cart item type is created with the Cart Delivery Group Method after the shipping integration?
- A. Charge
- B. Surcharge
- C. Delivery
- D. Shipping
Answer: A
Explanation:
A cart item with a type of Charge is created with the Cart Delivery Group Method after the shipping integration. A shipping integration is an integration that calculates and applies shipping costs and options to a cart or an order based on various factors, such as product weight, dimensions, quantity, location, and carrier service level. A shipping integration can use either an external shipping service provider or custom Apex code to perform the shipping calculation. The Cart Delivery Group Method is a method that determines how products are grouped into delivery groups based on their shipping methods and addresses. A delivery group is a logical grouping of products that are shipped together using the same shipping method and address. After performing the shipping calculation for each delivery group, the shipping integration creates a cart item with a type of Charge and a charge type of Shipping for each delivery group. These cart items represent the shipping costs and options that are applied to each delivery group. A cart item with a type of Surcharge, Shipping, or Delivery does not exist or is not related to the shipping integration. Salesforce Reference: [B2B Commerce Developer Guide: Shipping Integration], [B2B Commerce Developer Guide: Cart Delivery Group Method]
NEW QUESTION # 67
What are three advantages of using ccLog over the Salesforce
standard System.debug class? (3 answers)
- A. There is no need to create a User Trace Flag.
- B. ccLog can debug syntax errors found in the JavaScript.
- C. There is no need to use string concatenation to easily tag log statements with a subject.
- D. Append #ccLog=<Logging Token Name> to the end of the storefront URL in order to get logs in the inspector console.
- E. There is no need to manually set a cookie to debug with the Site Guest User.
Answer: C,D,E
Explanation:
Three advantages of using ccLog over the Salesforce standard System.debug class are:
There is no need to use string concatenation to easily tag log statements with a subject. ccLog allows passing a subject parameter to the log method, which will prepend the subject to the log message. For example, ccLog.log('This is a message', 'Subject') will log [Subject] This is a message.
There is no need to create a User Trace Flag. ccLog can be enabled by setting the value of CO.logToken to true in CCAdmin, which will activate logging for all users who access the storefront.
There is no need to manually set a cookie to debug with the Site Guest User. ccLog can be enabled for the Site Guest User by appending #ccLog=<Logging Token Name> to the end of the storefront URL in order to get logs in the inspector console. For example, https://my-storefront.com/#ccLog=debug will enable logging for the Site Guest User with the debug level. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Logging
NEW QUESTION # 68
Although Salesforce B2B Commerce and Salesforce recommend against using
"without sharing classes" whenever possible, sometimes it is unavoidable. Which three items will open up a major security hole? (3 answers)
- A. Executing dynamic SOQL inside a without sharing class with a bind variable from ccAPI.CURRENT_VERSION.
- B. Executing dynamic SOQL inside a without sharing class with a bind variable from cc_RemoteActionContentex class.
- C. Executing dynamic SOQL inside a without sharing class with a bind variable from PageReference.getParameters().
- D. Executing dynamic SOQL inside a without sharing class with a bind variable from the UserInfo class.
- E. Executing dynamic SOQL inside a without sharing class with a bind variable from PageReference.getCookies().
Answer: B,C,E
NEW QUESTION # 69
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. My_Field_Name__c
- D. myfieldname
Answer: A
Explanation:
The format that the custom Salesforce field with the API name My_Field_Name__c is transformed onto by default in Salesforce B2B Commerce is myFieldName. This is done to follow the JavaScript naming convention and to avoid conflicts with the standard Salesforce fields and relationships. The transformation rules are as follows:
Remove any namespace prefix from the field name, such as ccrz__ or cloudcraze__.
Remove any underscores from the field name and capitalize the first letter of each word after an underscore, such as MyFieldName.
Lowercase the first letter of the field name, such as myFieldName. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Query Transformation
NEW QUESTION # 70
How are variables bound when services use the ccSercviceDao class to execute queries?
- A. Apex local variables
- B. String substitution
- C. Global variables
- D. Apex class variables
Answer: D
NEW QUESTION # 71
Which three attributes are true regarding Subscriber pages? (3 answers)
- A. Out of the Box, Subscriber Pages are completely blank HTML pages.
- B. Standard Salesforce B2B Commerce components are automatically included on the page e.g. Header links, images, menu items, containers, etc.
- C. Subscriber pages can include additional standard Salesforce B2B Commerce components such as featured products, category tree, and mini cart.
- D. Subscriber pages allow customers to quickly create new custom pages for their storefront.
- E. All the user interface components must be createdmanually.
Answer: A,C,D
Explanation:
Three attributes that are true regarding Subscriber Pages are:
Subscriber Pages can include additional standard Salesforce B2B Commerce components such as featured products, category tree, and mini cart. These components can be added to the Subscriber Pages by using the CCRZ.pagevars.pageLabels and CCRZ.pagevars.pageSections objects, which contain the page labels and page sections that are defined in CCAdmin.
Subscriber Pages allow customers to quickly create new custom pages for their storefront. These pages can be used to display any content or functionality that is not available in the default pages, such as FAQs, testimonials, or promotions.
Out of the Box, Subscriber Pages are completely blank HTML pages. These pages do not have any predefined layout or content, so the user can customize them according to their requirements. The user can use Visualforce, HTML, CSS, JavaScript, or any other web technologies to create their own Subscriber Pages. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Subscriber Pages
NEW QUESTION # 72
Which two statements are true about Global API's in Salesforce B2B Commerce? (2 answers)
- A. Each global API method takes in a Map<String, Object> as a single parameter and returns a Map<String, Object>
- B. Global APIs are versioned.
- C. Global APIs will catch any Exceptions that are thrown as part of missing parameters.
- D. Global APIs will handle Transaction scope, and the Subscriber calling it does not need to handle scope.
Answer: A,B
NEW QUESTION # 73
What is default behavior for how theSalesforce B2B Commerce Global APIs transform Salesforce data?
- A. Fields names can be mapped to any naming convention desired
- B. Fields names are returned using the Salesforce naming convention.
- C. Fields names are returned with a lowercase first letter,camelcase convention
- D. Fields names are returned with ;c." prepended in their name.
Answer: C
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 name ccrz__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 Reference: B2B Commerce and D2C Commerce Developer Guide, Query Transformation
NEW QUESTION # 74
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 a remote action when the process payment button is selected to capture the payment.
- B. Trigger a remote action to store the payment information in the URL query parameters.
- C. Trigger the externalprocessedPayment and pass in the payment information object as an argument.
- D. Trigger the processPayment event and pass in the payment information object as an argument.
Answer: D
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 # 75
What are two considerations to keep in mind when including additional JavaScript files in a Lightning web component?
- A. Additional JavaScript files should be minified before deployment
- B. A module can export named functions or variables
- C. The files must be ES6 modules and must have names that are unique within the component's folder.
- D. Each additional file needs a corresponding .js-meta.xml file.
Answer: B,C
Explanation:
When including additional JavaScript files in a Lightning web component, a developer should keep in mind two considerations: the files must be ES6 modules and must have names that are unique within the component's folder and a module can export named functions or variables. The files must be ES6 modules because LWC uses ES6 modules as the standard for modular JavaScript code. The files must have names that are unique within the component's folder because LWC uses the file name as the module identifier and does not allow duplicate identifiers. A module can export named functions or variables because LWC supports named exports, which allow a module to export multiple values with different names. Each additional file does not need a corresponding .js-meta.xml file, as this is only required for the main JavaScript file of the component. Additional JavaScript files should not be minified before deployment, as this is not necessary or recommended for LWC. Salesforce Reference: [Lightning Web Components Developer Guide: Include JavaScript Files], [Lightning Web Components Developer Guide: ES6 Modules]
NEW QUESTION # 76
Which three attributes are true regarding Subscriber pages? (3 answers)
- A. Out of the Box, Subscriber Pages are completely blank HTML pages.
- B. Subscriber pages can include additional standard Salesforce B2B Commerce components such as featured products, category tree, and mini cart.
- C. Subscriber pages allow customers to quickly create new custom pages for their storefront.
- D. Standard Salesforce B2B Commerce components are automatically included on the page e.g. Header links, images, menu items, containers, etc.
- E. All the user interface components must be created manually.
Answer: B,C,D
NEW QUESTION # 77
In which three ways can Salesforce B2B Commerce API sizing blocks support multiple API sizing requests? (3 answers)
- A. SZ_ASSC is used.
- B. The sizing block is removed after the first handler.
- C. SZ_ASSC is not used.
- D. When different entities are specified in the method invocation.
- E. The sizing block is not removed.
Answer: B,C,D
NEW QUESTION # 78
......
Salesforce is a renowned cloud-based software company that provides various services such as customer relationship management (CRM) and enterprise resource planning (ERP) systems. The company offers a wide range of certifications for professionals to validate their skills and knowledge in different areas. One of these certifications is the Salesforce Accredited B2B Commerce Developer Certification, also known as the Salesforce B2B-Commerce-Developer Certification Exam.
Salesforce B2B-Commerce-Developer Real 2023 Braindumps Mock Exam Dumps: https://www.examtorrent.com/B2B-Commerce-Developer-valid-vce-dumps.html
B2B-Commerce-Developer Free Exam Questions and Answers PDF Updated on Dec-2023: https://drive.google.com/open?id=1f_Om-1t8-4PoBDlWZ3oldF0FG0Hh5tnv
