合格させるSalesforce B2B-Commerce-Developer試験には保証が付きます。更新されたのは179問があります [Q18-Q43]

合格させるSalesforce B2B-Commerce-Developer試験には保証が付きます。更新されたのは179問があります

最新のB2B-Commerce-Developer合格保証付き試験問題集の認定サンプル問題

質問 # 18
What interface must a developer implement to override Tax in Checkout?

• A. sfdc_checkout.TaxCalculations
• B. sfdc_commerce.CartTaxCalculations
• C. sfdc.commerce.TaxCalculations
• D. sfdc.commerce.CheckoutTaxCalculations
• E. sfdc.checkout.CartTaxCalculations

正解：A

解説：
To override tax in checkout, a developer must implement the sfdc_checkout.TaxCalculations interface. The sfdc_checkout.TaxCalculations interface is an Apex interface that provides methods for customizing the tax calculation logic for a cart or an order. The interface allows the developer to define how to retrieve tax rates and rules, how to apply tax amounts and adjustments, and how to handle tax errors and exceptions. The developer can use the sfdc_checkout.TaxCalculations interface to integrate with a third-party tax service provider or to implement their own tax calculation logic. The other interfaces do not exist or are not related to tax calculation. Salesforce Reference: B2B Commerce Developer Guide: Tax Integration, B2B Commerce Developer Guide: Tax Calculations Interface

質問 # 19
Which three attributes are true regarding Subscriber pages? (3 answers)

• A. Standard Salesforce B2B Commerce components are automatically included on the page e.g. Header links, images, menu items, containers, etc.
• B. Subscriber pages allow customers to quickly create new custom pages for their storefront.
• C. All the user interface components must be createdmanually.
• D. Out of the Box, Subscriber Pages are completely blank HTML pages.
• E. Subscriber pages can include additional standard Salesforce B2B Commerce components such as featured products, category tree, and mini cart.

正解：B、D、E

解説：
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 References: B2B Commerce and D2C Commerce Developer Guide, Subscriber Pages

質問 # 20
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. Append #ccLog=<Logging Token Name> to the end of the storefront URL in order to get logs in the inspector console.
• D. There is no need to use string concatenation to easily tag log statements with a subject.
• E. There is no need to manually set a cookie to debug with the Site Guest User.

正解：C、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

質問 # 21
Salesforce B2B leverages global API's for encapsulating business logic into blocks that can be extended and modified by subscribers. Which three statements are true regarding extending ccServiceProduct and exposing custom fields on the Product Detail Page? (3 answers)

• A. Ensure that any helper methods are defined as private andstatic only.
• B. Override the fetch method and add your subscriber specific code here.
• C. Create a public with sharing class that extends ccrz.ccServiceProduct.
• D. Override the getFieldsMap method and add subscriber specific code.
• E. Create a global with sharing class that extends ccrz.ccServiceProduct.

正解：B、D、E

解説：
Explanation
To extend ccServiceProduct and expose custom fields on the Product Detail Page, three statements are true:
* Override the getFieldsMap method and add subscriber specific code. This method returns a map of field names and field types for the product entity and its related entities. By overriding this method, the subscriber can add their custom fields to the map and make them available for the API.
* Create a global with sharing class that extends ccrz.ccServiceProduct. This class will inherit all the methods and properties of the ccServiceProduct class and allow overriding or extending them. The class should be global and with sharing to ensure that it can be accessed by the API framework and respect the sharing rules.
* Override the fetch method and add your subscriber specific code here. This method executes the query to fetch the product data and returns a result object. By overriding this method, the subscriber can modify the query or the result object to include their custom fields or logic. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Service Classes, ccServiceProduct Class

質問 # 22
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 the UserInfo class.
• B. Executing dynamic SOQL inside a without sharing class with a bind variable from PageReference.getCookies().
• C. Executing dynamic SOQL inside a without sharing class with a bind variable from ccAPI.CURRENT_VERSION.
• D. Executing dynamic SOQL inside a without sharing class with a bind variable from PageReference.getParameters().
• E. Executing dynamic SOQL inside a without sharing class with a bind variable from cc_RemoteActionContentex class.

正解：B、D、E

質問 # 23
Which cookie stores the effective account ID when effective account is enabled?

• A. apex__effacc
• B. apex__cc_anonymous_Country
• C. apex__currCartId
• D. apex__cclgtkn

