For this question, refer to the Helicopter Racing League (HRL) case study. Your team is in charge of creating a payment card data vault for card numbers used to bill tens of thousands of viewers, merchandise consumers, and season ticket holders. You need to implement a custom card tokenization service that meets the following requirements:
* It must provide low latency at minimal cost.
* It must be able to identify duplicate credit cards and must not store plaintext card numbers.
* It should support annual key rotation.
Which storage approach should you adopt for your tokenization service?
Neo_ACE
Highly Voted 3 years, 3 months agotechnodev
Highly Voted 3 years agoOrangeTiger
Most Recent 1 year agoTopTalk
1 year, 4 months agosampon279
1 year, 7 months agomimicha1
1 year, 8 months agobargou
1 year agoBiddlyBdoyng
1 year, 8 months agomtj2018
1 year, 7 months agotdotcat
2 years, 1 month agosurajkrishnamurthy
2 years, 2 months agomegumin
2 years, 3 months agoMahmoud_E
2 years, 3 months agoaut0pil0t
2 years, 5 months agoAzureDP900
2 years, 7 months agocpi_web
2 years, 8 months agokapara
2 years, 9 months agomad314
2 years, 9 months agoslars2k
2 years, 10 months ago