ExamGecko
Ask Question

Salesforce Certified B2B Commerce Developer Practice Test - Questions Answers, Page 4

List of questions

Question 31

Report
Export
Collapse

How can the display of CC Menu Items be customized for different users?

cc_hk_Category extension to pre-process which category items are cached as menu items
cc_hk_Category extension to pre-process which category items are cached as menu items
cc_hk_Menu extension to post-process any cached menu items
cc_hk_Menu extension to post-process any cached menu items
cc_hk_Menu extension to pre-process which menu items are cached
cc_hk_Menu extension to pre-process which menu items are cached
cc_hk_Category extension to post-process any cached menu items
cc_hk_Category extension to post-process any cached menu items
Suggested answer: B

Explanation:

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.

asked 23/09/2024
AJ Foraker
36 questions

Question 32

Report
Export
Collapse

How does a project implement the process to persist payment information datain the >Checkout flow for Salesforce B2B Commerce version 4.2 and beyond?

Trigger a remote action when the process payment button is selected to capture the payment.
Trigger a remote action when the process payment button is selected to capture the payment.
Trigger a remote action to store the payment information in the URL query parameters.
Trigger a remote action to store the payment information in the URL query parameters.
Trigger the processPayment event and pass in the payment information object as an argument.
Trigger the processPayment event and pass in the payment information object as an argument.
Trigger the externalprocessedPayment and pass in the payment information object as an argument.
Trigger the externalprocessedPayment and pass in the payment information object as an argument.
Suggested answer: C

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.

asked 23/09/2024
Jorge Andres Gutierrez
30 questions

Question 33

Report
Export
Collapse

How do the REST APIs in Salesforce B2B Commerce support pass-through parameter handling

An exception is generated for unknown API keys
An exception is generated for unknown API keys
Parameters are passed through the service handlers
Parameters are passed through the service handlers
Parameters are filtered out before the request is processed
Parameters are filtered out before the request is processed
Parameters are separated, but unused
Parameters are separated, but unused
Suggested answer: B

Explanation:

The REST APIs in Salesforce B2B Commerce support pass-through parameter handling by passing parameters through the service handlers. This means that any parameters that are not recognized by the REST API framework will be passed to the service handler class that implements the API logic. The service handler class can then use these parameters for custom logic or validation.

asked 23/09/2024
Vyas Dookhun
31 questions

Question 34

Report
Export
Collapse

How is a price group dynamically set?

By overriding the ccLogicProductPrice class
By overriding the ccLogicProductPrice class
By using contract pricing
By using contract pricing
By extending the ccApiPriceList API
By extending the ccApiPriceList API
By extending the cc_hk_priceing hook
By extending the cc_hk_priceing hook
Suggested answer: D

Explanation:

A price group can be dynamically set by extending the cc_hk_pricing hook. This hook allows modifying the price group based on various factors, such as the user, cart, product, or storefront. For example, the hook can apply a different price group for a specific product category or for a specific user segment.

asked 23/09/2024
Sharankumar Nadarajah
32 questions

Question 35

Report
Export
Collapse

Inwhich three different ways can a theme be enabled in

Salesforce B2B Commerce? (3 answers)

A Storefront setting
A Storefront setting
An Account Group field value
An Account Group field value
A per user setting
A per user setting
Account
Account
Dynamically through a hook
Dynamically through a hook
Suggested answer: A, B, E

Explanation:

A theme can be enabled in Salesforce B2B Commerce in three different ways:

A Storefront setting: The theme can be specified in the Storefront Configuration settings in CCAdmin. This will apply the theme to all users who access the storefront.

An Account Group field value: The theme can be specified in the Theme field of an Account Group record in Salesforce. This will apply the theme to all users who belong to that account group.

Dynamically through a hook: The theme can be specified dynamically by extending the cc_hk_theme hook. This hook allows changing the theme based on various factors, such as the user, cart, product, or storefront. For example, the hook can apply a different theme for a specific product category or for a specific user segment.

asked 23/09/2024
chalapathy naidu
39 questions

Question 36

Report
Export
Collapse

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

When different entities are specified in the method invocation.
When different entities are specified in the method invocation.
The sizing block is not removed.
The sizing block is not removed.
SZ_ASSC is used.
SZ_ASSC is used.
The sizing block is removedafter the first handler.
The sizing block is removedafter the first handler.
SZ_ASSC is not used.
SZ_ASSC is not used.
Suggested answer: A, C, E

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

Reference:B2B Commerce and D2C Commerce Developer Guide,Data Sizing Conventions

asked 23/09/2024
waleed Haridi
34 questions

Question 37

Report
Export
Collapse

In which three ways should useful debugging information in Salesforce B2B Commerce implementation be garnered? (3 answers) A) Enabling the logging token via

