Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 326 discussion

AB A : Access Pattern for each object inconsistent, Infrequent Access B : Deleting Incomplete Multipart Uploads to Lower Amazon S3 Costs

B because Abort Incomplete Multipart Uploads Using S3 Lifecycle => https://aws.amazon.com/blogs/aws-cloud-financial-management/discovering-and-deleting-incomplete-multipart-uploads-to-lower-amazon-s3-costs/ A because The objects will be used less frequently after 30 days, but the access patterns for each object will be inconsistent => random access => S3 Intelligent-Tiering

Inconsistent access patterns: A is correct, and D is out (could work but less ideal and costs more). C: "object delete markers" only apply to versioned buckets.

AB for sure

If we consider these statements: 1. For the first 30 days after upload, the objects will be accessed frequently 2.The objects will be used less frequently after 30 days, but the access patterns for each object will be inconsistent 3.The company must optimize its S3 storage costs while maintaining high availability and resiliency of stored assets. 4.The company uses multipart upload in parallel by using S3 APIs and overwrites if the same object is uploaded again. Statements 1 and 2 cloudl be completed with option D and not A because datas are infrequently accessed only after 30 days. Due to usage of multipart upload, to meet requirement regarding cost optimization, option B will be used to clean up buckets uncompleted file parts(statements 3 & 4).

Because A & D address the main ask, there's no mention of cost optimization.

Because A & C address the main ask, there's no mention of cost optimization.

A as the access pattern for each object is inconsistent so let AWS AWS do the handling. B deals with multi-part duplication issues and saves money by deleting incomplete uploads C No mention of deleted object so this is a distractor D The objects will be accessed in unpredictable pattern so can't use this E Not HA compliant

C is nonsense E does not meet the "high availability and resiliency" requirement B is obvious (incomplete multipart uploads consume space -> cost money) The tricky part is A vs. D. However, 'inconsistent access patterns' are the primary use case for Intelligent-Tiering. There are probably objects that will never be accessed and that would be moved to Glacier Instant Retrieval by Intelligent-Tiering, thus the overall cost would be lower than with D.

bd https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html#sc-infreq-data-access =>S3 Standard-IA objects are resilient to the loss of an Availability Zone. This storage class offers greater availability and resiliency than the S3 One Zone-IA class

I wouldnt go with D since " the access patterns for each object will be inconsistent.", so we cannot move all assets to IA

incosistent access pattern brings more sense to use Intelligent-Tiering after 30 days which also covers infrequent access.

A. Move assets to S3 Intelligent-Tiering after 30 days. B. Configure an S3 Lifecycle policy to clean up incomplete multipart uploads.

should be A and B

Option A has not been mentioned for resiliency in S3, check the page: https://docs.aws.amazon.com/AmazonS3/latest/userguide/disaster-recovery-resiliency.html Therefore, I am with B & D choices.

A. Move assets to S3 Intelligent-Tiering after 30 days. B. Configure an S3 Lifecycle policy to clean up incomplete multipart uploads. Explanation: A. Moving assets to S3 Intelligent-Tiering after 30 days: This storage class automatically analyzes the access patterns of objects and moves them between frequent access and infrequent access tiers. Since the objects will be accessed frequently for the first 30 days, storing them in the frequent access tier during that period optimizes performance. After 30 days, when the access patterns become inconsistent, S3 Intelligent-Tiering will automatically move the objects to the infrequent access tier, reducing storage costs. B. Configuring an S3 Lifecycle policy to clean up incomplete multipart uploads: Multipart uploads are used for large objects, and incomplete multipart uploads can consume storage space if not cleaned up. By configuring an S3 Lifecycle policy to clean up incomplete multipart uploads, unnecessary storage costs can be avoided.

AD. B makes no sense because multipart uploads overwrite objects that are already uploaded. The question never says this is a problem.