Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are developing a financial data pipeline that processes multi-gigabyte transaction files and archives them in both Google Cloud and an on-premises storage system. Security compliance requires the following:
How should you design the encryption workflow?
Envelope encryption is a multi-layered cryptographic pattern in which data is encrypted locally using a fast symmetric Data Encryption Key (DEK), and that DEK is then encrypted (wrapped) by a Key Encryption Key (KEK) stored in Cloud Key Management Service (Cloud KMS). This pattern allows applications to secure arbitrarily large payloads locally while maintaining centralized governance over the master key.
Unlike direct API encryption or server-side-only storage encryption, envelope encryption separates bulk data processing from centralized key management, delivering low-latency encryption with full Cloud KMS control.
Customer-Managed Encryption Keys (CMEK) for Cloud Storage is a server-side encryption integration where the Cloud Storage service agent uses your symmetric Cloud KMS key to wrap DEKs that protect objects at rest inside Google Cloud.
us-east1 or us), so a key in the global location cannot be used for bucket CMEK.roles/cloudkms.cryptoKeyEncrypterDecrypter IAM role on the key.The files only needed server-side encryption at rest inside a regional or multi-regional Cloud Storage bucket using a matching-location key ring, with no requirement for client-side encryption or on-premises archival protection.
This approach attempts to combine local in-memory encryption with centralized key storage by pulling symmetric KEK bytes out of Cloud KMS and persisting a shared plaintext DEK in Secret Manager.
No answer using exported Cloud KMS symmetric key material or stored plaintext DEKs is valid for envelope encryption; instead, applications must send small DEKs to the Cloud KMS API for wrapping and unwrapping.
Cloud KMS exposes encrypt and decrypt API endpoints for symmetric keys, along with automatic key rotation schedules that periodically generate a new primary key version.
You were encrypting tiny secrets under a few kilobytes directly via Cloud KMS and explicitly managing re-encryption workflows in your application, rather than processing multi-gigabyte transaction archives.
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