Free Salesforce-B2C-Commerce-Cloud-Developer Practice Test Questions (2026)

Explanation:

The Storefront Toolkit is the primary debugging and diagnostic tool for investigating frontend issues in B2C Commerce. When the wrong shopper's address appears on the Account Addresses page, the Toolkit provides several critical capabilities:

Session Inspection: View current session data including customer ID, authentication status, and basket contents to verify which customer's data is being loaded.
Pipeline Debugging: Trace through the Account-AddressList pipeline to see exactly what data is being fetched and how it's being processed.
Template Debugging: Inspect the ISML template rendering to see which address data is being passed to the view.
Request/Response Analysis: Examine HTTP requests and responses to identify data mismatches or caching issues.
Cookie and Session Tracking: Check authentication tokens and session cookies that might be causing customer mix-ups.

The Toolkit is accessible by appending ?debug=true to storefront URLs and provides real-time debugging without requiring code changes or redeployment. This makes it the ideal starting point for diagnosing display issues where the wrong customer data appears.

Why Other Options Are Incorrect

Option A (Pipeline Profiler): Useful for performance optimization but not for content debugging. It shows pipeline execution times, not data content.
Option B (Code Profiler): For server-side script performance analysis, not for diagnosing frontend display issues.
Option D (Reports and Dashboards): Provides business analytics, not technical debugging capabilities for specific page rendering issues.

References
Storefront Toolkit Documentation: "Debugging Frontend Issues"
B2C Commerce Troubleshooting Guide: "Using the Debug Toolkit"
Customer Data Management: "Session and Authentication Debugging"
SFRA Development: "Diagnostic Tools for Storefront Issues"

Explanation:

Why This Answer Is Correct
The optimal sequence for setting up a development environment with both SFRA reference data and custom site data is:

Task B: Import the SFRA Demo Sites - Start with a clean SFRA baseline. This provides:
- Standard SFRA functionality and templates
- Demo products, categories, and content
- Reference implementation for development

Task A: Import the custom Site - Overlay custom configurations on top of SFRA:
- Custom site definitions and preferences
- Custom templates and configurations
- Maintains SFRA foundation while adding customizations

Task C: Rebuild the custom Site search indexes - Final step to ensure product visibility:
- Indexes products from both SFRA demo data and custom imports
- Enables search and category browsing
- Should be done last after all data is imported

This sequence ensures that SFRA provides the foundational framework, custom configurations are applied correctly, and search functionality works with the complete product catalog.

Why Other Options Are Incorrect

Option A (A, C, B): Would import custom data first, then try to rebuild indexes (with incomplete data), then overlay SFRA—potentially overwriting custom configurations.

Option B (B, C, A): Would rebuild indexes after SFRA import but before custom import, requiring another rebuild anyway.

Option C (A, B, C): Would start with custom data that might not have SFRA dependencies, potentially causing conflicts or missing functionality.

References
SFRA Implementation Guide: "Setting Up Development Environments"
Site Import/Export Documentation: "Import Sequencing Best Practices"
Search Index Management: "When to Rebuild Indexes"
Development Workflow: "Combining Demo and Custom Data"

Explanation:

Why "D" is Correct
The Storefront Toolkit (SFT) Request Log provides immediate feedback during local development and debugging. To make custom debug statements appear in the SFT Request Log in real-time, the logging category must be activated at the appropriate log level (DEBUG) within the Custom Log Settings in Business Manager. The SFT Request Log honors the configured log levels. If the category is set to "Error," debug messages won't show up. If it's set to "Debug" or "Info," they will.

Why Other Options are Incorrect
A & B (Enable custom logging checkbox): There is no such specific checkbox in "Global preferences" or "Site Preferences" that globally enables all custom logs in the SFT Request Log. Logging is managed by the Log Settings module.

C.Check the DEBUG box for Select Log Levels Written to Files: This setting controls what gets written to the persistent file on the server's disk (available via WebDAV). It doesn't specifically control what appears in the real-time streaming SFT Request Log window. The SFT log dynamically reads based on the active log levels set in the config.

References
Salesforce Developers: Storefront Toolkit Request Logs
Salesforce Help: Custom Log Settings Configuration

Explanation:

