B2C-COMMERCE-ARCHITECT Practice Questions

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.

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.

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.

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.

To resolve the issue of incorrect page versions being served across different devices, changing the

URL structure to include device-specific parameters can be highly effective. By adding parameters

such as 'desktop' or 'mobile' to the URLs:

The caching mechanism can differentiate between the content for different device types, thus

caching and serving the correct version of the page according to the device type specified in the URL.

This method allows for maintaining existing caching strategies linked to promotions and ensures that

SEO is not adversely affected since the content remains the same per device type but is merely

served through different URLs.

This approach addresses the core issue without requiring disabling of caching or reengineering

existing promotional structures, hence preserving site performance and user experience.

To resolve issues where some customers are not seeing the correct pricing on the Product Detail

Page, the following places should be examined:

Global P

(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 a service that connects to an Email Marketing System where the endpoint can directly parse data

posted by the customer from the storefront for marketing material subscriptions, documenting the

service as an HTTP service is appropriate. This type of service will likely involve straightforward HTTP

requests with authentication and encoding to ensure data integrity and security. The HTTP service

type supports these requirements effectively, facilitating secure, reliable data transmission between

the storefront and the email marketing system.

To resolve the issue of Cross Site Scripting (XSS) where the quick search is not escaped, the developer

should use the tag with the 'jshtml' encoding option (Answer B). This method ensures that

any JavaScript included in the search phrase is properly escaped, preventing the execution of

potentially malicious scripts. The 'jshtml' encoding is specifically designed to encode text for HTML

contexts where JavaScript is embedded, providing a secure way to handle user input in Salesforce

B2C Commerce.

To enhance the security of the notification controller exposed for marking orders as paid, the

recommended approach is to add an order-specific token to the callback URL (Answer C). This token

should be verified against a stored value on the order to ensure the authenticity and integrity of the

payment notification. This method prevents unauthorized use of the controller, as only callbacks

containing the correct, order-specific token would be allowed to mark orders as paid. This strategy is

essential in maintaining secure and reliable transaction processes within Salesforce B2C Commerce.

When integrating a third-party service that relies on custom objects in B2C Commerce, the primary

technical concern is the impact on performance and site stability related to the usage of these

objects. Important considerations include:

Custom object quota: Ensuring that the use of custom objects does not exceed platform limits, which

could impact performance or even prevent new data from being stored.

Retention or deletion needs: Proper management of custom object lifecycle is crucial to prevent data

bloat and maintain database performance, including strategies for timely deletion or archiving of old

data.

Addressing these concerns is critical to maintaining the performance and stability of the site while

integrating third-party services that require extensive data handling.