You work for a large bank and are tasked to build an application that allows 30 large customers to perform more than 1000 online transactions per second swiftly and collectively in the us-east-1 region. The size of each transaction is around 5 KB. Your manager has told you to ensure data is encrypted end-to-end, you decide to use AWS KMS to meet your requirements. While using the SDK and testing you see ThrottlingException error. How will you deliver the application with optimum performance metrics?

Answer options:

A.Send data directly to AWS KMS for encryption.
B.Use LocalCryptoMaterialsCache operation.
C.Use RequestServiceQuotaIncrease operation.
D.Use AWS SQS to queue all requests made to AWS KMS.

Answer: B
Option A is incorrect as sending the data to KMS for encryption doesn’t meet the encryption requirement in transit and so can’t be used.
Option B is CORRECT as using LocalCryptoMaterialsCache is an in-memory cache that can be used to save data keys. It is a configurable cache that can configured to be made more secure.
Option C is incorrect as increasing the quota will change the performance metrics of the application.
Option D is incorrect as it will not improve the process of encryption and decryption and will not change the performance metrics of the application.
Reference:
https://aws.amazon.com/blogs/security/aws-encryption-sdk-how-to-decide-if-data-key-caching-is-right-for-your-application/