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 is deploying a mission-critical workload on Google Cloud to handle sensitive federal financial records and payment card transaction data. The organization's compliance officer determines that the cryptographic architecture must satisfy both FedRAMP High and PCI DSS standards, specifically mandating that cryptographic keys protecting data at rest be hosted inside cryptographic modules certified to FIPS 140-2 Level 3 for physical tamper resistance.
Which cryptographic key protection configuration in Google Cloud Key Management Service (Cloud KMS) should the security engineer deploy to fulfill these regulatory mandates while retaining native integration with Google Cloud services?
The default SOFTWARE protection level in Cloud KMS generates and stores cryptographic keys in hardened software modules running across Google's distributed production environments using software-based cryptographic libraries.
The workload only required baseline encryption at rest with general enterprise CMEK controls and was subject to regulations satisfied by FIPS 140-2 Level 1 validation.
Software-backed keys are the default protection level in Cloud KMS and provide automatic key rotation and IAM integration, but cannot fulfill hardware-enforced isolation mandates.
Cloud HSM (Hardware Security Module) is a fully managed, cloud-hosted hardware security module service integrated directly into Google Cloud KMS. When keys are created with the HSM protection level, all cryptographic operations and key generation routines occur strictly inside dedicated hardware devices certified to FIPS 140-2 Level 3.
Using Cloud KMS with the HSM protection level directly satisfies the stringent FIPS 140-2 Level 3 requirements for hardware isolation while preserving the automated lifecycle, scaling, and deep service integrations of native Google Cloud CMEK workflows.
Cloud External Key Manager (Cloud EKM) allows Google Cloud services to protect data at rest using cryptographic keys that reside in a supported key management partner system located outside Google's infrastructure.
The enterprise had a regulatory mandate requiring cryptographic keys to reside entirely outside of Google's physical custody and cloud boundary for sovereignty reasons.
Customer-Supplied Encryption Keys (CSEK) allow users to provide their own 256-bit AES encryption keys directly within individual API request headers (e.g., in Cloud Storage or Compute Engine) without storing the key material inside Google Cloud.
The organization wanted strict control over key possession without using any Google-managed key store and accepted manual client-side key delivery for supported storage resources.
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