Deal of The Day! 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 PL
Mob_nav_barsMENU

Salesforce Exam B2C-Commerce-Architect Topic 7 Question 37 Discussion

Actual exam question for Salesforce's B2C-Commerce-Architect exam
Question #: 37
Topic #: 7
[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 Leigha at Apr 25, 2024, 09:48 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
Ammie
3 months ago
True, but might complicate the implementation. Client-side read might be easier.
upvoted 0 times
...
Lenna
3 months ago
Option A all the way! Gotta keep that client happy, even if it means a little extra work on the dev side.
upvoted 0 times
...
Art
3 months ago
I'm just wondering, does the client really need to track the position on the product listing page? Seems a bit overkill if you ask me.
upvoted 0 times
Trina
2 months ago
User 3: C) Rework the implementation so it doesn't depend on that parameter.
upvoted 0 times
...
Chan
2 months ago
User 2: B) Add the key to the cache exclude parameters.
upvoted 0 times
...
Gussie
2 months ago
User 3: C) Rework the implementation so it doesn't depend on that parameter.
upvoted 0 times
...
Ashlee
2 months ago
User 2: B) Add the key to the cache exclude parameters.
upvoted 0 times
...
Casie
2 months ago
User 1: 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
...
Fletcher
2 months ago
User 1: 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
...
...
Geraldo
3 months ago
But what about D? Reading the parameter from the URL hash avoids caching issues too.
upvoted 0 times
...
Colton
3 months ago
Hiding the parameter in the URL hash? That's like trying to sweep the problem under the rug. Not a fan.
upvoted 0 times
Royal
2 months ago
User 3: Adding the key to the cache exclude parameters might also help improve the page cache hit ratio.
upvoted 0 times
...
Tiara
2 months ago
User 2: Maybe reworking the implementation so it reads the parameter on client-side could be a better option.
upvoted 0 times
...
Krissy
3 months ago
User 1: I agree, hiding the parameter in the URL hash doesn't seem like a good solution.
upvoted 0 times
...
Larae
3 months ago
User 2: Maybe reworking the implementation so it reads the parameter on client-side could be a better option.
upvoted 0 times
...
Verlene
3 months ago
User 2: Verlene is right, we should rework the implementation so it doesn't depend on that parameter.
upvoted 0 times
...
Elden
3 months ago
User 1: I agree, hiding the parameter in the URL hash seems like a temporary fix.
upvoted 0 times
...
Dianne
3 months ago
User 1: I agree, hiding the parameter in the URL hash doesn't seem like a good solution.
upvoted 0 times
...
...
Dyan
4 months ago
Option C is interesting, but it might require significant changes to the implementation. I'd rather try to work within the existing constraints.
upvoted 0 times
...
Bernadine
4 months ago
I'd go with option B. Adding the key to the cache exclude parameters seems like the easiest and most straightforward solution.
upvoted 0 times
...
German
4 months ago
I agree, reworking so it reads client-side makes sense. Keeps the analytics happy too.
upvoted 0 times
...
Zona
4 months ago
The parameter in the URL is a must-have for the client's analytics. Reworking the implementation to exclude it from the cache parameters is the logical choice here.
upvoted 0 times
Paola
3 months ago
B) Add the key to the cache exclude parameters.
upvoted 0 times
...
Rhea
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
...
...
Ammie
4 months ago
Yeah, and how to handle that parameter efficiently. Option A seems logical.
upvoted 0 times
...
Loreta
4 months ago
Looks like it's about optimizing the cache hit ratio while keeping a parameter for analytics.
upvoted 0 times
...
Geraldo
4 months ago
Hm, this question seems tricky. What do you think it's asking?
upvoted 0 times
...
Mitsue
5 months ago
That could work too, as long as the parameter is not affecting the cache hit ratio.
upvoted 0 times
...
Martha
5 months ago
What about adding the key to the cache exclude parameters?
upvoted 0 times
...
Quiana
5 months ago
But the client wants the parameter for analytics. Maybe they could pass it on the client-side.
upvoted 0 times
...
Mitsue
5 months ago
I think the developer should adjust the implementation to exclude the parameter from cache.
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