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-Solution-Architect Topic 5 Question 59 Discussion

Actual exam question for Salesforce's B2C-Solution-Architect exam
Question #: 59
Topic #: 5
[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:

Hyun
3 months ago
I don't think storing raw payment card details on the customer's profile is a good idea. It might pose a risk to data security.
upvoted 0 times
...
Lorenza
3 months ago
But wouldn't hashing the payment card details also be secure? It's a common practice for enhancing security.
upvoted 0 times
...
Rima
3 months ago
I agree, storing a tokenized value would be the best option to ensure customer payment information is secure.
upvoted 0 times
...
Tequila
3 months ago
I think we should store a tokenized value for the payment card to maintain security and compliance.
upvoted 0 times
...
Giuseppe
3 months ago
I think storing raw payment card details on the customer's profile is definitely not secure.
upvoted 0 times
...
Fidelia
3 months ago
One-click ordering and automatic renewals? Sign me up! As long as it's all secure and compliant, of course.
upvoted 0 times
...
Goldie
3 months ago
Base64 encoding? Really? That's like putting a lock on a cardboard box. Gotta do better than that.
upvoted 0 times
Justine
2 months ago
User 2
upvoted 0 times
...
Talia
2 months ago
User 1
upvoted 0 times
...
Dorcas
3 months ago
C: That's the best option to ensure security and compliance.
upvoted 0 times
...
William
3 months ago
B: I agree, we should go with storing a tokenized value for the payment card.
upvoted 0 times
...
Karon
3 months ago
A: Definitely not Base64 encoding, that's not secure at all.
upvoted 0 times
...
...
Bette
3 months ago
Hashing could work too, but tokenization is more recommended for handling sensitive payment info.
upvoted 0 times
...
Rasheeda
3 months ago
But wouldn't hashing the payment card details also be a secure option?
upvoted 0 times
...
Wilson
4 months ago
Tokenized value all the way! Keeps the sensitive data away from prying eyes. Smart thinking, Solution Architect.
upvoted 0 times
...
Adela
4 months ago
Hashing payment card details sounds like a solid approach to me. Keeps things secure and compliant.
upvoted 0 times
Youlanda
3 months ago
D) Store a tokenized value for the payment card.
upvoted 0 times
...
Lorita
3 months ago
B) Hash and store the payment card details.
upvoted 0 times
...
...
Torie
4 months ago
Storing raw payment card details? That's a big no-no! Security 101, people.
upvoted 0 times
Freeman
3 months ago
Storing raw payment card details? That's a big no-no! Security 101, people.
upvoted 0 times
...
Ethan
3 months ago
D) Store a tokenized value for the payment card.
upvoted 0 times
...
Buddy
3 months ago
B) Hash and store the payment card details.
upvoted 0 times
...
Weldon
3 months ago
A) Store Base64 encoded payment card details.
upvoted 0 times
...
...
Giuseppe
4 months ago
I agree with Bette, storing tokenized value is the best option to ensure compliance.
upvoted 0 times
...
Bette
4 months ago
I think we should store a tokenized value for the payment card to maintain security.
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