B2C Commerce Architect Certification (ARCH-303) - Salesforce

To resolve issues where some customers are not seeing the correct pricing on the Product Detail<br />
<br />
Page, the following places should be examined: Global Preferences (C): It's critical to check the global preferences settings to ensure they align with the intended pricing strategy and configurations. This includes checking currency settings, pricing rules, and tax configurations, which can all influence the pricing displayed to customers. Error during replication (D): If there were errors during data replication, this could lead to inconsistencies such as incorrect pricing being shown. Ensuring that data has been replicated correctly and without errors is essential, particularly when moving from staging to production environments. Cache settings (E): Incorrect cache settings or outdated cached data can cause old or incorrect pricing to be displayed. Clearing the cache or verifying that cache invalidation rules are correctly set can resolve such issues. These steps are critical for ensuring that the displayed pricing is accurate and consistent, providing a seamless user experience.

For deploying new services related to a payment LINK cartridge to Production, the correct method is<br />
through Code Replication (D). This approach ensures that all new code changes, including the integration services, are consistently applied across different environments. Code replication covers deploying all changes made in code, scripts, and service configurations from a staging or development environment to the production environment. This process ensures that all new functionalities are tested in a controlled environment before being moved to production, reducing the risk of errors affecting the live site.

Considering the existing metrics and forecasted 300% growth, the appropriate load testing targets for<br />
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.

For logging practices in a complex LINK cartridge integration, the recommendation is:<br />
Get logger for cartridge-specific category (C): This practice allows for more precise and relevant logging by focusing on the specific cartridge, making troubleshooting more efficient. Report debug level message for the back-end asynchronous communication: This ensures that all detailed interactions are logged, providing valuable data for diagnosing issues. Report all errors at error level message: This categorizes all critical issues under error logs, which is essential for quick identification and resolution of problems affecting the system's operations. This structured logging strategy enhances the ability to monitor and troubleshoot the system effectively, especially in complex integrations where multiple components interact asynchronously.

The appropriate tool to verify that the problem is indeed caused by the inventory check at the beginning of checkout is the Pipeline Profiler in Business Manager. This tool allows an architect to analyze the performance of specific code execution paths, including those involving third-party API calls. It helps identify bottlenecks and inefficiencies in the pipeline execution, particularly useful in situations where custom code like inventory checks may impact site functionality. The use of the Pipeline Profiler would enable the architect to pinpoint if the custom inventory check is causing the checkout process to fail or redirect users inappropriately.