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 healthcare organization is migrating its patient portal to Google Cloud. During a security architecture review, the security team wants to verify how patient data is protected against interception while in transit across the following stages:
How does Google Cloud natively secure and minimize exposure for this data in transit?
Full Disk Encryption (FDE) and Customer-Managed Encryption Keys (CMEK) are security controls used to protect data at rest. FDE encrypts the physical storage media (such as hard drives and solid-state drives) in Google data centers, while CMEK in Cloud Key Management Service (Cloud KMS) allows organizations to create, rotate, and manage the cryptographic keys used to encrypt their stored cloud data.
Neither FDE nor CMEK operates on network packets traveling between a user's browser and Google Cloud services. These mechanisms are strictly designed to secure stored data written to persistent storage layers and physical disks. Protecting data moving across the internet and between internal services requires dynamic session and transport protocols like TLS and ALTS.
This option would be the right choice if the organization needed to ensure that patient records stored in Cloud Storage or Persistent Disk were unreadable if a physical drive were compromised, and required direct control over the encryption keys used to protect that stored data.
While encryption at rest and encryption in transit are both enabled by default in Google Cloud, they rely on completely different cryptographic architectures. Storage systems break static data into chunks encrypted with data encryption keys (DEKs), whereas network communications use ephemeral session keys negotiated via TLS or ALTS.
Encryption in transit is a foundational security control that protects data against unauthorized interception or modification as it travels over the internet and moves within cloud infrastructure. Google Cloud combines Transport Layer Security (TLS), Google Front End (GFE) servers, its global private network, and Application Layer Transport Security (ALTS) to provide end-to-end protection for moving data.
Unlike solutions that rely exclusively on public internet routing or manual application-level configuration, Google Cloud enforces defense in depth across its network by default. Combining TLS at the edge via the GFE with ALTS inside Google's private fiber network ensures seamless protection across both external and internal transit paths without requiring custom intervention from the customer.
Confidential Computing is a Google Cloud security technology designed to protect data in use while it is actively being processed in system memory. It relies on a hardware-based Trusted Execution Environment (TEE) on Confidential VMs to perform computations in cryptographic isolation.
This option addresses the wrong state of data. While Confidential Computing protects sensitive workloads while they are running in system memory (RAM) on a virtual machine, it is not a network transport protocol and does not encrypt data traveling across public internet hops or moving between network endpoints. Securing data in transit requires transport encryption protocols like TLS and ALTS, rather than memory isolation hardware.
This option would be the right choice if the healthcare organization wanted to ensure that highly sensitive patient data remained encrypted and isolated inside system memory while actively being processed by an application running on a Compute Engine virtual machine.
A comprehensive data security strategy accounts for three distinct states of data: data at rest (stored on disks), data in transit (moving across networks), and data in use (being processed in memory). Confidential Computing specifically fills the gap for data in use, which is not encrypted by default unless Confidential VMs are enabled.
Binary Authorization for Borg (BAB) and Titan security chips are foundational components of Google's software supply chain integrity and hardware root of trust. BAB is an internal deployment control that reviews and authorizes production software code before it runs on Google's infrastructure, while Titan is a custom-designed hardware security chip deployed on Google servers and peripherals to verify legitimate hardware and boot code.
BAB and Titan are not network encryption protocols and are not deployed on external customer web browsers to encrypt internet traffic. Instead of encrypting data packets moving across networks, their role is to ensure that the underlying physical servers and production binaries processing data inside Google data centers are authentic and unmodified.
This option would be the right choice if the security team wanted to understand how Google Cloud verifies software supply chain integrity and ensures that only trusted, authenticated server hardware and authorized production code are permitted to run within Google data centers.
In Google's trusted infrastructure, hardware and software integrity work alongside network encryption to create a layered defense. While Titan and BAB guarantee that the services running at each endpoint are legitimate, TLS and ALTS are the protocols responsible for encrypting the actual network traffic moving between those endpoints.
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