Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam B2C Commerce Architect Topic 2 Question 50 Discussion

Actual exam question for Salesforce's B2C Commerce Architect exam
Question #: 50
Topic #: 2
[All B2C Commerce Architect Questions]

The Client has implemented a different category/search layout for mobile and desktop. The code uses a session attribute called deviceType to choose the corresponding layout. This attribute it populated from the browser user agent. After this implementation they have run into these problems:

* Sometimes desktop pages are being served to both desktop and mobile customers.

* Sometimes mobile pages ate being served to both desktop and mobile customers.

The page has caching implementedthat depends; on promotions. SEC is very important and the site traffic is high.

Which solution should the Architect select to resolve the issue without impacting the existing requirements?

Show Suggested Answer Hide Answer
Suggested Answer: D

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.


Contribute your Thoughts:

Felicidad
2 months ago
Option D with the URL structure change is intriguing. It could help us cache different versions without the need for customer groups. Hmm, I'm torn between that and option B.
upvoted 0 times
Tegan
30 days ago
I agree, both options have their merits. It depends on the specific requirements of the project.
upvoted 0 times
...
Howard
1 months ago
True, option D might be simpler to implement without the need for customer groups.
upvoted 0 times
...
Laquanda
1 months ago
But option B also seems like a good solution to ensure different cached versions based on customer groups.
upvoted 0 times
...
Kaitlyn
1 months ago
I think option D could work well to differentiate between desktop and mobile pages.
upvoted 0 times
...
...
Tomas
2 months ago
I think option D could also work, changing the URL structure seems like a good idea.
upvoted 0 times
...
Glen
2 months ago
I disagree, I believe option B is more appropriate.
upvoted 0 times
...
Gearldine
3 months ago
Option C, no caching, seems like the way to go. Disabling caching is the simplest solution to ensure the correct template is used for mobile and desktop.
upvoted 0 times
Van
2 months ago
Yeah, it's important to prioritize serving the correct layout to users based on their device to provide a seamless experience.
upvoted 0 times
...
Denny
2 months ago
I agree, disabling caching would definitely help in serving the correct pages to the right users without any mix-ups.
upvoted 0 times
...
Timothy
2 months ago
Option C, no caching, seems like the way to go. Disabling caching is the simplest solution to ensure the correct template is used for mobile and desktop.
upvoted 0 times
...
...
Broderick
3 months ago
I think option A is the best solution.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77