An enterprise operations team needs to allow a database administrator to create, update, and manage Cloud SQL database instances within project `proj-finance-db-4091`. The administrator must not receive read access to data stored inside the databases or permissions to manage non-database cloud resources. To adhere strictly to the Principle of Least Privilege, which identity configuration should you apply?
- AGrant the Editor (roles/editor) primitive role to the user on project proj-finance-db-4091.
- Grant the Cloud SQL Admin (roles/cloudsql.admin) predefined role to the user on project proj-finance-db-4091.Cevap
- CGrant the Cloud SQL Admin (roles/cloudsql.admin) predefined role to the user at the parent Folder level containing the project.
- DGrant the Owner (roles/owner) primitive role to the user at the Organization level.
Cevap
Grant the Cloud SQL Admin (roles/cloudsql.admin) predefined role bound specifically at project scope (proj-finance-db-4091).
Granting the Cloud SQL Admin (`roles/cloudsql.admin`) predefined role at the specific project scope (`proj-finance-db-4091`) strictly limits administrative permissions to Cloud SQL instances within that specific project, fully satisfying the Principle of Least Privilege.
Adım Adım Çözüm
Anahtar Kavram
Applying Least Privilege via Predefined Roles at Project Scope