B2B-Commerce-Developer Salesforce B2B Commerce for Developers Accredited Professional (AP-202) Free Practice Exam Questions (2025 Updated)

The XML fragment that the developer should include in the component’s configuration XML file to ensure the custom component is available to add to the page is option B. Option B uses the tag to specify where thecomponent can be used in an app. The tag contains a list of tags, each of which defines a valid target for the component. The value of the tag for the Product Detail page in the store is lightningCommunity__RecordPage, which means that the component can be used on any record page in a Lightning community. Option A is incorrect because it uses an invalid value for the tag. There is no such target as lightningCommunity__ProductDetailPage. Option C is incorrect because ituses an invalid syntax for the tag. The tag should not have any attributes, such as isAvailable. Option D is incorrect because it uses an invalid syntax for the tag. The tag should not be self-closing, but rather havea closing tag (). Salesforce References: Lightning Web Components Developer Guide: Configure Components for Lightning Communities, Lightning Web Components Developer Guide: Configure Components for Different Pages and Apps

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 overridingthis 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 theSVCDAO with the without sharing mode. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Service Classes, ccService Class

It is preferableto 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, whichallows logging messages and errors to the debug log or to a custom object. This can facilitate debugging and troubleshooting of the remote action.

In Salesforce, standard page reference types are used within the Lightning Component framework to reference different types of resources. The types includestandard__appfor Salesforce apps,standard__componentfor Lightning components, andstandard__recordPageto reference a specific record detail or edit page (notstandard__recordDetailPage, but it's implied). Thestandard__pageNamedandcomm_loginPageare not standard page reference types recognized by Salesforce. For more details, refer to the Salesforce documentation on PageReference Types:Salesforce PageReference Types Documentation.

When naming a Lightning Web Components folder and associated files, Salesforce best practices allow the name to begin with a lowercase letter and to use a single hyphen (dash) forcompound names. Whitespace and underscores are not recommended in the naming convention. This is in line with web standards for custom elements. More details can be found in the Salesforce LWC documentation on naming conventions:Salesforce LWC Naming Conventions.

The ccrz.ccUtil.defVal (Map 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 References: B2B Commerce and D2C Commerce Developer Guide, ccUtil Class

The conversion flag that allows for sObjectsto be returned from the Global API’s when provided as a Boolean parameter with a value of true is ccrz.ccAPI.SZ_SOBJECT. This flag indicates that the API should return the raw sObjects instead of the transformed objects that are usually returned by the API. For example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_SOBJECT,true) will return the Product2 sObjects instead of the ccrz__E_Product__c objects. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Data Sizing Conventions

In the context of Salesforce debug logs, code units represent discrete units of work within a transaction. Apexclasses (B), Web service invocations (C), and Workflow invocations (E) are considered code units as they encapsulate specific operations or sets of logic that can be executed as part of a transaction. Validation rules (A) and the loading of Lightning components (D) are not considered discrete units of work in the same way, as they are part of the declarative interface and front-end framework, respectively. For more details on how Salesforce handles transactions and debug logs, refer to the Salesforce Developer Documentation:Salesforce Developer Documentation on Transactions and Debug Logs.

When implementing an Inventory class for checkout and indicating that inventory is available for all items and amounts in the cart, the correct step is to returnsfdc_checkout.InventoryStatus.Status.SUCCESS. This indicates to the checkout process that the inventory check has passed and theitems are available. Salesforce documentation on customizing inventory validation in the checkout process would detail the expected return types and values, ensuring that developers implement the inventory checks in a manner consistent with the platform'srequirements.

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 References: B2B Commerce and D2C Commerce Developer Guide, API Classes

The event that is invoked by anyCCRZ Salesforce B2B Commerce View after the view is rendered is view:*:rendered. This event is triggered by the render method of the CCRZ.View class, which is the base class for all views in the framework. The event can be used to perform any actions or logic that depend on the view being rendered, such as initializing widgets, binding events, or updating the user interface. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Events, View Class

The handlebars helper function that is used on Salesforce B2B Commerce pages and components for formatting price values is formatPrice. Thisfunction will format a numeric value as a price according to the currency settings and locale of the storefront. For example, {{formatPrice price}} will format the price value as $1,234.56 for US dollars or €1.234,56 for euros. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Handlebars Helpers

The Global JavaScript Object that should be extended when writing custom Remote Actions is CCRZ.cc. This object contains all the Remote Actions that are defined in the cloudcraze managed package, which can be overridden or extended by subscriber code. The object also provides a mechanism for registering custom Remote Actions that can be invoked by the user interface components. For example, CCRZ.cc.customAction = function(params, callback){ // do something } will define a custom Remote Action named customAction that can be called by CCRZ.cc.customAction(params, callback). Salesforce References: B2B Commerce and D2C CommerceDeveloper Guide, Remote Actions

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 References: B2B Commerce and D2C Commerce Developer Guide, Hooks, Process Builder

In Lightning Web Components, to access the DOM elements within the component's template, including those passed into slots, developers usethis.template.querySelector()andthis.template.querySelectorAll(). These methods allow for querying the component's local DOM. Direct DOM manipulation or querying outside the component's template is discouraged to maintain component encapsulation and security. For more information, see the Salesforce LWC documentation on accessing the DOM:Salesforce LWC DOM Access Documentation.

The event that should be triggered when user facing info, warning or error messages need to be displayed on a Visualforce page is pageMessage. This event is triggered by the displayPageMessage method of the CCRZ.util class, which is a utility class thatprovides various helper methods for common tasks. The event can be used to display a message on the page with a specified type, title, and text. For example, CCRZ.util.displayPageMessage('error', 'Oops!', 'Something went wrong.') will trigger the pageMessage event and display an error message on the page. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Events, Util Class

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 thatoccur 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 webservice 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 Apexclass 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 rulecondition 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 codebut 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 separatecode unit in a debug log. Salesforce References: [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]

The sizing keys used in the Salesforce B2B Commerce Global APIs perform five distinct operations. Three of these operations are:

Refetch data (used on some Logic classes): This operation indicates that the data should be refetched from the database instead of using the cached data. For example, ccrz.ccServiceCart.getCart(ccrz.ccAPI.SZ_REFETCH) will refetch the cart data and refresh the cache.

Related Query to call (sub queries or direct queries): This operation indicates that the related entities should be retrieved by using sub queries or direct queries. For example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_SUBQUERY) will use sub queries to fetch the related entities for each product, while ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_DIRECTQUERY) will use direct queries to fetch the related entities separately.

