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 enterprise security architect must establish a secure key lifecycle process to import on-premises generated 256-bit AES symmetric keys into Google Cloud KMS for use with Customer-Managed Encryption Keys (CMEK) across Cloud Storage and BigQuery.
The solution must satisfy the following requirements:
Which end-to-end workflow and authorization strategy should the architect implement?
This option proposes Base64-encoding the symmetric key, importing it into a SOFTWARE protection level without client-side cryptographic wrapping, enabling automatic key rotation, and assigning a decrypt-only role.
SOFTWARE protection level complies with FIPS 140-2 Level 1, failing the requirement for FIPS 140-2 Level 3 HSM isolation.roles/cloudkms.cryptoKeyEncrypterDecrypter), not merely decrypter permissions.The workload permitted FIPS 140-2 Level 1 software keys, used Google-generated keys with automatic rotation schedules, and only required read-only decryption workflows.
This option suggests creating a standard Cloud KMS key with an automatically generated initial version, wrapping key material with an arbitrary project public key, and granting cryptographic permissions to individual end users.
skipInitialVersionCreation: true).Users were performing client-side application encryption using Cloud KMS SDKs directly rather than configuring server-side CMEK integrations.
This workflow establishes a secure Bring Your Own Key (BYOK) lifecycle within Google Cloud KMS by manually preparing an empty target key, generating an ephemeral Import Job protected by Cloud HSM, cryptographically wrapping the key material on-premises, importing it, activating it as the primary version, and delegating cryptographic usage permissions to Google Cloud service agents.
HSM protection level, the private unwrapping key portion resides strictly within Google Cloud HSMs and cannot be accessed outside the hardware boundary.service-PROJECT_NUMBER@gs-project-accounts.iam.gserviceaccount.com). Granting roles/cloudkms.cryptoKeyEncrypterDecrypter directly to these service agents—rather than human administrators or end users—enforces least privilege and strict role separation.roles/cloudkms.admin) from encryption/decryption execution.This procedure fully aligns with Google Cloud key import specifications, guarantees end-to-end envelope protection during transit, ensures active CMEK utilization, and satisfies strict regulatory separation-of-duties standards.
This option attempts to configure an imported key under the EXTERNAL (Cloud EKM) protection level and assign administrative permissions (roles/cloudkms.admin) to service agents.
EXTERNAL or EXTERNAL_VPC protection level. Cloud EKM is designed for Hold Your Own Key (HYOK) where keys remain permanently hosted in a third-party external key management system.roles/cloudkms.admin to service agents provides administrative management permissions (such as key destruction and IAM changes) rather than the roles/cloudkms.cryptoKeyEncrypterDecrypter role required to perform encryption/decryption.SOFTWARE and HSM protection levels.The requirement called for referencing keys stored entirely outside Google Cloud via Cloud EKM without importing the raw key bits into Google Cloud infrastructure.
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