Exam AWS Certified Database - Specialty topic 1 question 94 discussion

D, key words " static vendor dataset" & "lowest cost"

D gives the lower cost. It also meets the requirements - S3 can do tons of IOPS when needed. Most importantly, the data is loaded on startup and then used by the app in-memory, not used constantly - so there is no need for DynamoDB.

DynamoDB in on-demand capacity mode price: - DynamoDB Standard table class, Read Request Units (RRU) - $0.25 per MILLION read request units. - Data storage - First 25 GB stored per month is free using the DynamoDB Standard table class. - On-demand backup - Cold Backup Storage* $0.03 per GB-month (The information is static, you can do without a backup). https://aws.amazon.com/dynamodb/pricing/on-demand/ Amazon S3 pricing: S3 Standard - General purpose storage for any type of data, typically used for frequently accessed data. First 50 TB / Month - $0.023 per GB https://aws.amazon.com/s3/pricing/ Application does not start so often, I would choose answer C. DynamoDB will give this information much faster than reading from S3. The price of $0.25 per MILLION read request is cheaper than S3.

the lowest cost & a low application startup time -> Dynamo DB with OnDemand capacity mode. Option D (S3) will cause longer startup time in my opinion

simple option

Static small files. S3 is your best bet for costs

x A. RDS (costly for 1 GB data) x B. Amazon Aurora Serverless. (costly for 1 GB data) x C. Use Amazon DynamoDB in on-demand capacity mode. (postal codes and associated territorial data that is less than 1 GB in size => key value data, minimizing application launch time => dynamoDB, but caching is required at application and not database) D. Use Amazon S3 and load the data from flat files. (most cost-effective)

D is the answer

Let us see in this way, 1 GB file on boot uploading in to application time < (1 GB file from s3 to Application + load time). So definitely it is not D, I will go with B

I agree with D based on the link below: https://www.sumologic.com/insight/s3-cost-optimization/ For example, for 1 GB file stored on S3 with 1 TB of storage provisioned, you are billed for 1 GB only. In a lot of other services such as Amazon EC2, Amazon Elastic Block Storage (Amazon EBS) and Amazon DynamoDB you pay for provisioned capacity. For example, in the case of Amazon EBS disk you pay for the size of 1 TB of disk even if you just save 1 GB file. This makes managing S3 cost easier than many other services including Amazon EBS and Amazon EC2. On S3 there is no risk of over-provisioning and no need to manage disk utilization.

DDDDDDDDDDD. lowest cost. --> this says Application cache and NOT DB cache. applicationג€™s cache at start up

OR D is also a possibility

I will go with B. Will cover lowesr cost.

C or D I choose D

C: ? lowest start up time asked