B2C-Commerce-Developer Salesforce Certified B2C Commerce Developer (SU24) Questions and Answers

In Salesforce B2C Commerce, the $httpUrl method is used to generate a fully qualified URL to a specified route. For creating a link within a content asset to another content asset, you should use the $httpUrl function with the appropriate pipeline and parameters. In this case, ' Content-Show ' is the correct pipeline to use for fetching content assets based on their ID, and the ' cid ' parameter specifies the content asset ID. Thus, $httpUrl( ' Content-Show ' , ' cid ' , ' terms-and-conditions ' )$ correctly generates the URL needed to link to the content asset with the ID " terms-and-conditions " .

The method ProductSearchModel().getProductSearchHits() is efficient and scalable because it utilizes the product search index rather than conducting a direct search within the database. This indexing method enables quicker retrieval of product information and is optimized for performance in scenarios where multiple products need to be fetched based on various criteria. Using the product search index means that data retrieval is managed through indexed fields, which is significantly faster than querying a database directly for each request. This approach not only improves performance but also reduces the load on the database, making it a scalable solution for e-commerce environments where high traffic and large product catalogs are common.

The valid configuration to implement a call to an authentication-protected REST web service is to add the authentication password to the service credentials (Option A). This approach ensures that the credentials required for authentication are securely stored and utilized in the service configuration. Typically, credentials for external services should be configured within the service framework in Salesforce B2C Commerce, which allows for secure storage and usage of sensitive information such as passwords, thereby maintaining security best practices.

The initServiceClient callback method in the dw.svc.ServiceCallback class is specifically required when invoking a SOAP service because it is used to initialize and configure the SOAP service client before making the service call. This method sets up necessary configurations such as SOAP headers, namespaces, and other SOAP-specific settings that are not required for RESTful services. Other methods like createRequest , mockCall , and parseResponse are used in both SOAP and REST services but initServiceClient is unique to SOAP due to its specific requirements for client initialization.

To reduce the unavailability of a critical internally-hosted web service noticed in the service status reports, two practical solutions would be: A. Modify the code to include a try/catch block around the request to the external service. This approach ensures that even if the service is unavailable, the application can handle the error gracefully and continue functioning, possibly with a fallback mechanism. C. Increase the web service timeout. This allows the service more time to respond before the request is considered failed. It can be particularly useful if the service unavailability is due to delays in response rather than outright outages.

Both these strategies are recommended in handling external service interactions to ensure robustness and resilience in the application. They are supported by standard programming practices and Salesforce Commerce Cloud ' s guidelines on external integration.

The hook dw.ocapi.shop.basket.calculate is ideal for integrating taxation logic when preparing a storefront to use OCAPI in Salesforce B2C Commerce Cloud. This hook allows the system to apply custom business logic, such as tax calculations, each time the basket ' s totals are calculated. This ensures that the order totals remain consistent and accurate across various customer interactions and API calls.

Option B ( dw.ocapi.shop.basket.calculate ) : Correctly applies tax logic during the calculation of basket totals, which is critical for ensuring that all updates to the basket (like adding items, applying discounts, or changing quantities) consider tax implications correctly.

This approach aligns with the best practices for extending OCAPI in Commerce Cloud to maintain consistency in order totals, especially when the basket state changes.

After the server-side controller code is defined in Salesforce B2C Commerce Cloud, it is necessary to ensure that it can be consumed by other parts of the application. This is done by exporting the server object. The correct way to make a server-side controller available for page component display is by using the server.exports() method. This approach is validated by typical usage patterns seen in the SFRA where controllers are modular and need to be exported for application-wide accessibility.

For making Open Commerce API (OCAPI) requests in Salesforce B2C Commerce Cloud, the URL format must correctly specify the sandbox environment domain, site ID, API type (shop or data), API version, and relevant endpoint. The correct URL format for a sandbox environment involves using the .demandware.net domain, the site identifier, and the appropriate API version and endpoint.

Option C: https://test.demandware.net/s/test-site/dw/shop/v18_3/products/M1355?client_id=aaa... is the correct format because it uses:

test.demandware.net - Correct sandbox domain.

/s/test-site - Correct path to specify the site ID.

/dw/shop/v18_3 - Correctly specifies the OCAPI ' shop ' API with version ' v18_3 ' .

/products/M1355 - Specifies the endpoint for retrieving product information by ID.

