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 2 years, 10 months agotechnodev
Highly Voted 2 years, 8 months agoOrangeTiger
Most Recent 8 months, 1 week agoTopTalk
1 year agosampon279
1 year, 3 months agomimicha1
1 year, 3 months agobargou
7 months, 2 weeks agoBiddlyBdoyng
1 year, 3 months agomtj2018
1 year, 2 months agotdotcat
1 year, 8 months agosurajkrishnamurthy
1 year, 9 months agomegumin
1 year, 10 months agoMahmoud_E
1 year, 11 months agoaut0pil0t
2 years agoAzureDP900
2 years, 2 months agocpi_web
2 years, 3 months agokapara
2 years, 4 months agomad314
2 years, 5 months agoslars2k
2 years, 5 months ago