[Jan 10, 2024] Pass Your B2B-Commerce-Developer Dumps Free Latest Salesforce Practice Tests [Q67-Q92]

Share

[Jan 10, 2024] Pass Your B2B-Commerce-Developer Dumps Free Latest Salesforce Practice Tests

Get Top-Rated Salesforce B2B-Commerce-Developer Exam Dumps Now


Salesforce B2B Commerce Developer certification is an excellent way for individuals to advance their careers in the e-commerce industry. It demonstrates their ability to design and develop high-quality solutions that meet the demands of today's B2B customers. Salesforce Accredited B2B Commerce Developer certification also helps organizations identify qualified professionals who can develop and deploy effective B2B e-commerce solutions using Salesforce.

 

NEW QUESTION # 67
Which two statements are true regarding the cc_CallContext class in Salesforce B2B Commerce? (2 answers)

  • A. The class can be used internally within Salesforce B2B Commerce and in subscriber code to access context level parameters
  • B. The Salesforce session is accessible via the getSession method
  • C. The current storefront is accessible via this class
  • D. The userLocale variable returns the current Locale for storefront.

Answer: A,C


NEW QUESTION # 68
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. Click the Tools menu and select Diff Styles Against Org...
  • B. Right-click the folder for the component and choose Diff Files Against Org
  • C. Right-click the CSS file and choose Diff File Against Org
  • D. Right-click the folder for the component and choose Diff Styles Against Org

Answer: C

Explanation:
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]


NEW QUESTION # 69
What is a best practice when passing query parameters from user interface to an apex controller?

  • A. Query parameters should be stored on a backbone model prior to passing them to the server
  • B. Query parameters should be passed only to Salesforce B2B Commerce classes that you are extending.
  • C. Query parameters should be properly sanitized by using JSINHTMLENCODE within the VisualForce Page or Component.
  • D. String parameters should be trimmed using String.trim().

Answer: C


NEW QUESTION # 70
What two things happen with the Cart during tax implementation?

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

Answer: C,D

Explanation:
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


NEW QUESTION # 71
What is true regarding adding more Configuration Settings
to Salesforce B2B Commerce?

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

Answer: B

Explanation:
More modules and metadata can be added to Salesforce B2B Commerce by creating custom configuration settings. Configuration settings are custom settings that store various values and parameters that affect the functionality and appearance of the storefront. They are organized into modules, which group related settings together. To create a custom configuration setting, the user needs to create a custom setting record in Salesforce and specify its module, name, value, and description. The custom setting will then appear in CCAdmin under the specified module. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Configuration Settings


NEW QUESTION # 72
A user wants to leverage a three columnlayout on a page. The user also wants to move the mini-cart widget from the right to the center column. How can this requirement be fulfilled?

  • A. Page Include
  • B. HandleBar Template Override
  • C. Gross Layout Override
  • D. Subscriber Template

Answer: C

Explanation:
To leverage a three column layout on a page and move the mini-cart widget from the right to the center column, the requirement can be fulfilled by creating a Gross Layout Override. This is a custom Visualforce page that overrides the default layout of a page and allows changing its structure and content. The user can create a Gross Layout Override that uses a three column layout and places the mini-cart widget in the center column. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Gross Layout Overrides


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

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

Answer: B,D,E


NEW QUESTION # 74
What isthe difference between Gross Layout Overrides and Subscriber Templates?

  • A. Subscriber Templates allow for modification of the header and the footer, while Gross Layout Overrides allow for modification everything inside the header and footer.
  • B. Gross Layout Overrides allow modification to CSS of a page, while Subscriber Templates allows for modification of the entire page including header and footer.
  • C. Gross Layout Overrides allow for the modification of the footer, while Subscriber Templates allow for modification of everything inside the header and footer.
  • D. Subscriber Templates allows for modification of the header, the footer and the content in between them. Gross Layout Overrides only allow for modification of the header and footer.

Answer: A

Explanation:
The difference between Gross Layout Overrides and Subscriber Templates is that Subscriber Templates allow for modification of the header and the footer, while Gross Layout Overrides allow for modification everything inside the header and footer. Subscriber Templates are custom Visualforce pages that can replace the standard header and footer components on a page. Gross Layout Overrides are custom Visualforce pages that can replace the default layout of a page, such as the number of columns, the position of widgets, or the content of sections. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Subscriber Templates, Gross Layout Overrides


NEW QUESTION # 75
What is a valid way of referencing the global cc_api_CartExtentsion apex class via subscriber code?

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

Answer: B

Explanation:
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


