Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is designing a centralized Customer-Managed Encryption Key (CMEK) strategy in Google Cloud to protect sensitive datasets across several workload projects.
The security architecture must adhere to the following operational and compliance requirements:
Which architectural approach should you implement in Cloud Key Management Service (Cloud KMS)?
roles/editor) to workload service accounts on the key project, create a single shared CryptoKey for all workloads, and configure security administrators to manually rotate and re-encrypt data every 90 days.This approach relies on Google Cloud basic (primitive) roles (roles/editor), shares a single cryptographic key across multiple disparate workloads, and relies on manual operational intervention for key rotation and data re-encryption.
roles/editor primitive role grants broad permissions across virtually all cloud resources in the project, exceeding the minimum permissions needed for cryptographic operations.Owner, Editor, Viewer) do not offer the fine-grained control required for compliance-sensitive and cryptographic operations.The system was a simple, non-production proof-of-concept environment where granular access control, compliance boundaries, and automated key lifecycles were not required.
roles/cloudkms.admin) to workload service accounts.This configuration decentralizes key management into workload projects, configures automatic rotation, destroys previous key versions immediately upon the creation of a new version, and assigns administrative rights directly to application service accounts.
roles/cloudkms.admin. Granting admin privileges allows service accounts to manage key policies and lifecycles, and by default, roles/cloudkms.admin does not provide the roles/cloudkms.cryptoKeyEncrypterDecrypter capability required for workloads to encrypt and decrypt their data.The organization required strict ephemeral encryption where past data must become permanently inaccessible immediately after a 90-day retention window expires.
roles/cloudkms.cryptoKeyEncrypterDecrypter) at the project level, configure automatic rotation, and grant workload service accounts the Cloud KMS Admin role (roles/cloudkms.admin) on individual key rings.This approach inverses the required IAM roles by giving security administrators operational cryptographic access (roles/cloudkms.cryptoKeyEncrypterDecrypter) while giving workload service accounts administrative management privileges (roles/cloudkms.admin) over the key rings.
roles/cloudkms.admin allows compromised workloads to alter IAM policies, disable critical keys, or trigger accidental denial-of-service events across all keys in that ring.roles/cloudkms.admin role contains cloudkms.cryptoKeys.create, cloudkms.cryptoKeys.update, and cloudkms.cryptoKeys.setIamPolicy, none of which are appropriate for automated application identities.The goal was to allow developers full control over key infrastructure while centralizing all encryption/decryption operations into an administrative security pipeline.
roles/cloudkms.admin) on the key ring, configure an automatic rotation period of 90 days on the CryptoKey, and grant workload service accounts the Cloud KMS CryptoKey Encrypter/Decrypter role (roles/cloudkms.cryptoKeyEncrypterDecrypter) on their specific CryptoKeys.Google Cloud Key Management Service (Cloud KMS) provides a scalable and secure cryptographic key management system. In a secure enterprise architecture, keys are organized hierarchically within Projects, Key Rings, and CryptoKeys, allowing administrators to define fine-grained Identity and Access Management (IAM) policies and automate key lifecycle workflows.
roles/cloudkms.admin role allows them to manage key rings, create keys, set automatic rotation periods, and disable or destroy retired key versions without granting data access. The roles/cloudkms.admin role specifically does not include permissions to encrypt or decrypt data payload contents (cloudkms.cryptoKeyVersions.useToEncrypt or cloudkms.cryptoKeyVersions.useToDecrypt).roles/cloudkms.cryptoKeyEncrypterDecrypter role directly at the individual CryptoKey resource level ensures workload service accounts can only encrypt and decrypt using their designated key, preventing cross-workload access and administrative modifications.prj-c-kms project enables dedicated auditability and strict perimeter management.This design perfectly balances least privilege, operational automation, and separation of duties by keeping administrative permissions isolated from data plane cryptographic access.
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