Salesforce Exam B2C Commerce Architect Topic 7 Question 24 Discussion

Actual exam question for Salesforce's B2C Commerce Architect exam

Question #: 24
Topic #: 7

During the testing of the login form, QA finds out that the first time the user can log in, but every other login attempt from another computer leads to the homepage and the basket being emptied. Developers tried to debug the issue, but when they add a breakpoint to the login action, it is not hit by the debugger.

Whatshould the Architect recommend developers to check?

ARemove CSRF protection from Login Form Action.

BAdd remote include for the login page

CAdd disable cache page in the template ISML - <iscache status--off''/>.

DCheck Login Form and any includedtemplates for includes that enable page caching.

Show Suggested Answer

Suggested Answer: A, B

by Daniel at Jul 26, 2023, 04:31 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Oneida

2 months ago

Wait, so the developers can't even hit the breakpoint? Looks like they need to upgrade their debugging skills, not just check the caching! Option D, and maybe throw in some comedy lessons too.

upvoted 0 times

...

Kathrine

2 months ago

Funny Guy

upvoted 0 times

Basilia

5 days ago

D) Check Login Form and any included templates for includes that enable page caching.

upvoted 0 times

...

Genevieve

17 days ago

B) Add remote include for the login page

upvoted 0 times

...

Nan

21 days ago

A) Remove CSRF protection from Login Form Action.

upvoted 0 times

...

Paola

2 months ago

Oh man, I can just imagine the developers staring at the code, scratching their heads. Option D sounds like the right approach to me.

upvoted 0 times

Alecia

8 days ago

Developer 1: Alright, let's get to work on that then.

upvoted 0 times

...

Tasia

10 days ago

Developer 3: I agree, let's focus on that first before trying anything else.

upvoted 0 times

...

Jaclyn

13 days ago

Developer 2: Yeah, that sounds like a good idea. Maybe that's causing the issue.

upvoted 0 times

...

Rickie

15 days ago

Architect: I agree, let's focus on checking for any includes that enable page caching.

upvoted 0 times

...

Tegan

17 days ago

Developer 2: Yeah, that sounds like a good idea. Maybe that's causing the issue.

upvoted 0 times

...

Arleen

18 days ago

Developer 1: Let's check the Login Form and included templates for includes that enable page caching.

upvoted 0 times

...

Tori

22 days ago

Developer 1: Let's get to work on it and see if we can find the problem.

upvoted 0 times

...

Emelda

1 months ago

Developer 1: Let's check the Login Form and included templates for includes that enable page caching.

upvoted 0 times

...

Florencia

1 months ago

Developer 3: I agree, let's focus on that first before trying anything else.

upvoted 0 times

...

Arlette

2 months ago

Developer 2: Yeah, that sounds like a good idea. Maybe that's causing the issue.

upvoted 0 times

...

Malinda

2 months ago

Developer 1: Let's check the Login Form and included templates for any includes that enable page caching.

upvoted 0 times

...

Chantay

2 months ago

Removing CSRF protection? Yikes, that's a big no-no! Option A is definitely not the way to go. I'd go with D and dig into those caching settings.

upvoted 0 times

...

Aliza

2 months ago

I'm not sure, but maybe they should also consider adding disable cache page in the template ISML - .

upvoted 0 times

...

Yvonne

2 months ago

I agree with Carylon, checking for includes that enable page caching seems like the right thing to do.

upvoted 0 times

...

In

2 months ago

Haha, the developers must be pulling their hair out trying to figure this one out. I'd say go with Option D as well, seems like the most likely culprit.

upvoted 0 times

Darrin

1 months ago

Yeah, I agree. That could be causing the issue with the login form and basket being emptied.

upvoted 0 times

...

Annice

2 months ago

Option D seems like the best choice. Let's check for any includes that enable page caching in the Login Form and templates.

upvoted 0 times

...

Carylon

2 months ago

I think the developers should check the Login Form and included templates for includes that enable page caching.

upvoted 0 times

...

Marva

2 months ago

I'm not sure, but maybe they should also consider adding disable cache page in the template ISML.

upvoted 0 times

...

Anglea

3 months ago

Hmm, this sounds like a tricky issue. I'm leaning towards Option D - checking the login form and included templates for any caching-related code that could be causing the problem.

upvoted 0 times

Fannie

22 days ago

Let's not forget to add disable cache page in the template ISML as another potential solution.

upvoted 0 times

...

Mabel

28 days ago

I think removing CSRF protection from the login form action could also be worth looking into.

upvoted 0 times

...

Glenna

2 months ago

Maybe we should also consider adding a remote include for the login page to see if that helps.

upvoted 0 times

...

Gerald

2 months ago

I agree, checking for caching-related code in the login form and templates is a good idea.

upvoted 0 times

...

Lili

3 months ago

I agree with Alise, checking for page caching in the templates could be the issue causing the problem.

upvoted 0 times

...

Alise

3 months ago

I think the developers should check for includes that enable page caching in the Login Form and templates.

upvoted 0 times

...