Front matter
Who This Book Is Not For
No technical book is useful if it tries to be everything to everybody.
This book makes several deliberate choices.
It is not an introduction to computers §
The book does not stop to explain what an IP address, shell, process, database, Git repository, or public/private key is.
Those concepts are used as building blocks.
It is not only an Associate Cloud Engineer exam guide §
Certification objectives may overlap heavily with the material because both deal with Google Cloud.
The book is not organized around an exam blueprint and does not attempt to predict exam questions.
If your only goal is passing a specific certification as quickly as possible, use the official exam guide and a current certification-focused study resource.
It is not a click-by-click Console tutorial §
Screenshots age badly.
More importantly, a production environment should not depend on a long sequence of undocumented human clicks.
The Console appears where it is useful for inspection or explanation, but the book favors APIs, command-line tools, Terraform, OpenTofu, Ansible, and repeatable configuration.
It is not a catalog of every Google Cloud service §
GCP contains a large number of products, specialized platforms, APIs, and industry-specific services.
This book concentrates on the services and patterns most useful to modern SaaS, enterprise, cloud infrastructure, platform engineering, security, and operations.
Some services receive a chapter. Some receive a section. Some are only mentioned. Some are not covered.
That is intentional.
It is not a promise that one architecture fits everybody §
The book contains strong recommendations because vague advice is not useful.
Those recommendations still exist inside a context.
A small SaaS company and a regulated multinational enterprise should not have identical organization structures. A public API and an internal batch processor should not have identical network exposure. A disposable development environment and a financial production database should not be treated as equally critical.
The correct design is the one whose tradeoffs are understood and appropriate to the system being built.