正解：A

解説：
The cookie that stores the effective account ID when effective account is enabled is apex__effacc. This cookie is set by the cc_hk_EffectiveAccount hook when a user switches to another account that they have access to. The cookie value is the ID of the effective account, which is used to determine the pricing, availability, and visibility of products and categories for that account. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Effective Account

質問 # 24
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. Salesforce B2B Commerce includes do not support standard SalesForce remote actions.
• B. The APEX method called by the remote action will be passed as a Salesforce B2B Commerce context object.
• C. A standard remote action will not have access to Salesforce B2B Commerce objects.
• D. The Salesforce B2B Commerce logger cannot be utilized in standard remote actions

正解：B、D

質問 # 25
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 theUserInfo class.
• B. Executing dynamic SOQL inside a without sharing class with a bind variable fromPageReference.getCookies().
• C. Executing dynamic SOQL inside a without sharing class with a bind variable fromPageReference.getParameters().
• 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 fromcc_RemoteActionContentex class.

正解：B、C、E

解説：
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.

質問 # 26
Northern Trail Outfitters (NTO) has a B2B Commerce store for its resellers. It has received many customer service calls involving questions about the delivery date of customer orders.
How should a developer expose delivery time estimates to NTO's customers in the storefront to reduce call volume?

• A. Display the Expected Delivery Date on the order page with a Lightning web component.
• B. Configure an email alert to the customer when the Expected Delivery Date changes.
• C. Add a Desired Delivery Date input field during the checkout flow.
• D. Add the Expected Delivery Date field to the order confirmation email.

正解：A

解説：
To expose delivery time estimates to NTO's customers in the storefront, a developer should display the Expected Delivery Date on the order page with a Lightning web component. The Expected Delivery Date is a custom field on the Order object that stores the date when the order is expected to be delivered to the customer. The developer can use the @wire decorator to get the current order object and use its properties, such as order number, status, total amount, and expected delivery date, to display them on the order page. The developer can also use Apex methods or third-party APIs to calculate and update the expected delivery date based on various factors, such as inventory availability, shipping method, shipping address, and carrier service level. Displaying the expected delivery date on the order page allows the customer to see their delivery time estimate at any time and reduce their need to call customer service. Adding the Expected Delivery Date field to the order confirmation email is not a good solution, as it does not allow the customer to see their delivery time estimate if they lose or delete their email. Adding a Desired Delivery Date input field during the checkout flow is not a good solution either, as it does not guarantee that the customer's desired delivery date will be met or reflect any changes in delivery time due to unforeseen circumstances. Configuring an email alert to the customer when the Expected Delivery Date changes is not a good solution either, as it can create confusion or frustration for the customer if they receive multiple or conflicting emails about their delivery date. Salesforce Reference: B2B Commerce Developer Guide: Order Object, [B2B Commerce Developer Guide: Order Page], [Lightning Web Components Developer Guide: Call an Apex Method Imperatively]

質問 # 27
A developer has the task to bring some historical data into an org. The data must reside in the org, but cannot be populated in standard or custom objects. The customer is fine with developers building Ul components to surface this data on a case-by-case basis.
Which option allows a developer to meet all of these requirements?

• A. Lightning Canvas
• B. Lightning Out
• C. Big objects
• D. External objects

正解：C

解説：
Explanation
To bring some historical data into an org, the data must reside in the org, but cannot be populated in standard or custom objects, and the customer is fine with developers building UI components to surface this data on a case-by-case basis, the option that allows a developer to meet all of these requirements isbig objects. Big objects are a type of object that can store and manage massive amounts of data on the Salesforce platform. Big objects can store up to billions of records and are accessible through a subset of SOQL or custom user interfaces. Big objects are not subject to the same storage limits or performance issues as standard or custom objects and are suitable for storing historical or archived data that does not need to be updated frequently. Big objects can be defined using Metadata API or declaratively in Setup. Lightning Canvas is not an option that allows a developer to meet all of these requirements, as it is a framework that allows developers to integrate third-party applications into Salesforce. Lightning Canvas does not store data in the org, but rather displays data from external sources using an iframe. External objects are not an option either, as they are a type of object that map to data stored outside Salesforce. External objects do not store data in the org, but rather access data from external systems using OData services. Lightning Out is not an option either, as it is a feature that allows developers to use Lightning components outside Salesforce. Lightning Out does not store data in the org, but rather renders components on external web pages or applications. Salesforce References: Salesforce Help: Define BigObjects, Salesforce Help: Lightning Canvas Developer's Guide, Salesforce Help: External Objects, Salesforce Developer Blog: Lightning Out

