Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A data engineering team needs to implement envelope encryption to protect sensitive data files stored across multiple client environments. The architecture requires that client applications encrypt a locally generated Data Encryption Key (DEK) without granting them direct access to decrypt data or manage the private key.
Which workflow correctly describes how Cloud KMS asymmetric keys should be used to protect the DEK?
This option suggests extracting the private key from Cloud KMS to perform local encryption operations on client nodes and relying on the public key within Cloud KMS for decryption.
A legacy system required client-side software encryption without a centralized KMS, though this would still use the public key for encryption rather than exporting private keys.
This option proposes managing individual Data Encryption Keys (DEKs) directly inside Cloud KMS to encrypt large storage blocks and destroying raw data tables whenever keys rotate.
The requirement specifically asked for database lifecycle management and storage retention policies rather than asymmetric key encryption workflows.
Asymmetric encryption in Google Cloud Key Management Service (Cloud KMS) uses a mathematically linked public and private key pair. In this model, the public key is made available to encrypt plaintext data, while the corresponding private key is kept secure within Cloud KMS and used exclusively for decryption operations.
roles/cloudkms.publicKeyViewer), preventing them from decrypting data.This workflow allows decentralized encryption across numerous distributed clients without exposing sensitive decryption keys. It keeps private key material centralized and safeguarded within Cloud KMS while supporting high-throughput local data encryption.
This option describes using a private key to encrypt arbitrary data files directly via an API call and distributing the public key to downstream clients for local decryption.
The scenario required generating a digital signature with a private key in Cloud KMS to allow external consumers to verify message authenticity and integrity using the public key.
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