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 organization uses Cloud KMS to manage Customer-Managed Encryption Keys (CMEK) protecting sensitive workloads, including Vertex AI RAG corpora. During an active security incident, the security operations team suspects that unauthorized callers are attempting to access protected data.
The incident response protocol mandates that the security engineer must immediately render all encrypted data irretrievable to all services and identities, maintain the ability to quickly restore decryption operations if the incident is a false alarm, and establish an irreversible cryptographic erasure path if key compromise is confirmed.
Which action should the security engineer take?
In Cloud KMS, a KeyRing is an administrative grouping container that organizes individual CryptoKey resources within a specific location. Key rings define the geographic boundary and logical hierarchy for encryption keys across projects.
KeyRing resources and CryptoKey containers cannot be deleted. Once created, key rings and keys persist indefinitely to preserve resource naming integrity and audit trails in Cloud Logging.Project > Location > KeyRing > CryptoKey > CryptoKeyVersion.CryptoKeyVersion resources can have their key material destroyed; key rings and crypto keys remain in the project permanently.Cloud KMS supported hard deletion of administrative resource containers, and the organization required immediate, irreversible purging of all key metadata without investigative retention.
The Cloud KMS Admin role (roles/cloudkms.admin) governs key metadata management, such as creating keys, modifying IAM policies, and adjusting rotation periods. Automated key rotation creates a new CryptoKeyVersion and sets it as the primary version for future encryption operations while leaving existing key versions active for decryption.
roles/cloudkms.cryptoKeyEncrypterDecrypter), not the Admin role, to decrypt data. Revoking admin privileges does not block decryption operations.CryptoKeyVersion, which stays ENABLED and accessible to unauthorized entities.The organization wanted to implement routine preventative hygiene to ensure future data is encrypted with fresh key material without disrupting access to historical datasets.
In Cloud Key Management Service (Cloud KMS), key lifecycle management occurs at the individual CryptoKeyVersion level. When a key version is active, it resides in the ENABLED state, allowing authorized principals and service agents holding the roles/cloudkms.cryptoKeyEncrypterDecrypter role to execute cryptographic operations. Changing the state of a key version to DISABLED immediately halts all cryptographic use without deleting the underlying key material. Scheduling destruction transitions the version to DESTROY_SCHEDULED for a designated retention window before permanent cryptographic erasure occurs.
CryptoKeyVersion to DISABLED takes effect immediately across Google Cloud services. Any decryption request initiated by workload service agents (such as Vertex AI or RAG Engine) will fail, rendering the underlying ciphertext completely irretrievable.ENABLED, instantly restoring normal workload operations without data loss.gcloud kms keys versions destroy). This moves the version into the DESTROY_SCHEDULED state. Once the destruction schedule duration elapses, the key material is permanently expunged, rendering all associated data permanently unrecoverable in compliance with secure deletion mandates.DESTROY_SCHEDULED state provides a configurable grace period (from 24 hours up to 120 days) during which key destruction can be aborted via the restore command if needed.Disabling the CryptoKeyVersion directly at the KMS level guarantees total cryptographic revocation across all callers regardless of IAM permissions, while preserving the key material until the forensic evaluation confirms whether permanent key destruction is warranted.
A CryptoKey purpose defines the cryptographic capability of a key upon creation (such as ENCRYPT_DECRYPT, ASYMMETRIC_SIGN, or MAC). Service agents (such as service-PROJECT_NUMBER@gcp-sa-vertex-rag.iam.gserviceaccount.com) are Google-managed identities that perform automated tasks on behalf of managed services.
CryptoKey is immutable and cannot be modified after resource creation. Any request attempting to change a symmetric key to an asymmetric signing key is rejected by the Cloud KMS API.Symmetric encrypt/decrypt purpose.DISABLED/DESTROY_SCHEDULED) disable the cryptographic engine directly.Key purposes were dynamically editable in Cloud KMS and the security team solely needed to convert a key into an asymmetric signing identity.
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