質問 # 28
What two things happen with the Cart during tax implementation?

• A. New entries are written to the Order Summary
• B. New entries are written to the Cart
• C. Previous entries are copied to another object
• D. Previous entries are deleted from the Cart

正解：B、D

解説：
Two things that happen with the cart during tax implementation are that new entries are written to the cart and previous entries are deleted from the cart. A tax implementation is an integration that calculates and applies tax rates and amounts to a cart or an order based on various factors, such as product type, price, quantity, location, and tax rules. A tax implementation can use either an external tax service provider or custom Apex code to perform the tax calculation. When a tax implementation is invoked for a cart, it writes new entries to the cart with a type of Charge and a charge type of Tax. These entries represent the tax amounts and adjustments that are applied to the cart. Before writing new entries to the cart, the tax implementation deletes any existing entries with a type of Charge and a charge type of Tax from the cart. This ensures that the tax calculation is accurate and up-to-date based on the current state of the cart and avoids any conflicts or inconsistencies with previous tax entries. Previous entries are not copied to another object or modified with the new tax calculation, as these are not valid actions for handling existing tax entries. Salesforce Reference: B2B Commerce Developer Guide: Tax Integration, B2B Commerce Developer Guide: Tax Calculation Flow

質問 # 29
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. WhethertouseJSONorXML
• B. What events to fire in the Lightning web component
• C. What to implement
• D. Steps to complete in the Tax Service
• E. How to handle results

正解：C、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 References: B2B Commerce Developer Guide: Tax Integration, [B2B Commerce Developer Guide:
Tax Calculations Interface]

質問 # 30
In which threeways can Salesforce B2B Commerce API sizing blocks support multiple API sizing requests? (3 answers)

• A. SZ_ASSC is not used.
• B. When different entities are specified in the method invocation.
• C. SZ_ASSC is used.
• D. The sizing block is removedafter the first handler.
• E. The sizing block is not removed.

正解：A、B、C

解説：
Explanation
Salesforce B2B Commerce API sizing blocks can support multiple API sizing requests in three ways:
* When different entities are specified in the method invocation. For
example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_M, ccrz.ccAPI.SZ_L) will use the SZ_M sizing block for the product entity and the SZ_L sizing block for the related entities.
* SZ_ASSC is used. This flag indicates that the associated entities should use the same sizing block as the primary entity. For example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_M, ccrz.ccAPI.SZ_ASSC) will use the SZ_M sizing block for both the product entity and the related entities.
* SZ_ASSC is not used. This flag indicates that the associated entities should use the default sizing block, which is SZ_M, unless otherwise specified. For example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_M) will use the SZ_M sizing block for the product entity and the SZ_M sizing block for the related entities. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Data Sizing Conventions

質問 # 31
What is true regarding adding more Configuration Settings
to Salesforce B2B Commerce?

• A. More modules and metadata can be added to Salesforce B2B Commerce.
• B. Configuration settings can only be extended through API's
• C. Metadata can be added to existing modules, but you cannot add new modules.
• D. Select "New" in your storefront's Configuration Settings and create a custom setting.

正解：A

質問 # 32
The ccUtil apex class in Salesforce B2B Commerce provides numerous utility functions that can be leveraged in subscriber classes.
What are two ways to check the input or return data of the Global API's? (2 answers)

• A. ccrz.ccUtil.isEmpty(Map<String, Object>) and ccrz.ccUtil.isEmpty(List<Object>)
• B. ccrz.ccUtil.isValid(Map<String, Object>) and ccrz.ccUtil.isValid(List<Object>)
• C. ccrz.ccUtil.isNotEmpty(Map<String, Object>) andccrz.ccUtil.isNotEmpty(List<Object>)
• D. ccrz.ccUtil.isNotValid(Map<String, Object>) andccrz.ccUtil.isNotValid(List<Object>)

正解：A、C

