An enterprise data engineering team is designing a cost-optimized storage architecture on Cloud Storage for large-scale analytical training datasets and compliance logs. The data lifecycle and operational requirements are as follows: Ingestion & Active Processing (Days 1–30): Newly ingested datasets are actively read, transformed, and queried multiple times per day by data pipelines. Periodic Validation (Days 31–90): Datasets are accessed at most once per month for model validation and intermittent quarterly reporting. Long-term Compliance (Day 91 to 7 Years): Data must be retained for regulatory compliance for seven years, accessed less than once a year, but any ad-hoc audit queries require sub-second (millisecond) retrieval latency. Cost Governance: The strategy must minimize total storage costs while strictly avoiding early deletion fees and premature class transition penalties. Which Object Lifecycle Management policy should the team configure to meet these requirements?

Store incoming objects as Standard storage; configure a lifecycle rule to transition objects to Nearline at age 30 days, transition to Archive at age 90 days, and delete objects at age 2,555 days.: ### What Cloud Storage Object Lifecycle Management Is **Cloud Storage Object Lifecycle Management** allows administrators to define declarative rules that automatically manage object lifecycles, such as transitioning data to colder **storage classes** or permanently deleting expired objects based on attributes like **object age**, creation date, or versioning state. ### How It Meets the Requirements - **Ingestion & Active Processing (Days 1–30)**: Storing objects initially in **Standard storage** incurs no data retrieval fees and imposes no **minimum storage duration**, accommodating frequent pipeline read/write cycles without penalties. - **Periodic Validation (Days 31–90)**: Transitioning objects to **Nearline storage** at **age 30 days** aligns perfectly with workloads accessed at most once a month. Because objects remain in Nearline for 60 days (from day 30 to day 90), this exceeds Nearline's **30-day minimum storage duration**, avoiding any early deletion or early transition fees. - **Long-term Compliance (Day 91 to 7 Years)**: Moving data to **Archive storage** at **age 90 days** provides the lowest at-rest storage pricing for objects accessed less than once per year. Crucially, Google Cloud Storage provides **consistent millisecond time-to-first-byte latency** across all storage classes (including Archive), fulfilling the sub-second retrieval requirement without pre-warming. - **Cost Governance & Deletion**: Objects remain in Archive storage for approximately 6.75 years, far exceeding Archive's **365-day minimum storage duration**, ensuring that deletion at **age 2,555 days** (7 years) incurs zero early deletion charges. ### Key Advantages - **Zero Early Transition/Deletion Penalties**: Respects all minimum commitment durations (Nearline: 30 days; Archive: 365 days). - **High Retrieval Performance**: Maintains sub-second latency for audit requests regardless of tier. - **Automated Hands-off Tiering**: Enforces retention and deletion policies natively without custom code or orchestrators. ### Why This Is Optimal This configuration aligns storage classes directly with actual access frequency while strictly adhering to billing duration constraints, resulting in the lowest total cost of ownership (TCO).

Cloud Storage Lifecycle Tiering Optimization | professional-cloud-data-engineer

Cloud Storage Lifecycle Tiering Optimization

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise data engineering team is designing a cost-optimized storage architecture on Cloud Storage for large-scale analytical training datasets and compliance logs. The data lifecycle and operational requirements are as follows:

Ingestion & Active Processing (Days 1–30): Newly ingested datasets are actively read, transformed, and queried multiple times per day by data pipelines.
Periodic Validation (Days 31–90): Datasets are accessed at most once per month for model validation and intermittent quarterly reporting.
Long-term Compliance (Day 91 to 7 Years): Data must be retained for regulatory compliance for seven years, accessed less than once a year, but any ad-hoc audit queries require sub-second (millisecond) retrieval latency.
Cost Governance: The strategy must minimize total storage costs while strictly avoiding early deletion fees and premature class transition penalties.

Which Object Lifecycle Management policy should the team configure to meet these requirements?

Store incoming objects as Standard storage; configure a lifecycle rule to transition objects to Nearline at age 30 days, transition to Archive at age 90 days, and delete objects at age 2,555 days.

Store incoming objects as Standard storage; configure a lifecycle rule to transition objects to Coldline at age 30 days, transition to Archive at age 60 days, and delete objects at age 2,555 days.

Store incoming objects as Nearline storage upon bucket ingestion; configure a lifecycle rule to transition objects to Archive at age 90 days, and delete objects at age 2,555 days.

Store incoming objects as Standard storage; configure a lifecycle rule to transition objects to Archive at age 30 days, and configure asynchronous batch restore pipelines for compliance access.

Professional Cloud Data Engineer

Cloud Storage Lifecycle Tiering Optimization

Related questions