Other options incorrectly format the domain, path, or omit necessary API path components as per Salesforce B2C Commerce Cloud OCAPI standards.

When logging information about an operation that succeeds but has an unexpected outcome that may produce side effects, the appropriate log level is: D. Logger.warn(‘Unexpected service response’) - The warn level is used to indicate potentially harmful situations that are not immediate errors but could potentially lead to issues. It’s appropriate here because the operation did not fail outright, but the outcome was not as expected, warranting attention but not a full error declaration.

For storing country-specific data such as price book details and image URLs for a country flag, particularly in a multi-country Salesforce B2C Commerce implementation, the most effective approach is to use a replicable, site-specific Custom Object. Custom Objects in B2C Commerce are ideal for storing structured data that can vary from one site to another and need to be replicated across different environments from staging to production. This method allows developers to maintain a consistent data structure while being able to tailor the data content to specific country requirements without impacting the global data model. Additionally, Custom Objects can be managed through Business Manager and replicated across environments, making them suitable for both development and production settings.

When choosing between a content slot and a Page Designer component, an important factor to consider is localization capabilities. Only Page Designer components can be localized for different languages. This feature is crucial for merchants who need to manage site content in multiple languages from the Business Manager, enabling them to modify content per locale without developer intervention. Content slots, while flexible for many uses, do not support localization directly, making Page Designer components the preferable choice for multinational and multilingual sites. This distinction is critical in enabling merchants to manage localized content effectively within Salesforce Commerce Cloud.

In Salesforce B2C Commerce, extending existing controllers and routes is the recommended approach for adding new functionalities to adapt to business requirements without disrupting the existing codebase. By extending a route, developers can add new steps or logic to the registration process in a modular and maintainable manner. This technique involves using hooks or calling super functions where applicable, ensuring that the base functionality is preserved while new features are integrated seamlessly. Extending a route allows for easier updates and maintenance compared to copying or overriding entire routes, which can lead to future upgrade issues or conflicts with other customizations. This approach aligns with Salesforce B2C Commerce ' s best practices for scalability and maintainability in development.

Two possible reasons why a newly created Storefront category in storefront-catalog-m-en is not visible on the storefront site are: A) The Storefront catalog is offline - If the catalog is not active, none of its contents, including new categories, will be displayed on the storefront. B) The category does not contain available products - A category without products will typically not appear on the storefront as there is nothing to display under that category. Categories need to have at least one available product to be visible to customers.

These factors are crucial in ensuring the visibility of categories on the storefront and should be checked whenever a category does not appear as expected.

In the Salesforce B2C Commerce logging system, logs are categorized by severity levels, which include DEBUG, INFO, WARN, and ERROR. With the log level set to WARN in the Business Manager, any log entries with a severity of WARN or higher (which includes ERROR) will be recorded. Therefore, the messages from log.warn( " This is a warn message " ) and log.error( " This is an error message " ) will be written to the log. The INFO and DEBUG messages will not be recorded since their severity is lower than the WARN level set in the configuration.

To integrate with an external web service using HTTP requests and set up a testing mechanism using the Service Framework in Salesforce B2C Commerce, the best approach is to implement the mockFill callback and set the service mode to " mock " . This configuration allows the developer to test the integration with a simulated response from the service. By using the mockFill method, developers can specify the expected response from the external service when it is not yet available. This approach is particularly useful for testing and debugging the integration in a controlled environment before the actual web service goes live. Setting the service mode to " mock " enables this simulated environment, ensuring that the service behaves as if it is interacting with the actual external service.

QUESTIONNO: 67

A developer needs to update the package.json file so that it points to the hock file for a cartridge, using the hooks keyword. Which snippets work correctly when added to the file?:

A. { “hooks”: “./cartridge/scripts/hooks.json” }

B. { “hooks”: “./scripts/hooks.json” }

C. { hooks: “./cartridge/scripts/hooks.json” }

D. { hooks: ./scripts/hooks.json }

Answer: A

In the context of Salesforce B2C Commerce Cloud, particularly when configuring hooks in a package.json file for a cartridge, the correct format to specify the location of the hooks configuration file must be a valid JSON string. The snippet { " hooks " : " ./cartridge/scripts/hooks.json " } is correctly formatted as it includes double quotes around both the key and the value, which is a requirement in JSON syntax. The path ./cartridge/scripts/hooks.json correctly assumes that the hooks configuration file is located within a cartridge in the scripts directory, which is a common setup in SFCC. This matches best practices as documented in the Salesforce Commerce Cloud Script API documentation and developer guides.

