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

Salesforce Exam B2C Commerce Architect Topic 7 Question 24 Discussion

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

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?

Show Suggested Answer Hide Answer
Suggested Answer: A, B

Contribute your Thoughts:

Paola
8 hours 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
...
Chantay
4 days 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
9 days ago
I'm not sure, but maybe they should also consider adding disable cache page in the template ISML - .
upvoted 0 times
...
Yvonne
12 days ago
I agree with Carylon, checking for includes that enable page caching seems like the right thing to do.
upvoted 0 times
...
In
13 days 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
...
Carylon
13 days ago
I think the developers should check the Login Form and included templates for includes that enable page caching.
upvoted 0 times
...
Marva
15 days ago
I'm not sure, but maybe they should also consider adding disable cache page in the template ISML.
upvoted 0 times
...
Anglea
17 days 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
...
Lili
18 days ago
I agree with Alise, checking for page caching in the templates could be the issue causing the problem.
upvoted 0 times
...
Alise
24 days ago
I think the developers should check for includes that enable page caching in the Login Form and templates.
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