DVA-C02 Development with AWS Services 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 configuration

  Why this is correct

  S3 Lifecycle configuration is the correct choice because it allows developers to define rules for automatically transitioning objects between different S3 storage classes (e.g., S3 Standard to S3 Standard-IA, Glacier, or Glacier Deep Archive) based on their age or access patterns. This is ideal for application logs, which typically become less frequently accessed over time but still require retention, enabling significant cost savings by moving them to progressively colder storage tiers. Furthermore, lifecycle policies can also be configured to automatically expire and permanently delete objects after a specified period, ensuring compliance and managing storage footprint efficiently.

• ✗

  S3 Object Lock

  Why it's wrong here

  S3 Object Lock is designed to prevent objects from being deleted or overwritten for a fixed amount of time or indefinitely, providing Write Once Read Many (WORM) capabilities for regulatory compliance. While it ensures data immutability, it does not automate the transition of objects to different storage classes or manage their expiration based on age. Its primary purpose is data retention and protection against accidental or malicious deletion, not cost-optimized lifecycle management through storage class changes.

• ✗

  S3 Replication

  Why it's wrong here

  S3 Replication, whether Cross-Region Replication (CRR) or Same-Region Replication (SRR), is used to automatically copy objects between S3 buckets for purposes like disaster recovery, compliance, or reducing latency for geographically dispersed users. It creates duplicate copies of data but does not manage the lifecycle of objects within a single bucket, nor does it automatically transition objects to different storage classes based on their age or access patterns. Replication is about data redundancy and distribution, not internal lifecycle optimization.

• ✗

  S3 Event Notifications

  Why it's wrong here

  S3 Event Notifications allow developers to receive alerts or trigger actions when specific events occur in an S3 bucket, such as an object being created, deleted, or restored. These notifications can be sent to Amazon SNS, SQS, or AWS Lambda functions to initiate downstream processing of logs or other data. However, S3 Event Notifications do not directly manage the storage class transitions or expiration of objects within S3 itself; they only provide a mechanism to react to object-level events, requiring external logic to implement lifecycle management.

Go deeper

Related to this question