Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A company is onboarding a new database administrator who is responsible for managing Cloud SQL database instances within a Google Cloud project. Company security policies enforce the principle of least privilege, requiring that the administrator have full administrative control over Cloud SQL resources while preventing modification of unrelated services such as Compute Engine instances and Cloud Storage buckets.
Which approach should you take to grant the required permissions while minimizing administrative maintenance overhead?
In Google Cloud IAM, permissions (such as cloudsql.instances.create or cloudsql.instances.update) are the atomic units that define specific actions on resources. However, permissions cannot be assigned directly to users or principals.
service.resource.verb).Google Cloud IAM supported direct access control lists (ACLs) of discrete API methods on user entities, but IAM strictly operates via role assignments.
Custom roles are user-defined IAM roles that allow organizations to bundle specific IAM permissions together when no predefined role meets their exact security or business requirements.
roles/cloudsql.admin and roles/cloudsql.editor) that align with database administration tasks, creating a custom role adds unwarranted operational burden.Google Cloud did not offer a predefined role that matched the company's specific compliance constraints—for instance, if the company required an administrator who could only restart database instances but was strictly forbidden from viewing configuration metadata.
Predefined roles in Google Cloud are service-specific collections of granular permissions created and managed directly by Google. They are mapped to common industry job functions and specific cloud services (such as Cloud SQL, Compute Engine, or Cloud Storage), giving principals exactly the permissions needed to perform a specific job role.
roles/cloudsql.admin) limits the principal's administrative capabilities exclusively to Cloud SQL resources. It prevents unwanted access or modifications to other services across the project, such as virtual machines or storage buckets.Compared to primitive roles, predefined roles enforce least privilege by scoping access strictly to Cloud SQL rather than the entire project. Compared to custom roles, predefined roles minimize operational overhead because Google manages and updates the underlying permissions automatically.
Primitive roles (also known as basic roles) are the legacy IAM roles that existed prior to granular IAM in Google Cloud: Owner (roles/owner), Editor (roles/editor), and Viewer (roles/viewer). They apply broad permissions across nearly all Google Cloud services within a project.
roles/editor role provides write and modify access across almost every resource in the project. The database administrator would gain the ability to deploy or delete Compute Engine VMs, modify Cloud Storage data, alter network routes, and disrupt services unrelated to their job function.The project were a personal sandbox or early development environment where a single engineer requires unrestricted, blanket edit access to experiment across all available Google Cloud services without configuring fine-grained permissions.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated