完全版B2B-Commerce-Developer練習テスト142特別な問題と解答が待ってます！ [Q69-Q84]

完全版B2B-Commerce-Developer練習テスト142特別な問題と解答が待ってます！

Salesforce Developer問題集でB2B-Commerce-Developer試験完全版問題で試験学習ガイド

Salesforce B2B-Commerce-Developer試験は、Salesforce B2B Commerceプラットフォームに特化したい開発者にとって不可欠な認証です。この認定は、Salesforceプラットフォームを使用して革新的で効率的なB2B Commerce Solutionsの作成を希望する開発者のスキルと知識をテストするように設計されています。この認定は、Salesforceプラットフォームと協力し、B2B Commerceの概念を十分に理解している開発者を対象としています。

試験は60の複数選択の質問で構成されており、105分以内に完了する必要があります。試験の合格スコアは68％で、英語で利用できます。候補者は、オンラインまたはテストセンターで試験を受けることができ、試験の費用は200ドルです。試験を受ける前に、候補者はB2B Commerce Developer Trainingを完了し、B2B Commerce Solutionsの実装において少なくとも6か月の経験が必要です。

 

質問 # 69
Salesforce B2B Commerce natively provides a robots.txt file, however, a customer can also create its own version.Which three scenarios are valid reasons for customer to create their own robots.txt file? (3 answers)

• A. The customer wants to reference multiple storefront sitemap indexes in a single robots.txt file
• B. The customer wants to reference a custom sitemap index.
• C. The customer's store is not located at the root of their domain.
• D. robot.txt only works if there is one storefront in the org
• E. The customer wants to have multiple robot.txt files in a single Salesforce Community.

正解：A、B、C

質問 # 70
A developer is working in Visual Studio Code on a previously deployed project which is rather large and deployments are time consuming. The developer wants to know if a CSS file containing small changes was actually deployed to the org. What is one way this can be accomplished?

• A. Right-click the folder for the component and choose Diff Styles Against Org
• B. Right-click the CSS file and choose Diff File Against Org
• C. Click the Tools menu and select Diff Styles Against Org...
• D. Right-click the folder for the component and choose Diff Files Against Org

正解：B

解説：
To know if a CSS file containing small changes was actually deployed to the org, one way that a developer can accomplish this is by right-clicking the CSS file and choosing Diff File Against Org. Diff File Against Org is an option that allows the developer to compare a local file with its remote version in the org using Salesforce CLI commands. The developer can use Visual Studio Code to execute these commands by right-clicking on files or folders in the project and choosing from various diff options. Right-clicking the CSS file and choosing Diff File Against Org allows the developer to see the differences between the local CSS file and the remote CSS file in the org side by side in Visual Studio Code. This way, the developer can verify if their changes were deployed successfully or not. Clicking the Tools menu and selecting Diff Styles Against Org... is not a valid way to know if a CSS file was deployed to the org, as there is no such option in Visual Studio Code or Salesforce CLI. Right-clicking the folder for the component and choosing Diff Styles Against Org is not a valid way either, as there is no such option in Visual Studio Code or Salesforce CLI. Right-clicking the folder for the component and choosing Diff Files Against Org is not a valid way either, as it will compare all the files in the folder, not just the CSS file, which may not be efficient or necessary. Salesforce Reference: [Salesforce CLI Command Reference: force:source:diff], [Salesforce Developer Tools for Visual Studio Code]

質問 # 71
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. The API version is scoped at the Class API level and NOT at the method level.
• C. 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.
• D. 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.
• E. 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、D、E

解説：
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 Reference: B2B Commerce and D2C Commerce Developer Guide, API Versioning

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

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

正解：B

質問 # 73
What two kinds of queries do the methods in Salesforce B2B Commerce services perform by default? (2 answers)

• A. SOQL
• B. SOSL
• C. Schema-less queries
• D. SQL

正解：A、C

解説：
Two kinds of queries that the methods in Salesforce B2B Commerce services perform by default are SOQL and schema-less queries. SOQL is the query language that is used to retrieve data from Salesforce objects and fields. Schema-less queries are queries that do not specify the object or field names explicitly, but use placeholders instead. For example, ccrz.ccServiceDao.getQuery('SELECT Id FROM Account WHERE Name = :name') is a schema-less query that uses :name as a placeholder for the field name. The framework will transform this query to use the actual field name based on the query transformation rules. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Query Transformation

質問 # 74
Which cart item type is created with the Cart Delivery Group Method after the shipping integration?

• A. Charge
• B. Surcharge
• C. Delivery
• D. Shipping

正解：A

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

質問 # 75
Which two event settings are required for a custom event called CustomEvent to fire from the Lightning web component and propagate up to the DOM?

• A. composed: true
• B. cancelable: true
• C. bubbles: true
• D. composed: false

正解：A、C

解説：
To fire a custom event called CustomEvent from the Lightning web component and propagate it up to the DOM, the developer must set two event settings: bubbles and composed. The bubbles setting determines whether the event bubbles up through the component's ancestors in the DOM tree. The composed setting determines whether the event crosses the shadow boundary and reaches the light DOM. Setting both bubbles and composed to true allows the event to be handled by any element in the DOM that listens for it. The cancelable setting is not required for firing or propagating the event, as it only determines whether the event can be canceled by calling preventDefault() on it. Setting composed to false would prevent the event from reaching the light DOM and limit its propagation to the shadow DOM. Salesforce Reference: Lightning Web Components Developer Guide: Create and Dispatch Events, Lightning Web Components Developer Guide: Event Propagation

質問 # 76
A query containing a subquery is executed. What is appended to the subquery name as part of its transformation by default in Salesforce B2B Commerce?

• A. "__ccrz"
• B. A subscriber-supplied token
• C. The "*" symbol
• D. The letter "S"

正解：D

質問 # 77
While working on a commerce rollout, a developer needs to update the checkout process so that buyers can purchase with one of the below payment types.
* Credit Card
* Purchase Order
* Contract Now & Pay Later
Additionally, the developer needs to show only Purchase Order and Contract Now & Pay Later if a custom checkbox field on the account is checked.
How should the developer meet these requirements?

• A. Create a custom Lightning web component that can be used with the standard payment component. Use a publish-<g, subscribe (pub-sub) model to listen to events from the standard component to determine which additional payment options should be shown.
• B. Add a new payment gateway through the reference implementation steps so the payment shows up on the checkout payment screen. Configure the different payment options required.
• C. Create a custom Lightning web component for the checkout flow that has all the options available. Within that component, pull data from the account to determine which options to show.
• D. Modify the standard payment component settings in the checkout screen flow and add the new payment method. Use the component visibility feature in screen flows to fulfill the account-based payment option criteria.

正解：C

解説：
To update the checkout process so that buyers can purchase with one of the below payment types:
Credit Card
Purchase Order
Contract Now & Pay Later Additionally, show only Purchase Order and Contract Now & Pay Later if a custom checkbox field on the account is checked, a developer should create a custom Lightning web component for the checkout flow that has all the options available. Within that component, pull data from the account to determine which options to show. Creating a custom Lightning web component for the checkout flow allows the developer to define custom logic and user interface for processing payments using different payment types. The developer can use Apex methods or third-party APIs to integrate with payment service providers or payment gateways and handle payment authorization, capture, void, and refund. The developer can also use @wire or @api decorators to get data from the account object and use its properties, such as the custom checkbox field, to determine which payment options to show or hide based on business logic. Creating a custom Lightning web component that can be used with the standard payment component is not a valid way to meet this requirement, as it does not allow the developer to replace or modify the standard payment component's logic or user interface. Modifying the standard payment component settings in the checkout screen flow and adding the new payment method is not a valid way either, as it does not allow the developer to add custom payment types or conditional logic based on account data. Adding a new payment gateway through the reference implementation steps so the payment shows up on the checkout payment screen is not a valid way either, as it does not allow the developer to add multiple payment options or conditional logic based on account data. Salesforce Reference: B2B Commerce Developer Guide: Payment Integration, B2B Commerce Developer Guide: Payment Component, B2B Commerce Developer Guide: Checkout Subflow

