SOA-C02 Cost and Performance Optimization 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.

• ✗

  Enable S3 Object Tagging to categorize data.

  Why it's wrong here

  S3 Object Tagging is a metadata feature that lets you attach key-value pairs to objects for cost allocation, access control (via bucket policies), and filtering, but it does not alter the physical storage class or pricing tier of the object. Tagging alone has zero effect on storage costs because you still pay the same per-GB rate for the underlying S3 Standard storage. To reduce spend, tags must be used in conjunction with lifecycle rules or as a filter for transitions, not as a standalone cost-saving measure.

• ✗

  Enable S3 Replication to another region for disaster recovery.

  Why it's wrong here

  Enabling S3 Replication, whether Cross-Region Replication (CRR) or Same-Region Replication (SRR), duplicates every qualifying object into a destination bucket, which doubles your storage footprint and incurs additional data transfer charges for CRR. It is designed for disaster recovery, compliance, and low-latency data access, not cost reduction, so it actually increases your monthly S3 bill. Replication also adds per-object replication fees, making it an expensive choice when the goal is purely to lower storage costs.

• ✓

  Use S3 Lifecycle policies to transition objects to S3 Glacier Deep Archive after a period.

  Why this is correct

  S3 Lifecycle policies are the correct, native mechanism to reduce storage costs by automatically transitioning objects to more cost-effective storage classes after a defined age, such as moving from S3 Standard to S3 Glacier Deep Archive after 30 days. Glacier Deep Archive offers the lowest per-GB storage price in S3, with retrieval times of up to 12 hours, making it ideal for rarely accessed, long-term retention data. You can define transitions based on object age, prefix, or tags, and also set expiration to delete objects, directly cutting ongoing storage spend.

• ✓

  Use S3 Intelligent-Tiering for data with unknown or changing access patterns.

  Why this is correct

  S3 Intelligent-Tiering is a storage class that automatically monitors access patterns and moves objects between four access tiers—frequent, infrequent, archive instant, and archive—without retrieval fees or lifecycle management overhead. It is best for data with unknown, unpredictable, or changing access patterns because you only pay a small monthly monitoring fee per object, and you still benefit from lower storage costs when objects become cold. Unlike manual lifecycle policies, Intelligent-Tiering reacts dynamically to real-time usage, but it does charge a per-object monitoring fee that may not be worthwhile for very small or highly predictable datasets.

• ✗

  Enable S3 Transfer Acceleration for faster uploads.

  Why it's wrong here

  S3 Transfer Acceleration uses AWS edge locations to speed up uploads over long distances by routing traffic through an optimized network path, but it adds a per-GB transfer acceleration charge to your bill. It does not affect how much you pay for storage—only the cost of uploads—and is intended for large, time-sensitive uploads from geographically dispersed clients. For cost reduction, Transfer Acceleration is counterproductive because it increases data transfer costs and provides no benefit for stored object pricing or lifecycle efficiency.

Go deeper

Related to this question