New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified B2C Commerce Architect (Arch-303) Exam - Topic 2 Question 50 Discussion

Actual exam question for Salesforce's Salesforce Certified B2C Commerce Architect (Arch-303) exam
Question #: 50
Topic #: 2
[All Salesforce Certified B2C Commerce Architect (Arch-303) 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.


by Tracey at Sep 17, 2024, 04:50 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified B2C Commerce Architect (Arch-303) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Novella
3 months ago
Option B could work, but it feels like a workaround.
upvoted 0 times
...
Eden
3 months ago
Wait, mobile pages are being served to desktops? That's wild!
upvoted 0 times
...
Elsa
3 months ago
Disagree, disabling caching seems risky for performance.
upvoted 0 times
...
Melissia
4 months ago
I think option D makes the most sense for caching.
upvoted 0 times
...
Crista
4 months ago
Sounds like a caching issue with user agent detection.
upvoted 0 times
...
Kayleigh
4 months ago
I feel like option B could be a safe bet since it allows for different cached versions without completely disabling caching. But I'm not entirely confident.
upvoted 0 times
...
Elden
4 months ago
I practiced a similar question where caching was a problem, and I think disabling caching like in option C could lead to performance issues.
upvoted 0 times
...
Merri
4 months ago
I'm a bit unsure about the customer groups idea in option A. It seems like it could work, but what if the user agent detection fails?
upvoted 0 times
...
Steffanie
5 months ago
I remember we discussed how caching can really mess with user experience if not handled properly. I think option D might help with that by creating unique URLs.
upvoted 0 times
...
Raylene
5 months ago
Okay, I think I've got a handle on this. The issue seems to be with the device detection and the caching implementation. Disabling caching might work, but that could impact performance. Creating separate customer groups and using that to render the pages could be a good compromise, but it might be overkill. I think changing the URL structure to include desktop and mobile as parameters could be the most elegant solution here.
upvoted 0 times
...
Refugia
5 months ago
Hmm, this is a tough one. I think the key here is to find a solution that doesn't impact the existing requirements, like the caching implementation and the importance of SEC. Creating separate customer groups and using that to render the pages could be a good approach, but I'm not sure if that's the most efficient solution.
upvoted 0 times
...
Thurman
5 months ago
I'm a bit confused by the question. It seems like the issue is with the device detection and the caching implementation. I'm not sure if creating customer groups is the right approach here. Maybe we could try changing the URL structure instead?
upvoted 0 times
...
Tijuana
5 months ago
This is a tricky one. I'm not sure if disabling caching is the best solution since that could impact performance, especially with high site traffic. Maybe we could try creating separate customer groups for desktop and mobile users instead.
upvoted 0 times
...
Santos
5 months ago
Hmm, I'm a bit confused about the different weekly distribution options and how they work. I'll need to review that part carefully.
upvoted 0 times
...
Felicidad
1 year 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
1 year ago
I agree, both options have their merits. It depends on the specific requirements of the project.
upvoted 0 times
...
Howard
1 year ago
True, option D might be simpler to implement without the need for customer groups.
upvoted 0 times
...
Laquanda
1 year ago
But option B also seems like a good solution to ensure different cached versions based on customer groups.
upvoted 0 times
...
Kaitlyn
1 year ago
I think option D could work well to differentiate between desktop and mobile pages.
upvoted 0 times
...
...
Tomas
1 year ago
I think option D could also work, changing the URL structure seems like a good idea.
upvoted 0 times
...
Glen
1 year ago
I disagree, I believe option B is more appropriate.
upvoted 0 times
...
Gearldine
1 year 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
1 year 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
1 year 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
1 year 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
1 year ago
I think option A is the best solution.
upvoted 0 times
...

Save Cancel