Deploy, operate, and secure workloads on Google Cloud, from projects and billing to IAM, and track your readiness for the Associate Cloud Engineer exam Domain by Domain.
Points to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
agent policies configures Compute Engine VMs From the official documentation: “You can create a policy for a Google Cloud project that governs existing and new VMs associated with that Google Cloud project, ensuring proper installation, uninstallation, and optional auto-upgrade of all Google Cloud Observability agents on those VMs.”
AlloyDB depends on Compute Engine VMs From the official documentation: “When you scale a primary instance vertically or scale a read pool instance vertically or horizontally, AlloyDB provisions replacement or additional Compute Engine VMs in your cluster's region.”
Compute Engine VMs works with Terraform From the official documentation: “If you plan on using private networking, then you can deploy both the private networking setup of your choice and the Cloud SQL instance along with clients such as Compute Engine VMs by using Terraform.”
Compute Engine VMs is part of VPC Networks From the official documentation: “Published services: VPC-hosted services that run on Compute Engine VMs in VPC networks. Published services can be managed by Google, third parties, or your own organization.”
VM extension policy configures Compute Engine VMs From the official documentation: “With VM Extension Manager, you create policies that declare which extensions you want to install on VMs.”