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

The service method that should be overridden in order to allow ''without sharing'' queries is ccrz.ccService.initSVCDAO. This method is responsible for initializing the service data access object (SVCDAO) that is used by the service class to perform queries. By overriding this method, the user can specify the sharing mode of the SVCDAO, which will determine whether the queries respect or ignore the sharing rules of the current user. For example,ccrz.ccService.initSVCDAO(ccrz.ccAPI.SZ_WITHOUTSHARING)will initialize the SVCDAO with the without sharing mode. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Service Classes,ccService Class

Three actions that are applicable when extending a default Salesforce B2B Commerce page via a page include are:

Create the VisualForce page you wish to include to the Salesforce B2B Commerce page. This page will contain the custom content or logic that you want to add to the existing page. For example, you can create a VisualForce page named MyPageInclude that displays some additional information or functionality on the product detail page.

Create a configuration setting for enabling the page include and assigning the new page include via CC Admin. This setting will specify which page include you want to use for which page and section. For example, you can create a configuration setting named CO.MyPageInclude with the value PDV.BodyIncludeBegin.MyPageInclude, which means you want to use MyPageInclude as the body include begin for the product detail view (PDV) page.

Build and activate a new configuration cache setting via CC Admin. This action will refresh the cache and apply the changes to the storefront. You need to do this whenever you make any changes to the configuration settings or VisualForce pages. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Page Includes

Three actions that are applicable when modifying the number of steps required in the Salesforce Commerce Checkout flow are:

Perform a template override on the Checkout page. This action will allow you to change the structure and content of the Checkout page, such as adding or removing sections, widgets, or fields. For example, you can override the checkout.handlebars template and modify it according to your requirements.

Set the value of the configuration setting defined as CO.overrideFlow to TRUE. This setting will enable you to use your own custom checkout flow instead of the default one. You need to set this value to true before you can modify the checkout flow.

Set the value of the configuration setting defined as CO.useDef to TRUE. This setting will enable you to use a single-page checkout flow instead of a multi-step checkout flow. You need to set this value to true if you want to reduce the number of steps in the checkout flow to one. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Checkout Flow

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

Reference:B2B Commerce and D2C Commerce Developer Guide,Subscriber Pages

Three pages that should be enabled for the Guest user profile for a storefront to have anonymous checkout are:

CCPaymentInfo: This page allows the guest user to enter their payment information, such as credit card number, expiration date, and security code. The page also displays the order summary and total amount.

CheckoutNew: This page allows the guest user to enter their shipping and billing information, such as name, address, phone number, and email. The page also displays the cart items and shipping options.

OrderConfirmation: This page displays the confirmation message and order number after the guest user places their order. The page also provides a link to view the order details or print the invoice. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Anonymous Checkout

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

Three statements that are true regarding event handling in the Salesforce B2B Commerce managed package are:

Salesforce B2B Commerce relies on a central event channel for communication across various Salesforce B2B Commerce Backbone Views and Models called CCRZ.pubSub. This object allows different components to publish or subscribe to events without being coupled with each other. For example, CCRZ.pubSub.trigger('cartChange') will publish an event named cartChange that can be subscribed by any component that needs to react to it.

CCRZ.pubSub defines the following three functions which can be used for event handling: trigger, on, and once. The trigger function is used to publish an event with a name and optional arguments. The on function is used to subscribe to an event with a name and a callback function. The once function is similar to on, but it will only execute the callback function once for each event.

CCRZ.pubSub extends the Backbone.Events JavaScript object. This object provides methods for managing events in Backbone.js, which is a JavaScript framework that provides models, views, collections, and events for building single-page applications. CCRZ.pubSub inherits all the methods and properties of Backbone.Events and adds some custom ones. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Events,PubSub Class

Three steps that are necessary to have a subscriber page added to Salesforce B2B Commerce after creating a custom Visualforce page are:

Create a new CC Subscriber Page record that points to your custom Visualforce page. This record will store information about the subscriber page, such as the name, description, URL, and Visualforce page. For example, you can create a new record named MySubscriberPage that points to your custom Visualforce page named MyPage.

Refresh the Page Keys Index in CC Admin. This action will update the page keys index, which is a cache that stores the mapping between the page keys and the subscriber pages. You need to do this whenever you create or modify a subscriber page record.

Enable the Subscriber Page in CC Admin. This action will allow you to select the subscriber page from the CC Page Settings configuration and assign it to a CC Page. For example, you can enable MySubscriberPage and assign it to the Home page. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Subscriber Pages

Two aspects that are applicable to Page Includes are:

Standard Visualforce controls such as apex:form should not be used within a page include. This is because the page include is rendered inside an existing Visualforce page that already has a form element. Using another form element inside the page include will cause conflicts and errors. Instead, the page include should use HTML elements or custom components that do not require a form element.

Page Includes can be configured as Body Includes Begin. This means that the page include will be rendered at the beginning of the body section of the page, before any other content or widgets. This can be useful for adding some custom content or functionality that applies to the whole page, such as a banner, a modal, or a script. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Page Includes