New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified B2C Commerce Architect (Arch-303) Exam - Topic 2 Question 68 Discussion

Actual exam question for Salesforce's Salesforce Certified B2C Commerce Architect (Arch-303) exam
Question #: 68
Topic #: 2
[All Salesforce Certified B2C Commerce Architect (Arch-303) Questions]

Northern Trail Outfitters (NTO) wants to migrate its online shoo from a custom ecommerce platform to B2CCommerce. NTO needs to migrate several thousands of customer records profile information, address book). WTO can provide a B2C Commerce feed. It is currently using SHA-256 as an encryption mechanism for the customer passwords.

What approach can the Architect propose?

Show Suggested Answer Hide Answer
Suggested Answer: C

B2C Commerce does not directly support the import of hashed passwords for use in authentication due to security protocols and the platform's password management system. The best approach is to import customer records without the password field. Upon their first login attempt on the new system, customers would be prompted to reset their password. This method ensures that password security is maintained according to B2C Commerce standards and that customer data remains secure during the transition from the old platform.


Contribute your Thoughts:

0/2000 characters
Fletcher
2 months ago
C is the safest choice, forcing a reset is smart.
upvoted 0 times
...
Barb
2 months ago
Wait, can we really import hashed passwords like that?
upvoted 0 times
...
In
2 months ago
I disagree, B is better for security.
upvoted 0 times
...
Yong
3 months ago
D sounds complicated, not sure it's worth the effort.
upvoted 0 times
...
Stephane
3 months ago
Option A seems solid since it keeps existing passwords.
upvoted 0 times
...
Jeff
3 months ago
I’m leaning towards option D, but I’m a bit confused about how the custom attribute would work in practice. Would it really be secure to compare the passwords like that?
upvoted 0 times
...
Pearly
4 months ago
I practiced a similar question where we had to consider user experience. I think option B might frustrate customers since they would have to create new accounts.
upvoted 0 times
...
Margurite
4 months ago
I'm not entirely sure, but I feel like option C could be a safer approach. It would ensure customers reset their passwords, which might be better for security.
upvoted 0 times
...
Odette
4 months ago
I remember discussing the importance of password security in our last class. I think option A makes sense since B2C Commerce supports SHA-256.
upvoted 0 times
...
Ena
4 months ago
I like the idea of option D, where we import the hashed passwords as a custom attribute and then handle the comparison during login. That way we can preserve the existing passwords and avoid any issues with the migration.
upvoted 0 times
...
Tequila
4 months ago
Option C sounds like a good compromise - import the customer records without the passwords, and then have B2C Commerce force a password reset. That way we don't have to worry about the hashing compatibility.
upvoted 0 times
...
Jonelle
5 months ago
Hmm, I'm a bit unsure about that. Doesn't B2C Commerce have its own password hashing mechanism? I'm wondering if we'd need to do some kind of conversion or mapping to get the existing hashed passwords to work.
upvoted 0 times
...
Laurel
5 months ago
This seems like a straightforward migration question. I think option A is the best approach - just import the customer records with the hashed passwords, and they'll be able to log in with their existing credentials.
upvoted 0 times
...
Ryann
5 months ago
I disagree, I believe option D is better. It adds an extra layer of security by comparing the entered password with the hashed one.
upvoted 0 times
...
Jerry
5 months ago
I'm not so sure about that. Option C seems like a better approach - reset the passwords and make customers more secure in the long run.
upvoted 0 times
Quentin
2 months ago
Option A could work too, but I see the value in C for long-term security.
upvoted 0 times
...
Erick
2 months ago
True, but security is key. Better to reset than risk old passwords.
upvoted 0 times
...
Nadine
3 months ago
But what about the hassle for customers? They might not like it.
upvoted 0 times
...
Marti
3 months ago
I agree, Option C sounds safer. Password resets are a good idea.
upvoted 0 times
...
...
Quentin
6 months ago
Option A makes the most sense to me. Migrating the hashed passwords directly is the easiest way to go, and customers won't even notice the change.
upvoted 0 times
...
Donte
6 months ago
I think option A is the best approach. It will make it easier for customers to log in with their existing passwords.
upvoted 0 times
...

Save Cancel