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 establishing a data governance and encryption framework on Google Cloud to comply with strict regional data sovereignty and regulatory standards. The compliance baseline dictates the following technical requirements:
Which Cloud KMS configuration and lifecycle management strategy should the security architect specify?
This option provisions Cloud HSM keys in a multi-region location and immediately disables older key versions as soon as a new primary version is generated during rotation.
The organization intended to cryptographically shred all legacy data immediately upon rotation and only maintain regional data in a multi-region topology.
Cloud External Key Manager (Cloud EKM) coordinates encryption with keys hosted outside of Google's infrastructure in a third-party key management system. This option also schedules immediate destruction of older key versions when a new key is promoted.
The organization's compliance regulations explicitly mandated external third-party key custody outside of Google Cloud and required cryptographic erasure of all past data upon key rollover.
Customer-Managed Encryption Keys (CMEK) hosted in Cloud Key Management Service (Cloud KMS) with the Cloud HSM protection level provide hardware-rooted FIPS 140-2 Level 3 cryptographic security. By creating key rings in a dedicated key management project, organizations enforce a strict separation of duties between KMS Administrators (who manage key lifecycles and IAM policies on keys) and Service Project Administrators (who manage storage and database resources).
This architecture establishes a robust governance model where key access, location constraints, and cryptographic lifecycles are centralized and secured without disrupting ongoing storage read and write operations.
This approach uses default software-protected Cloud KMS keys colocated inside the same Google Cloud project as the workload resources, expecting Google Cloud to automatically rewrite existing data with new key versions.
The compliance policy permitted software-level encryption within individual project boundaries and manual re-encryption pipelines were implemented.
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