nerdexam
Amazon

SAA-C03 · Question #358

A company wants to store a large amount of data as objects for analytics and long-term archiving. Resources from outside AWS need to access the data. The external resources need to access the data…

The correct answer is B. Store the data in Amazon S3 Intelligent-Tiering. Amazon S3 Intelligent-Tiering is designed for data with unknown or changing access patterns. It automatically moves data between frequent and infrequent access tiers based on usage. This tier offers immediate access to all objects, regardless of which tier they are stored in…

Submitted by skyler.x· Mar 4, 2026Design Cost-Optimized Architectures

Question

A company wants to store a large amount of data as objects for analytics and long-term archiving. Resources from outside AWS need to access the data. The external resources need to access the data with unpredictable frequency. However, the external resource must have immediate access when necessary. The company needs a cost-optimized solution that provides high durability and data security. Which solution will meet these requirements?

Options

  • AStore the data in Amazon S3 Standard. Apply S3 Lifecycle policies to transition older data to S3
  • BStore the data in Amazon S3 Intelligent-Tiering.
  • CStore the data in Amazon S3 Glacier Flexible Retrieval. Use expedited retrieval to provide
  • DStore the data in Amazon Elastic File System (Amazon EFS) Infrequent Access (IA). Use lifecycle

How the community answered

(35 responses)
  • A
    3% (1)
  • B
    89% (31)
  • C
    3% (1)
  • D
    6% (2)

Explanation

Amazon S3 Intelligent-Tiering is designed for data with unknown or changing access patterns. It automatically moves data between frequent and infrequent access tiers based on usage. This tier offers immediate access to all objects, regardless of which tier they are stored in, while optimizing storage costs. S3 Intelligent-Tiering also provides the same high durability, availability, and security as other S3 storage classes and supports access from external resources using standard S3 APIs. Lifecycle policies and Glacier classes are more suitable for archival when infrequent access is predictable, but retrieval from Glacier classes is not immediate and incurs extra charges

Community Discussion

No community discussion yet for this question.

Full SAA-C03 Practice