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 ensure that a new product is visible in the Storefront, the following configurations are necessary: A. The product has a Price - Without a set price, the product cannot be purchased, and in many configurations, it might not even be displayed to the customer. B. The Storefront catalog that contains the product is assigned to a site - This ensures that the product is included in a catalog that is actively linked to the storefront site where it is supposed to appear. D. The product is online and searchable - The product must be set to ' online ' to be visible on the storefront. Additionally, being marked as ' searchable ' allows it to be found through the site ' s search functionality.

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.

To associate a region code value with an order in a way that is persistent and accessible whenever the order history is displayed, the best practice within Salesforce B2C Commerce is to use custom attributes on system objects. By defining a custom attribute on the Order system object type, the region code can be stored directly with the order data, ensuring it is available and easily retrievable in any context where order data is accessed.

Option B is correct because:

Custom attributes are designed specifically for extending the data model of system objects like Order with additional information.

This method ensures that the region code is not only saved with the order but is also managed through the platform ' s standard data handling processes, making it robust and integrated with the order management lifecycle.

Other options do not provide a persistent, reliable way to associate data with an order object:

A session variable (Option A) is temporary and not suitable for long-term storage of order-related data.

Creating a custom object type (Option C) would unnecessarily complicate data retrieval and is not as integrated as using a system object ' s attribute.

Storing the region code in a geolocation system attribute (Option D) is not appropriate since geolocation attributes serve a different purpose.

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 update a sandbox environment using a site export file from staging, the Digital Developer should use the “Import & Export” module located under Site Development in the Business Manager. This tool allows developers to import site export files directly into the sandbox environment. This method is efficient and ensures that the environment is updated with the latest staging configurations and data, which can include catalog data, site preferences, and other site-specific settings. This approach is preferred over data replication or manual file transfers, as it ensures a complete and consistent import of the site data.

To add a new order comments attribute to the existing SiteGenesis checkout flow and include it as part of the standard order export, the correct steps involve modifying the system objects and controller logic directly associated with order processing: A. Add the new attribute to the " Order " system object. Modify the " COPlaceOrder " controller to add this new attribute to the current session ' s " Order " object. This approach integrates the new attribute into the existing order data structure, allowing it to be seamlessly included in the standard order export process without the need for additional data handling or storage mechanisms. This method is supported by the Salesforce B2C Commerce documentation on system object extensions and controller modifications for enhancing functionality.

In Salesforce B2C Commerce, when you need to return a custom status code from a job step, you should use the dw.system.Status class to create and return a new status object with the appropriate status and custom status message. The correct code snippet is option B: var status = require( ' dw/system/status ' ); return new Status(Status.OK, ' NO_FILES_FOUND ' ); . This snippet correctly creates a new status object indicating a successful completion ( Status.OK ) but also communicates the specific outcome of " NO_FILES_FOUND " by using the second parameter of the Status constructor to set a custom status message, aligning with the API ' s way of handling custom statuses.

In Salesforce B2C Commerce, the configuration of payment methods is managed through Business Manager. A default payment method is critical for ensuring that there is always an available method for customers to complete purchases. While you can add or disable payment methods as needed, you cannot delete a default payment method from the system configuration. Instead, it can only be disabled if it is no longer needed. This ensures that the site maintains at least one viable payment method at all times, preventing issues during checkout.

When importing configurations specific to different sites into the same sandbox, the XML files that should be imported using site-specific Merchant Tools rather than through the Administration section are: B. Site Jobs - These files relate to scheduled jobs configured at the site level, containing settings and parameters specific to operations within individual sites. D. Promotions - These involve marketing and promotional settings that are typically specific to individual sites, affecting how discounts and special offers are applied and managed within that site ' s context. Importing these using the site-specific Merchant Tools ensures that configurations apply correctly and are managed in the context of the intended site, maintaining consistency and specificity in site operations.