Salesforce B2C-Commerce-Architect Practice Test Questions Answers

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 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.

The provided data schema includes several fields that do not match the stated business requirements, which focus on the custom dimensions and materials of the containers:

Option A: The inclusion of unique identifiers for materials and color fields in the data schema suggests a level of detail and structure around these attributes that is not reflected in the business requirements. If the business does not require tracking or differentiating materials beyond just naming them, this might be unnecessarily complex.

Option D: The data schema includes a Color_ID field, which implies the ability to specify the color of the container. However, the business requirements do not mention color as a customization option available to customers. This discrepancy needs to be addressed to ensure that the database design aligns with actual business needs.

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 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.