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 enterprise is designing a secure storage and compute architecture on Google Cloud for sensitive workload data across Cloud Storage and Compute Engine persistent disks.
The enterprise has established the following security and compliance requirements:
Which encryption strategy should the organization implement?
Google-default encryption is the standard, baseline security mechanism that automatically encrypts all user data at rest across Google Cloud using AES-256 or AES-128 algorithms. Google owns, manages, stores, and rotates both the Data Encryption Keys (DEKs) and Key Encryption Keys (KEKs) using internal key management systems (Keystore and Root Keystore).
gcp.restrictCmekCryptoKeyProjects) do not apply to default encryption.The organization required effortless, zero-maintenance encryption at rest without needing custom key rotation cycles, manual key revocation capabilities, or dedicated cryptographic access auditing.
Customer-Supplied Encryption Keys (CSEK) allow customers to supply their own raw AES-256 keys in API headers when performing storage or compute operations. Google uses the supplied key in temporary, transient memory to encrypt or decrypt data, and immediately discards the key after the operation completes without persisting it to disk.
gcp.restrictCmekCryptoKeyProjects cannot govern or restrict CSEK keys.The company had a strict regulatory requirement forbidding cryptographic key material from ever being stored in any cloud service or cloud-hosted key management system.
Customer-Managed Encryption Keys (CMEK) allow organizations to protect data at rest in Google Cloud services while retaining full administrative control over the cryptographic keys. Through Cloud Key Management Service (Cloud KMS) or Cloud HSM, organizations create, manage, rotate, disable, and destroy the Key Encryption Keys (KEKs) that protect service-level data encryption keys (DEKs).
constraints/gcp.restrictCmekCryptoKeyProjects to restrict which Google Cloud projects are permitted to supply CMEK keys across the organization.CMEK strikes the optimal balance between granular administrative governance and seamless cloud native operational efficiency. Unlike default encryption, it provides user control over key lifecycles and compliance audits. Unlike CSEK or client-side encryption, it avoids the burden of managing and injecting raw key strings during service API interactions.
Client-side encryption refers to the practice of encrypting data locally in the client application or on-premises environment using tools like the Tink cryptographic library before sending the resulting ciphertext to Google Cloud services like Cloud Storage.
The organization required complete end-to-end zero-trust confidentiality where no cloud compute service or cloud operator could ever view plaintext data under any circumstances.
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