NEW QUESTION # 76
Which two behaviors does a target value of lightning__FlowScreen in metadata allow for a Lightning web component?

  • A. It allows the Lightning web component to replace standard functionality in flows and subflows
  • B. It automatically generates configuration properties for the Lightning web component
  • C. It allows the Lightning Web component to be dragged onto a page in Lightning AppBuilder
  • D. It allows the Lightning web component to be used in guided user experiences to gather input

Answer: B,D

Explanation:
A target value of lightning__FlowScreen in metadata allows for a Lightning web component to be used in guided user experiences to gather input and to automatically generate configuration properties for the Lightning web component. The lightning__FlowScreen target value specifies that the component can be used on a flow screen, which is a type of flow element that displays information and collects user input in a flow. A flow is a guided user experience that can automate business processes and guide users through screens, actions, and decisions. By using the lightning__FlowScreen target value, the developer can expose their Lightning web component as a custom screen component that can be added to any flow screen. The developer can also use the @api decorator to expose public properties of their Lightning web component as configuration properties that can be set in Flow Builder. Flow Builder is a tool that allows the developer to create and modify flows using a drag-and-drop interface. A target value of lightning__FlowScreen does not allow the Lightning web component to replace standard functionality in flows and subflows or to be dragged onto a page in Lightning App Builder, as these are not related to the flow screen target value. Salesforce Reference: Lightning Web Components Developer Guide: Configure Components for Flows, Lightning Web Components Developer Guide: Communicate with Flow, Lightning Flow Developer Guide: Screen Components Basics


NEW QUESTION # 77
What are three ways to implement custom post Order processing? (3 answers)

  • A. Use cc_hk_Order.placeTarget to define a new Order Confirmation page which executes additional business logic.
  • B. Extend cc_hk_invoice tohandle custom business logic post Order processing
  • C. Use Process builder to implement business processes that execute when an Order record is created.
  • D. Modify or add custom Cart formula fields to handle logic.
  • E. Use a Salesforce workflow rule that executes when an Order record is created.

Answer: A,B,C

Explanation:
Three ways to implement custom post Order processing are:
Extend cc_hk_invoice to handle custom business logic post Order processing. This hook allows modifying the invoice data or performing additional actions after an Order is placed. For example, the hook can send an email notification or update a custom field on the invoice record.
Use cc_hk_Order.placeTarget to define a new Order Confirmation page which executes additional business logic. This hook allows specifying a custom Visualforce page that will be displayed after an Order is placed. The custom page can include additional business logic or user interface elements.
Use Process Builder to implement business processes that execute when an Order record is created. Process Builder is a tool that allows creating workflows and actions based on criteria and conditions. For example, Process Builder can create a task, send an email, or update a record when an Order record is created. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Hooks, Process Builder


NEW QUESTION # 78
Which two statement are true for Mass Order (2 answers)

  • A. Mass order works with the default wishlists
  • B. Mass Order is mobile ready with the ccrz templates.
  • C. Mass Order pricing is done via a batch job.
  • D. The variation product is leveraged for SKUs.

Answer: C,D


NEW QUESTION # 79
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 an Apex class that implements the sfdc_checkout.PaymentGatewayAdapter
  • B. Create a RegisteredExternalService record for the custom payment provider class.
  • C. Create an Apex class that implements the commercepayments.PaymentGatewayAdapter.
  • D. Create a PaymentProviderGateway record for the custom payment provider class.
  • E. Create a named credential for authentication with the payment provider.

Answer: A,D,E

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 Reference: B2B Commerce Developer Guide: Payment Integration, B2B Commerce Developer Guide: Payment Gateway Adapter Interface, B2B Commerce Developer Guide: Payment Provider Gateway Object


NEW QUESTION # 80
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.defv (Map<String.Object> mp, String key , Object ob)
  • D. ccrz.ccUtil.defVal (Map<String.Object> mp, String key, Object ob)

Answer: D

Explanation:
The ccrz.ccUtil.defVal (Map<String.Object> mp, String key, Object ob) method 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. This method is useful for providing fallback values for configuration settings or input parameters that may be missing or invalid. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, ccUtil Class


NEW QUESTION # 81
Which two usages of ccLog should be avoided in Salesforce B2B Commerce? (2 answers)

  • A. ccrz.ccLog.log(System.LoggingLevel.ERROR, 'D:something', myCallToGetMessage(pl) ), where myCallToGetMessage(pl) is a method invocation
  • B. crz.ccLog.log(System.LoggingLevel.DEBUG, 'D:myOrder', myOrder), where myOrder is an order object
  • C. crz.ccLog.log(System.LoggingLevel.WARN, 'D:something', 'Something unexpected occurred: The data we were expecting for pl was not there,')
  • D. crz.ccLog.log(System.LoggingLevel.DEBUG, 'D:myOrderList', myOrderList), where myOrderList is a list of orders

