Question 242 of 315
Single answerFor 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?
* 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?
AStore the card data in Secret Manager after running a query to identify duplicates.
✓BEncrypt the card data with a deterministic algorithm stored in Firestore using Datastore mode.
CEncrypt the card data with a deterministic algorithm and shard it across multiple Memorystore instances.
DUse column-level encryption to store the data in Cloud SQL.
✓
Correct Answer: B
Encrypt the card data with a deterministic algorithm stored in Firestore using Datastore mode.
▥
Explanation
The correct answer is highlighted above. Review the wording carefully, then use the next question to continue building your understanding of Google certification topics.