解説：
The ccUtil apex class provides two methods to check the input or return data of the Global API's: ccrz.ccUtil.isNotEmpty(Map<String, Object>) and ccrz.ccUtil.isEmpty(Map<String, Object>). These methods return true if the map is not null and contains at least one entry, or if the map is null or empty, respectively. Similarly, ccrz.ccUtil.isNotEmpty(List<Object>) and ccrz.ccUtil.isEmpty(List<Object>) return true if the list is not null and contains at least one element, or if the list is null or empty, respectively. These methods are useful for validating the input parameters or the output results of the Global API's.

質問 # 33
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 processPayment event 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 externalprocessedPayment 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.

正解：A

解説：
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.

質問 # 34
What is the recommended method for increasing the number of required autocomplete characters that are typed before autocomplete works?

• A. Override the autocomplete template and create and register a new handlebars helper.
• B. Update the...minLength property in CC Admin, then build and activate a new cache.
• C. Override and extend the autoComplete method in cc_hk_Catalog.
• D. Override the autoComplete.search_input.minLength value in the CCRZ.uiProperties file

正解：D

質問 # 35
How can the display of CC Menu Items be customized for different users?

• A. cc_hk_Menu extension to post-process any cached menu items
• B. cc_hk_Menu extension to pre-process which menu items are cached
• C. cc_hk_Category extension to post-process any cached menu items
• D. cc_hk_Category extension to pre-process which category items are cached as menu items

正解：A

解説：
The display of CC Menu Items can be customized for different users by using the cc_hk_Menu extension to post-process any cached menu items. This extension allows modifying the menu items based on the user context, such as the user role, account, or cart. For example, the extension can hide or show certain menu items based on the user's permissions or preferences.

質問 # 36
Which three statements are true about Global API versioning? (3 answers)

• A. There is no need to pass API_VERSION to the Global APIs, and based on the Salesforce B2B Commerce Managed Package version, Global APIs are able to figure out what version of the API to use.
• B. Calling in with an API version set to more than current maximum will result in exception case where the exception class ccrz.ExceedsMaxAPIVersionException will be returned to callers.
• C. Minimum API_VERSION is 1 and the Maximum API version follows the releases. E.g. The maximum was 4 as of Salesforce B2B Commerce Release-4.5, 5 as of Salesforce B2B CommerceRelease 4.6, etc.
• D. The API version is scoped at the Class API level and NOT at the method level.
• E. Calling in with an API version set to lower than 1 will result in an exceptional case where the exception classccrz.BelowMinAPIVersionException will be returned tocallers.

正解：B、C、E

解説：
Explanation
Three statements that are true about Global API versioning are:
* Calling in with an API version set to lower than 1 will result in an exceptional case where the exception class ccrz.BelowMinAPIVersionException will be returned to callers. This exception indicates that the API version is not supported by the framework and the caller should use a higher API version.
* The API version is scoped at the Class API level and NOT at the method level. This means that all the methods in a class will use the same API version that is specified by the caller. For example, if the caller passes an API version of 4 to ccrz.ccServiceProduct.getProducts(), then all the other methods in ccrz.ccServiceProduct will also use API version 4.
* Calling in with an API version set to more than current maximum will result in exception case where the exception class ccrz.ExceedsMaxAPIVersionException will be returned to callers. This exception indicates that the API version is not supported by the framework and the caller should use a lower API version. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, API Versioning

質問 # 37
Which two technologies can subscribe to the CommerceDiagnosticEvents event?

• A. Lightning web components
• B. Aura Components
• C. Streaming API
• D. Processes

正解：A、B

解説：
Two technologies that can subscribe to the CommerceDiagnosticEvents event are Aura Components and Lightning web components. 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. Aura Components are a type of component that can be used to create custom user interfaces for Salesforce apps. Aura Components can subscribe to CommerceDiagnosticEvents using an aura:handler tag in their markup file. The aura:handler tag specifies an event name, an action attribute that defines a controller function to handle the event, and other optional attributes. Lightning web components are another type of component that can be used to create custom user interfaces for Salesforce apps. Lightning web components can subscribe to CommerceDiagnosticEvents using an @wire decorator in their JavaScript file. The @wire decorator specifies an event name, a function name that defines a handler for the event, and other optional parameters. Processes are not a technology that can subscribe to CommerceDiagnosticEvents, as they are not related to user interface development or event handling. Processes are automated workflows that execute actions based on certain criteria or conditions in Salesforce. Streaming API is not a technology that can subscribe to CommerceDiagnosticEvents either, as it is not related to user interface development or event handling. Streaming API is an API that allows applications to receive notifications of data changes in Salesforce in near real-time. Salesforce Reference: [B2B Commerce Developer Guide: Handle Errors], [Aura Components Developer Guide: Handle Component Events], [Lightning Web Components Developer Guide: Communicate with Events], [Salesforce Help: Process Automation], [Salesforce Developer Guide: Streaming API]

