A new operations engineer must be able to start, stop, and reconfigure Compute Engine VM instances in a production project. They must not be able to change VPC networks, firewall rules, Cloud Storage buckets, or IAM policies. Following Google-recommended practices, which role should you grant on the project?
Choose one.
Predefined roles are Google-maintained permission sets scoped to one service and job function. Several Compute Engine roles sound similar but cover different resources.
The engineer needs instance lifecycle and configuration control and nothing else. roles/compute.instanceAdmin.v1 is the predefined role for exactly that. roles/compute.admin would also let them start and stop VMs, which makes it tempting, but it adds network and firewall administration the stem rules out. compute.storageAdmin covers disks and images, and osAdminLogin plus compute.viewer gives guest-OS login and visibility, not control of the instance resource.
- List the actions required: start, stop, reconfigure instances.
- List what is forbidden: networks, firewalls, storage, IAM.
- Find the predefined role whose scope matches the allowed actions only.
- Eliminate roles that cover the wrong resource (disks, guest login) or too many resources (compute.admin).
Exam tip: Choose the predefined role scoped to the resource the person manages: instances means compute.instanceAdmin.v1, not compute.admin.
Managing Cloud IAM: Roles, Policies, and Inheritance — the lesson that teaches this.