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 organization is deploying a regional managed database and storage service on Google Cloud to handle sensitive customer workload data. Compliance regulations mandate that all data at rest must be protected using Customer-Managed Encryption Keys (CMEK) to ensure strict cryptographic sovereignty and organizational key lifecycle control.
You need to configure Cloud Key Management Service (Cloud KMS) and grant the necessary permissions so that the Google Cloud service can perform automated cryptographic operations on the underlying data.
Which set of actions should you take?
This option suggests using a globally located Cloud KMS key ring containing an asymmetric signing key and granting full administrative privileges (Cloud KMS Admin) to the default Compute Engine service account.
roles/cloudkms.admin provides administrative control over key configurations and IAM policies rather than cryptographic encrypt/decrypt operations, violating the principle of least privilege.This setup would be relevant if you were developing a custom application that generates and verifies software binary signatures globally, where administrative automation is managed via Compute Engine virtual machines.
This option proposes managing Customer-Supplied Encryption Keys (CSEK) inside Cloud KMS and granting the read-only Cloud KMS Viewer role to the project's default service account.
roles/cloudkms.viewer) role provides read-only access to key metadata and audit data. It grants no cryptographic capabilities (cloudkms.cryptoKeyVersions.useToEncrypt or cloudkms.cryptoKeyVersions.useToDecrypt).CSEK is appropriate for organizations whose regulatory policies strictly forbid storing key encryption keys on cloud infrastructure, requiring key material to be transmitted dynamically per API request.
Customer-Managed Encryption Keys (CMEK) allow organizations to protect data at rest in Google Cloud services using symmetric keys managed in Cloud Key Management Service (Cloud KMS). Instead of relying on Google default encryption keys, the customer controls key location, key rotation schedules, IAM access policies, and key lifecycle states (such as disabling or destroying keys).
service-PROJECT_NUMBER@gcp-sa-*.iam.gserviceaccount.com). Granting the Cloud KMS CryptoKey Encrypter/Decrypter (roles/cloudkms.cryptoKeyEncrypterDecrypter) role on the specific key allows the service agent to encrypt and decrypt data automatically on behalf of authorized user requests.This architecture adheres to the principle of least privilege by granting cryptographic rights strictly to the service agent responsible for backend encryption while enforcing regional locality alignments required across Google Cloud services.
This option places the Cloud KMS key ring in a different region from the managed storage resource and attempts to grant individual end users direct decryption permissions (roles/cloudkms.cryptoKeyDecrypter) on the Cloud KMS key.
roles/cloudkms.cryptoKeyDecrypter role only permits decryption. It lacks the cloudkms.cryptoKeyVersions.useToEncrypt permission required when writing new data to the service.Granting decryption roles directly to individual users or worker instances is appropriate only in client-side encryption architectures where the client application decrypts ciphertexts locally before processing.
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