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 US
Mob_nav_barsMENU

Salesforce Exam B2C Commerce Developer Topic 2 Question 86 Discussion

Actual exam question for Salesforce's B2C Commerce Developer exam
Question #: 86
Topic #: 2
[All B2C Commerce Developer Questions]

In Log Center, a developer notes j number of Cross Site Request Forgery (CSRF) log entries.

After adding the token in the 15ML template, which action might solve this problem'

Show Suggested Answer Hide Answer
Suggested Answer: C

by Stevie at Feb 11, 2025, 04:42 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Laurel
28 days ago
I'd go with option A, but only if I can also add a few extra layers of security, like a secret handshake and a decoder ring. You can never be too careful, you know?
upvoted 0 times
Judy
9 days ago
User 2: Yeah, adding csrfProtection middleware steps sounds like a good idea.
upvoted 0 times
...
Susana
15 days ago
User 1: I think option A is the way to go.
upvoted 0 times
...
...
Theron
1 months ago
Option A sounds like the way to go. After all, you can't spell 'CSRF' without 'CSR', so the middleware is clearly the key here.
upvoted 0 times
Dominga
12 days ago
User 2: Agreed, that seems like the best solution to prevent CSRF attacks.
upvoted 0 times
...
Rosendo
14 days ago
User 1: I think we should go with option A and add csrfProtection middleware steps in the controller.
upvoted 0 times
...
...
Leonora
2 months ago
Deleting the CSRF allow list? That's like trying to fix a leaky faucet by turning off the water supply. Not the best approach in my opinion.
upvoted 0 times
Corrina
7 days ago
C) Delete the existing CSRF allow list in Business Manager.
upvoted 0 times
...
Wenona
14 days ago
C) Delete the existing CSRF allow list in Business Manager.
upvoted 0 times
...
Jesusa
15 days ago
B) Extend the CSRF token validity to avoid timeouts.
upvoted 0 times
...
Pamela
23 days ago
B) Extend the CSRF token validity to avoid timeouts.
upvoted 0 times
...
Gerald
30 days ago
A) Add csrfProtection middleware steps in the controller
upvoted 0 times
...
Miles
1 months ago
A) Add csrfProtection middleware steps in the controller
upvoted 0 times
...
...
Freida
2 months ago
Extending the CSRF token validity might work, but that's just a temporary fix. It's better to implement the proper CSRF protection mechanisms to ensure long-term security.
upvoted 0 times
...
Tamar
2 months ago
Adding the CSRF token in the template is a good start, but we need to make sure the middleware is set up correctly to protect against CSRF attacks. Option A seems like the best solution here.
upvoted 0 times
Shay
13 days ago
I agree, setting up the csrfProtection middleware is crucial for preventing CSRF attacks.
upvoted 0 times
...
Buffy
17 days ago
C) Delete the existing CSRF allow list in Business Manager.
upvoted 0 times
...
Rodolfo
1 months ago
B) Extend the CSRF token validity to avoid timeouts.
upvoted 0 times
...
Chantay
2 months ago
A) Add csrfProtection middleware steps in the controller
upvoted 0 times
...
...
Juliann
2 months ago
I'm not sure, but extending the CSRF token validity could also be a good solution.
upvoted 0 times
...
Fidelia
2 months ago
I agree with Rachael, adding csrfProtection middleware can help prevent CSRF attacks.
upvoted 0 times
...
Rachael
2 months ago
I think the answer is A) Add csrfProtection middleware steps in the controller.
upvoted 0 times
...

Save Cancel