Salesforce Exam B2C Commerce Architect Topic 7 Question 37 Discussion

Actual exam question for Salesforce's B2C Commerce Architect exam

Question #: 37
Topic #: 7

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?

ARework the implementation so it reads the parameter on client-side, passes it to the analytics and exclude It from cache parameters.

BAdd the key to the cache exclude parameters.

CRework the Implementation so it doesn't depend on that parameter.

DRework the Implementation so the parameter is not passed In the URL and is read from the URL hash.

Show Suggested 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

6 months ago

True, but might complicate the implementation. Client-side read might be easier.

upvoted 0 times

...

Lenna

6 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

6 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

5 months ago

C) Rework the implementation so it doesn't depend on that parameter.

upvoted 0 times

...

Chan

5 months ago

B) Add the key to the cache exclude parameters.

upvoted 0 times

...

Gussie

5 months ago

C) Rework the implementation so it doesn't depend on that parameter.

upvoted 0 times

...

Ashlee

5 months ago

B) Add the key to the cache exclude parameters.

upvoted 0 times

...

Casie

6 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

...

Fletcher

6 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

...

Geraldo

6 months ago

But what about D? Reading the parameter from the URL hash avoids caching issues too.

upvoted 0 times

...

Colton

6 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

6 months ago

Adding the key to the cache exclude parameters might also help improve the page cache hit ratio.

upvoted 0 times

...

Tiara

6 months ago

Maybe reworking the implementation so it reads the parameter on client-side could be a better option.

upvoted 0 times

...

Krissy

6 months ago

I agree, hiding the parameter in the URL hash doesn't seem like a good solution.

upvoted 0 times

...

Larae

6 months ago

Maybe reworking the implementation so it reads the parameter on client-side could be a better option.

upvoted 0 times

...

Verlene

6 months ago

Verlene is right, we should rework the implementation so it doesn't depend on that parameter.

upvoted 0 times

...

Elden

6 months ago

I agree, hiding the parameter in the URL hash seems like a temporary fix.

upvoted 0 times

...

Dianne

6 months ago

I agree, hiding the parameter in the URL hash doesn't seem like a good solution.

upvoted 0 times

...

Dyan

7 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

7 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

7 months ago

I agree, reworking so it reads client-side makes sense. Keeps the analytics happy too.

upvoted 0 times

...

Zona

7 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