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 security engineer is hardening identity governance for a production Google Cloud environment. A security audit reveals that several Compute Engine virtual machines (VMs) are utilizing the Compute Engine default service account (PROJECT_NUMBER-compute@developer.gserviceaccount.com) with the Editor role (roles/editor). Additionally, multiple legacy workloads are being decommissioned, and the operations team plans to immediately delete their associated service accounts.
Which strategy should the security engineer implement to remediate the VM identities and manage the decommissioning lifecycle according to Google Cloud best practices?
User-managed service accounts are custom identities created and managed by administrators within a project to provide workload-specific authentication and authorization. Managing the service account lifecycle by disabling unused accounts before permanently deleting them is a recommended security control that prevents operational disruption while mitigating lateral movement and privilege escalation risks.
roles/editor role.This approach directly resolves the security vulnerabilities of over-privileged default accounts by implementing least-privilege custom identities, while following established enterprise lifecycle practices to prevent catastrophic configuration loss caused by premature service account deletion.
This option suggests continuing to use the Compute Engine default service account after stripping its privileges, while immediately executing permanent deletion on decommissioned accounts under the assumption that identical email names restore permissions upon recreation.
deleted: and completely non-functional for the new account.Google Cloud IAM mapped allow policies directly to string-based email addresses without internal unique IDs, and if sharing a single sanitized account across multiple workloads met architectural least-privilege standards.
The Google APIs Service Agent (PROJECT_NUMBER@cloudservices.gserviceaccount.com) is a built-in service agent created and managed by Google to run internal platform processes and automation routines (such as managed instance group provisioning) on behalf of the project.
roles/editor). Attempting to use or modify this account for application workloads breaks underlying Google Cloud management infrastructure and automation.The objective was to configure internal Google-managed background processes rather than authenticating custom user workloads running on Compute Engine instances.
The Compute Engine Service Agent (service-PROJECT_NUMBER@compute-system.iam.gserviceaccount.com) is a specialized Google-managed service account that enables Compute Engine system controllers to access disks, manage instances, and access attached service account identities. IAM deny policies prevent principals from exercising specific permissions regardless of their granted allow roles.
roles/compute.serviceAgent role can cause severe outages in VM operations and metadata retrieval.The organization needed to enforce organization-wide guardrails to prevent specific high-risk API operations across all identities, rather than managing individual workload credentials and decommissioning application accounts.
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