The B2C Commerce Service Framework includes built-in support for "Mocking." This allows developers to simulate a service response without actually making an outgoing network call. This is critical when the external API provider has not finished building the endpoint.

To implement this:
mockCall: In the service definition script, the developer implements the mockCall function, which returns a hard-coded or generated response object that mimics the expected real API response.

Service Mode: In Business Manager (or via script), the Service Mode is changed from Live to Mock. When the code executes service.call(), the framework sees the "Mock" mode and immediately executes the mockCall logic instead of the createRequest logic, allowing the developer to test their business logic seamlessly.

Why the Incorrect Answers are Wrong
A is incorrect: The callback is named mockCall, not mockfull.
C and D are incorrect: While using Site Preferences to toggle between two different service objects or using conditionals works, it is considered a "hack" or anti-pattern. The Service Framework already provides a native, standardized way to handle mocking without adding extra "if/else" complexity to the business logic.

References
Salesforce Developers: Mocking Services
dw.svc.ServiceCallback API Reference

Explanation:

To create a link in an ISML template, a developer must handle both the URL generation and the localized text correctly.

URLUtils.url('Account-Show'): This is the mandatory API for generating URLs in B2C Commerce. It ensures that the URL includes the correct protocol (http/https), site context, and any necessary session identifiers. Using hardcoded strings or custom URL builders is a security risk and can break SEO or session persistence.

Resource.msg(): This is the API for retrieving localized text from .properties files. It takes the key (myaccount), the bundle name (account), and a default value or null. This allows the "My Account" link to automatically translate into different languages based on the shopper's locale.

Why the Incorrect Answers are Wrong
- A is incorrect: URLUtils.get() is not a valid method; the correct method is .url().
- B is incorrect: url.get() is not a standard B2C Commerce API for templates. Resource.message() is also incorrect; the method is .msg().
- D is incorrect: ResourceMgr.getProperties() returns a map of all properties in a bundle; it is not the correct way to retrieve a single string for a link.

References:
dw.web.URLUtils API Reference
ISML: Localizing Templates

Explanation:

Why This Answer Is Correct
Apple Pay configuration and geographic restrictions are managed in the Payment Methods module of Business Manager. To disable Apple Pay for specific countries like Denmark:

Navigation Path: Merchant Tools > Ordering > Payment Methods
Locate Apple Pay: Find Apple Pay in the payment methods list
Country Restrictions: Configure which countries can use Apple Pay
Disable Denmark: Remove Denmark from allowed countries or add to excluded countries

The Payment Methods module provides granular control over:
Which payment methods are available
Geographic restrictions per payment method
Customer group restrictions
Order amount limitations
Site-specific configurations

For Apple Pay specifically, Business Manager typically provides:
Enable/disable toggle
Merchant certificate configuration
Supported country list
Currency restrictions
Display preferences

Disabling for Denmark ensures Danish customers won't see Apple Pay as a checkout option, while keeping it available for other European countries as required.

Why Other Options Are Incorrect
Option A (Locale Payments): Not a standard Business Manager module. Locale settings affect language/currency, not payment method restrictions.
Option C (Payment Processors): Configuration for backend payment processing (gateways, credentials), not frontend payment method availability by country.
Option D (Apple Pay): While Apple Pay might have its own configuration section, country restrictions are managed within the broader Payment Methods module, not a separate Apple Pay module.

References
Payment Configuration Guide: Geographic Restrictions for Payment Methods
Apple Pay Integration: Country-Specific Configuration
Business Manager Modules: Payment Methods Management
Multi-Country Store Setup: Payment Method by Country

Explanation:

In Salesforce B2C Commerce, libraries are used to store reusable content such as content assets, content slots, and media files. When multiple sites share a library, they gain access to the same content assets, enabling reuse and centralized content management.

In this scenario, two sites share a library while one site uses a private library. This means that only the sites sharing the library can access the same content assets. Libraries are not locale-specific; rather, locales are handled within content assets themselves via localization features.

Therefore, the shared library enables sharing content assets between sites, which is exactly what option C describes.

Why the Other Options Are Incorrect

A. Sharing content slots between sites
❌ Incorrect. Content slots are site-specific and cannot be shared across sites, even if they use the same library.
B. Sharing content assets among locales
❌ Incorrect. Locales do not require shared libraries. Localization is handled inside the content asset.
D. Sharing content slots among locales
❌ Incorrect. Content slots are not locale-based; they are site-based.

