Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise organization is establishing baseline security and lifecycle standards for Identity and Access Management (IAM) across its Google Cloud resource hierarchy. The DevOps engineering team is tasked with defining standard operating procedures for provisioning new workload identities, managing default service accounts, and retiring decommissioned service accounts.
The strategy must satisfy the following architectural requirements:
Which strategy should the DevOps team implement?
iam.automaticIamGrantsForDefaultServiceAccounts organization policy constraint, provision dedicated single-purpose user-managed service accounts using a vm-[app-name] naming convention with documented descriptions, and disable unused service accounts for a validation period before permanently deleting them.This solution implements an enterprise-grade Identity and Access Management (IAM) governance framework by combining organization policy enforcement, least-privilege workload identity provisioning, standardized naming conventions, and staged lifecycle deprovisioning.
iam.automaticIamGrantsForDefaultServiceAccounts at the organization or folder level disables the automatic assignment of the basic roles/editor role to default service accounts when APIs like Compute Engine or App Engine are enabled.vm-[app-name]) provides clear traceability in Cloud Audit Logs. Maintaining documentation and contact metadata in the description field prevents identity sprawl and aligns workload access with least privilege.uniqueId) or reapplying lost permission bindings.vm-) clearly associate operational logs with specific infrastructure resources and workloads.This strategy aligns directly with Google Cloud security best practices. Deleting a service account immediately breaks all IAM bindings permanently because recreating an account with the identical email generates a completely new unique ID. Disabling first provides a safety buffer while maintaining compliance across the resource hierarchy.
This option modifies the permissions of Google-managed service agents, relies on legacy VM access scopes to constrain default service account authorization, and relies on identical naming to recover deleted service accounts.
[PROJECT_NUMBER]@cloudservices.gserviceaccount.com) runs internal Google Cloud processes on your behalf. Revoking its Editor role breaks core platform operations, such as Managed Instance Group (MIG) provisioning and autoscaling.deleted:serviceAccount:... will ignore newly created service accounts despite identical names.This approach is never correct under Google Cloud enterprise architecture standards, as modifying internal service agent policies is explicitly discouraged.
This option attempts to secure the environment by deleting default service accounts upon project creation, consolidating identity management across projects via shared service accounts, and purging deleted identities immediately.
uniqueId, leaving previous role bindings orphaned under deleted:serviceAccount:... syntax.This approach would only be considered in short-lived, ephemeral sandbox projects where resources are torn down entirely and lifecycle rollback is unnecessary.
This option delegates broad service account administration at the folder level, provisions long-lived private key files (JSON keys) for Compute Engine instances, and executes automated scripts to delete inactive accounts immediately.
roles/iam.serviceAccountAdmin at the folder level allows developers to manage, create, and delete service accounts across all projects within that folder hierarchy, violating separation of duties.This approach would only be used if workloads were running on external legacy platforms without support for Workload Identity Federation or metadata server authentication, and where automated key generation was mandated.
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