When attributes do not appear for a custom object in the Business Manager, it ' s typically because they are not organized into an attribute group. To resolve this issue, the developer should create an attribute group and include all the desired attributes within this group. This configuration allows the attributes to be properly displayed and managed in the Business Manager. This practice ensures that attributes are correctly categorized and accessible, which aligns with Salesforce B2C Commerce ' s data management strategies and administrative best practices.

Based on the given OCAPI definitions in the image, the permission specified allows only the " put " method under " methods " . This method corresponds to the HTTP PUT request, typically used for updating resources. In the context of the OCAPI setting, this would specifically allow external applications to update existing coupons on the Salesforce B2C Commerce platform. There are no permissions granted for creating or deleting coupons, or for handling coupon codes, as the methods for those actions (POST for creating and DELETE for deleting) are not listed.

To diagnose an issue where the Account Addresses page is showing the wrong shopper ' s address, the best tool to start with is the C. Storefront Toolkit . This tool allows developers to inspect the storefront ' s behavior in real-time, providing insights into the rendered content, application state, and session data, which can help identify issues related to shopper context mismanagement or session data errors. It offers a direct view into how data is being presented to the user, making it a first-line tool for diagnosing user-facing issues.

For supporting German language strings in Salesforce B2C Commerce, the developer needs to:

A. checkout_de.properties in resources folder Resource bundles in Salesforce B2C Commerce are managed per locale by naming the file with the appropriate locale suffix. For German ( de ), the resource bundle file should be named checkout_de.properties and placed in the resources folder. This file will then contain all the German translations for the strings used in the checkout process, allowing the system to automatically fetch the correct localized strings based on the user’s locale setting.

To disable Apple Pay for a specific country such as Spain, the appropriate module in the Salesforce B2C Commerce Business Manager is:

Merchant Tools > Site Preferences > Payment Types (D) : This module allows the developer to configure and manage different payment methods available on the site, including enabling or disabling them for specific countries or regions.

Options like Payment Methods (A) and Payment Processors (C) generally deal with setting up and managing the details of how payments are processed but do not specifically allow for enabling/disabling payment methods by country. There is no specific module under " Apple Pay " in Site Preferences (B), as Apple Pay settings would be grouped under general payment types settings.

In Salesforce Commerce Cloud, the proper storage location for translation files for specific locales follows a structured directory path to ensure that the system correctly recognizes and applies the translations. The correct path for storing locale-specific translation messages, such as for the French locale, is under cartridge/templates/resources/fr . This structure allows the platform to efficiently load the appropriate resources based on the locale settings, ensuring that the correct translations are displayed for each supported locale.

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.

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 " .