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.
A financial enterprise uses Google Cloud Storage to store sensitive audit logs and transaction records. The bucket is configured with Customer-Managed Encryption Keys (CMEK) managed in Cloud Key Management Service (Cloud KMS).
To align with internal data governance and cost optimization frameworks, the security team implements the following configurations:
SetStorageClass action to transition objects from Standard to Archive storage after 90 days.Delete action for objects older than 7 years.How do these lifecycle actions and security controls affect object availability, legal holds, and encryption states?
This option incorrectly assumes that a Legal Hold freezes all object lifecycle modifications—including storage class transitions—and that Cloud KMS key rotation initiates automated background re-encryption of existing data in Cloud Storage.
storage.objects.delete operations but permits storage.objects.update (such as storage class transitions).This behavior would apply if legal holds acted as a complete write/update freeze on all object metadata and if Cloud Storage had a built-in automated cryptographic re-encryption pipeline tied to Cloud KMS rotation events.
This option assumes that storage tier transitions automatically modernize object encryption to the newest Cloud KMS primary key version, and that older key versions can be disabled or destroyed without risking data loss.
gsutil rewrite or Cloud Storage batch operations).This would be true if Cloud Storage performed cryptographic re-encryption during class transitions and maintained an independent cache of decrypted data encryption keys, which would violate envelope encryption security models.
In Google Cloud Storage, Object Lifecycle Management allows organizations to automate data tiering and deletion. However, governance controls like Legal Holds and cryptographic policies governing Customer-Managed Encryption Keys (CMEK) dictate exact availability and protection states during these automated operations.
Delete actions. However, non-destructive lifecycle actions—specifically SetStorageClass transitions (such as moving from Standard to Nearline, Coldline, or Archive)—are permitted and execute as scheduled. This ensures cost optimization without compromising data preservation.This architecture balances compliance mandates (preserving evidentiary records via legal holds), financial governance (downward storage class tiering to Archive), and cryptographic integrity (maintaining established envelope encryption keys).
This option asserts that automated lifecycle deletion rules take precedence over regulatory compliance locks like Legal Holds, and that transitioning data to cold storage tiers strips away CMEK encryption in favor of Google-managed default encryption.
Delete action, evaluates the active legal hold, and fails/aborts the deletion. The object remains safely stored until the legal hold is explicitly lifted by an authorized identity.This would only occur if lifecycle policies were configured with unconstrained administrative privileges designed to bypass legal discovery holds, which contradicts Google Cloud security and compliance architecture.
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