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.
An organization is deploying a data analytics pipeline on Google Cloud and needs to define security controls for different stages of the data lifecycle. The security architecture requires two fundamental protections:
Which combination of mechanisms correctly distinguishes between encryption in transit and encryption at rest to satisfy these requirements?
This option suggests using SSH port forwarding (a network tunneling protocol) as a storage encryption technique and database table partitioning (a data layout optimization) as an in-transit encryption method.
The scenario asked for a method to optimize SQL query execution costs via table partitioning and establish a secure administrative terminal session to a VM instance using SSH.
Confusing performance optimization techniques with cryptographic security controls is a common pitfall. Partitioning organizes data layout but requires underlying encryption at rest to be secure.
Transport Layer Security (TLS) and server-side disk-level encryption represent two complementary layers of data protection in Google Cloud. Encryption in transit protects network packets while they are being transmitted between a client and Google Cloud (or between Google Cloud services) by establishing an encrypted communication channel. Encryption at rest protects stored data by transforming readable plaintext into ciphertext before it is committed to non-volatile physical storage devices such as persistent disks, solid-state drives (SSDs), or object storage buckets.
This configuration aligns precisely with Google Cloud security best practices by mapping each protection state (data in transit vs. data at rest) to its dedicated cryptographic protocol and storage mechanism, ensuring complete end-to-end security.
This option proposes using Customer-Managed Encryption Keys (CMEK) to negotiate TLS sessions for in-transit network traffic while leaving local storage tiers completely unencrypted.
The organization required regulatory key ownership over data residing in Cloud Storage or BigQuery tables (CMEK at rest) rather than managing in-transit transport layers.
In Google Cloud, all data at rest—including temporary scratch disks and swap space—is encrypted by default at the hardware/disk layer, making unencrypted storage configurations non-standard and insecure.
This option inverts the roles of network transport protocols and storage layer encryption, proposing that disk-level cryptographic mechanisms secure network packets and network encryption protocols protect stored files.
The question swapped the two concepts, asking how to protect stored data on physical media (which requires disk-level encryption) versus data moving over network links (which requires TLS/SSL).
A fundamental concept of cloud security is distinguishing between the three states of data: data in transit (network packets), data at rest (storage volumes and databases), and data in use (active processing in CPU/memory).
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