Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A financial services company is deploying Cloud SQL for PostgreSQL and Spanner databases on Google Cloud to store regulated payment cardholder data under PCI DSS. To satisfy compliance audits, the database architecture must meet the following requirements:
Which encryption and key management strategy should the company implement?
Software-protected CMEKs are customer-managed keys generated and stored within Cloud KMS's software cryptographic backend, complying with FIPS 140-3 Level 1 (and FIPS 140-2 Level 1). Placing these keys inside the same project as the databases consolidates compute, storage, and cryptographic resources.
roles/cloudkms.admin) role to database administrators allows the same personnel to manage both the data and the keys that unlock it.constraints/gcp.restrictNonCmekServices, teams can still deploy databases using Google default encryption.roles/cloudkms.admin role includes permissions to destroy key versions, which could cause permanent data loss if misused by a database administrator.The organization needed basic software CMEK key ownership for a non-regulated development environment where FIPS 140-2 Level 3 HSMs and strict separation of duties were not required.
Google default encryption automatically encrypts all data at rest in Google Cloud using AES-256 and Google's internal Keystore service without requiring customer configuration. Its cryptographic modules are validated to FIPS 140-3 Level 1.
The organization had no regulatory mandate for customer-managed keys, did not require FIPS 140-2 Level 3 HSM protection, and wanted zero-cost, zero-overhead encryption at rest.
Customer-Supplied Encryption Keys (CSEKs) allow customers to generate and store their own encryption key material externally and supply it in-memory per API request. Google Cloud does not persistently store CSEK key material on its servers.
constraints/gcp.restrictNonCmekServices and constraints/gcp.restrictCmekCryptoKeyProjects.The workload only used Cloud Storage buckets and required Google Cloud never to store key material at rest, rather than deploying managed databases with Cloud KMS and HSM protection.
Customer-Managed Encryption Keys (CMEK) in Cloud Key Management Service (Cloud KMS) allow organizations to own, control, and audit the symmetric key encryption keys (KEKs) used to protect data at rest across Google Cloud database services such as Cloud SQL and Spanner. When backed by Cloud HSM, key material is generated and stored inside FIPS 140-2 Level 3 validated hardware security modules.
constraints/gcp.restrictNonCmekServices blocks creation of databases without CMEK, while constraints/gcp.restrictCmekCryptoKeyProjects ensures keys are only sourced from the centralized key project.roles/cloudkms.cryptoKeyEncrypterDecrypter role, keeping database operations seamless.constraints/cloudkms.minimumDestroyScheduledDuration prevents premature key deletion.Unlike Google default encryption or software-backed keys in shared projects, this architecture combines hardware-backed cryptographic boundaries, strict least-privilege role isolation, and automated organization-wide guardrails required by PCI DSS.
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