Answer: A,C


NEW QUESTION # 82
Which method needs to be implemented when rendering a Salesforce B2B
Commerce view in order to have it called after rendering has finished?

  • A. postRender()
  • B. onRender()
  • C. There are no methods called on the view after rendering has finished
  • D. afterRender()

Answer: A

Explanation:
The method that needs to be implemented when rendering a Salesforce B2B Commerce view in order to have it called after rendering has finished is postRender. This method is an optional hook that can be defined by the user to perform any actions or logic that depend on the view being rendered, such as initializing widgets, binding events, or updating the user interface. The method will be called by the render method of the CCRZ.View class, which is the base class for all views in the framework. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, View Class


NEW QUESTION # 83
What are three advantages of using ccLog over the Salesforce
standard System.debug class? (3 answers)

  • A. There is no need to use string concatenation to easily tag log statements with a subject.
  • B. There is no need to manually set a cookie to debug with the Site Guest User.
  • C. ccLog can debug syntax errors found in the JavaScript.
  • 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 create a User Trace Flag.

Answer: A,B,E


NEW QUESTION # 84
An administrator has just provided a developer with a completely new org and a username. Assuming the username is [email protected], what is the correct set of steps to authorize the org for Command Line Interface (CLI) access so the developer can deploy Lightning web components?

  • A. Run the command 'sfdx force:auth:web:login -r "https://login.salesforce.com" -username^'mefaJmy-new-org.org"'
  • B. Run the command: 'sfdx force:login -r "https://login.salesforce.com'' and supply the credentials in the browser when it opens.
  • C. Run the command: 'sfdx force:auth:web:login -r "https://login.salesforce.com" and then supply the credentials in the ^ browser when it opens ^
  • D. Run the command 'sfdx force:auth:web:login -a "https://login.salesforce.com'"' and then supply the credentials in the browser when it opens.

Answer: C

Explanation:
To authorize the org for Command Line Interface (CLI) access so the developer can deploy Lightning web components, the developer should run the command: 'sfdx force:auth:web:login -r "https://login.salesforce.com" and then supply the credentials in the browser when it opens. The sfdx force:auth:web:login command is a Salesforce CLI command that authorizes an org using the web server flow. The web server flow is an OAuth 2.0 authentication flow that opens a browser window and prompts the user to log in to Salesforce and allow access to the CLI. The -r flag specifies the login URL of the org, which is https://login.salesforce.com for production or developer orgs. Running this command will open a browser window and ask the developer to enter their username and password for the org. After successfully logging in, the developer will be able to use the CLI to perform various tasks with the org, such as deploying or retrieving metadata, running tests, or executing commands. Running the command: 'sfdx force:login -r "https://login.salesforce.com" is not a valid way to authorize the org for CLI access, as there is no such command as sfdx force:login. Running the command 'sfdx force:auth:web:login -a "https://login.salesforce.com"' is not a valid way either, as the -a flag specifies an alias for the org, not a login URL. Running the command 'sfdx force:auth:web:login -r "https://login.salesforce.com" -username'[email protected]"' is not a valid way either, as there is no such flag as -username. Salesforce Reference: Salesforce CLI Command Reference: force:auth:web:login, Salesforce Developer Tools for Visual Studio Code


NEW QUESTION # 85
Why is the use of a standard Visualforce control such as apex:form discouraged in Salesforce B2B Commerce page includes and subscriber pages?

  • A. The CCRZ Javascript object is not accessible within an apex:form control.
  • B. Apex:form render DOM components slowly
  • C. Visualforce "scopes" controls that are present on a page and scope of the control will be set to "ccrz"
  • D. Javascript events are not supported within an apex:form control

Answer: C


NEW QUESTION # 86
Which two are considered discrete units of work (code units) within a transaction in the debug logs?

  • A. Lightning component load
  • B. Validation rule
  • C. Web service invocation
  • D. Apex class

Answer: C,D

