SOA-C02 Reliability and Business Continuity Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  S3 Lifecycle policies

  Why this is correct

  S3 Lifecycle policies are the correct answer because they provide exactly the automation needed to manage the data's full lifecycle. You define rules that transition objects to less expensive storage classes like S3 Standard-IA or S3 Glacier after specified durations, and you can also set expiration actions that permanently delete objects or their versions. Lifecycle policies act on prefixes, tags, and object age, giving you precise control over when data moves to colder tiers and when it is eventually removed, which directly accomplishes both transitioning and expiring critical data.

• ✗

  S3 Intelligent-Tiering

  Why it's wrong here

  S3 Intelligent-Tiering is incorrect because it does not delete or expire objects. This storage class automatically monitors data access patterns and moves objects between its own tiers (S3 Intelligent-Tiering Frequent Access, Infrequent Access, and Archive Instant Access) to optimize storage costs without any impact on availability or performance, but it never removes data. While it can optionally transition objects to deep archive tiers, it lacks lifecycle rules for expiration or explicit scheduling, so it cannot perform the full lifecycle management that the scenario requires.

• ✗

  S3 Object Lock

  Why it's wrong here

  S3 Object Lock is wrong because it is a compliance feature, not a lifecycle automation tool. Object Lock prevents objects from being deleted or overwritten for a specified retention period, using either retention dates or legal holds, which actually works against the requirement to delete data. Although Object Lock can be used alongside lifecycle policies to govern deleted versions, it does not automate transitions and does not provide any mechanism to move data between storage classes or to expire it.

• ✗

  S3 Cross-Region Replication

  Why it's wrong here

  S3 Cross-Region Replication is not the correct answer because it only duplicates objects from one S3 bucket to another in a different AWS Region for the purposes of geographic redundancy, disaster recovery, or latency reduction. Replication does not manage lifecycle actions; it merely copies new or changed objects asynchronously, and while you can combine replication with lifecycle rules, the replication alone never transitions objects to cheaper storage or schedules their deletion. Therefore, it cannot handle the company's need to automate transitions and expire old data.

Go deeper

Related to this question