Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise organization is establishing separation of duties for an automated compliance bot. The bot must continuously audit and remediate Identity and Access Management (IAM) allow policies across multiple Google Cloud projects.
The solution must satisfy the following security constraints:
Which IAM role configuration should the security team grant to the bot?
roles/owner) on the target projects.The Owner role (roles/owner) is a legacy primitive/basic role that grants universal control over virtually all Google Cloud resources within a project, including managing allow policies, billing associations, service configurations, and project lifecycle deletion.
roles/owner role contains thousands of granular permissions across all services. Granting it to an automated compliance bot introduces massive over-privilege.roles/owner allows reading, writing, and deleting any underlying infrastructure, disks, and data storage systems.The automated bot were required to act as the primary project creator and full lifecycle manager with universal resource deployment and deletion privileges in a non-production sandbox.
roles/resourcemanager.projectIamAdmin) on the target projects.The Project IAM Admin role (roles/resourcemanager.projectIamAdmin) is a specialized predefined IAM role designed for administrative control over identity and access policies at the project level. It provides the essential permissions—such as resourcemanager.projects.getIamPolicy and resourcemanager.projects.setIamPolicy—required to inspect, update, and manage allow policy bindings without bundling broad infrastructure access.
roles/resourcemanager.projectIamAdmin decouples policy administration from resource administration. It does not include data plane access permissions or privileges to create, mutate, or delete workload infrastructure (such as Compute Engine VMs or Cloud Storage objects).Owner or Editor, the bot is restricted purely to authorization management, eliminating unnecessary privilege escalation paths.Granting roles/resourcemanager.projectIamAdmin directly meets all operational and security specifications without requiring the ongoing maintenance of custom roles, while strictly honoring the principle of least privilege.
resourcemanager.projects.get and resourcemanager.projects.update permissions.A custom role combining resourcemanager.projects.get and resourcemanager.projects.update allows a principal to retrieve project metadata (such as project name, ID, and labels) and modify project configuration properties.
resourcemanager.projects.update permission only allows updating general project metadata, not IAM allow policies.resourcemanager.projects.getIamPolicy and resourcemanager.projects.setIamPolicy. Without these distinct permissions, all policy audit and remediation API calls will fail with permission denied errors.resourcemanager.projects.get grants read access to project attributes, not access policies.resourcemanager.projects.update allows modifying project display names and labels, not authorization bindings.*getIamPolicy and *setIamPolicy permissions.The compliance bot only needed to inspect and standardize project metadata, organizational tags, or project display names without managing access control policies.
roles/editor) combined with the Security Reviewer role (roles/iam.securityReviewer).The Editor role (roles/editor) is a basic role that provides wide read-write access to deploy, modify, and delete project resources across most Google Cloud services. The Security Reviewer role (roles/iam.securityReviewer) is a predefined role that grants read-only permissions to inspect security configurations and IAM policies.
roles/iam.securityReviewer provides read access to IAM policies, the basic roles/editor role explicitly does not include setIamPolicy permissions (which are reserved for Owner and specific IAM Admin roles). Therefore, the bot cannot remediate or update allow policies.roles/editor grants broad access to modify, deploy, and delete infrastructure components, violating the strict constraint prohibiting infrastructure and data modifications.roles/editor cannot modify allow policies (setIamPolicy).roles/editor grants dangerous data plane and resource mutation access across services.The requirement called for a principal to deploy application infrastructure while having read-only visibility into the organization's overall security and compliance posture.
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 Validated