Cyber Monday 2024! 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 Solution Architect Topic 2 Question 77 Discussion

Actual exam question for Salesforce's B2C Solution Architect exam
Question #: 77
Topic #: 2
[All B2C Solution Architect Questions]

A company uses a Salesforce solution to sell one-off products and subscription-based products to its customers. However, the company wants to let customers save their payment details when buying products online using credit cards, in order to facilitate a one-click ordering mechanism as well as an automatic payment for subscription-based item renewals.

What should a Solution Architect recommend to store payment information while still maintaining security and compliance?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Jillian
2 months ago
Ah, the age-old debate: security vs. convenience. Tokenization FTW! *high fives the solution architect*
upvoted 0 times
...
Justine
2 months ago
Base64 encoding? What is this, the '90s? Let's keep up with the times and go for that tokenized value option.
upvoted 0 times
...
Mica
2 months ago
Hashing the payment card details? Interesting, but I'm not sure that's the best approach for a one-click ordering system.
upvoted 0 times
Precious
20 days ago
A: Hashing the payment card details might not be the best approach for a one-click ordering system, as it could make it difficult to retrieve the original information.
upvoted 0 times
...
Celestine
1 months ago
B: I agree, using a tokenized value would allow for one-click ordering without compromising sensitive payment information.
upvoted 0 times
...
Ozell
1 months ago
A: I think storing a tokenized value for the payment card would be the best option for security and compliance.
upvoted 0 times
...
...
Claribel
2 months ago
A tokenized value is the way to go here. Keeps the payment info secure and compliant. Gotta love those clever solution architects!
upvoted 0 times
Amie
1 months ago
C) Definitely, it's important to prioritize security and compliance.
upvoted 0 times
...
Gaston
1 months ago
B) That sounds like a secure option to me.
upvoted 0 times
...
Verona
2 months ago
A) Store a tokenized value for the payment card.
upvoted 0 times
...
...
Mitsue
2 months ago
I'm not sure about that. Wouldn't hashing the payment card details be a better option?
upvoted 0 times
...
Charolette
3 months ago
I agree with Quentin. Storing a tokenized value is more secure and compliant.
upvoted 0 times
...
Sylvie
3 months ago
Storing raw payment card details on the customer's profile? No way, that's a security disaster waiting to happen!
upvoted 0 times
Tamekia
2 months ago
A: Storing a tokenized value sounds like a good compromise for security and convenience.
upvoted 0 times
...
Sarina
2 months ago
C: What about storing a tokenized value for the payment card? That could work too.
upvoted 0 times
...
Shawna
2 months ago
B: I agree, we need to hash and store the payment card details for security and compliance.
upvoted 0 times
...
Jeff
2 months ago
A: Definitely not storing raw payment card details, that's a huge security risk.
upvoted 0 times
...
...
Quentin
3 months ago
I think we should store a tokenized value for the payment card.
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