In Salesforce B2C Commerce, controllers are responsible for handling application logic and responding to user requests. The operations best suited to be done in a controller include: A. Generate the response as JSON or HTML - Controllers handle the final rendering of data in the desired format for the client, whether as web pages (HTML) or data endpoints (JSON). B. Use the Script API to generate data for the view - Controllers often leverage server-side Script APIs to fetch or manipulate data necessary for the view. E. Use the model needed for the view - It is a common practice to construct models that encapsulate data and business logic which are then passed to the view for rendering, keeping views clean and focused solely on presentation.

For setting up a new site correctly in Salesforce B2C Commerce, it ' s essential to configure certain default settings to ensure the site functions properly:

Assign a default payment method : This setting determines the payment options available to customers and is critical for the checkout process. A default payment method ensures that there is always at least one valid payment option for customers to use.

Assign a default currency : Setting a default currency is crucial for displaying prices, processing transactions, and managing financial records in the local currency of the market the site serves. This ensures that all monetary values are relevant to the customer ' s locale.

These configurations are foundational for the operational readiness of the site, affecting both user experience and backend processing.

To change the functionality of a content slot from displaying top sellers to rendering a specific content asset, the following actions are necessary:

Change the Content Type: Since the merchant wishes to shift from displaying products to a content asset, it ' s necessary to change the content type in the slot configuration. This defines what type of content the slot will handle (from products to content assets).

Change the Rendering Template: The rendering template used for displaying top sellers (likely product-focused) will not be suitable for a content asset. It needs to be changed to a template that is designed to render content assets, facilitating a more personalized content experience.

These two changes ensure that the slot is reconfigured to suit the new purpose without the need for deleting and recreating the slot, which preserves any existing settings and customizations. This approach is more efficient and less error-prone.

In order to view DEBUG level messages for the myLogCategory in the Request Log tool of Salesforce B2C Commerce, the developer will need to adjust both the log category settings and the log file settings, as detailed in option C.

Here’s why both adjustments are necessary:

Changing the Log Level for myLogCategory to DEBUG : Initially, the log level for myLogCategory is set to INFO as seen in the image. This means that only INFO and higher severity messages (WARN, ERROR, FATAL) will be logged under this category. To capture DEBUG messages, the log level must be explicitly set to DEBUG. This step ensures that DEBUG messages are generated and considered for logging.

Checking the DEBUG box in the Log Files section : This section controls which log levels are actually written to the log files. Even if DEBUG messages are generated (after adjusting the log level for myLogCategory ), they won’t be written to the log files unless DEBUG is specifically selected in the Log Files settings. By default, only FATAL, ERROR, and WARN levels are selected to be written to files, as shown in the image. To include DEBUG messages in the logs, this setting must be adjusted to check the DEBUG box.

Both steps are necessary because one dictates the generation of DEBUG level logs ( myLogCategory set to DEBUG), and the other dictates the persistence of these logs in the log files (checking the DEBUG box). If only one of these actions is performed, DEBUG messages for myLogCategory will not be fully enabled and viewable in the Request Log tool.

Therefore, the correct and complete action to take is option C: Change the Log Level for myLogCategory to DEBUG and check the DEBUG box in the Log Files section.

Efficient and scalable methods for accessing product data in Salesforce B2C Commerce involve: B. ProductSearchHit.getRepresentedProducts() - This method retrieves the products represented by search hits in a search result. It is efficient because it allows batch retrieval of product data based on search criteria, reducing the need for individual product queries. C. ProductSearchModel.getProductSearchHits() - This method retrieves a collection of search hits from a product search, which can be used to fetch multiple products efficiently. Using a search model to manage product data retrieval is scalable as it leverages indexed search data rather than querying all products directly.

Both methods are part of the Commerce Cloud ' s search framework, designed to handle large volumes of data efficiently and are recommended for scalable product retrieval operations. The direct querying methods like ProductMgr.queryAllSiteProducts() and Category.getProducts() can be less efficient and scalable due to their broad scope and direct database access.

