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.
Your organization is automating nightly exports from production databases in Project A to a Cloud Storage destination bucket in us-central1 in Project B. The architecture must meet these requirements:
Project C), blocking Google-managed and customer-supplied keys.How should you configure the destination bucket and IAM permissions?
This option uses fine-grained access control, configures a locked retention policy for 90 days, grants Storage Object Admin to the exporting service account, and assigns KMS permissions to Project A's Cloud Storage service agent.
Project B), not the database's project (Project A). Additionally, omitting encryption enforcement rules leaves Google-managed and customer-supplied keys unrestricted.roles/storage.objectAdmin allows reading, updating, and deleting existing exports, violating least privilege.A locked 90-day retention policy would be appropriate if compliance required immutable WORM (Write-Once-Read-Many) protection preventing deletion before 90 days, paired with a lifecycle Delete rule to remove objects after 90 days.
Administrators often confuse retention policies (which prevent premature deletion) with lifecycle rules (which automate deletion or storage-class transitions).
This option attempts to configure cross-project CMEK and lifecycle deletion, but it uses a global Cloud KMS key, over-provisions the exporting service account with roles/storage.admin, and assigns KMS encryption permissions to the wrong identity.
global location. The key ring must reside in the exact same location as the bucket (us-central1) to encrypt objects in that bucket.roles/cloudkms.cryptoKeyEncrypterDecrypter to the exporting service account instead of Project B's Cloud Storage service agent will cause export writes to fail.roles/storage.admin) grants full control over the bucket, including deleting the bucket, reading or deleting all objects, and modifying IAM policies (setIamPolicy), far exceeding what an automated export job needs.roles/storage.admin to an automated pipeline exposes historical database backups to unauthorized modification or deletion if the job credentials are compromised.No configuration using a global KMS key works for Cloud Storage CMEK. This pattern would only approach validity if the key were moved to us-central1, Project B's Cloud Storage service agent were granted the KMS role, and the exporting service account were downgraded to storage.objects.create.
A common misconception is that the service account initiating a database export directly encrypts objects with Cloud KMS. In reality, Cloud Storage handles server-side CMEK encryption via its own project service agent.
This configuration combines Cloud Storage encryption enforcement, cross-project CMEK, uniform bucket-level access, Object Lifecycle Management, and least-privilege IAM to secure automated database exports.
FullyRestricted for Google-managed and customer-supplied keys, NotRestricted for CMEK) ensures every new export uses CMEK. Placing the Cloud KMS key ring in us-central1 satisfies the requirement that the key ring match the bucket's location while residing in Project C.service-PROJECT_NUMBER@gs-project-accounts.iam.gserviceaccount.com) of the project that owns the bucket (Project B). Granting this service agent roles/cloudkms.cryptoKeyEncrypterDecrypter on the key in Project C allows seamless encryption and decryption.Delete action with an age condition of 90 automatically purges expired exports.storage.objects.create (such as via roles/storage.objectCreator) allows the export job to write files without granting read, delete, or IAM-modification privileges.Project C.This is the only configuration that aligns KMS key location with the bucket, authorizes the correct project's Cloud Storage service agent, enforces CMEK-only uploads, automates deletion after 90 days, and strictly applies least-privilege IAM.
This option enables uniform bucket-level access and object versioning, applies a lifecycle rule targeting noncurrent object versions, grants Storage Legacy Bucket Owner to the exporting service account, and relies solely on a default Cloud KMS key without encryption enforcement rules.
Delete rule using daysSinceNoncurrentTime only deletes noncurrent (overwritten or deleted) versions created by Object Versioning. Because scheduled database exports typically write uniquely named files that are never overwritten, live exports remain indefinitely.roles/storage.legacyBucketOwner grants bucket management capabilities—such as deleting objects and modifying the bucket's IAM policy—rather than least-privilege object creation.daysSinceNoncurrentTime cleanup rules in addition to live-object age rules if exports overwrite fixed filenames.Project B's Cloud Storage service agent roles/cloudkms.cryptoKeyEncrypterDecrypter on the key in Project C.A daysSinceNoncurrentTime lifecycle rule would be appropriate if exports overwrote the same object name nightly with versioning enabled and you wanted to purge superseded versions after 90 days, alongside encryption enforcement rules and proper KMS permissions.
To guarantee compliance-grade encryption boundaries, encryption enforcement rules must explicitly set FullyRestricted on disallowed encryption types rather than relying on default bucket encryption settings.
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