BlackFriday 2024! 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 Exam B2C Commerce Architect Topic 4 Question 44 Discussion

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

A developer is validating the pipeline cache and noticed that the PDP page is very low cached. The one parameter is snowing the position on the product fisting page upon checking the site and code.

What should the developer adjust in order to improve the page cache hit ratio, keeping in mind that the client is Insisting on the parameter for their analytics?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Valentin at Jul 06, 2024, 06:21 AM

Limited Time Offer

25%

Off

Get Premium B2C Commerce Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Pearlie
3 months ago
Ah, the old cache problem. Gotta love those pesky parameters, am I right? Option A is definitely the way to go here.
upvoted 0 times
...
Shala
3 months ago
Option D looks interesting, but it might be a bit of a stretch to change the URL structure just for this one parameter. Option A is probably the safest bet.
upvoted 0 times
Leota
2 months ago
Let's go with Option A to keep the client happy and improve the cache hit ratio.
upvoted 0 times
...
Eliseo
2 months ago
Yeah, changing the URL structure for just one parameter seems like overkill.
upvoted 0 times
...
Helaine
3 months ago
I agree, Option A seems like the most practical solution.
upvoted 0 times
...
...
Johnetta
3 months ago
That could work! It would improve the page cache hit ratio while still satisfying the client's analytics requirement.
upvoted 0 times
...
Donte
3 months ago
Hmm, I'm not sure Option C is a good idea since the client insists on the parameter. Might as well just go with Option A and avoid any potential issues.
upvoted 0 times
Carmelina
2 months ago
I agree, let's go with Option A to avoid any potential issues.
upvoted 0 times
...
Benton
2 months ago
That's true, but Option A seems like the safest bet.
upvoted 0 times
...
Mose
2 months ago
But wouldn't adding the key to the cache exclude parameters also work?
upvoted 0 times
...
Ryan
3 months ago
I think Option A is the best choice to keep the client happy.
upvoted 0 times
...
...
James
4 months ago
What if we rework the implementation so the parameter is not passed in the URL and is read from the URL hash instead?
upvoted 0 times
...
Tijuana
4 months ago
But the client is insisting on the parameter for their analytics. Maybe we can find a compromise?
upvoted 0 times
...
Johnetta
4 months ago
I think we should rework the implementation so it reads the parameter on client-side and exclude it from cache parameters.
upvoted 0 times
...
Pearly
4 months ago
Option A seems like the best approach here. Keeping the analytics parameter while improving the cache hit ratio is a good compromise.
upvoted 0 times
Shakira
3 months ago
That sounds like a good solution. It keeps the analytics parameter while improving the cache hit ratio.
upvoted 0 times
...
Evan
3 months ago
A) Rework the implementation so it reads the parameter on client-side, passes it to the analytics and exclude it from cache parameters.
upvoted 0 times
...
...

Save Cancel