Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise is migrating general application workloads, secrets, and log data to Google Cloud services such as Cloud Storage and Secret Manager. The enterprise's security policy mandates that all data at rest must satisfy NIST-approved baseline encryption standards, while the operations team wants to avoid the administrative burden of provisioning and managing custom key infrastructure.
Which statement accurately evaluates the underlying architecture, baseline security capabilities, and operational limitations of Google default encryption (Google-managed encryption keys)?
constraints/gcp.restrictCmekCryptoKeyProjects organization policy, which restricts key storage to software protection levels within the local deployment region.This option confuses default encryption with organization policy guardrails designed specifically to govern Customer-Managed Encryption Keys (CMEK).
constraints/gcp.restrictCmekCryptoKeyProjects constraint is used by security administrators to restrict which Google Cloud projects can supply Cloud KMS keys when developers configure CMEK integrations, preventing unauthorized cross-project key associations.CryptoKeys can reside across the resource hierarchy.The organization wanted to enforce centralized governance over CMEK usage by restricting developers to provisioning keys strictly from a designated centralized security project.
This option describes client-side encryption (CSE) rather than Google default server-side encryption at rest.
The scenario required an end-to-end zero-knowledge architecture where data must be encrypted by custom software before network transmission to Cloud Storage.
This option incorrectly asserts that default encryption relies on a single static master key stored inside Cloud KMS and outputs key usage telemetry to customer-accessible Cloud Audit Logs.
storage.objects.get), not the cryptographic unwrapping of DEKs by internal storage subsystems.An enterprise were utilizing Customer-Managed Encryption Keys (CMEK) hosted in Cloud KMS, where key metadata, rotation intervals, and cryptographic operation audit logs are directly visible and manageable within the customer's Google Cloud project.
Google default encryption (also known as Google-managed encryption keys or GMEK) is the baseline security control automatically enforced across all Google Cloud storage, database, and secret services. By default, raw customer data is split into chunks and encrypted at rest using AES-256 (or AES-128) with a unique Data Encryption Key (DEK). Google's internal infrastructure then uses envelope encryption to wrap each DEK with a Key Encryption Key (KEK) managed within Google's distributed, hardened Keystore and Root Keystore systems.
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