Free Practice Questions for the Salesforce Architect Exams B2C-Commerce-Architect Exam (2026 Updated)

Reducing the basket lifetime is a strategic approach to minimizing the impact of disabling a promotional coupon. This action will cause baskets that may still contain the now-disabled coupon to expire sooner, thereby reducing the potential volume of calls to the Call Center from customers inquiring about the coupon. This method also avoids the drastic measure of clearing all existing baskets or restarting the production instance, which could disrupt user experience and lead to further customer dissatisfaction.

When facing build failures that are not reproducible in developers ' environments, a common and effective first step is to clean up the build server workspace (Answer A). This action clears any residual files, settings, or data that might be influencing the build process and causing discrepancies between local and server builds. By resetting the workspace to a clean state, it helps ensure that the build process is starting from a consistent base, potentially resolving issues caused by stale data or corrupted build artifacts. This step often resolves hidden configuration or environment-specific issues that are not immediately apparent in the code or module versions.

To manage custom settings for a product finder that needs to be accessible both on the storefront and in a job context, storing these settings in a Custom Object with an Organizational Scope is most appropriate. This allows the settings to be centralized and accessible across different sites and job contexts, ensuring consistency and reusability of the configurations:

Organizational Scope : Enables settings to be shared across multiple sites without duplicating data, maintaining a single source of truth for configurations that affect various parts of the organization.

Custom Object : Provides the flexibility to define specific attributes and values that are unique to the business requirements of the product finder and other integrations.

For integrating the B2C Commerce platform with the client ' s OMS using REST services, the required configurations include:

Service Configuration : This specifies the service endpoints, HTTP methods, and any other service-specific settings necessary for the integration.

Service Profile Configuration : This defines the behavior of the service such as timeout settings, retry logic, and cache settings.

Service Credential Configuration : This involves setting up the credentials that will be used to authenticate the requests to the client’s OMS. These credentials are often managed securely through encrypted storage and retrieval mechanisms.

These configurations ensure secure, efficient, and reliable communication between the B2C Commerce platform and the client’s OMS, adhering to best practices in web service integration.

This approach addresses all concerns: data retention, reattempt on failure, and follow-up communication. By storing survey data in a custom object, data is preserved even if the API call fails, allowing for reprocessing. This method also facilitates sending follow-up emails by querying custom objects for surveys that were skipped, ensuring comprehensive coverage and reliability in data handling and customer engagement.

The code sample shows the creation of a service request to a third-party service provider, where the authentication method is explicitly set to ' NONE ' using the line svc.setAuthentication( " NONE " ); . This configuration implies that the request does not use Basic Authentication or any embedded credentials like client ID and secret in the HTTP headers for authentication purposes. Instead, it builds the authentication details into the request body, which suggests that the service expects credentials as part of the payload rather than as part of the standard authentication headers, thus effectively disabling Basic Auth for this transaction.

For optimal job flow concerning data import from a PIM system, the sequence should begin with downloading files globally from an SFTP site, followed by importing data into the B2C Commerce platform:

First flow : Download files, ensuring all required files are available and ready for import.

Second flow : Import the storefront catalog which likely has dependencies on the master catalog but is generally smaller and can be updated more rapidly.

Third flow : Import the master catalog, as it typically contains the foundational data needed for various site functionalities.

This sequence respects data dependency and integrity, ensuring that the storefront reflects the most current and accurate information after all relevant data is imported.

For integrating a LINK cartridge that is certified for pipelines and controllers into a system using the Storefront Reference Architecture (SFRA), which primarily uses scripts instead of the older pipeline technology, the architect should update the job pipelines to work as custom job steps. This approach allows the existing LINK cartridge functionalities to be maintained while making them compatible with the SFRA framework. Custom job steps enable more flexibility and the ability to leverage the full capabilities of SFRA, ensuring that the jobs run correctly within the newer architecture.

When facing a deprecated API that is used in a LINK integration cartridge, the recommended approach is to check for an updated version of the cartridge that may have replaced the deprecated API with a supported one. If an update is available:

Integrate the updated cartridge into the site, ensuring compatibility with the current site configuration.

Re-apply customizations that were made to the original cartridge to maintain functional consistency.

