A Software-as-a-Service (SaaS) company builds software applications and stores build artif… — AWS Certified Solutions Architect - Associate

A Software-as-a-Service (SaaS) company builds software applications and stores build artifacts in an Amazon S3 Standard bucket. The average size of each artifact is $120\text{ MB}$ . The artifacts are accessed frequently during the first $15\text{ days}$ after creation for verification and deployments. After $15\text{ days}$ , the artifacts are rarely accessed but must be retained for compliance audits for a total of $120\text{ days}$ from creation, after which they can be safely deleted. In the event of an audit, the company must be able to retrieve the artifacts within $5\text{ hours}$ . Which combination of actions should a solutions architect configure in the Amazon S3 Lifecycle policy to meet these requirements in the most cost-effective manner? (Select TWO.)

Transition the artifacts to Amazon S3 Glacier Flexible Retrieval $15\text{ days}$ after creation.Answer
Permanently delete the artifacts $120\text{ days}$ after creation.Answer
C
Transition the artifacts to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) $15\text{ days}$ after creation, and then to Amazon S3 Glacier Flexible Retrieval $35\text{ days}$ after creation.
D
Transition the artifacts to Amazon S3 Glacier Deep Archive $15\text{ days}$ after creation.
E
Transition the artifacts to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) $15\text{ days}$ after creation, and then permanently delete them $40\text{ days}$ after creation.

Answer

Transitioning the artifacts to Amazon S3 Glacier Flexible Retrieval

15\text{ days}

after creation and permanently deleting the artifacts

120\text{ days}

after creation.

Transitioning the artifacts to Amazon S3 Glacier Flexible Retrieval after

15\text{ days}

is the most cost-effective option because the artifacts are rarely accessed after that time and can be retrieved within

3\text{ to }5\text{ hours}

using standard retrieval, which complies with the

5\text{ hour}

retrieval SLA. Deleting the artifacts after

120\text{ days}

complies with the compliance retention requirement while avoiding unnecessary ongoing storage costs. Since the artifacts are stored in Glacier Flexible Retrieval for

105\text{ days}

(from day

15

to day

120

), this exceeds the

90\text{ day}

minimum storage duration, avoiding early deletion fees.

Step-by-Step Solution

Analyze the access patterns, file sizes, and retrieval SLA of the build artifacts.

Artifacts are

120\text{ MB}

(no minimum size constraints), frequently accessed for

15\text{ days}

, and rarely accessed for the next

105\text{ days}

(total retention of

120\text{ days}

). Retrieval SLA is within

5\text{ hours}

To determine the most cost-effective storage classes that satisfy the operational and retrieval speed requirements.

Select the most cost-effective storage class for the retention phase (Day

15

to Day

120

Amazon S3 Glacier Flexible Retrieval is selected. Its standard retrieval option delivers data in

3\text{ to }5\text{ hours}

, meeting the

5\text{ hour}

SLA. S3 Glacier Deep Archive is ruled out because its standard retrieval takes

12\text{ hours}

S3 Glacier Flexible Retrieval has significantly lower storage costs than S3 Standard-IA while still meeting the retrieval SLA.

Calculate the duration the objects will reside in the Glacier tier to check for minimum storage duration penalties.

Objects will reside in Glacier Flexible Retrieval from Day

15

to Day

120

, which is

105\text{ days}

. Since

105 \geq 90\text{ days}

(the minimum storage duration for Glacier Flexible Retrieval), no early deletion fees are incurred.

S3 storage classes like Glacier and Standard-IA have minimum storage durations; violating them results in early deletion/transition charges.

Define the lifecycle rules to execute the storage transitions and deletion.

Rule 1: Transition to S3 Glacier Flexible Retrieval after

15\text{ days}

. Rule 2: Expire (permanently delete) the objects after

120\text{ days}

To automate the cost-optimization lifecycle without administrative overhead.

Key Concept

Cost-Optimized Storage Tiering and Lifecycle Management

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics