Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An organization is establishing a secure cloud data warehouse architecture on Google Cloud. Corporate compliance policies mandate strict data governance, data residency, and cryptographic controls across all projects:
Which combination of Google Cloud controls should the data engineering team implement to satisfy these requirements?
This design uses VPC Service Controls (VPC SC) perimeters for network boundary protection, creates decentralized keys in individual workload projects, and grants decryption privileges to end users.
The primary objective were preventing data exfiltration between external networks and untrusted client perimeters rather than enforcing organization-wide CMEK policies and centralized key management.
This solution implements Google Cloud Organization Policies combined with Cloud Key Management Service (Cloud KMS) access control to create an end-to-end governance and cryptographic enforcement framework for analytical workloads.
constraints/gcp.restrictNonCmekServices constraint at the organization or folder level denies the creation of services or buckets unless they specify a customer-managed encryption key.constraints/gcp.restrictCmekCryptoKeyProjects constraint restricts the resource hierarchy so services can only consume Cloud KMS crypto keys originating from the authorized security project.roles/cloudkms.cryptoKeyEncrypterDecrypter) directly to the Google-managed service agent gives it the exact permissions required to encrypt and decrypt data at rest on behalf of the service.Organization policies provide declarative guardrails that prevent non-compliant infrastructure provisioning before it starts, while assigning the Encrypter/Decrypter role directly to service agents ensures seamless background decryption without granting broad administrative permissions.
This configuration attempts to use Cloud KMS Admin privileges assigned to service agents and a single global Cloud KMS key ring to handle encryption across multiple regions.
roles/cloudkms.admin role provides administrative privileges (such as managing IAM policies, key rings, and key configurations) rather than cryptographic operations. Service agents require the CryptoKey Encrypter/Decrypter role to perform runtime encryption and decryption.constraints/gcp.restrictCmekCryptoKeyProjects, allowing users to potentially utilize unauthorized keys from outside the centralized project.cryptoKeyVersions.useToEncrypt / cryptoKeyVersions.useToDecrypt actions.Service agents needed full administrative control over Cloud KMS configuration and data residency was globally distributed with no region-specific encryption requirements.
This approach restricts crypto key projects and attempts to use default Google-managed encryption combined with compute service account permissions.
constraints/gcp.restrictNonCmekServices, developers and automated pipelines can continue to provision resources with default encryption without restriction.compute-system or default Compute Engine service accounts) rather than the specific service agents (e.g., Dataplex, Metastore, or BigQuery service agents) leaves the target services unable to authenticate against Cloud KMS.constraints/gcp.restrictCmekCryptoKeyProjects only limits key selection when CMEK is explicitly supplied; it does not block the creation of non-CMEK resources on its own.The organization accepted default Google-managed encryption and only required basic key project filtering when CMEK happened to be specified.
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