Salesforce Updated B2C-Commerce-Architect Exam Questions and Answers by gurfateh

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

• Option Ainvolves 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 Dcalls 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 customizing the Storefront Reference Architecture to meet specific requirements, the following items would require detailed technical documentation:

• Option A (One Click checkout process): Implementing a one-click checkout process involves significant customization to streamline the checkout flow, potentially requiring integration with payment providers and modifications to the user session management.
• Option C (Log in through a standard OAuth2 social media account): Integrating OAuth2 for social media logins involves handling authentication tokens, user sessions, and potentially syncing user data with the B2C Commerce profiles, all of which require detailed security and integration documentation.

These customizations require careful planning and implementation to ensure they work seamlessly with existing Storefront Reference Architecture components and meet security standards.

To resolve issues where some customers are not seeing the correct pricing on the Product Detail 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.

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.