Admin andsubsequently inspecting the logs via the browser console.
Admin andsubsequently inspecting the logs via the browser console.
Logging a case with Salesforce support to enable advanced debugging options.
Logging a case with Salesforce support to enable advanced debugging options.
Enabling debugging options for the current user and visually inspecting the Salesforce debug logs.
Enabling debugging options for the current user and visually inspecting the Salesforce debug logs.
Placing a System.debug() statement anywhere in the class being debugged.
Placing a System.debug() statement anywhere in the class being debugged.
Logging into the community as a system administrator to identify any potential permissions or Visualforce exceptions.
Logging into the community as a system administrator to identify any potential permissions or Visualforce exceptions.
Suggested answer: A, C, E

Explanation:

Useful debugging information in Salesforce B2B Commerce implementation can be garnered in three ways:

Enabling the logging token via Admin and subsequently inspecting the logs via the browser console. This will enable logging messages and errors to the browser console, which can be viewed by opening the Developer Tools in the browser. The logging token can be enabled by setting the value of CO.logToken to true in CCAdmin.

Enabling debugging options for the current user and visually inspecting the Salesforce debug logs. This will enable logging messages and errors to the Salesforce debug logs, which can be viewed by opening the Debug Logs page in Salesforce Setup. The debugging options can be enabled by creating a Debug Level and a Trace Flag for the current user in Salesforce Setup.

Logging into the community as a system administrator to identify any potential permissions or Visualforce exceptions. This will allow viewing any errors or warnings that may occur on the community pages due to insufficient permissions or Visualforce issues. The system administrator can also access CCAdmin and other tools from within the community. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Logging, Debug Your Code

asked 23/09/2024
Chun Yin Lau
44 questions

Question 38

Report
Export
Collapse

A new payment type for the Checkout flow has been implemented. Which three descriptors follow best practice for possible configuration metadata are needed to enable a flow? (3 answers)

*.pay
*.pay
Cart
Cart
Checkout
Checkout
*.Edit
*.Edit
*.New
*.New
Suggested answer: A, D, E

Explanation:

To enable a new payment type for the Checkout flow, three possible configuration metadata descriptors are needed:

*.pay: This descriptor defines the payment type name, label, description, icon, and handler class. For example,CO.pmts.CreditCard.paydefines the payment type for credit card payments.

*.Edit: This descriptor defines the Visualforce page that is used to edit or update an existing payment of this type. For example,CO.pmts.CreditCard.Editdefines the page that allows editing a credit card payment.

*.New: This descriptor defines the Visualforce page that is used to create a new payment of this type. For example,CO.pmts.CreditCard.Newdefines the page that allows creating a new credit card payment. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Payment Configuration Settings

asked 23/09/2024
benakli rabah
27 questions

Question 39

Report
Export
Collapse

Numerous flags ... have a directimpact on the result set provided by the Global

API's. What Global API Data-Sizing convention flag prevents an API request from propagating to further requests when provided as a Boolean parameter with a value of true?

ccrz.ccAPI.SZ_REL
ccrz.ccAPI.SZ_REL
ccrz.ccAPI.SZ_ASSC
ccrz.ccAPI.SZ_ASSC
ccrz.ccAPISizing.ASSC
ccrz.ccAPISizing.ASSC
ccrz.ccAPISizing.REL
ccrz.ccAPISizing.REL
Suggested answer: B

Explanation:

The Global API Data-Sizing convention flag that prevents an API request from propagating to further requests when provided as a Boolean parameter with a value of true is ccrz.ccAPI.SZ_ASSC. This flag indicates that only one API request should be executed with the specified sizing block, and any subsequent requests should use their own default sizing blocks. For example,ccrz.ccServiceCart.getCart(ccrz.ccAPI.SZ_L,true)will use the SZ_L sizing block for retrieving the cart data, but any other requests that are triggered by this method will use their own default sizing blocks. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Data Sizing Conventions

asked 23/09/2024
Robert Andrade
47 questions

Question 40

Report
Export
Collapse

Numerous flags, when set, have a direct impact on the result set provided by the Global API's. What is the default Global API DataSizing convention flag that is used by theAPI's unless otherwise specified?

CCRZ.ccPAI.SZ_XL
CCRZ.ccPAI.SZ_XL
CCRZ.ccPAI.SZ_M
CCRZ.ccPAI.SZ_M
CCRZ.ccPAI.SZ_L
CCRZ.ccPAI.SZ_L
CCRZ.ccPAI.SZ_S
CCRZ.ccPAI.SZ_S
Suggested answer: B

Explanation:

The default Global API Data-Sizing convention flag that is used by the API's unless otherwise specified is CCRZ.ccAPI.SZ_M. This flag indicates that the medium sizing block should be used for retrieving data, which includes the most commonly used fields and related entities. For example,ccrz.ccServiceProduct.getProducts()will use the SZ_M sizing block by default, unless another sizing block is specified as a parameter. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Data Sizing Conventions

asked 23/09/2024
Stefan Finke
41 questions
Total 221 questions
Go to page: of 23

Related questions