質問 # 38
Northern Tail Outfitters (NTO) is converting an existing aura component into a Lightning Web Component.
The aura component has the following source code:

What is the equivalent of this code in a Lightning Web Component?

• A.
• B.
• C.
• D.

正解：B

解説：
Explanation
The equivalent of this code in a Lightning web component is option B. Option B uses the @api decorator to expose firstName as a public property of the Lightning web component and communicate it with other components or services. The @api decorator is a decorator that marks a property or method as public, which means that it can be accessed by other components or services that use or consume this component. The @api decorator also makes the property reactive, which means that it can track changes and update the component accordingly. In option B, firstName is exposed as a public property using the @api decorator and passed to the child element using an attribute. Option A is incorrect because it uses an invalid syntax for exposing firstName as a public property. The @api decorator should be used before the property declaration, not after it. Option C is incorrect because it uses an invalid syntax for exposing firstName as a public property. The @api decorator should be used with parentheses, not without them. Option D is incorrect because it uses an invalid syntax for exposing firstName as a public property. The @api decorator should be used with camel case, not with hyphens. Salesforce References: Lightning Web Components Developer Guide: Communicate with Properties, Lightning Web Components Developer Guide: Decorators

質問 # 39
What is a valid way of referencing the CC Cart Object whose API name is E_Cart__c in a SOQL query?

• A. ccrz__E_Cart__c
• B. c.E_Cart__c
• C. _Cart__c
• D. cloudcraze__E_Cart__c

正解：A

解説：
A valid way of referencing the CC Cart Object whose API name is E_Cart__c in a SOQL query is to use ccrz__E_Cart__c. This is the transformed name of the object that is used by the Salesforce B2B Commerce framework. All custom objects and fields that are part of the cloudcraze managed package have the prefix ccrz__ in their API names. For example, SELECT Id, Name FROM ccrz__E_Cart__c will query the CC Cart Object records. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Query Transformation

質問 # 40
Which two log levels does a developer need to include to debug platform events?

• A. Database
• B. Apex Code
• C. Callout
• D. Workflow

正解：B、D

解説：
Explanation
According to the Platform Events Developer Guide, to debug platform events, a developer needs to include the Apex Code and Workflow log levels in the trace flag entry for the Automated Process entity or the overridden user. The Apex Code log level captures the execution of the Apex trigger that subscribes to the platform event. The Workflow log level captures the execution of the event process or the resumed flow interview that subscribes to the platform event. The other log levels are not relevant for debugging platform events. The Database log level captures database operations, such as DML statements and SOQL queries. The Callout log level captures the details of HTTP requests and responses, such as web service callouts. References: Platform Events Developer Guide, Set Up Debug Logs for Event Subscriptions, Set Up Debug Logging

質問 # 41
A configuration value, CO.NewOrder, is set to TRUE. What is one way of
preventing an existing payment page from being shown on the checkout payment page?

• A. Override the front end template and modify the way the embedded payment page gets loaded from the payment list configuration.
• B. Remove the payment type associated with the payment page from CO.pmts, then rebuild and activate a new cache.
• C. Remove the value matching the page name from the pmt.whitelist configuration setting, then rebuild and activate a new Configuration cache
• D. Delete the Visualforce page from the code base.

正解：C

質問 # 42
In which threeways can Salesforce B2B Commerce API sizing blocks support multiple API sizing requests? (3 answers)

• A. SZ_ASSC is not used.
• B. When different entities are specified in the method invocation.
• C. SZ_ASSC is used.
• D. The sizing block is removedafter the first handler.
• E. The sizing block is not removed.

正解：A、B、C

質問 # 43
......

最新B2B-Commerce-Developerテスト材料には有効なB2B-Commerce-Developerテストエンジン：https://www.passtest.jp/Salesforce/B2B-Commerce-Developer-shiken.html

B2B-Commerce-Developer更新された試験問題集で[2024年最新] 練習には有効な試験問題集：https://drive.google.com/open?id=139GlDZ6aEXb0XpS0WjMPkL1c3Dvj4S0v