Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A financial services organization stores sensitive customer records in Google Cloud. While the company relies on Google Cloud to host its cryptographic keys, regulatory compliance mandates that the internal security team maintain direct control over the encryption key lifecycle for data at rest, including:
Which encryption method should the organization implement to meet these requirements?
Google-owned and Google-managed encryption (also known as Google Cloud default encryption) is the foundational security mechanism that automatically encrypts all customer data stored at rest across Google Cloud services. It uses Keystore, Google Cloud's internal key management service, along with FIPS 140-3 Level 1 validated cryptographic modules to protect data without requiring any manual setup or configuration from the customer.
While default encryption protects stored data against physical storage compromise, it does not give customers visibility or administrative control over the underlying cryptographic keys. Because Google completely owns and manages the key lifecycle internally, the organization's security team cannot configure custom rotation intervals, assign Identity and Access Management (IAM) permissions to individual keys, or manually revoke and destroy specific key versions to mitigate suspected unauthorized access.
The organization wanted to ensure that all data at rest is cryptographically protected out of the box with zero operational overhead, and did not have strict regulatory mandates requiring customer ownership, custom rotation schedules, or granular access control over the encryption keys.
Google Cloud default encryption operates independently of Cloud Key Management Service (Cloud KMS). When organizations need to move beyond default encryption to satisfy compliance audits, they transition to customer-managed or customer-supplied key architectures.
Confidential Computing is a security technology that encrypts customer data in use while it is being processed in system memory (RAM). Using specialized hardware-based trusted execution environments—such as Confidential VM, Confidential Google Kubernetes Engine (GKE) Nodes, and Confidential Dataflow—it ensures that sensitive workloads remain encrypted during active computation.
The organization is seeking a solution to manage the encryption key lifecycle—including custom rotation schedules, IAM access controls, and manual key version destruction—for data at rest. Confidential Computing specifically addresses the risk of unauthorized access to data in use within system memory, rather than providing customer-managed lifecycle controls for stored data at rest.
The organization already had data-at-rest and data-in-transit protections in place, and needed to protect highly sensitive workloads against memory-based threats by encrypting data while it is actively being processed in RAM.
A comprehensive, end-to-end cloud data protection strategy addresses data across three distinct states: encryption at rest (using Default Encryption, CMEK, CSEK, or Cloud EKM), encryption in transit (using TLS, IPsec, or MACsec), and encryption in use (using Confidential Computing).
Customer-supplied encryption keys (CSEKs) are a data-at-rest encryption option where the customer generates and stores their own cryptographic keys outside of Google Cloud and provides the raw key material directly to Google Cloud only when performing read or write operations. Google Cloud uses the provided key in memory to encrypt or decrypt the data and immediately discards it after the operation completes.
The scenario specifies that the organization relies on Google Cloud to host its cryptographic keys and wants to manage key rotation schedules and IAM permissions within the platform. With CSEKs, Google Cloud never permanently stores the keys on its servers. Instead, the customer must maintain their own external key infrastructure, manage rotation manually outside of Google Cloud, and pass the key with every API request.
The organization had a strict security policy prohibiting Google Cloud from ever persistently storing their encryption keys on Google servers, and wanted to supply their own locally stored key material only in memory during active Cloud Storage operations.
If an organization wants to keep keys outside of Google's infrastructure while still integrating with Cloud KMS management workflows across broader services, they would typically evaluate Cloud External Key Manager (Cloud EKM) rather than raw CSEKs.
Customer-managed encryption keys (CMEKs) are cryptographic keys created, owned, and controlled by the customer within Cloud Key Management Service (Cloud KMS) to protect data at rest in CMEK-integrated Google Cloud services. CMEKs use envelope encryption, where the customer's Cloud KMS key encryption key (KEK) wraps and encrypts the underlying data encryption keys (DEKs) that protect stored resources.
Implementing CMEKs in Cloud KMS strikes the ideal balance between security control and operational simplicity. Unlike default encryption, it gives the security team direct administrative authority over key rotation, IAM policies, and key destruction. Unlike customer-supplied encryption keys (CSEKs), it eliminates the operational burden of storing keys on-premises and transmitting raw key material with every API call.
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