MENU
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?
43 comments · newest first
PA
Patria
11 months ago
Definitely D! It keeps everything compliant and safe.
JE
Jesus
11 months ago
Hashing isn't enough for compliance, just saying.
AM
Amber
12 months ago
Wait, can we really trust tokenization? Seems risky.
JO
Johnna
12 months ago
Storing raw card details? That's a big no-no!
RE
Rene
1 year ago
D is the way to go! Tokenization is super secure.
GA
Gail
1 year ago
I vaguely recall that Base64 encoding isn't secure enough for sensitive data. I think we should avoid that option.
LO
Lourdes
1 year ago
I feel like we practiced a similar question where tokenization was emphasized as a secure method. Option D seems like the best choice to me.
SH
Sharita
1 year ago
I’m not entirely sure, but I think hashing payment details might not be reversible, which could be a problem for automatic payments.
RO
Rosita
1 year ago
I remember discussing the importance of not storing raw payment details due to compliance issues. So, I think option D sounds right.
JU
Juan
1 year ago
Base64 encoding the payment card details doesn't really provide any additional security. I think the key is finding a solution that keeps the sensitive information protected, so the tokenized value option seems like the way to go.
KR
Kristel
1 year ago
Storing raw payment card details on the customer's profile is definitely not the way to go - that's a huge security risk! I'm pretty confident that the tokenized value option is the right answer here.
DE
Denny
1 year ago
I'm a bit confused on the differences between the options. Hashing and storing the payment card details sounds like it could work, but I'm not sure if that's the most secure approach.
MA
Maricela
1 year ago
This seems like a tricky question, but I think storing a tokenized value for the payment card is the best approach to maintain security and compliance.
RO
Rozella
1 year ago
I'm a bit unsure about this one. The question mentions ensuring access in the event of a regional outage, and I'm not sure if Azure Application Gateway alone can handle that requirement.
LA
Lawrence
1 year ago
Hmm, I'm a bit unsure about this one. The options seem similar, but I'll try to think through the key differences and select the most complete and relevant answer.
DE
Deandrea
1 year ago
I'm pretty confident this is MPLS configuration mode, since the question specifically mentions the "mpls ldp graceful-restart" command.
MA
Margret
1 year ago
I'm pretty confident that the answer is C. Vulnerable Items. Filter groups are a feature in Vulnerability Response that allow you to group and organize vulnerability records.
BI
Billye
1 year ago
Ah, I see the key is to use the correct jsonpath expression to extract the pod name and start time. I'll need to review my notes on that.
HY
Hyun
2 years 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.
LO
Lorenza
2 years ago
But wouldn't hashing the payment card details also be secure? It's a common practice for enhancing security.
RI
Rima
2 years ago
I agree, storing a tokenized value would be the best option to ensure customer payment information is secure.
TE
Tequila
2 years ago
I think we should store a tokenized value for the payment card to maintain security and compliance.
GI
Giuseppe
2 years ago
I think storing raw payment card details on the customer's profile is definitely not secure.
FI
Fidelia
2 years ago
One-click ordering and automatic renewals? Sign me up! As long as it's all secure and compliant, of course.
GO
Goldie
2 years ago
Base64 encoding? Really? That's like putting a lock on a cardboard box. Gotta do better than that.
JU
Justine
2 years ago
User 2
TA
Talia
2 years ago
User 1
DO
Dorcas
2 years ago
C: That's the best option to ensure security and compliance.
WI
William
2 years ago
B: I agree, we should go with storing a tokenized value for the payment card.
KA
Karon
2 years ago
A: Definitely not Base64 encoding, that's not secure at all.
BE
Bette
2 years ago
Hashing could work too, but tokenization is more recommended for handling sensitive payment info.
RA
Rasheeda
2 years ago
But wouldn't hashing the payment card details also be a secure option?
WI
Wilson
2 years ago
Tokenized value all the way! Keeps the sensitive data away from prying eyes. Smart thinking, Solution Architect.
AD
Adela
2 years ago
Hashing payment card details sounds like a solid approach to me. Keeps things secure and compliant.
YO
Youlanda
2 years ago
D) Store a tokenized value for the payment card.
LO
Lorita
2 years ago
B) Hash and store the payment card details.
TO
Torie
2 years ago
Storing raw payment card details? That's a big no-no! Security 101, people.
FR
Freeman
2 years ago
Storing raw payment card details? That's a big no-no! Security 101, people.
ET
Ethan
2 years ago
D) Store a tokenized value for the payment card.
BU
Buddy
2 years ago
B) Hash and store the payment card details.
WE
Weldon
2 years ago
A) Store Base64 encoded payment card details.
GI
Giuseppe
3 years ago
I agree with Bette, storing tokenized value is the best option to ensure compliance.
BE
Bette
3 years ago
I think we should store a tokenized value for the payment card to maintain security.