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.
A financial services organization is implementing customer-managed encryption keys (CMEK) using Cloud Key Management Service (Cloud KMS) to protect data across several Cloud Storage buckets. The compliance team requires a strict separation of duties and the enforcement of least privilege across cryptographic assets:
Which IAM role configuration should you implement to satisfy these requirements?
roles/cloudkms.admin) role to the key administrators, and assign the Storage Admin (roles/storage.admin) role to the Cloud Storage service agent on the target Cloud Storage bucket.This setup assigns the administrative KMS role to key administrators but assigns a storage administration role (roles/storage.admin) to the Cloud Storage service agent on the storage bucket.
cloudkms.cryptoKeyVersions.useToEncrypt and cloudkms.cryptoKeyVersions.useToDecrypt) to perform CMEK envelope encryption operations. Granting storage roles on the bucket does not grant any access to Cloud KMS.roles/storage.admin is unnecessary and does not resolve the cryptographic access requirement.roles/cloudkms.cryptoKeyEncrypterDecrypter on the key, attempts by Cloud Storage to encrypt new objects with the CMEK key will fail with permission denied errors.You needed a human storage administrator to manage bucket configurations, lifecycle rules, and object retention policies.
roles/owner) role to the key administrators at the project level, and assign the Cloud KMS Admin (roles/cloudkms.admin) role to the Cloud Storage service agent on the KMS KeyRing.This configuration uses the primitive Owner (roles/owner) role for human administrators and assigns administrative KMS capabilities to the Cloud Storage service agent.
useToEncrypt and useToDecrypt), which are not provided by roles/cloudkms.admin. Granting roles/cloudkms.admin to the service agent gives it key management capabilities it does not need while failing to allow it to perform actual encryption/decryption operations.You were configuring initial sandbox access for a single project developer who required full, unrestricted management over all services and deployment pipelines.
roles/cloudkms.admin) role to the key administrators on the KeyRing or project, and assign the Cloud KMS CryptoKey Encrypter/Decrypter (roles/cloudkms.cryptoKeyEncrypterDecrypter) role to the Cloud Storage service agent on the specific CryptoKey.This configuration establishes a strict separation of duties and implements the principle of least privilege by assigning distinct predefined Cloud KMS roles to human administrators and service identities at the appropriate resource hierarchy levels.
roles/cloudkms.admin) role allows key administrators to create, update, and manage the lifecycle of KeyRings and CryptoKeys, as well as set IAM policies. Crucially, this role does not grant cloudkms.cryptoKeyVersions.useToEncrypt or cloudkms.cryptoKeyVersions.useToDecrypt permissions, preventing administrators from encrypting or decrypting data.roles/cloudkms.cryptoKeyEncrypterDecrypter) role provides the Cloud Storage service agent (service-PROJECT_NUMBER@gs-project-accounts.iam.gserviceaccount.com) the exact permissions required to encrypt and decrypt object data during read and write operations.Predefined Cloud KMS roles are inherently engineered to separate key administration from data plane cryptographic operations. Applying these bindings at the CryptoKey level ensures that both least privilege and organizational duty separation are strictly enforced.
roles/cloudkms.cryptoKeyEncrypterDecrypter) role to both the key administrators and the Cloud Storage service agent at the project level.This design grants the same cryptographic data-plane role (roles/cloudkms.cryptoKeyEncrypterDecrypter) to both key management personnel and the storage service account across the entire Google Cloud project.
cloudkms.cryptoKeys.create, cloudkms.cryptoKeys.update, cloudkms.cryptoKeys.setIamPolicy) to manage key rotation schedules, create new keys, or update access policies.Both entities were worker processes or microservices that strictly needed to encrypt and decrypt application data without any requirement for administrative separation.
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