An enterprise analytics application deployed in Google Cloud processes financial transaction logs. The compliance team mandates that all log data must strictly adhere to data residency regulations and never leave the europe-west3 (Frankfurt) location. The data access pattern is characterized as follows: Data is accessed continuously with high frequency during the first 30 days after generation. Between 31 and 90 days, data is queried approximately once a month for reconciliation reports. After 90 days, data is rarely accessed but must be retained until it reaches 365 days of age for auditing purposes. Which Cloud Storage bucket configuration and lifecycle management strategy should you implement to minimize costs while complying with all requirements?

Create a regional Cloud Storage bucket in europe-west3 with the Standard storage class. Configure Object Lifecycle Management rules to transition objects to Nearline storage after 30 days, transition to Coldline storage after 90 days, and delete objects after 365 days.: What the Recommended Solution Is This architecture leverages a regional Cloud Storage bucket in europe-west3 combined with automated Object Lifecycle Management rules. It places objects initially in Standard storage and progressively shifts them through Nearline and Coldline storage before deleting them at the end of their compliance retention window. How It Meets Every Requirement Data Residency Compliance: By selecting a regional bucket in europe-west3, all object data at rest is guaranteed to remain strictly within the Frankfurt region, satisfying the regulatory requirements. First 30 Days (Continuous Access): Storing active data in the Standard storage class eliminates data retrieval fees and provides the lowest latency and optimal throughput for frequent reads. Days 31 to 90 (Monthly Access): Transitioning data to Nearline storage at day 30 drastically reduces the at-rest storage cost while aligning perfectly with the once-per-month access frequency and 30-day minimum storage duration. Days 91 to 365 (Rare Access): Moving data to Coldline storage after 90 days further decreases at-rest storage charges for rarely accessed historical logs that meet the 90-day minimum storage threshold. Retention and Cleanup: Setting an automatic Delete action at 365 days prevents unnecessary ongoing storage costs once the mandatory retention window has elapsed. Key Advantages Strict Regulatory Conformance: Restricts data replication exclusively across zones in a single region without cross-border transit. Granular Cost Optimization: Progressively lowers per-gigabyte storage pricing based on decaying access frequency. Automated Lifecycle Transitions: Removes operational overhead and human error through serverless policy enforcement. Optimized Data Retrieval: Avoids early deletion and minimum duration penalty fees by matching transitions to storage class minimum periods. Why This Is Optimal Using a regional bucket satisfies data residency mandates without incurring multi-region egress or replication overhead. Matching the data lifecycle transitions to the exact access cadence (Standard for hot data, Nearline for monthly access, Coldline for rare access) minimizes total cost of ownership (TCO).

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Intermediate

Prepare and test your skills

Regional Bucket Lifecycle from Standard to Coldline

Section: Data storage allocation

...

Explanations

...

View source documentation

Keep the momentum going with these hand-picked practice scenarios

IntermediateProfessional Cloud Architect

A Cloud Solutions Architect is using natural language prompts in Gemini Cloud Assist to generate Terraform Infrastructure as Code (IaC) and deployment scripts for a secure internal workload on Compute Engine. The organizational security policy dictates the following technical requirements: Compute Engine VM instances must not have public/external IP addresses assigned to their network interfaces. Compute Engine VM instances must maintain outbound internet connectivity to download operating system updates and packages. The deployment must not use the default VPC network. Compute Engine VM instances must run using a custom least-privilege service account instead of the default Compute Engine service account. Which infrastructure architecture and configuration generated by Gemini Cloud Assist meets all organizational technical and security requirements while adhering to Google Cloud best practices?

Gemini Cloud Assist

AdvancedProfessional Cloud DevOps Engineer

Your team is preparing a deployment strategy for a mission-critical checkout microservice hosted on Cloud Run. To adhere to Site Reliability Engineering (SRE) principles and minimize customer impact, your deployment plan must satisfy the following criteria: Deploy updates progressively using canary traffic splitting without exposing all users to new code at once. Monitor real-time telemetry and error budget burn rates during each stage of the rollout. Automatically halt the release and revert 100% of traffic to the previous healthy revision if Service Level Objective (SLO) error budget burn rates exceed acceptable thresholds. Which deployment and release strategy should you implement?

Service management (e.g., planning, deployment, maintenance, retirement)

Want more questions like this?

Get a free certification question every week.

Last updated August 28, 2026

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Intermediate

Prepare and test your skills

Regional Bucket Lifecycle from Standard to Coldline

Section: Data storage allocation

An enterprise analytics application deployed in Google Cloud processes financial transaction logs. The compliance team mandates that all log data must strictly adhere to data residency regulations and never leave the europe-west3 (Frankfurt) location.

The data access pattern is characterized as follows:

Data is accessed continuously with high frequency during the first 30 days after generation.
Between 31 and 90 days, data is queried approximately once a month for reconciliation reports.
After 90 days, data is rarely accessed but must be retained until it reaches 365 days of age for auditing purposes.

Which Cloud Storage bucket configuration and lifecycle management strategy should you implement to minimize costs while complying with all requirements?

...

Create a zonal Cloud Storage bucket in europe-west3-a with the Rapid storage class. Use Cloud Functions triggered by Cloud Tasks to manually rewrite objects into Archive storage after 90 days and delete them after 365 days.