Object type casting: This operation indicates that the data should be cast to a specific object type. For example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_SOBJECT) will cast the data to sObjects instead of transformed objects. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Data Sizing Conventions

 A developer needs to make a call to a long running web service which is critical to finalizing their checkout process. The developer should consider the following items in their implementation:

A new CORS entry may need to be created in Setup. CORS stands for Cross-Origin Resource Sharing, which is a mechanism that allows web browsers to make requests to servers on different domains. If the web service is hosted on a different domain than the B2B Commerce site, the developer may need to add a CORS entry in Setup to allow the browser to access the web service. This entry specifies the origin, path, and method of the request, as well as any headers or cookies that are allowed1.

A new Named Credential may need to be created in Setup. A Named Credential is a type of metadata that stores the URL and authentication settings of a web service. By using a Named Credential, the developercan avoid hardcoding the web service URL and credentials in their code, and instead reference the Named Credential by name. This makes the code more secure and easier to maintain2.

An Apex method returning a Continuation will need to be created. A Continuation is a special type of Apex object that allowsthe developer to make asynchronous calls to long running web services. By using a Continuation, the developer can avoid blocking the main thread and improve the user experience. A Continuation method must return a Continuation object, specify the web service URL and parameters, and register a callback method that handles the response3.

Option D and Option E are incorrect because they are not relevant to the scenario. Option D suggests that the developer should broker the requests to the web service, which means to use an intermediary service that manages the requests and responses. This may be useful for some scenarios, but it is not required for making a call to a long running web service. Option E suggests that the developer should create a new Remote Site in Setup, which is a way to whitelist the domains that can be accessed from Apex code. However, this is not necessary if the developer uses a Named Credential, which automatically handles the Remote Site setting2. References:

Set UpCORS

Named Credentials

Continuation Class