What's changed: Created Associate Cloud Engineer Chapter 4 (Domain 4 "Operating": operating compute/storage/networking = snapshots/images/GKE node pools-autoscaling/Cloud Run traffic splitting/object lifecycle/DB backup/subnet expansion/static IPs/Cloud DNS/Cloud NAT; monitoring and logging = Cloud Monitoring (metrics/alerts/custom metrics)/Ops Agent/Managed Service for Prometheus/Cloud Logging (log router/export)/audit logs).
4.1Operating compute, storage, and networking
Understand operational tasks: Compute Engine snapshots and images, GKE node pools and horizontal/vertical autoscaling, Cloud Run versions and traffic splitting, Cloud Storage object lifecycle management and database backup/restore, and subnet expansion, static IPs, Cloud DNS, and Cloud NAT.
After deploying, you must keep things running and apply changes safely. Here are key operational tasks per service.
4.1.1Operating compute
On Compute Engine, use disk snapshots for backup/restore (schedulable) and create images from a VM or snapshot to mass-produce identical VMs. On GKE, add/edit/remove node pools and configure horizontal autoscaling (Pod count) and vertical autoscaling (resource size) with load. On Cloud Run, deploy new versions and use traffic splitting to roll out gradually (canary) and tune autoscaling parameters (min/max instances). Map "roll out a new version gradually = traffic splitting."
4.1.2Operating storage and networking
On Cloud Storage, use object lifecycle management to automate "delete after N days" or "move old data to a cheaper class," cutting cost. Databases use Google-managed backup and restore. For networking, operate adding a subnet to an existing VPC, expanding a subnet when IPs run short, reserving static IPs, Cloud DNS for internal/external name resolution, and Cloud NAT to let VMs without external IPs reach the internet outbound.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.