Study guide
11.2 Working with Snapshots and Custom Images
Google Cloud Associate Cloud Engineer ACE
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & Exam Overview
1.1 About the GCP Associate Cloud Engineer Exam 1.2 How to Use This Study Guide & Build a Study Plan
2 Chapter 2: Resource Hierarchy, IAM Basics & Cloud Identity
2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects 2.2 Organization Policies & Granting IAM Roles 2.3 Cloud Identity: Managing Users and Groups
3 Chapter 3: APIs, Quotas & Billing Configuration
3.1 Enabling APIs and Provisioning Cloud Operations Suite 3.2 Assessing and Requesting Quota Increases 3.3 Billing Accounts, Project Linking & Billing Exports 3.4 Billing Budgets and Alerts
4 Chapter 4: Planning Compute & Storage Resources
4.1 Choosing the Right Compute Option: GCE vs. GKE vs. Cloud Run vs. Cloud Functions 4.2 Spot VMs, Custom Machine Types & Cost-Optimized Compute Planning 4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable 4.4 Cloud Storage Classes & Persistent Disk Types
5 Chapter 5: Planning Network Resources
5.1 Load Balancing Options and Use Cases 5.2 Regional Resource Placement & High Availability Planning 5.3 Network Service Tiers: Premium vs. Standard
6 Chapter 6: Deploying Compute Engine Workloads
6.1 Launching Compute Engine Instances: Disks, SSH Keys & Availability Policies 6.2 Managed Instance Groups, Instance Templates & Autoscaling 6.3 OS Login and VM Manager for Fleet Configuration
7 Chapter 7: Deploying Google Kubernetes Engine Workloads
7.1 Installing and Configuring kubectl 7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise 7.3 Deploying Containerized Applications to GKE
8 Chapter 8: Deploying Serverless & Event-Driven Applications
8.1 Deploying Applications to Cloud Run and Cloud Functions 8.2 Event-Driven Architectures: Pub/Sub, Cloud Storage Triggers & Eventarc
9 Chapter 9: Deploying Data Solutions
9.1 Deploying Data Products: Cloud SQL, Firestore, Spanner, BigQuery & AlloyDB 9.2 Deploying Pub/Sub, Dataflow & Loading Data into Google Cloud
10 Chapter 10: Deploying Networking Resources & Infrastructure as Code
10.1 Creating VPCs, Subnets & Shared VPC 10.2 Firewall Rules, Cloud VPN & VPC Network Peering 10.3 Infrastructure as Code: Terraform, Config Connector, Cloud Foundation Toolkit & Helm
11 Chapter 11: Managing Compute Engine & GKE in Production
11.1 Connecting to and Managing Running Compute Engine Instances 11.2 Working with Snapshots and Custom Images 11.3 Managing GKE Clusters: Node Pools, Workloads & Artifact Registry Access 11.4 Horizontal and Vertical Pod Autoscaling in GKE
12 Chapter 12: Managing Cloud Run, Storage & Database Operations
12.1 Managing Cloud Run Revisions, Traffic Splitting & Scaling 12.2 Managing and Securing Cloud Storage Objects & Lifecycle Policies 12.3 Querying, Estimating Costs, Backup & Job Monitoring for Databases (Cloud SQL, BigQuery, Spanner, Dataflow)
13 Chapter 13: Networking Operations, Monitoring & Logging
13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT 13.2 Cloud Monitoring: Alerts, Custom Metrics & Dashboards 13.3 Cloud Logging: Buckets, Log Analytics, Routers & Filtering 13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs
14 Chapter 14: IAM Policies & Role Types
14.1 IAM Policies: Structure, Bindings & Policy Hierarchy 14.2 IAM Role Types: Basic, Predefined & Custom Roles
15 Chapter 15: Service Accounts & Security Configuration
15.1 Creating Service Accounts & Assigning Least-Privilege Permissions 15.2 Assigning Service Accounts to Resources & Managing SA IAM Policies 15.3 Service Account Impersonation & Short-Lived Credentials
16 Chapter 16: Exam Readiness — Scenarios & Test-Day Strategy
16.1 Common ACE Exam Scenarios & Decision Frameworks 16.2 Test-Day Logistics, Time Management & Final Review Checklist
11.2 Working with Snapshots and Custom Images
Key Takeaways Explain This Topic AI
A snapshot is an incremental, point-in-time backup of a persistent disk; an image is a bootable template (often built from a snapshot) used to create new VM instances.
Only the first snapshot in a chain is a full copy — later snapshots store only changed blocks — but Compute Engine manages the dependency chain automatically, so deleting an older snapshot never breaks a newer one's ability to restore.
Custom images can be created from a disk (attached or detached) or from an existing snapshot, and support four lifecycle states: ACTIVE, DEPRECATED, OBSOLETE, and DELETED.
Snapshot schedules (resource policies) automate recurring backups and are attached directly to a persistent disk with gcloud compute disks add-resource-policies .
Snapshots can be scoped regionally or to a multi-region for storage/compliance reasons; images default to the nearest multi-region unless a --storage-location is specified.
Last updated: July 2026
Why This Topic Matters
Exam Domain 4 explicitly lists "working with snapshots" and "working with images" as tested sub-topics under managing Compute Engine resources. These two artifacts look similar (both are stored disk data) but serve very different operational purposes, and the exam frequently tests whether you know which one to reach for: backup/recovery of an existing disk's data (snapshot) versus standing up new, identically configured VMs at scale (image). Confusing the two is one of the most common wrong answers on ACE practice exams.
Snapshots: Point-in-Time Disk Backups
A snapshot is an incremental, point-in-time backup of a persistent disk (PD) — zonal or regional. Key properties:
You can snapshot a disk while it is still attached to a running instance ; Compute Engine handles this safely, though for applications sensitive to write-consistency it's best practice to briefly quiesce writes first.
Snapshots are incremental after the first one : the first snapshot in a chain is a full copy of the disk's blocks; every snapshot after that stores only the blocks that changed since the previous snapshot. This keeps both storage cost and snapshot creation time down for large disks that change slowly.
Despite being incremental, each snapshot is independently restorable — Compute Engine tracks the underlying block dependency chain for you, so deleting an older snapshot in the middle of a chain does not corrupt or invalidate newer snapshots. This is a frequently-tested trap: candidates assume deleting snapshot #1 breaks snapshot #3's ability to restore, but it does not.
Two snapshot types exist: standard snapshots (for regular backup/DR) and archive snapshots (cheaper, intended for long-term, infrequently-accessed retention).
Storage scope can be regional or multi-regional ; a regional snapshot (still labeled Preview in some contexts) restricts storage to a specific region for data-residency or cost reasons, while the default multi-region scope maximizes durability and availability.
- Creating and Scheduling Snapshots gcloud compute snapshots create my-snapshot \
- -source-disk=my-disk --source-disk-zone=us-central1-a \
- -snapshot-type=STANDARD
For production workloads, ACE expects you to know that ad hoc gcloud compute snapshots create calls are not the recommended pattern — snapshot schedules (a type of resource policy ) are: gcloud compute resource-policies create snapshot-schedule my-daily-schedule \
- -region=us-central1 \
- -daily-schedule --start-time=03:00 \
- -max-retention-days=14
- gcloud compute disks add-resource-policies my-disk \
- -resource-policies=my-daily-schedule --zone=us-central1-a
This attaches a recurring backup cadence directly to the disk, with automatic retention/expiry — the ACE-correct answer whenever a scenario says "automate nightly backups with a defined retention window."
Custom Images: Reusable VM Templates
A custom image is a bootable template used to create new VM instances with a pre-configured OS, patches, and application software already baked in — the "golden image" pattern. Two source paths:
From a disk — gcloud compute images create my-image --source-disk=my-disk --source-disk-zone=us-central1-a . Best practice is to stop the source VM first (or at minimum run sudo sync and pause writes) to guarantee a consistent image.
From a snapshot — gcloud compute images create my-image --source-snapshot=my-snapshot . This is the common enterprise pattern: take a snapshot as the durable backup artifact, then build a versioned image from it whenever a new golden image release is needed, without touching the running source VM at all.
Image Families and Deprecation States
Google groups related image versions into an image family (e.g., debian-12 ), so that instance templates can reference --image-family=my-app-image and always resolve to the latest non-deprecated image in that family — a critical pattern for rolling out patched images without editing every template. Each image carries one of four lifecycle states:
- State Meaning
- ACTIVE Default state; can be used to create new instances and is returned by family lookups
- DEPRECATED Still usable, but family lookups skip it in favor of a newer ACTIVE image (a warning is shown)
- OBSOLETE Cannot be used to create new instances at all; existing instances are unaffected
- DELETED Fully removed and unusable
- Snapshot vs. Image: The Core Distinction
- Snapshot Custom Image
- Purpose Backup/restore a disk's data Reusable bootable template for new VMs
- Source A persistent disk A disk or a snapshot
- Incremental? Yes — only changed blocks after the first No — each image is a complete, standalone template
- Typical use Disaster recovery, point-in-time rollback Instance templates, MIGs, golden-image pipelines
- Automation primitive Snapshot schedule (resource policy) Image family + deprecation lifecycle
- Realistic Exam Scenario
A platform team patches a base OS image monthly and needs every new VM created by an autoscaling managed instance group (MIG) to automatically pick up the latest patched image without editing the instance template each month, while old instances remain untouched. The ACE-correct pattern: publish each monthly build into the same image family , mark the previous month's image DEPRECATED (not OBSOLETE, since already-running instances still reference it), and point the instance template at --image-family=patched-base rather than a specific image version. Combine this with a nightly snapshot schedule on any stateful data disks for independent disaster-recovery coverage — the image protects the VM template, the snapshot protects the data.