Explanation:
Two data types that are considered discrete units of work (code units) within a transaction in the debug logs are web service invocation and Apex class. A discrete unit of work (code unit) is a segment of executable code that runs as part of a transaction in Salesforce. A transaction is a sequence of operations that are treated as a single unit of work and are executed under certain isolation and consistency rules. A transaction can consist of one or more discrete units of work (code units) that are executed sequentially or concurrently depending on various factors such as triggers, asynchronous calls, or limits. A debug log is a record of database operations, system processes, and errors that occur when executing a transaction or running unit tests in Salesforce. A debug log can capture information about each discrete unit of work (code unit) within a transaction, such as its start time, end time, duration, events, variables, and limits. A web service invocation is a type of discrete unit of work (code unit) that involves calling an external web service from Apex code using SOAP or REST protocols. A web service invocation can be synchronous or asynchronous depending on the method used to make the callout. A web service invocation can be captured in a debug log with its details and results. An Apex class is another type of discrete unit of work (code unit) that involves executing Apex code that defines a class with properties and methods. An Apex class can be invoked from various sources such as triggers, Visualforce pages, Lightning components, or API calls. An Apex class can be captured in a debug log with its details and results. A validation rule is not a type of discrete unit of work (code unit) within a transaction in the debug logs, as it is not a segment of executable code but rather a formula expression that defines a business rule for a field or object. A validation rule can be evaluated during a transaction and cause an error if the rule condition is not met, but it cannot be captured as a separate code unit in a debug log. A Lightning component load is not a type of discrete unit of work (code unit) within a transaction in the debug logs either, as it is not a segment of executable code but rather an event that occurs when a Lightning component is rendered on a web page or application. A Lightning component load can be measured by various performance tools such as Lightning Inspector or Lighthouse, but it cannot be captured as a separate code unit in a debug log. Salesforce Reference: [Salesforce Developer Blog: Transactions and Request Processing], [Salesforce Help: Debug Logs], [Salesforce Developer Guide: Invoking Callouts Using Apex], [Salesforce Developer Guide: Apex Classes], [Salesforce Help: Validation Rules], [Salesforce Developer Blog: Measuring Lightning Component Performance]


NEW QUESTION # 87
A developer attempts to export data from an org by launching Data Loader, selecting a standard entity, clicking the "Select All Fields" button and clicking the Finish button. The developer finds that the CustomField_c field they added to the entity has no values under the header in the CSV file output. What is the root cause?

  • A. The developer does not have the correct JDK that is recommended by Salesforce and this is known to cause issues with exporting custom attributes
  • B. The field is not populated
  • C. The developer does not have access to the object's metadata
  • D. The user does not have rights to the custom field

Answer: D

Explanation:
The root cause of why the CustomField__c field they added to the entity has no values under the header in the CSV file output is that the user does not have rights to the custom 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 developer does not have the correct JDK that is recommended by Salesforce and this is known to cause issues with exporting custom attributes is not the root cause of why CustomField__c has no values under the header in the CSV file output, as it is not related to field access or Data Loader functionality. The developer does not have access to the object's metadata is not the root cause either, as it is not related to field access or Data Loader functionality. The object's metadata defines its structure and properties, such as fields, relationships, and layouts. The field is not populated is not the root cause either, as it contradicts the fact that CustomField__c has no column header in the CSV file output. If the field was not populated but accessible to the user, Data Loader would still include CustomField__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]


NEW QUESTION # 88
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.

Answer: C

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 Reference: Lightning Web Components Developer Guide: Communicate with Properties, Lightning Web Components Developer Guide: Decorators


NEW QUESTION # 89
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)

  • A. *.pay
  • B. *.Edit
  • C. *.New
  • D. Cart
  • E. Checkout

Answer: A,B,C

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.pay defines 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.Edit defines 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.New defines the page that allows creating a new credit card payment. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Payment Configuration Settings


NEW QUESTION # 90
Which two statement are true for Mass Order (2 answers)

  • A. Mass Order is mobile ready with the ccrz templates.
  • B. Mass order works with thedefault wishlists
  • C. Mass Order pricing is done via a batch job.
  • D. The variation product is leveraged for SKUs.

Answer: C,D

Explanation:
Mass Order pricing is done via a batch job, which means that the prices are not calculated in real time, but rather at a scheduled time. Mass order works with the variation product, which is a product that has multiple SKUs with different attributes, such as size or color. Mass order does not work with the default wishlists, which are used to store products that the customer wants to buy later. Mass order is not mobile ready with the ccrz templates, which are the default templates for the storefront pages. Salesforce Reference: B2B Commerce Developer Guide: Mass Order, B2B Commerce Developer Guide: Variation Products


NEW QUESTION # 91
Which two steps are necessary to enable Salesforce B2B Commerce
logging in the managed package?

  • A. Ensure the value saved in the Logging token field is appended to the ccLog query parameter.
  • B. Set a cookie with the Id of the user accessing the storefront in CC Admin
  • C. Ensure you save a value in the Logging Token input field in the Global Settings section of CC Admin.
  • D. Turn On the Checkbox "Cloudcraze Logging" in CC Admin.

Answer: A,C


NEW QUESTION # 92
......

Passing Key To Getting B2B-Commerce-Developer Certified Exam Engine PDF: https://realexamcollection.examslabs.com/Salesforce/Salesforce-Developer/best-B2B-Commerce-Developer-exam-dumps.html