質問 # 78
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. Override theautoComplete.search_input.minLength value in the CCRZ.uiProperties file
• C. Update the...minLength property in CC Admin, then build and activate a new cache.
• D. Override and extend the autoComplete method in cc_hk_Catalog.

正解：B

解説：
The recommended method for increasing the number of required autocomplete characters that are typed before autocomplete works is to override the autoComplete.search_input.minLength value in the CCRZ.uiProperties file. This file contains various properties that control the behavior and appearance of the user interface components. The autoComplete.search_input.minLength property specifies the minimum number of characters that must be entered before the autocomplete feature is triggered. The default value is 3, but it can be changed to any desired value by overriding it in the CCRZ.uiProperties file. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, UI Properties

質問 # 79
What is a valid way of referencing the global cc_api_CartExtentsion apex class via subscriber code?

• A. cloudcraze.cc_api_CartExtension
• B. c__cc_api_CartExtension
• C. ccrz__cc_api_CartExtension
• D. ccrz.cc_api_CartExtension

正解：D

解説：
A valid way of referencing the global cc_api_CartExtension apex class via subscriber code is to use ccrz.cc_api_CartExtension. This is the name of the class that is defined in the cloudcraze managed package. The class is global, so it can be accessed by subscriber code. The other options are either invalid or incorrect. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, API Classes

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

正解：B、C

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

質問 # 81
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 session ID for replay, and select Run.
• B. Open the flow, select Debug, provide the Input values, and select Run.
• C. Open the flow, select Attach to Live Session, provide the session ID, and select Attach.
• D. Open the flow, select Debug with Inputs, provide the Input values, and select Run.

正解：B

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

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

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

正解：D

解説：
One way of preventing an existing payment page from being shown on the checkout payment page is to remove the payment type associated with the payment page from CO.pmts, then rebuild and activate a new cache. This will exclude the payment type from the list of available payment options on the checkout page. The other options are either not feasible or not effective in hiding the payment page. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Payment Configuration Settings

質問 # 83
A developer is building a custom component in Lightning web components (LWC) that needs to fetch data from an API.
Which lifecycle hook should the developer use to make the API call?

• A. disconnectedCallback
• B. renderedCallback
• C. connectedCallback
• D. errorCallback

正解：C

解説：
To make an API call in a Lightning web component (LWC), a developer should use the connectedCallback lifecycle hook. The connectedCallback lifecycle hook is invoked when the component is inserted into the DOM. This is the ideal time to make an API call, as the component is ready to receive and display data. The developer can use the fetch API or a third-party library, such as axios, to make the API call and handle the response. The renderedCallback lifecycle hook is not a good choice for making an API call, as it is invoked every time the component is rendered or rerendered. This can cause unnecessary or repeated API calls and affect performance. The errorCallback lifecycle hook is not a good choice either, as it is invoked when an error occurs in the component or in one of its children. This is not related to making an API call, but rather to handling errors. The disconnectedCallback lifecycle hook is not a good choice either, as it is invoked when the component is removed from the DOM. This is not a suitable time to make an API call, as the component is no longer visible or active. Salesforce Reference: Lightning Web Components Developer Guide: Lifecycle Hooks, Lightning Web Components Developer Guide: Call an Apex Method Imperatively

質問 # 84
......

B2B-Commerce-Developer正真正銘のベスト資料、オンライン練習試験：https://www.goshiken.com/Salesforce/B2B-Commerce-Developer-mondaishu.html

優れもの良質なB2B-Commerce-Developer問題集が待ってます：https://drive.google.com/open?id=1K1TUQKmlkEKHuB6Dj8mVkSZ7VVZGkl44