References
Salesforce B2C Commerce Documentation – Libraries
Salesforce Content Management Guide
Salesforce B2C Commerce Site Development Guide

Explanation:

The Storefront Reference Architecture (SFRA) is built on a "Plug-and-Play" philosophy. To modify an existing business process—like adding a step to the registration flow—the best practice is to Extend the route using middleware.

Using the server.append() or server.prepend() methods allows a developer to add new logic to an existing route without touching the original base code. For example, if you need to perform an extra check or save extra data during registration, you append a new middleware function to the Account-Registration route. This ensures that the original registration logic still runs, but your new step is executed as part of the chain. This makes the code easier to maintain and upgrade.

Why the Incorrect Answers are Wrong

A. Change the controller route...: Modifying the base cartridge code directly is an "anti-pattern." It makes future upgrades to SFRA nearly impossible because your custom changes will be overwritten.

C. Copy the code...: This leads to "code rot." If the original route is updated for a security patch, your copied version will remain vulnerable.

D. Override the route...: While server.replace() exists, it is used to completely swap out the original logic. If you only need to add a step, extend (append/prepend) is the correct and safer choice to ensure the core registration still functions.

Reference
Salesforce Developers: Extending Controllers
Infocenter: SFRA Middleware

Explanation:

B2C Commerce's logging system uses hierarchical category inheritance and specific file naming conventions. Given the configuration:

Category Inheritance: category1.eu and category1.us inherit settings from category1 (their parent category) because no explicit configurations exist for them
Enabled Level: category1 is configured for WARN level, meaning all descendant categories (category1.eu, category1.us) also log at WARN level unless explicitly configured otherwise
Log File Naming: Custom log files follow the pattern custom-{category}.log when no specific filename is configured
Level-Based Filtering: DEBUG level messages (from the code snippet) won't be written because only WARN level is enabled

Since loggerFile is specified as the category in the logging code (Logger.getLogger('loggerFile')), and this category isn't explicitly configured in Business Manager, it likely inherits from a parent configuration or uses default settings. However, the question's setup suggests loggerFile would be treated as a custom logging category.

With all custom log targets enabled and no specific configuration for loggerFile, the system creates a log file named custom-loggerFile.log (following the standard custom-{category}.log naming convention) and writes WARN level messages to it. DEBUG messages from the code won't appear because only WARN level is enabled for the parent category configuration.

Why Other Options Are Incorrect

Option A: Logs will be written because custom log targets are enabled and a parent category (category1) is configured at WARN level, providing a configuration context.
Option B: Missing the custom- prefix that B2C Commerce automatically prepends to custom log filenames.
Option D: Uses incorrect level-based naming (customwarn) rather than category-based naming (custom-loggerFile).

References
Custom Logging Documentation: "File Naming Conventions"
Log Category Inheritance Guide: "Parent-Child Category Relationships"
Business Manager Log Configuration: "Custom Log File Creation"
Debugging Implementation: "Understanding Log File Naming"

Explanation:

In the provided SFRA controller snippet (implied context), if a developer sees an error or a "failure to show" in the debugger for a variable like viewdata, it is usually a result of Hoisting or Implicit Globals in JavaScript.

If a developer writes viewdata = res.getViewData(); without the var, let, or const keyword, they are assigning a value to a variable that hasn't been declared in the current scope. While the B2C Commerce script engine is somewhat permissive, modern debuggers often struggle to "watch" or inspect variables that are not properly scoped to the current function. If the debugger is stopped at a specific line and the variable was never formally declared in that scope, it may not appear in the "Local Variables" list, even if it holds a value.

Why the Incorrect Answers are Wrong
A. cache.applyDefaultCache is not a valid middleware: This is a standard SFRA middleware and would not prevent a variable from being inspected.
B. viewdata is declared but not assigned: If it were declared (var viewdata;), the debugger would show it as undefined, not fail to show it entirely.
D. viewdata is a reserved name: viewdata is not a reserved keyword in JavaScript or the B2C Commerce API.

Reference
Salesforce Developers: Debugging B2C Commerce Scripts