To fulfill the requirement of saving SKUs of out-of-stock products and customer emails for notification purposes, the most effective solution is to create a new custom object type. This custom object type would include a set-of-string type custom attribute to store the SKUs of products a customer is interested in and a string type custom attribute for storing the email address of the customer. This approach allows for greater flexibility and organization, making it easier to manage and query the data as needed for notifying customers when products are back in stock.

In Salesforce B2C Commerce, passing control to an ISML template along with data involves using ISML.renderTemplate() . This method allows passing a dictionary of data to the template. In the case where you want to load a product on the pipeline dictionary with the name myProduct , the correct way to pass this product to the ISML template is to use the product ' s variable name as the key in the dictionary. Thus, {product: myProduct} correctly associates the variable myProduct with the key product which the ISML template can reference. This ensures that within the ISML template, the product can be accessed using the key product .

To configure the RefArch site to use the same customer list as another site, such as RefArchGlobal, the developer should select RefArchGlobal from the dropdown for Customer List in the site settings as shown in the screenshot. This direct selection changes the customer list that the RefArch site references, enabling it to utilize the same customer data as RefArchGlobal without the need for importing customer data or enabling customer list sharing options. This setting is site-specific and directly modified in the site ' s general settings in Business Manager.

To disable the " Discover " credit card type for all checkouts in Salesforce B2C Commerce, the developer should:

B. Credit card exclusion rules in the Merchant Tools > Site Preferences > Payment Preferences module. In the Business Manager, the Payment Preferences module under Site Preferences allows administrators to configure which credit cards are accepted by setting credit card exclusion rules. This module provides a user interface where specific credit card types, such as " Discover " , can be enabled or disabled across the site. This is the correct approach to centrally manage payment options without requiring code changes.

In Salesforce B2C Commerce, when log levels are configured for specific categories and subcategories, the settings dictate the minimum level of logging that will be captured. If WARN logging is enabled for the ' product ' category, it means that WARN and ERROR logs will be recorded for ' product ' and all its subcategories because ERROR is a higher severity level than WARN. However, if DEBUG is enabled specifically for the ' product.import ' subcategory, this setting will additionally capture DEBUG and INFO logs for ' product.import ' . This granular control allows developers to capture more detailed logs where needed while maintaining a higher-level overview for broader categories.

In Salesforce B2C Commerce, site preferences allow customization and configuration of various site-specific settings, which can be managed independently across different regional sites on the same instance. By creating a new custom preference under the Site Preference object type, developers can introduce a setting that specifies the number of products eligible for gift wrapping per order for each specific site. This approach provides the flexibility needed to adjust these numbers independently for the U.S. and European markets as required by the business logic. Such preferences are accessed and modified through the Business Manager, ensuring that business users can easily update them without needing further code deployment. This solution aligns with Salesforce B2C Commerce ' s best practices for managing site-specific behaviors and configurations without hardcoding values, thereby maintaining scalability and manageability across multiple market-specific sites.

When extending a system object in Salesforce B2C Commerce, such as adding a new attribute to the Product object, custom attributes are accessed through the custom namespace. Therefore, if a Boolean attribute named " sellable " is added to the Product object, it should be accessed as prod.custom.sellable . This approach is part of the platform ' s data customization framework, where custom provides a namespace for all user-defined extensions to system objects, ensuring that they do not conflict with existing system properties. Detailed usage and examples of accessing custom attributes can be found in the Salesforce Commerce Cloud Script API documentation under " System Object Types " .

In scenarios where a job executes a pipeline that makes calls to an external system, the following actions can help prevent performance issues: B. Configure a timeout for the script pipelet. Setting a timeout ensures that the job does not hang indefinitely if the external system does not respond within a reasonable timeframe. This prevents the pipeline from being blocked by a slow or non-responsive external service. D. Use asynchronous import or export jobs. Asynchronous jobs allow the main execution flow to continue without waiting for the external system’s response, which can improve the overall performance of the system by not delaying other operations.

These actions are recommended within Salesforce Commerce Cloud for managing interactions with external systems efficiently, as detailed in the " Performance Best Practices " and " Asynchronous Processing " sections of the documentation.

To create a content slot that is included on the homepage and displayed correctly, the code should specify the context appropriate to the homepage. The correct line of code, <</b> isslot id= " my_banner " description= " for home page " type= " global " context= " homepage " / > , indicates that the slot is a global type and the context is set to " homepage " . This means the content slot ' my_banner ' is designed to be used across various pages of the site but specifically renders in the homepage context, aligning with common ISML template practices.