AWS SAA-C03 #49

A company stores call transcript files on a monthly basis. Users access the files randomly within 1 year of the call, but users access the files infrequently after 1 year. The company wants to optimize its solution by giving users the ability to query and retrieve files that are less than 1-year-old as quickly as possible. A delay in retrieving older files is acceptable.

Which solution will meet these requirements MOST cost-effectively?

A. Store individual files with tags in Amazon S3 Glacier Instant Retrieval. Query the tags to retrieve the files from S3 Glacier Instant Retrieval.

B. Store individual files in Amazon S3 Intelligent-Tiering. Use S3 Lifecycle policies to move the files to S3 Glacier Flexible Retrieval after 1 year. Query and retrieve the files that are in Amazon S3 by using Amazon Athena. Query and retrieve the files that are in S3 Glacier by using S3 Glacier Select.

C. Store individual files with tags in Amazon S3 Standard storage. Store search metadata for each archive in Amazon S3 Standard storage. Use S3 Lifecycle policies to move the files to S3 Glacier Instant Retrieval after 1 year. Query and retrieve the files by searching for metadata from Amazon S3.

D. Store individual files in Amazon S3 Standard storage. Use S3 Lifecycle policies to move the files to S3 Glacier Deep Archive after 1 year. Store search metadata in Amazon RDS. Query the files from Amazon RDS. Retrieve the files from S3 Glacier Deep Archive.


The most cost-effective solution would be Option B.

Storing individual files in Amazon S3 Intelligent-Tiering allows for automatic cost savings as the access patterns change, without performance impact or operational overhead. Using S3 Lifecycle policies to move the files to S3 Glacier Flexible Retrieval after 1 year is a cost-effective solution for infrequently accessed data where retrieval times of a few minutes to hours are acceptable.

You can query and retrieve the files that are in Amazon S3 by using Amazon Athena , which is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. For the files that are in S3 Glacier, you can use S3 Glacier Select to retrieve only the data you need from an archive, which can further save costs.

This solution meets the requirement of quick retrieval for files less than 1-year-old and acceptable delay for older files, while optimizing costs.

相关推荐
chillxiaohan1 天前
GO学习记录九——数据库触发器的使用+redis缓存策略
数据库·缓存·golang
l1t1 天前
DuckDB新版rusty_sheet 插件测试
xml·数据库·rust·插件·xlsx·duckdb
白鹭1 天前
Mysql主从同步
linux·运维·数据库·mysql
siliconstorm.ai1 天前
开源与闭源的再对决:从Grok到中国力量,AI生态走向何方?
大数据·图像处理·人工智能·语言模型·ai作画·云计算·机器翻译
M_Reus_111 天前
MySQL-Redo Log(重做日志)
数据库·mysql
llm大模型算法工程师weng1 天前
mysql常见面试题
数据库·mysql
Darenm1111 天前
SQLite数据库
数据库·sqlite
得意霄尽欢1 天前
MySQL8.0 新特性随笔
数据库·mysql
assibe1 天前
cmake基本语法结构
数据库·c++·cmake
阿雄不会写代码1 天前
python-pptx 库(最常用,适合生成/修改 PPT 文件)
云计算·aws