The Salesforce Certified B2C Commerce Architect (Arch-303) (B2C-Commerce-Architect)

To resolve the issue of violating the spi.basket.addResolveInSameRequest quota and to maintain the functionality of dynamically calculating shipping costs for items before they are added to the basket, the best approach is:

Option D : Wrapping the adding of product and shipping cost calculation in a transaction, which is then rolled back to restore the original state. This method ensures that the system can calculate potential shipping costs without permanently altering the state of the basket. This approach keeps the basket ' s original state intact while allowing for multiple shipping calculations, effectively managing the load on system resources and adhering to platform quotas.

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.

Considering the existing metrics and forecasted 300% growth, the appropriate load testing targets for the new B2C Commerce site would be:

15000 visits per hour : This figure is calculated by applying the expected growth to the peak visits per hour (1000 visits), resulting in 4000 visits. The choice of 15000 provides a higher buffer to accommodate unforeseen spikes in traffic.

300000 page views per hour : Similarly, this is scaled up from the peak page views per hour (20000) considering the growth, ensuring the site can handle high demand and interactions.

3750 orders per hour : This target is based on the peak orders per hour (250) with the growth applied, allowing testing of the system ' s ability to handle transactions under significant load.

These targets ensure that the system is robust enough to handle increased traffic and transactions without performance degradation, crucial for maintaining customer satisfaction and operational stability.

Given the concerns about the reliability of the OMS, implementing scheduled batch exports ensures that order data is not lost due to potential OMS downtime and allows for reattempting failed exports. Option B uses SFTP for a high-frequency batch export, which can be scheduled to run multiple times a day, ensuring minimal delay in order synchronization while marking orders as exported upon successful transmission. Option C provides a similar safeguard but via web service, which can be scheduled to run hourly. Both methods enable tracking of export status and can handle temporary downtimes by reattempting the export until successful, aligning with the need for reliability in integration processes.

For efficient caching of HTTP GET requests used to fetch product reviews, the best practice is to use a cached remote include combined with caching of the HTTP service itself (Answer D). This method involves caching the output of the remote service call at the service layer and reusing it for subsequent requests. This approach minimizes the number of calls to the remote service, reduces load times, and ensures that the displayed reviews are up-to-date as per the cache ' s freshness settings. It optimally balances the performance benefits of caching with the need to keep content like reviews current.

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.

When QA encounters issues with login persistence across multiple computers, where subsequent logins lead to a redirection and an emptied basket, the likely culprit could be unintended caching of login-related pages or processes. In Salesforce B2C Commerce, certain cache settings might inadvertently cause user sessions to be shared or not properly invalidated. The recommendation D, to check the login form and related templates for caching directives that might be erroneously caching login actions or user-specific data, addresses this potential issue. Developers should ensure that pages handling user sessions and authentication are configured to disable caching, thus preventing session data from being mistakenly retained or shared across different users.

In scenarios where a third-party service impacts page performance, implementing a Circuit Breaker pattern (Option C) can prevent the service from becoming a bottleneck. This pattern helps manage failing service calls by temporarily disabling the service interaction when failures reach a certain threshold, allowing it to recover. Asynchronously loading the data (Option E) ensures the page ' s primary content loads without delay, while data from the third-party service is fetched in the background, improving the user ' s perceived performance and page load times.

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.