MENU
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?
Suggested Answer: A, B
Get Premium Salesforce Certified B2C Commerce Architect (Arch-303) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
45 comments · newest first
KE
Kerry
11 months ago
Adding remote includes won't solve this problem.
AR
Arlen
11 months ago
Wait, why would the debugger not hit the breakpoint? That's weird.
SA
Samuel
12 months ago
I think removing CSRF protection is a bad idea.
LO
Loreta
12 months ago
Definitely check for page caching!
CH
Chi
12 months ago
Sounds like a caching issue to me.
HO
Hoa
1 year ago
I'm leaning towards checking the Login Form for includes that might be causing caching issues. It seems like the most logical step based on what we've practiced.
PE
Pearlie
1 year ago
I think we had a similar question about login issues and caching before. Maybe the template ISML cache setting could be the problem?
FR
Francis
1 year ago
I'm not entirely sure, but removing CSRF protection seems risky. I feel like it could lead to security vulnerabilities.
WA
Walker
1 year ago
I remember we discussed caching issues in our last session, so I think checking for includes that enable page caching could be crucial here.
CH
Cherry
1 year ago
This is a good opportunity to apply my knowledge of the energy industry. I'll carefully consider each option and select the one that I believe is the correct answer.
SH
Shaunna
1 year ago
Hmm, this looks like a tricky one. I'll need to think carefully about the different disk formats and which one would be best for portability.
LY
Lynelle
1 year ago
Okay, I've got this. Fluorescent lights have a specific frequency that can cause flickering in the video feed from a surveillance camera. That's why the answer is B - flickering effects on the video.
RO
Roslyn
1 year ago
I'm a bit confused by the wording of the question. I'll need to re-read it a few times to make sure I understand.
ON
Oneida
1 year 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.
KA
Kathrine
1 year ago
Funny Guy
BA
Basilia
1 year ago
D) Check Login Form and any included templates for includes that enable page caching.
GE
Genevieve
1 year ago
B) Add remote include for the login page
NA
Nan
1 year ago
A) Remove CSRF protection from Login Form Action.
PA
Paola
1 year 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.
AL
Alecia
1 year ago
Developer 1: Alright, let's get to work on that then.
TA
Tasia
1 year ago
Developer 3: I agree, let's focus on that first before trying anything else.
JA
Jaclyn
1 year ago
Developer 2: Yeah, that sounds like a good idea. Maybe that's causing the issue.
RI
Rickie
1 year ago
Architect: I agree, let's focus on checking for any includes that enable page caching.
TE
Tegan
1 year ago
Developer 2: Yeah, that sounds like a good idea. Maybe that's causing the issue.
AR
Arleen
1 year ago
Developer 1: Let's check the Login Form and included templates for includes that enable page caching.
TO
Tori
1 year ago
Developer 1: Let's get to work on it and see if we can find the problem.
EM
Emelda
1 year ago
Developer 1: Let's check the Login Form and included templates for includes that enable page caching.
FL
Florencia
1 year ago
Developer 3: I agree, let's focus on that first before trying anything else.
AR
Arlette
1 year ago
Developer 2: Yeah, that sounds like a good idea. Maybe that's causing the issue.
MA
Malinda
1 year ago
Developer 1: Let's check the Login Form and included templates for any includes that enable page caching.
CH
Chantay
2 years 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.
AL
Aliza
2 years ago
I'm not sure, but maybe they should also consider adding disable cache page in the template ISML -
YV
Yvonne
2 years ago
I agree with Carylon, checking for includes that enable page caching seems like the right thing to do.
IN
In
2 years 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.
DA
Darrin
1 year ago
Yeah, I agree. That could be causing the issue with the login form and basket being emptied.
AN
Annice
1 year ago
Option D seems like the best choice. Let's check for any includes that enable page caching in the Login Form and templates.
CA
Carylon
2 years ago
I think the developers should check the Login Form and included templates for includes that enable page caching.
MA
Marva
2 years ago
I'm not sure, but maybe they should also consider adding disable cache page in the template ISML.
AN
Anglea
2 years 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.
FA
Fannie
1 year ago
Let's not forget to add disable cache page in the template ISML as another potential solution.
MA
Mabel
1 year ago
I think removing CSRF protection from the login form action could also be worth looking into.
GL
Glenna
1 year ago
Maybe we should also consider adding a remote include for the login page to see if that helps.
GE
Gerald
1 year ago
I agree, checking for caching-related code in the login form and templates is a good idea.
LI
Lili
2 years ago
I agree with Alise, checking for page caching in the templates could be the issue causing the problem.
AL
Alise
2 years ago
I think the developers should check for includes that enable page caching in the Login Form and templates.