Thorough testing should be conducted to ensure that the integration works seamlessly without causing disruptions in the site ' s functionality.

This approach minimizes effort by leveraging updates provided by the cartridge vendor while ensuring the site remains functional and compliant with current API standards.

For the shoe producer implementing Salesforce B2C Commerce, the attribute used to specify the type of shoes (boots, sandals, sneakers) should be set as a single selectable value, hence the use of an enum-of-string type. This data type allows for the selection of one option from a predefined list, which is ideal for cases where each product can only be categorized into one type. This ensures that data integrity is maintained while providing clear and distinct categorization that can easily be used for filtering on the Product Search Results page and for customized messaging on the Product Detail page.

Given that the OMS provides a web-service interface and updates tracking numbers for orders modified the previous day, it is crucial to manage the potential risks of service unavailability or delays that could lead to thread exhaustion in Salesforce Commerce Cloud. Implementing a circuit breaker pattern helps to manage failures gracefully by halting the interaction with the OMS if it becomes unresponsive, thereby preventing the service from impacting the entire system. Additionally, configuring timeouts ensures that the service calls do not hold up resources indefinitely. These strategies help maintain system stability and responsiveness, particularly when dealing with external systems over which there may be limited control.

To implement a specific cache period for Page Designer pages in SFRA:

Option A involves creating a new Page.js controller in the client’s cartridge, where the existing Page-Show route can be modified to include a custom caching logic. This ensures that the specific caching requirements for Page Designer pages are met without altering the base functionality for other pages.

Option D calls for extending the existing cache.js module in the client’s cartridge to include a function specifically for Page Designer caching. This allows for reusing the existing caching logic while adding enhancements specific to the Page Designer pages, thus maintaining efficiency and clarity in the codebase.

Both options provide a clean, maintainable approach to customizing caching for specific requirements in SFRA, avoiding disruptions in other areas of the site functionality.

For handling multiple pricing groups with specific discounts or prices for different customer groups, the optimal approach involves setting up separate customer groups for customers, employees, and vendors (Answer A). This setup allows the storefront to apply specific price books to each group accurately based on their designation. Furthermore, utilizing campaigns and multiple promotions tailored to each customer group (Answer C) facilitates targeted marketing efforts and pricing strategies effectively. These practices ensure that each group receives relevant pricing adjustments and promotional offers, thereby enhancing the shopping experience and managing financial transactions efficiently within Salesforce B2C Commerce.

For Northern Trail Outfitters to ensure that only products available in a customer’s closest physical store are shown:

Option B is effective because it organizes inventory by store-specific categories, which can then be dynamically linked to a customer’s location via their postal/zip code. This allows the system to filter search results based on the relevant category that corresponds to the closest store.

Option D leverages separate pricebooks that are specific to each store, enabling product availability to be managed through price refinements. This method also uses the customer ' s zip code to activate the appropriate pricebook, ensuring that only products priced (and thus available) in the nearest store are displayed.

Both methods are scalable and integrate seamlessly with the existing infrastructure of the Salesforce B2C Commerce platform.

When integrating a new brand ' s ecommerce site into an existing realm, the architect needs to ensure that product data and inventory from the new brand ' s Enterprise Resource Planning (ERP) system are correctly managed within the realm. Therefore, creating new import jobs for products (Answer B) and inventory (Answer C) is essential. These import jobs will facilitate the synchronization of the new brand’s product catalog and inventory levels with the existing Order Management System (OMS) and Customer Relationship Management (CRM) systems of the realm. Such integration is crucial for maintaining up-to-date product and inventory information across the systems, ensuring seamless operations and data consistency.

The optimal solution for this requirement is to modify the search results dynamically based on the user ' s customer group membership. This approach:

Ensures that all users can navigate the same catalog and categories without seeing separate categories for special segments.

Dynamically includes or excludes products from search results based on the user ' s membership in the special segment, effectively using existing catalog structures while personalizing product visibility.

Maintains scalability by leveraging existing catalog and category infrastructure without needing additional custom attributes for navigation purposes.

This method aligns with best practices for creating personalized customer experiences in B2C Commerce without complicating catalog management.