Salesforce B2B-Commerce-Developerリアル試験問題解答は無料
試験問題集でB2B-Commerce-Developer練習無料最新のSalesforce練習テスト
Salesforce B2B-Commerce-Developer 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
Salesforce B2B-Commerce-Developer試験は、Salesforce B2B Commerceプラットフォームに特化したい開発者にとって不可欠な認証です。この認定は、Salesforceプラットフォームを使用して革新的で効率的なB2B Commerce Solutionsの作成を希望する開発者のスキルと知識をテストするように設計されています。この認定は、Salesforceプラットフォームと協力し、B2B Commerceの概念を十分に理解している開発者を対象としています。
質問 # 23
Where is the API-based record creation generally handled in Salesforce B2B Commerce?
- A. Logic classes that implement the businesslogic for create operations
- B. In the methods available in extension hooks
- C. The service-layer responsible for the entity
- D. Data creation is not allowed
正解：C
解説：
The API-based record creation is generally handled in the service-layer responsible for the entity in Salesforce B2B Commerce. The service-layer is a set of classes that provide methods for interacting with the data layer and performing business logic. Each entity, such as product, cart, or order, has a corresponding service class that handles the create, read, update, and delete operations for that entity. For example, ccrz.ccServiceProduct provides methods for creating and retrieving products. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Service Classes
質問 # 24
Which three components should a developer use on the product page to replace the out-of-the-box Product Detail Card component?
- A. Product Field Long component
- B. Product Detail Breadcrumbs component
- C. Product Detail Purchase Options component
- D. Product Fields Short component
- E. Product Detail Image Gallery component
正解：D
解説：
Explanation
The Product Detail Card component is a standard component that displays the product information and options on the product page. It includes the following elements1:
* The product's SKU
* The product's unit of measure
* The product's available inventory, or a generic availability message, if specified
* The product's short description
* The product's price information
* The product's quantity selector
* The product's add to cart button
* The product's image gallery
To replace this component with custom components, a developer can use the following three components:
* Product Fields Short component: This component displays the product's short description, SKU, unit of measure, and price information. It also allows the developer to specify which fields to display and how to format them2.
* Product Field Long component: This component displays the product's long description, which can include rich text and images. It also allows the developer to specify which field to display and how to format it2.
* Product Detail Image Gallery component: This component displays the product's image gallery, which can include multiple images and thumbnails. It also allows the developer to specify the image field, the image size, and the image zoom option3.
These three components can be combined to create a custom product page that shows the product information and options in a different layout and style than the out-of-the-box Product Detail Card component.
References: Configure Product Info and Options on the Product Detail Page, Product Fields Short Component, Product Detail Image Gallery Component
質問 # 25
Where are handlebar Templates defined in the Cloudcraze managed package?
- A. Configuration Setting configuration
- B. Page Settings configuration
- C. uiProperties file
- D. cc_hk_UserInterface extension
正解：C
質問 # 26
Based on error emails flowing in, a developer suspects that recent edits made to a checkout flow have created a defect. The developer has data points available to use as inputs in reproducing the scenario.
What should the developer do next?
- A. Open the flow, select Debug, provide the Input values, and select Run.
- B. Open the flow, select Debug, provide the session ID for replay, and select Run.
- C. Open the flow, select Debug with Inputs, provide the Input values, and select Run.
- D. Open the flow, select Attach to Live Session, provide the session ID, and select Attach.
正解：A
解説：
The next step that the developer should do after suspecting that recent edits made to a checkout flow have created a defect and having data points available to use as inputs in reproducing the scenario is to open the flow, select Debug, provide the Input values, and select Run. A flow is a type of application that automates a business process by collecting data and performing actions in Salesforce or an external system. A flow can be used to customize the checkout process in the storefront by defining the steps and logic that are executed when a customer places an order. A flow can be edited or modified using Flow Builder, a point-and-click tool that allows developers to create and manage flows. Flow Builder also provides debugging and testing tools that allow developers to run and troubleshoot flows before deploying them. To debug or test a flow, the developer can open the flow in Flow Builder, select Debug from the toolbar, provide the Input values for the flow variables, and select Run. This will execute the flow in debug mode, which simulates how the flow runs in the org with real data. The developer can use debug mode to verify if the flow works as expected or if there are any errors or issues with the flow logic or actions. Open the flow, select Attach to Live Session, provide the session ID, and select Attach is not a valid next step, as it is not a feature or option available in Flow Builder or Salesforce CLI. Attach to Live Session is a feature that allows developers to attach a debugger to a running Apex session and inspect the state of the code execution. Open the flow, select Debug with Inputs, provide the Input values, and select Run is not a valid next step either, as it is not a feature or option available in Flow Builder or Salesforce CLI. Debug with Inputs is a feature that allows developers to debug an Apex class or trigger with predefined input values and breakpoints. Open the flow, select Debug, provide the session ID for replay, and select Run is not a valid next step either, as it is not a feature or option available in Flow Builder or Salesforce CLI. Replay is a feature that allows developers to replay an Apex log file and inspect the state of the code execution at each line. Salesforce Reference: [B2B Commerce Developer Guide: Customize Checkout Flows], [Salesforce Help: Flow Builder], [Salesforce Help: Debug Your Flows], [Salesforce Developer Blog: Apex Replay Debugger]
質問 # 27
What are three advantages of using ccLog over the Salesforce
standard System.debug class? (3 answers)
- A. ccLog can debug syntax errors found in the JavaScript.
- B. There is no need to manually set a cookie to debug with the Site Guest User.
- C. There is no need to create a User Trace Flag.
- 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 use string concatenation to easily tag log statements with a subject.
正解：B、D、E
解説：
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
質問 # 28
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 fromcc_RemoteActionContentex class.
- B. Executing dynamic SOQL inside a without sharing class with a bind variable fromPageReference.getParameters().
- C. Executing dynamic SOQL inside a without sharing class with a bind variable fromPageReference.getCookies().
- D. Executing dynamic SOQL inside a without sharing class with a bind variable fromccAPI.CURRENT_VERSION.
- E. Executing dynamic SOQL inside a without sharing class with a bind variable from theUserInfo class.
正解：A、B、C
解説：
Explanation
Executing dynamic SOQL inside a without sharing class with a bind variable from PageReference.getParameters(), PageReference.getCookies(), or cc_RemoteActionContext class will open up a major security hole because these sources of input are not sanitized and can be manipulated by malicious users to inject SOQL queries that bypass the sharing rules and access data that they are not supposed to see.
For example, a user can modify the URL parameters or cookies to include a SOQL query that returns sensitive data from the database. To prevent this, it is recommended to use static SOQL or escape the bind variables before executing dynamic SOQL.
質問 # 29
What is essential for a Salesforce B2B Commerce theme to show up in the theme section in CC Admin?
- A. The theme needs to be set in the Configuration Settings.
- B. The theme needs to be set as a Custom Setting in Salesforce.
- C. The theme needs to have "theme" in the name of the Static Resource.
- D. The theme needs to be referred to in the head element on the page
正解：C
解説：
An essential requirement for a Salesforce B2B Commerce theme to show up in the theme section in CC Admin is that the theme needs to have "theme" in the name of the Static Resource. For example, a theme named "MyTheme" will not appear in CC Admin, but a theme named "MyTheme_theme" will. This is how the framework identifies which static resources are themes and which are not. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Themes
質問 # 30
A developer has made a component with a lightning combobox in the follow! markup. To handle changes on the combobox, what should replace <CHANGE FVENT>?
- A. javascript:void(0);handleChange();
- B. {handleChange()}
- C. {event:handleChange}
- D. {handleChange}
正解：D
解説：
Explanation
To handle changes on the combobox, the developer should replace <CHANGE EVENT> with {handleChange}. The handleChange is a function that is defined in the JavaScript file of the Lightning web component and is invoked when the value of the combobox changes. The developer can use this functionto perform custom logic or actions based on the selected value of the combobox, such as updating other components or properties, calling Apex methods or services, or firing events. The developer can use the onchange attribute to bind the handleChange function to the combobox element in the HTML file of the Lightning web component. The onchange attribute is an HTML attribute that specifies a function to be executed when the value of an element changes. {event:handleChange} is not a valid way to handle changes on the combobox, as it is not a valid syntax for binding a function to an element.
javascript:void(0);handleChange(); is not a valid way either, as it is not a valid syntax for binding a function to an element. {handleChange()} is not a valid way either, as it is not a valid syntax for binding a function to an element. Salesforce References: Lightning Web Components Developer Guide: Handle Events, Lightning Web Components Developer Guide: Communicate with Properties, Lightning Web Components Developer Guide: lightning-combobox
質問 # 31
Which three actions are applicable when extendinga default Salesforce B2B Commerce page via a page include? (3 answers)
- A. Create the VisualForce page you wish to include to the Salesforce b2B Commerce page.
- B. Build and activate a new configuration cache setting via CC admin.
- C. Prepend "c." to the name ofthe page referenced in the configuration setting.
- D. Create a configuration setting for enabling the page include and assigning the new page include via CC admin.
- E. Create a Service Class override to query the new page include.
正解：A、B、D
解説：
Explanation
Three actions that are applicable when extending a default Salesforce B2B Commerce page via a page include are:
* Create the VisualForce page you wish to include to the Salesforce B2B Commerce page. This page will contain the custom content or logic that you want to add to the existing page. For example, you can create a VisualForce page named MyPageInclude that displays some additional information or functionality on the product detail page.
* Create a configuration setting for enabling the page include and assigning the new page include via CC Admin. This setting will specify which page include you want to use for which page and section. For example, you can create a configuration setting named CO.MyPageInclude with the valuePDV.BodyIncludeBegin.MyPageInclude, which means you want to use MyPageInclude as the body include begin for the product detail view (PDV) page.
* Build and activate a new configuration cache setting via CC Admin. This action will refresh the cache and apply the changes to the storefront. You need to do this whenever you make any changes to the configuration settings or VisualForce pages. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Page Includes
質問 # 32
Which three actions must a developer take, in a B2B Commerce store, to accept credit card payments using a client's chosen payment provider?
- A. Create a named credential for authentication with the payment provider.
- B. Create an Apex class that implements the commercepayments.PaymentGatewayAdapter.
- C. Create an Apex class that implements the sfdc_checkout.PaymentGatewayAdapter
- D. Create a PaymentProviderGateway record for the custom payment provider class.
- E. Create a RegisteredExternalService record for the custom payment provider class.
正解：A、C、D
解説：
Explanation
Three actions that a developer must take, in a B2B Commerce store, to accept credit card payments using a client's chosen payment provider are: create a named credential for authentication with the payment provider, create an Apex class that implements the sfdc_checkout.PaymentGatewayAdapter interface, and create a PaymentProviderGateway record for the custom payment provider class. Creating a named credential for authentication with the payment provider allows the developer to securely store and manage authentication information, such as username, password, token, or certificate, for connecting to the payment provider's API or service. Creating an Apex class that implements the sfdc_checkout.PaymentGatewayAdapter interface allows the developer to define custom logic for processing credit card payments using the payment provider's API or service. The interface provides methods for validating credit card information, authorizing payments, capturing payments, voiding payments, and refunding payments. Creating a PaymentProviderGateway record for the custom payment provider class allows the developer to register the custom payment provider class as a payment gateway in the store and associate it with a payment method. Creating a RegisteredExternalService record for the custom payment provider class is not a required action, as this is only used for registering external services that are not related to payment processing, such as tax or shipping services. Creating an Apex class that implements the commercepayments.PaymentGatewayAdapter interface is not a required action either, as this is only used for D2C Commerce stores, not B2B Commerce stores. Salesforce References: B2B Commerce Developer Guide: Payment Integration, B2B Commerce Developer Guide: Payment Gateway Adapter Interface, B2B Commerce Developer Guide: Payment Provider Gateway Object
質問 # 33
Which handlebars helper function is used on Salesforce B2B Commerce pages and components for formatting price values?
- A. priceAbs
- B. formatPrice
- C. showprice
- D. price
正解：B
解説：
The handlebars helper function that is used on Salesforce B2B Commerce pages and components for formatting price values is formatPrice. This function will format a numeric value as a price according to the currency settings and locale of the storefront. For example, {{formatPrice price}} will format the price value as $1,234.56 for US dollars or €1.234,56 for euros. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Handlebars Helpers
質問 # 34
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 not removed.
- C. The sizing block is removed after the first handler.
- D. SZ_ASSC is not used.
- E. When different entities are specified in the method invocation.
正解：C、D、E
質問 # 35
The ccUtil apex class in Salesforce B2B Commerce provides numerous utility functions that can be leveraged in subscriber classes. Which command will return the value in the given Map if found or a default value in the event that the Map is null, empty, or an object is not found for that key?
- A. ccrz.ccUtil.defaultValue(Map<String.Object> mp, String key , Object ob)
- B. ccrz.ccUtil.... (Map<String.Object> mp, String key, Object ob)
- C. ccrz.ccUtil.defVal (Map<String.Object> mp, String key, Object ob)
- D. ccrz.ccUtil.defv (Map<String.Object> mp, String key , Object ob)
正解：D
質問 # 36
What are two guidelines for logging that are used within the core Salesforce B2B Commerce product? (2 answers)
- A. The close method of ccrz.ccLog must be called at the end of the remote action.
- B. No calls to ccrz.ccLog can be made before cc_CallContext.initRemoteContext is executed.
- C. It is okay to log any data on the server that is already logged on the client side.
- D. Items or data within computational intensive loops should be logged.
正解：A、B
質問 # 37
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. My_Field_Name__c
- C. myfieldname
- D. MyFieldName
正解：A
質問 # 38
A developer exports data from an org on a standard entity which has a custom attribute. When they launch Data Loader, select the entity, click the Select All Fields button and click Finish, the custom field they added called MyCustomField_c has no values and no column header in the CSV file. What is the root cause?
- A. A mapping file was not used when the data was loaded in
- B. The user does not have access to the field
- C. The user has rights to the field but there are no values in it
- D. The user needs to install a specific Zulu JDK that is recommended by Salesforce.
正解：B
解説：
The root cause of why the custom field MyCustomField__c has no values and no column header in the CSV file is that the user does not have access to the 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 user needs to install a specific Zulu JDK that is recommended by Salesforce is not the root cause of why MyCustomField__c has no values and no column header in the CSV file, as it is not related to field access or Data Loader functionality. A mapping file was not used when the data was loaded in is not the root cause either, as it is not related to field access or Data Loader functionality. A mapping file is an optional file that maps fields between Salesforce objects and CSV files when using Data Loader to import or export data. The user has rights to the field but there are no values in it is not the root cause either, as it contradicts the fact that MyCustomField__c has no column header in the CSV file. If the user had rights to the field but there were no values in it, Data Loader would still include MyCustomField__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]
質問 # 39
Which practice is allowed when it comes to naming a Lightning web component's folder and associated files?
- A. Using consecutive underscores
- B. Using a single underscore
- C. Using a single hyphen (dash)
- D. Including whitespace
正解：C
解説：
Explanation
To name a Lightning web component's folder and associated files, the developer should follow these naming rules:
* Must begin with a lowercase letter
* Must contain only alphanumeric or underscore characters
* Must be unique in the namespace
* Can't include whitespace
* Can't end with an underscore
* Can't contain two consecutive underscores
* Can't contain a hyphen (dash)
The only exception to the last rule is when separating the namespace from the component name in markup. For example, if the component is in the example namespace and has the name myComponent, the folder name should be myComponent, but the markup tag should be <example-my-component>. The hyphen character (-) is required by the HTML standard for custom element names. The other options are either invalid or not recommended. For example, including whitespace or using consecutive underscores will cause errors, and using a single underscore will look odd and may confuse developers consuming the component. References: B2B Commerce and D2C Commerce Developer Guide, Lightning Web Components Developer Guide
質問 # 40
Which event is triggered within Salesforce B2B Commerce whenever a cart's statechanges?
- A. cart
- B. cartChange
- C. pageMessage
- D. cartState
正解：B
解説：
Explanation
The event that is triggered within Salesforce B2B Commerce whenever a cart's state changes is cartChange.
This event is triggered by the updateCart method of the CCRZ.Cart class, which is responsible for updating the cart data and performing any actions that depend on the cart state, such as applying discounts, taxes, or shipping charges. The event can be used to notify all the components that are listening to it that the cart has changed and they should refresh their data accordingly. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Events, Cart Class
質問 # 41
......
確認済みB2B-Commerce-Developer試験問題集と解答で時間限定無料提供！B2B-Commerce-Developerには正解付き：https://jp.fast2test.com/B2B-Commerce-Developer-premium-file.html