...

Create a multi-regional Cloud Storage bucket in the eu location with the Standard storage class. Configure Object Lifecycle Management rules to transition objects to Nearline storage after 30 days, transition to Archive storage after 90 days, and delete objects after 365 days.

...

Create a regional Cloud Storage bucket in europe-west3 with the Coldline storage class as default. Configure Object Lifecycle Management rules to transition objects to Archive storage after 90 days and delete objects after 365 days.

...

Create a regional Cloud Storage bucket in europe-west3 with the Standard storage class. Configure Object Lifecycle Management rules to transition objects to Nearline storage after 30 days, transition to Coldline storage after 90 days, and delete objects after 365 days.

...

Explanations

What the Recommended Solution Is

This architecture leverages a regional Cloud Storage bucket in europe-west3 combined with automated Object Lifecycle Management rules. It places objects initially in Standard storage and progressively shifts them through Nearline and Coldline storage before deleting them at the end of their compliance retention window.

How It Meets Every Requirement

Data Residency Compliance: By selecting a regional bucket in europe-west3, all object data at rest is guaranteed to remain strictly within the Frankfurt region, satisfying the regulatory requirements.
First 30 Days (Continuous Access): Storing active data in the Standard storage class eliminates data retrieval fees and provides the lowest latency and optimal throughput for frequent reads.
Days 31 to 90 (Monthly Access): Transitioning data to Nearline storage at day 30 drastically reduces the at-rest storage cost while aligning perfectly with the once-per-month access frequency and 30-day minimum storage duration.
Days 91 to 365 (Rare Access): Moving data to Coldline storage after 90 days further decreases at-rest storage charges for rarely accessed historical logs that meet the 90-day minimum storage threshold.
Retention and Cleanup: Setting an automatic Delete action at 365 days prevents unnecessary ongoing storage costs once the mandatory retention window has elapsed.

Key Advantages

Strict Regulatory Conformance: Restricts data replication exclusively across zones in a single region without cross-border transit.
Granular Cost Optimization: Progressively lowers per-gigabyte storage pricing based on decaying access frequency.
Automated Lifecycle Transitions: Removes operational overhead and human error through serverless policy enforcement.
Optimized Data Retrieval: Avoids early deletion and minimum duration penalty fees by matching transitions to storage class minimum periods.

Why This Is Optimal

Using a regional bucket satisfies data residency mandates without incurring multi-region egress or replication overhead. Matching the data lifecycle transitions to the exact access cadence (Standard for hot data, Nearline for monthly access, Coldline for rare access) minimizes total cost of ownership (TCO).

...

View source documentation

Keep the momentum going with these hand-picked practice scenarios

IntermediateProfessional Cloud Architect

Cloud SQL Automatic Storage Increase Limit

Data storage allocation

IntermediateProfessional Cloud Architect

Persistent Disk IOPS vCPU and Capacity Limit

Data storage allocation

IntermediateProfessional Cloud Architect

Private Service Connect Global Access

VPC design and load balancing (e.g., access to cloud, internet, and cloud adjacent services)

IntermediateProfessional Cloud Architect

VPC Firewall Rule Priority Ordering

Security protection (e.g. intrusion protection, access control, and firewalls)

IntermediateProfessional Cloud Architect

A Cloud Solutions Architect is using natural language prompts in Gemini Cloud Assist to generate Terraform Infrastructure as Code (IaC) and deployment scripts for a secure internal workload on Compute Engine. The organizational security policy dictates the following technical requirements: Compute Engine VM instances must not have public/external IP addresses assigned to their network interfaces. Compute Engine VM instances must maintain outbound internet connectivity to download operating system updates and packages. The deployment must not use the default VPC network. Compute Engine VM instances must run using a custom least-privilege service account instead of the default Compute Engine service account. Which infrastructure architecture and configuration generated by Gemini Cloud Assist meets all organizational technical and security requirements while adhering to Google Cloud best practices?

Gemini Cloud Assist

AdvancedProfessional Cloud DevOps Engineer

Your team is preparing a deployment strategy for a mission-critical checkout microservice hosted on Cloud Run. To adhere to Site Reliability Engineering (SRE) principles and minimize customer impact, your deployment plan must satisfy the following criteria: Deploy updates progressively using canary traffic splitting without exposing all users to new code at once. Monitor real-time telemetry and error budget burn rates during each stage of the rollout. Automatically halt the release and revert 100% of traffic to the previous healthy revision if Service Level Objective (SLO) error budget burn rates exceed acceptable thresholds. Which deployment and release strategy should you implement?

Service management (e.g., planning, deployment, maintenance, retirement)

Want more questions like this?

Get a free certification question every week.

Last updated August 28, 2026

An enterprise analytics application deployed in Google Cloud processes financial transaction logs. The compliance team mandates that all log data must strictly adhere to data residency regulations and never leave the europe-west3 (Frankfurt) location.

The data access pattern is characterized as follows:

Data is accessed continuously with high frequency during the first 30 days after generation.
Between 31 and 90 days, data is queried approximately once a month for reconciliation reports.
After 90 days, data is rarely accessed but must be retained until it reaches 365 days of age for auditing purposes.